From: John Carey <aeolus@electric-cloud.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: pthread_kill: signals remain pending after target thread exits
Date: Mon, 02 Nov 2015 23:55:00 -0000 [thread overview]
Message-ID: <28F5B565B6F6424C87E4AC0DCC84316575D81F11@S1P5DAG5C.EXCHPROD.USA.NET> (raw)
In-Reply-To: <20151102175800.GA13010@calimero.vinschen.de>
> From: Corinna Vinschen [corinna-cygwin@cygwin.com]
> Sent: Monday, November 02, 2015 9:58 AM
> On Nov 2 15:18, Corinna Vinschen wrote:
> > On Oct 29 16:16, John Carey wrote:
> > > > 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.
> >
> > 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.
I tested snapshot cygwin1-20151102.dll, and it works in all of my tests. Nice!
I'm glad you figured out how to delete those pending signals.
Thanks,
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
next prev parent reply other threads:[~2015-11-02 23:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 18:11 John Carey
2015-10-21 11:48 ` Corinna Vinschen
2015-10-22 8:34 ` John Carey
2015-10-23 14:30 ` Corinna Vinschen
2015-10-27 11:15 ` Corinna Vinschen
2015-10-28 3:39 ` John Carey
2015-10-28 13:28 ` Corinna Vinschen
2015-10-29 13:23 ` Corinna Vinschen
2015-10-29 17:34 ` John Carey
2015-10-29 17:40 ` John Carey
2015-11-02 14:18 ` Corinna Vinschen
2015-11-02 17:58 ` Corinna Vinschen
2015-11-02 23:55 ` John Carey [this message]
2015-11-03 9:00 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28F5B565B6F6424C87E4AC0DCC84316575D81F11@S1P5DAG5C.EXCHPROD.USA.NET \
--to=aeolus@electric-cloud.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).