Re: Catching signal errors
Re: Catching signal errors
- Subject: Re: Catching signal errors
- From: Matt Watson <email@hidden>
- Date: Mon, 7 Feb 2005 11:27:01 -0800
void fatalSigHandler(int sig, siginfo_t* info, void* context)
{
// We are very limited in what we are allowed to do in a signal
handler. // Memory should not be allocated, and most libc functions
should not be used.
static char sig_message[] = "Aborting: Fatal signal occurred!\n";
write(1, sig_message, sizeof(sig_message));
exit(1);
}
Never call exit() from a signal handler. You want _Exit() instead.
exit() will call atexit() handlers which will are likely not
signal-safe. And you probably want to use fd 2 (stderr), instead of fd
1 in the write() call.
That said: if you're not going to add any more info in your signal
handler, or do any cleanup like unlink() files, it may just be best to
let it crash and generate a crash log.
matt.
_______________________________________________
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