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:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=rvFpdge9yN+/ZMPF3Kis5BE9eaQtkdm0Ud6W+8YcXrs7lnvOE4N7Q
	V5iEaS70T7YvvhhmyCnDfNWTWefbnXFfxPytksbQwp6JXsQOnPotdIGCvC8XzsEH
	487OjJ98uyBcB9bN6EoE2UaZiAUT5acaCgepzZ/DCZbtAEklRrRD2w=
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:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=7fVP2zkLMuwJ0lui5EJok2jsTWk=; b=mdqSoZ4rle0f3pPlWLaHLgpsD2qG
	wxc6K1LJc1p0eY/cT7YtmtQGxDC+vTZrz0eMIKGGA065gMlaFfK1Ym3C0/wOHz7m
	w1I83r9UU9jB80mpjgCFdftNnsRc2FfzcV2FtiSPWxb2XRxmYxmGA0EMXpwxBmx9
	h+Rogk28yDvPEF4=
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=-5.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Mon, 2 Nov 2015 15:18:38 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: pthread_kill: signals remain pending after target thread exits
Message-ID:	<20151102141838.GB963@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	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>
MIME-Version:	1.0
In-Reply-To:	<28F5B565B6F6424C87E4AC0DCC84316575D81A49@S1P5DAG5C.EXCHPROD.USA.NET>
User-Agent:	Mutt/1.5.23 (2014-03-12)

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

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 cygwin1-=
20151023.dll .
> > > >
> > > > 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 diff=
erent
> > > > 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.

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.


Thanks,
Corinna

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

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

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

iQIbBAEBCAAGBQJWN3C+AAoJEPU2Bp2uRE+gbfIP9jLtYwSKtmkTBPIH/KQ38Sxe
wIRpnMNXjjcPm4eQy9b201Kl5LnLp2IhsTxuasm2sslzJzy00K0mNk1o408ur6ET
rTPUhnY3346YnGu767NIOGpHnYYtMuoiCrEvXFm69LtGSykqilcDO3umCqMpvH1D
VOP2QY3+CqTIgiOLmxUuptC/prfYzLwGoBGc/sgIgvDLc/+WfDW4U7hftVXQAn4G
tWLSobE94ccFvzBlTG7vNc+RepcS+MX68XUF656cRbJAfdeJJOuUpwIoXbBkecXV
p7Iyni01Y4V9mlZWhQeQ+meV4l5JDjrsS6jOqkWekBJsXWDjDZnASyTKE7X0VSfC
MTxSaNsf9hmKH+p/UWXC9jOC7F3HXMHAzohfYh1DVzceHwYRD9bPV/NEnTXlzejt
JdtQCEa3NxojRVCptqY8qHwuBXf7nCJlERQoIKGsBhyRvZBaBs6pYJSVMsklPTWq
K4gKt2GSo7zS12+DTloKn/C9i2JGGx5Pn/FfkZc7MTvBER44j7o2vC7/M1WKIKtG
j2iRPQ4+biisOm2Ul8jN4qTe+ROqlcNbflpS3lZ3ZjQvdgw27I5UPdKXsBzyE+uk
jgFVC858I4WH9Jx9nsqEGN5ztf8jbSot3G6O+3efUclvett+L3YDx5c9yDjho06p
48IQtTa0LCb/Pin+UX0=
=G0mW
-----END PGP SIGNATURE-----

--V0207lvV8h4k8FAm--

- Raw text -