NSExceptionHandler causing crash to not really terminate process; NSExceptionHandlerUncaughtSignalHandler loop
NSExceptionHandler causing crash to not really terminate process; NSExceptionHandlerUncaughtSignalHandler loop
- Subject: NSExceptionHandler causing crash to not really terminate process; NSExceptionHandlerUncaughtSignalHandler loop
- From: Dan Wood <email@hidden>
- Date: Sun, 26 Mar 2006 22:49:43 -0800
Way back when, Steve Gehrman of CocoaTech asked about a problem where
the app would hang in a tight CPU-sucking loop around
NSExceptionHandlerUncaughtSignalHandler:
http://www.cocoabuilder.com/archive/message/cocoa/2003/7/11/82566
Douglas Davidson's reply was that they were working on this issue.
Here it is, years later, and I'm finding something similar. We are
capturing exceptions with NSExceptionHandler, implementing the
delegate method exceptionHandler:shouldHandleException:mask:, and
overriding [NSApplication reportException:] to send exception
backtraces to us.
What has been happening lately is that if our application crashes,
the application doesn't really go away, even though we get the crash
report notification.
Our stack trace from a sample looks something like this (excerpt)
913 -[NSApplication sendAction:to:from:]
913 0xffffffff
913 _sigtramp
913 0x30
913 0xf
913 _sigtramp
913 NSExceptionHandlerUncaughtSignalHandler
913 NSExceptionHandlerUncaughtSignalHandler
I've tried to isolate the problem as best as I can, and it appears
that just having this line called in my application's init method
seems to cause this behavior.
NSExceptionHandler *handler = [NSExceptionHandler
defaultExceptionHandler];
_______________________________________________
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