From: Dan Bonachea <dobonachea@lbl.gov>
To: cygwin@cygwin.com, Dan Bonachea <dobonachea@lbl.gov>
Cc: "E. Madison Bray" <erik.m.bray@gmail.com>, gasnet-devel@lbl.gov
Subject: Re: Bug: Incorrect signal behavior in multi-threaded processes
Date: Thu, 31 Jan 2019 00:12:00 -0000 [thread overview]
Message-ID: <CAJTO8-Z18U+g+8kzRxpY-g7Ds5CGpuJG0-n6Pmevt_2dPS60AQ@mail.gmail.com> (raw)
In-Reply-To: <20190130212303.GQ3912@calimero.vinschen.de>
On Wed, Jan 30, 2019 at 4:23 PM Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> > > > Poking around further, I find that replacing the signal generation
> > > > code in the test program for all cases with :
> > > >
> > > > pthread_kill(pthread_self(),sigid)
> > > >
> > > > generates compliant signal delivery behavior!
> > >
> > > Thanks, I fixed that in Cygwin. It will be part of the 3.0 release.
> >
> > I think I have a solution for the SISEGV misbehaviour. I have to
> > test it a bit but this may make it into Cygwin 3.0 if all is well.
>
> Please try the latest developer snapshot from https://cygwin.com/snapshots/
> or the new 3.0.0-0.3 test release. I hope this fixes the problem
> sufficiently.
Hi Corinna -
I've installed the 3.0.0-0.3 test release on my workstation and
confirmed that it fixes all the reported misbehaviors in the test
program.
It also appears to fix the signal-related problems encountered in our
multi-threaded production code.
Thanks so much for the prompt fixes!
-D
--
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:[~2019-01-31 0:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 20:33 Dan Bonachea
2019-01-22 9:13 ` Corinna Vinschen
2019-01-22 11:16 ` E. Madison Bray
2019-01-22 20:43 ` Dan Bonachea
2019-01-23 12:44 ` E. Madison Bray
2019-01-29 23:22 ` Dan Bonachea
2019-01-30 10:44 ` Corinna Vinschen
2019-01-30 15:48 ` Corinna Vinschen
2019-01-30 21:23 ` Corinna Vinschen
2019-01-31 0:12 ` Dan Bonachea [this message]
2019-01-31 19:48 ` 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=CAJTO8-Z18U+g+8kzRxpY-g7Ds5CGpuJG0-n6Pmevt_2dPS60AQ@mail.gmail.com \
--to=dobonachea@lbl.gov \
--cc=cygwin@cygwin.com \
--cc=erik.m.bray@gmail.com \
--cc=gasnet-devel@lbl.gov \
/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).