Date: Fri, 7 Dec 2012 12:38:40 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sigwait() ignores non-thread-specific pending signals
Message-ID: <20121207173840.GA30939@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <50C09142.1090904@mathematik.uni-kl.de> <20121207012753.GA10201@ednor.casa.cgf.cx> <50C1BAF5.6000802@mathematik.uni-kl.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50C1BAF5.6000802@mathematik.uni-kl.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Fri, Dec 07, 2012 at 10:46:29AM +0100, Andreas Steenpa? wrote:
>Le 07/12/2012 02:27, Christopher Faylor a ?crit :
>> I don't see any difference between Cygwin and Linux when I run the
>> test program.
>>
>> cgf
>
>I re-compiled and ran the test program under Cygwin 1.7.17 as well as on
>several Linux machines (Debian/Fedora/Gentoo/Ubuntu, kernel versions
>2.6.29/2.6.32/3.0.6/3.2.0/3.2.12/3.4.9/3.6.6, different kinds of CPUs
>etc.) and I definitely see a difference.
>
>The difference is that after typing in the commands
>kill -SIGUSR2 [pid]
>kill -SIGUSR1 [pid]
>kill -SIGUSR2 [pid]
>kill -SIGUSR1 [pid]
>(in this order!) in another console, the program blocks under Cygwin
>while it exits normally under Linux. The last output under Cygwin is
>'thread 2 waiting for SIGUSR2' while under Linux, one more line 'thread
>2 received SIGUSR2' is printed out before the program exits.

Sorry, I missed the extra kills in your example.

This should be fixed in CVS and in the upcoming snapshot.

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