From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Dan Bonachea <dobonachea@lbl.gov>, gasnet-devel@lbl.gov
Subject: Re: Bug: Incorrect signal behavior in multi-threaded processes
Date: Tue, 22 Jan 2019 09:13:00 -0000 [thread overview]
Message-ID: <20190122091324.GM2802@calimero.vinschen.de> (raw)
In-Reply-To: <CAJTO8-bD0jPR3Vyr84Z_4BUdh3pPiZ-9ekeMBFUOFJRn5e0wQQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
On Jan 20 15:33, Dan Bonachea wrote:
> I'm writing to report some POSIX compliance problems with Cygwin
> signal handling in the presence of multiple pthreads that our group
> has encountered in our parallel scientific computing codes.
>
> A minimal test program is copied below and also available here:
> https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=589
>
> I believe the test program is fully compliant with ISO C 99 and POSIX
> 1003.1-2016. In a nutshell, it registers one signal handler, spawns a
> number of pthreads, and then synchronously generates a signal from
> exactly one thread while others sit in a pthread_barrier_wait. The
> "throwing" thread and signal number can be varied from the command
> line, and diagnostic output indicates what happened.
> [...]
> Is there any hope of this situation ever improving?
Signal handling is a real beast and phread_barriers probably haven't
been tested as extensively yet as your testcase.
No guarantees for a patch, but I'll look into that as time permits.
Patches to fix bugs are very welcome: https://cygwin.com/contrib.html
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-22 9:13 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 [this message]
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
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=20190122091324.GM2802@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=dobonachea@lbl.gov \
--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).