Re: Force a crash on SIGABRT
Re: Force a crash on SIGABRT
- Subject: Re: Force a crash on SIGABRT
- From: Damien Sorresso <email@hidden>
- Date: Thu, 16 Apr 2009 01:47:27 -0700
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's possible that ReportCrash on Leopard and Tiger could not handle
double-faults, meaning that it would not send an exception reply to
the kernel indicating that the faulting process could exit once per
fault. So the kernel would keep a thread parked in ipc_mqueue_receive
() waiting for a reply before allowing the process to exit.
--
Damien Sorresso
BSD Engineering
Apple Inc.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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