From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: REVISITED: Signal delivered while blocked
Date: Fri, 18 Aug 2017 16:20:00 -0000 [thread overview]
Message-ID: <20170818162040.GC6314@calimero.vinschen.de> (raw)
In-Reply-To: <c05c742f0f3809e6d1afb8fb2c646ad7@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
On Aug 16 23:22, Houder wrote:
> Hi,
>
> Please read this post first:
>
> https://cygwin.com/ml/cygwin/2017-08/msg00048.html
> ( Signal delivered while blocked -- by Noah Misch, August 4th 2017 )
>
> This post is not intended to "hijack" the post by Noah Misch; this post only
> ships an alternative (i.e. revised) testcase for the one by provided by Noah
> Misch.
>
> The alternative testcase in fact consists of 2 testcases (2 files):
>
> 1. sigprocmask-exclusion4.c
> 2. sigprocmask-exclusion5.c
Thanks for the testcases. This is still a pretty tricky problem and a
few hours of debugging haven't shown anything conclusive. The signal
code was my former co-maintainer's domain, so I'm not as fluent in
debugging it.
ATM it looks like a race inside of the Cygwin DLL to me. The checks if
a signal should be handled and the *creation* of the call to the signal
handler (but *not* the actual call to the signal handler) may occur
before the signal is blocked, while the call then occurs after the
blocking.
Anyway, I'm not sure I have enough time to fully immerse into that
problem any time soon. I'd be not too unhappy if somebody would try to
debug this in the Cygwin DLL, too...
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-18 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 21:22 Houder
2017-08-18 16:20 ` Corinna Vinschen [this message]
2017-08-20 13:20 ` Houder
2017-08-20 12:59 ` Houder
2017-08-20 15:44 ` Kaz Kylheku
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=20170818162040.GC6314@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).