From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Dan Bonachea <dobonachea@lbl.gov>
Cc: "E. Madison Bray" <erik.m.bray@gmail.com>,
cygwin@cygwin.com, gasnet-devel@lbl.gov
Subject: Re: Bug: Incorrect signal behavior in multi-threaded processes
Date: Wed, 30 Jan 2019 15:48:00 -0000 [thread overview]
Message-ID: <20190130154804.GJ3912@calimero.vinschen.de> (raw)
In-Reply-To: <20190130104421.GC3912@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
On Jan 30 11:44, Corinna Vinschen wrote:
> On Jan 29 18:21, Dan Bonachea wrote:
> > > A minimal test program is copied below and also available here:
> > > https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=589
> >
> > > It's worth noting POSIX 1003.1-2016 sec XRAT.B.2.4.1 (p.3577)
> > > specifically requires that any given signal should be delivered to
> > > exactly one thread. Also the spec for abort (p.565) requires the
> > > signal to be delivered as if by `raise(SIGABRT)` (p.1765) aka.
> > > `pthread_kill(pthread_self(),SIGABRT)` (p.1657), which implies
> > > any registered SIGABRT handler should run only on the thread
> > > which called abort().
> >
> > 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.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-30 15:48 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 [this message]
2019-01-30 21:23 ` Corinna Vinschen
2019-01-31 0:12 ` Dan Bonachea
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=20190130154804.GJ3912@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=dobonachea@lbl.gov \
--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).