Re: [1.7] sigwait bug (SIGCHLD delayed to a next regular signal)

[Waldemar Rachwal <waldemar dot rachwal at gmail dot com>]

Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes:

> 
> On Sat, Sep 19, 2009 at 10:31:58AM +0000, Waldemar Rachwal wrote:
> >
> >If the action associated with a blocked signal is anything other than to
> >ignore the signal, and if that signal is generated for the thread,
> >
> 
> Since the "above" never mentioned the word handler, I don't see how your
> point is valid.  (...)  
> Setting the handler doesn't seem to serve any useful purpose since it isn't
> being used.

To satisfy the condition (quoted from posix) "action is anything other than to
ignore",
SIGCHLD (and all other signals which default action is to ignore) must be setup
a handler even if it seems "not useful". Being blocked is not sufficient.

> 
> In any event, you provided a test case, I provided a fix.  That's the
> desired outcome.  Arguing about this is pointless unless the fix didn't
> actually fix anything.
> 

Completely agree. I hope not to start 3rd thread on the same problem anymore
(the root cause of the problem from
http://sourceware.org/ml/cygwin/2009-08/msg00797.html
is exactly the same as from this thread).



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple