Re: Crashing on all relevant exceptions
Re: Crashing on all relevant exceptions
- Subject: Re: Crashing on all relevant exceptions
- From: Shaun Wexler <email@hidden>
- Date: Tue, 8 Aug 2006 14:12:48 -0700
On Aug 7, 2006, at 8:56 PM, Aaron Jacobs wrote:
This will print a bunch of memory locations in hexadecimal and then
continue the program, which is not exactly ideal and is not even
close to what my request for help continues to be.
If you read the thread you will see that lot of that code is
unnecessary as the same can be accomplished by simply overriding -
run in NSApplication.
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?
Moreover, your RTFM quip is also unnecessary, as I mentioned
basically the exact same solution of printing a stack trace (human-
readable, no less) on the list an hour ago.
Thanks for the help, but next time please read my request more
closely if you're going to be hostile about it.
Hostile? Not me. Pretty sensitive for some reason there, aren't we,
darling?
;)
--
Shaun Wexler
MacFOH
http://www.macfoh.com
"Tact is the ability to describe others as they see themselves." -
Abraham Lincoln
_______________________________________________
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