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:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=s/sAxEXIAY99n1aAME/fMzkrBZlY+HtLwoHvAoNS+2PlRD2f86nTE
	21mruzkps3qliHhP1rPbWYj5IWdveY5yMO6hpcShqzSrIrPZnMtXA2afuZTIYJj3
	8QkVAoqpbv7MlRJJHaDn/8mHMJevXjjla8JGMciWLr617Xt+NuE4pA=
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:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=zQ++hG/zHTewjKVteZHp6rJn618=; b=E/GwMKvaHQbWslhAZGmBXBkT62Sc
	FfOiP1oXKxsuG1w0nTGunQ7TNp3e7Xl3A7J74srBwunxsDCs+jUfMfgaOc+X/3EW
	T7Xg4bEl7C/tH1qWnmcO8Pk7v4LKFTSYVcRaLJaKi4++LIwB3WzZRnbLh9t3NxBx
	lfSjoILlxYG4BBE=
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=-4.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Mon, 2 Nov 2015 18:58:00 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	John Carey <aeolus AT electric-cloud DOT com>
Cc:	cygwin AT cygwin DOT com
Subject:	Re: pthread_kill: signals remain pending after target thread exits
Message-ID:	<20151102175800.GA13010@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	John Carey <aeolus AT electric-cloud DOT com>, cygwin AT cygwin DOT com
References:	<28F5B565B6F6424C87E4AC0DCC84316575D71070 AT S1P5DAG5C DOT EXCHPROD DOT USA DOT NET> <20151021114810 DOT GQ5319 AT calimero DOT vinschen DOT de> <28F5B565B6F6424C87E4AC0DCC84316575D73A86 AT S1P5DAG5C DOT EXCHPROD DOT USA DOT NET> <20151023125540 DOT GI5319 AT calimero DOT vinschen DOT de> <28F5B565B6F6424C87E4AC0DCC84316575D8071E AT S1P5DAG5C DOT EXCHPROD DOT USA DOT NET> <20151028091459 DOT GZ5319 AT calimero DOT vinschen DOT de> <20151029080218 DOT GF5319 AT calimero DOT vinschen DOT de> <28F5B565B6F6424C87E4AC0DCC84316575D81A49 AT S1P5DAG5C DOT EXCHPROD DOT USA DOT NET> <20151102141838 DOT GB963 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
In-Reply-To:	<20151102141838.GB963@calimero.vinschen.de>
User-Agent:	Mutt/1.5.23 (2014-03-12)

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

On Nov  2 15:18, Corinna Vinschen wrote:
> On Oct 29 16:16, John Carey wrote:
> > > From: Corinna Vinschen [corinna-cygwin AT cygwin DOT com]
> > > Sent: Thursday, October 29, 2015 1:02 AM
> > > On Oct 28 10:14, Corinna Vinschen wrote:
> > ...
> > > > > Thanks; that was fast!  I tried replacing cygwin1.dll with cygwin=
1-20151023.dll .
> > > > >
> > > > > The original test case now works.  I checked some of my other tes=
ts,
> > > > > and unfortunately some of them failed, so I extracted out a new t=
est
> > > > > case, which is attached.  My guess is that something is subtly di=
fferent
> > > > > about the timing on this test.
> > > >
> > > > Is this a regression?  Did it work with 2.2.1?
> > >=20
> > > Answering myself here, this didn't work at all in 2.2.1.  I can
> > > reproduce the problem and I'm going to take a look.  Not sure if
> > > there's a quick solution, though.  This looks like a deadlock
> > > situation.  The signal definitely got send, I just don't see yet
> > > why it's not handled in wait_sig.
> >=20
> > Yes, test_pending_signal2.c fails in 2.2.1, though the symptoms
> > differ: there is no Cygwin process left hanging that cannot be
> > killed by a Cygwin signal.
> >=20
> > But both tests appear to pass in Cygwin 1.7.9, so in that sense
> > it is a regression, just not a recent one.
>=20
> The regression here was my original fix.  It didn't clear pending
> signals for an exiting thread thorougly enough.  I applied a patch now
> which should fix this issue.  I'll upload a new developer snapshot to
> https://cygwin.com/snapshots/ later today or tomorrow (still looking
> into the PrlFS issue).  Please give it a try.

Snapshot is up.  The fix is in the 2.3.0-0.5 test release as well.
Please give any one of them a try.


Thanks,
Corinna

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

--3V7upXqbjpZ4EhLz
Content-Type: application/pgp-signature

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

iQIcBAEBCAAGBQJWN6QoAAoJEPU2Bp2uRE+gZbgP/3YA0vCQ2GbGIKM6oYcqMTbm
kJea92h1QCQctVxOF6+JbjKkunLQsDHsGK/RXwg0jK3pUBg4qOYdLJlf34H8HHz8
8jTmjQwF/Wd1LyLBGz5Yl2iOzqXhlVFppn8qgOeh3mMYRNlKb8aSjwZ9TY1ugFUU
PcGnrgBtsUfkqSVY8w5kBC7Nj/f0G6KNICerLygPjIFA7eT8d3RZFs0H+tooweay
nIfwMTwHX9GoaZcflU9ss9gnDAPO9u1Em+dAdJ/nsQJWNDA5bRtlaMVZMJpQjaGr
RB9Q/g73bFm3pLNb5Kez4cPpAYHua4kLsC66Fp7S7Ow5OoGL74xatro0WoZUWgcm
tew0odbII9zyd/BdmxxhZ8oh9Gtqpgc4thjHubVAHu7wZ+rMczrx74Rz6B9tEO5Q
+XSA1NxrK6A7KnW/duj5Gz2bE4sW+MSSRW5rh5rifdKcpFnQts1vrhVM/wDJgZzx
d2eLOiec+DbWSQj5Ch06iyiX5Lbu6emVaPPmJOvMXVk45pIKuoDOsR/pDQxC4Blb
bILSLOF1a8+mq5Zl3ZUSd/2dZcEkP+O05GDzhvU98ooQcjVXpIwJPm4XDaPhIfWX
+cOptlPRfpSSpIKB8u1zIiCFyoNnDt8hgQFUTzf60XN70y8cQjuYKb7bFtP3Y3gz
NUJDUQAJZw+t0kbMpjJw
=E8xA
-----END PGP SIGNATURE-----

--3V7upXqbjpZ4EhLz--

- Raw text -