DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=A8BMx9iEoZrAW1M2X7193/57oyAfv
	Xef+WB1QkISaLHv24SUXBqjP7UV8jSCFT3SpJ1qwrvUDWS5BQfEkFc3JPe56smXj
	OU59NNGLzgvwwab7wPD0UbM8JouVbDD6Exe35HxfsHZi4wcL5EN56aD+5yv/U24Y
	PW7VFF9Gnc3wUk=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: John Carey <aeolus@electric-cloud.com>
To: Corinna Vinschen <corinna-cygwin@cygwin.com>,
        "cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: RE: pthread_kill: signals remain pending after target thread exits
Date: Thu, 29 Oct 2015 16:16:50 +0000
Message-ID: <28F5B565B6F6424C87E4AC0DCC84316575D81A49@S1P5DAG5C.EXCHPROD.USA.NET>
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> <20151028091459.GZ5319@calimero.vinschen.de>,<20151029080218.GF5319@calimero.vinschen.de>
In-Reply-To: <20151029080218.GF5319@calimero.vinschen.de>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

> From: Corinna Vinschen [corinna-cygwin@cygwin.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 different
> > > about the timing on this test.
> >
> > Is this a regression?  Did it work with 2.2.1?
> 
> 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.

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.

But both tests appear to pass in Cygwin 1.7.9, so in that sense
it is a regression, just not a recent one.

-- John Carey

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