[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: busyloop in sigchld_handler

From: David Kastrup
Subject: Re: busyloop in sigchld_handler
Date: Wed, 14 Mar 2007 11:52:36 +0100
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

Andreas Schwab <address@hidden> writes:

> David Kastrup <address@hidden> writes:
>> The signal manpage says:
>>      When a signal  occurs, and func points to  a function, it is
>>      implementation-defined whether the equivalent of a:
>>              signal(sig, SIG_DFL);
>>      is   executed   or    the   implementation   prevents   some
>>      implementation-defined  set of  signals (at  least including
>>      sig) from  occurring until  the current signal  handling has
>>      completed.
>> So even though SIGCHLD may be interrupted by another signal, this does
>> not mean that the other signal handler gets a chance to run.
> This is a complete red herring.  The Linux kernel (and all XSI compliant
> systems) always blocks the invoking signal when a handler is invoked.

Who is talking about the invoking signal?  Other signals can occur
(i.e., SIGALRM).

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]