DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=UP+jXeVns/RRGTyl3Z84uuAUGswYiX+vKczAV44cwJO7rNpScT5B/
	k9aRP9RIMTOeLXdk2FA2ywnTpl8DdnGtP4URdbv8DSy46qvZomOOTC45xnJTlLTn
	f8sFgNXB3r4aHBkx3GERM8Wpt0vW12cvSzoJNbZeEITZRj7zf82awQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 28 Oct 2015 10:14:59 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: pthread_kill: signals remain pending after target thread exits
Message-ID: <20151028091459.GZ5319@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <28F5B565B6F6424C87E4AC0DCC84316575D71070@S1P5DAG5C.EXCHPROD.USA.NET> <20151021114810.GQ5319@calimero.vinschen.de> <28F5B565B6F6424C87E4AC0DCC84316575D73A86@S1P5DAG5C.EXCHPROD.USA.NET> <20151023125540.GI5319@calimero.vinschen.de> <28F5B565B6F6424C87E4AC0DCC84316575D8071E@S1P5DAG5C.EXCHPROD.USA.NET>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="YgZDKPIOvldTssBR"
Content-Disposition: inline
In-Reply-To: <28F5B565B6F6424C87E4AC0DCC84316575D8071E@S1P5DAG5C.EXCHPROD.USA.NET>
User-Agent: Mutt/1.5.23 (2014-03-12)

--YgZDKPIOvldTssBR
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Oct 27 19:06, John Carey wrote:
> Sorry for the delay.
>=20
> From: Corinna Vinschen [corinna-cygwin@cygwin.com]
> Sent: Friday, October 23, 2015 5:55 AM
> > > I've attached a test case that I *think* gets into the right spot, at
> > > least for 64-bit Cygwin 2.0.4.  That is, it hangs trying to receive
> > > the signal, instead of terminating.  (This test passes (terminates) in
> > > 32-bit Cygwin 1.7.9 and 64-bit Ubuntu 14.04.3 LTS.)
> >=20
> > Thanks for the testcase.  I applied a patch which hopefully works as
> > desired, at least to fix the immediate problem of the remaining pending
> > signal when a thread exits.  I uploaded a new developer snapshot to
> > https://cygwin.com/snapshots.  Please give it a try.
>=20
> Thanks; that was fast!  I tried replacing cygwin1.dll with cygwin1-201510=
23.dll .
>=20
> The original test case now works.  I checked some of my other tests,
> and unfortunately some of them failed, so I extracted out a new test
> case, which is attached.  My guess is that something is subtly different
> about the timing on this test.

Is this a regression?  Did it work with 2.2.1?


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--YgZDKPIOvldTssBR
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWMJISAAoJEPU2Bp2uRE+gSj4P/idephpLy5Vn79ykXaPQieOv
hrQDMGzBA+XHE5GyMU+BRgdiadBQU23CxrAD9oyVodDVW4j9htE/4KGW5qD7JTVV
vP/hmOHsU28BX3zUjMtiJQyGWQX4zR3X0MM7RJnLdSQrfJBYkzQcjE+8gn6EyFx+
nIkfZ0kX+V9PHJi4xGc5UbHvYtHZfeetCDmk6vHQKAUOuS33bQz0JJx6HkninRON
eMUm+7pRmae+L5NRssnyVVJwspZJOm85eTCa9odZMa1Qm7a5CWer87Zl59/DUuAt
f26AaRUb9+CTKqaK2dYjaYoVyVRKt06PfjHDT+W/UR5YQilSKSigBUQAyQBB5dlg
sORb1O3+sK5jEDvyCD8EGvns7tTTbmqVCG7AzFMH3sMLJ1Wx17/xX4aXvhJ/PPY5
Jexq9W/xIoOOBsG1JUSbFqGmQ5Nf54YphqoJYabDX+cIdVGfDzBcFJsqPqpkHz2f
uyuk1ArYsH45m11JCohWDwqPFPNRzC1sM7kF+8SYfMeI7ZRqBX8EsU9kQOId/L5Z
sZaA5l8pJrshYga0V10bKZHMdUekp+iExNuyh/AAil+P7o3hAwYLEvHXc5sEIJ0w
PnL0FUt9HLrFnFNT/9xS/7LyFo15391/fBcvzkxCZcTFFfQrmm3ktA9Ts2Tunmnd
vp0qsMDiVwkVO8fVy4Fb
=7zS6
-----END PGP SIGNATURE-----

--YgZDKPIOvldTssBR--