From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Signal delivered while blocked
Date: Fri, 04 Aug 2017 17:02:00 -0000 [thread overview]
Message-ID: <20170804170254.GM25551@calimero.vinschen.de> (raw)
In-Reply-To: <20170804074445.GB3154757@rfd.leadboat.com>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
On Aug 4 00:44, Noah Misch wrote:
> The attached demonstration program blocks signals (with sigprocmask()) to
> achieve mutual exclusion between signal handlers. It aborts upon receipt of a
> blocked signal. On "CYGWIN_NT-10.0 2.7.0(0.306/5/3) 2017-02-12 13:18 x86_64",
> signals regularly arrive despite being blocked. Essential parts of the
> program include handling two signal numbers and having handlers run for at
> least 1-2ms; this problem goes away if I remove one of those attributes.
> GNU/Linux, AIX, Solaris, and "CYGWIN_NT-6.0 1.7.27(0.271/5/3) 2013-12-09 11:57
> i686" never deliver a blocked signal to this program. I think this Cygwin
> behavior is non-conforming.
Thanks for the testcase. I debugged this a while today but the problem
is far from trivial, apparently. Don't hold your breath for a quick
solution.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-08-04 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 7:45 Noah Misch
2017-08-04 17:02 ` Corinna Vinschen [this message]
2017-08-04 18:58 ` Kaz Kylheku
2017-08-05 6:40 ` Noah Misch
2017-08-14 6:03 ` Houder
2017-08-14 8:36 ` Signal delivered while blocked (2) Houder
2017-08-19 8:01 ` Signal delivered while blocked Noah Misch
2017-08-20 12:18 ` Houder
2017-08-20 16:16 ` Noah Misch
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=20170804170254.GM25551@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).