Re: Process Signal Bug On Intel Dual Core Machines?
Re: Process Signal Bug On Intel Dual Core Machines?
- Subject: Re: Process Signal Bug On Intel Dual Core Machines?
- From: William Kucharski <email@hidden>
- Date: Thu, 31 Aug 2006 03:24:02 -0600
On Aug 31, 2006, at 2:58 AM, Markus Hanauska wrote:
It also does not explain why SIGQUIT won't work (it is not blocked,
I made my app print out the whole signal mask and SIGQUIT is not
blocked), but since we don't use it anyway, this might be an
entirely different bug and should maybe be ignored for this issues.
It could be that SIGQUIT is being ignored; if the signal is ignored it
will be silently discarded rather than appear in the blocked or pending
signal lists.
I'd tell you to use "ps -O ignored," which is documented but apparently
doesn't actually work:
$ ps -O ignored
ps: sigignore: keyword not found
so the next easiest thing would be to use sigaction(2) to get the
previous
disposition of SIGQUIT for your daemon and check to see if its
handler is
set to SIG_IGN.
William Kucharski
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden