This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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

Christopher Faylor <cgf-use-the-mailinglist-please <at>> 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
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
is exactly the same as from this thread).

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]