Re: busyloop in sigchld_handler

[Andreas Schwab]

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.

Andreas.

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."