X-Recipient: archive-cygwin AT delorie DOT com
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
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Hactc9vbpT4TgSzwjZxlNjVbnevzszAQcTwumGO7Vw8
	xeo21i2CVy/Gq19p7VF4VuV4Uci4dtCSmzOTmXNFxM2UR07+g+bB4L0IJlrp36mg
	uVo/klshoBWqqvJZUa7dp0Z0HlkTkrrCeUoq6mEDitdhWeiS5osazpG6hiDqbjZk
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=BBNE4lTi+1CXVorJqyqZMFpa+IE=; b=EVUi7e6DNo15sFef2
	e4NMgYUG6efzJlOiHr4Csuc7W2QCD5E4KFTsjDf4xn08hGtGjYnU8XsezVyEH5bp
	3hTTYPJGdJ4oEOrkFF9T+OVbJkTZ4n8T0FWI2wV6ZRNu+NX+pYJ860IiXKby8+69
	3KAL7swdyQ/U1dR6g72yFCDxh8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED autolearn=ham version=3.3.2
X-HELO: mailgw1.uni-kl.de
Message-ID: <5220AEEC.2090900@mathematik.uni-kl.de>
Date: Fri, 30 Aug 2013 16:40:44 +0200
From: =?ISO-8859-1?Q?Andreas_Steenpa=DF?= <steenpass AT mathematik DOT uni-kl DOT de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: previously reported test case does not work in Cygwin 1.7.18
References: <51790015 DOT 1090304 AT mathematik DOT uni-kl DOT de>
In-Reply-To: <51790015.1090304@mathematik.uni-kl.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

I would like to bring the issue described below up again. I have just
tested this with Cygwin 1.7.24, and it shows the same behaviour as
before, so it seems that this bug still persists.

My system is:
$ uname -a
CYGWIN_NT-6.1-WOW64 zoppo 1.7.24(0.269/5/3) 2013-08-15 11:55 i686 Cygwin

Best regards,
Andreas


Le 25/04/2013 12:06, Andreas Steenpaß a écrit :
> 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
>
>
>


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