Re: Force a crash on SIGABRT
Re: Force a crash on SIGABRT
- Subject: Re: Force a crash on SIGABRT
- From: Neal Sidhwaney <email@hidden>
- Date: Tue, 14 Apr 2009 12:32:52 -0700
It turns out that on Leopard, I don't need the handler at all, just calling abort() causes the "unexpectedly quit" dialog to appear, and the app to go away.
I wonder if this is because of how signals are implemented - e.g. according to OS X Internals section 9.8.8, if a signal is being delivered, we're already in the middle of the task's exception handler; the original exception had been converted to a signal. So the "double-faulting" might have caused the kernel to never get an 'exception-handled' reply message for the original exception, causing the process to never resume and then terminate.
For Tiger, I am not sure, other than the technote(
http://developer.apple.com/technotes/tn2004/tn2123.html ) indicates that there have been a lot of changes in Crash Reporter before 10.5
Neal
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden