Re: Force a crash on SIGABRT
Re: Force a crash on SIGABRT
- Subject: Re: Force a crash on SIGABRT
- From: James Walker <email@hidden>
- Date: Tue, 14 Apr 2009 12:04:10 -0700
Kevin Van Vechten wrote:
Just an untested idea... try kill(getpid(), SIGILL);?
On Apr 13, 2009, at 3:14 PM, James Walker wrote:
When my app receives SIGABRT, I want to force some kind of crash that
will generate a crash report. I tried installing a SIGABRT signal
handler like this:
static void AbortHandler( int /* inSignal */ )
{
long* badAddr = 0;
*badAddr = 7;
}
On Tiger, it partly works: There is a crash log, but the app keeps
running in a hung state. On Leopard, there's just a hang, no crash
report.
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.
On Tiger, your suggestion is no better or worse than what I had
before... the dialog appears, but the app hangs around.
--
James W. Walker, Innoventive Software LLC
<http://www.frameforge3d.com/>
_______________________________________________
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