DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; q=dns; s=default; b=Cyc
	gnjJEIAy3U/tAPEo1PO0KQdzObmKNtGlSyjSD4F4RZvR8FzpQAXsHI2IhN2o5t9F
	a4ImiHkbEsz9bNKiErKM4DtNj2jUZ2luCUuNYfYbCcPfxnYevCYqsJc9sBIUh3wC
	K7fIPIZoS38do8YGQ57W01p9ts0DQdj/282/5gnA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51790015.1090304@mathematik.uni-kl.de>
Date: Thu, 25 Apr 2013 12:06:13 +0200
From: =?ISO-8859-1?Q?Andreas_Steenpa=DF?= <steenpass@mathematik.uni-kl.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: previously reported test case does not work in Cygwin 1.7.18
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I have tried to run the following test case with the newest release:

http://cygwin.com/ml/cygwin/2012-12/msg00076.html

It used to work after it was fixed, but now it seems to be broken again.
Actually, it is even worse than before because now, not even thread 1
catches SIGUSR2:

$ uname -a
CYGWIN_NT-6.1-WOW64 zoppo 1.7.18(0.263/5/3) 2013-04-19 10:39 i686 Cygwin
$ ./testcase1
pid: 3628
thread 1 waiting for SIGUSR1

// from another console, send SIGUSR2, then SIGUSR1 (in this order!)
$ kill -SIGUSR2 3628
$ kill -SIGUSR1 3628

// The program catches only SIGUSR1, but not SIGUSR2:
thread 1 received SIGUSR1
thread 1 waiting for SIGUSR2

Best regards,
Andreas


--
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