This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: sigwait() ignores non-thread-specific pending signals
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 6 Dec 2012 20:27:53 -0500
- Subject: Re: sigwait() ignores non-thread-specific pending signals
- References: <50C09142.1090904@mathematik.uni-kl.de>
- Reply-to: cygwin at cygwin dot com
On Thu, Dec 06, 2012 at 01:36:18PM +0100, Andreas Steenpa? wrote:
>I have noticed that sigwait() does not return immediately if called in
>the following situation:
>* One of the signals the command is looking for isalready pending.
>* This signal was send to the entire process rather than to a specific
>thread.
>* sigwait() is called from a thread other than the 'main' thread.
>
>Look at the test case below. The function test_sigwait() is first called
>from the 'main' thread and then from another thread created in main().
>This should not make a difference here, but the function shows different
>behaviour.
>
>My interpretation is that sigwait() simply forgets to look for
>non-thread-specific signals which are already pending at the time when
>it is called.
I don't see any difference between Cygwin and Linux when I run the
test program.
cgf
--
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