Jeff Trawick wrote:

> Currently the signal mask blocks all synchronous signals. That is
> bogus, and on (at least) AIX it can be seen to interfere with proper
> recovery if one of those signals, such as SIGSEGV, is generated during
> the time that it is blocked. Here is text from the Solaris 8 manpage
> for pthread_sigmask:
>
> Signals which are generated synchronously should not be
> masked. If such a signal is blocked and delivered, the
> receiving process is killed.
>
> An idle child process being terminated can hold the pthread mutex and
> have these signals blocked while running a 3rd-party module's child
> exit hook or pool cleanups. (I hope to address that with a future
> patch, but this patch is appropriate independently.) If such code
> segfaults, having the corresponding synchronous signal blocked
> (SIGSEGV) is bad news.


Reviewed. +1

Bill