Re: Crashing on all relevant exceptions
Re: Crashing on all relevant exceptions
- Subject: Re: Crashing on all relevant exceptions
- From: Aaron Jacobs <email@hidden>
- Date: Tue, 8 Aug 2006 15:35:11 -0700
Parse the stackTrace string, then use dyld to look up the symbols
and print them out. Or pipe it to GDB like CrashReporter. Or
write better code that doesn't throw exceptions. And before you
start crying again, this means that in production code, a program
should not crash. Bomb-out all you want in development builds, but
then again we do have GDB... and it's even built right into Xcode.
Amazing?
I already know how to take care of the stack trace, as indicated in
my earlier e-mail. For anyone who is curious, I'll give a direct
link to a page describing it:
http://www.cocoadev.com/index.pl?StackTraces
As for your assertion about production code not ever crashing: that's
certainly an admirable goal, but it is far from attainable in the
real world. If big companies with lots of developers like Apple
can't always manage it (*ahem* Mail and Safari), what chance does an
independent developer such as myself have? I try my hardest to make
sure nothing goes wrong, but if something weird and unforeseen
happens, it's better to crash immediately than go on in an
inconsistent state and possibly cause corruption of data. Hence the
"crash early" mantra.
Hostile? Not me. Pretty sensitive for some reason there, aren't
we, darling?
Yeah, I'll just let your e-mail above speak for itself. If you want
to continue making jabs at me, take it off-list, alright?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden