public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Signal delivered while blocked (2)
Date: Mon, 14 Aug 2017 08:36:00 -0000	[thread overview]
Message-ID: <3b48072dd1f4f1931dd7bb8b4bfc701b@xs4all.nl> (raw)
In-Reply-To: <8f7f7f8ae098c1321f608645c750cae4@smtp-cloud7.xs4all.net>

On 2017-08-14 08:03, Houder wrote:
> On Fri, 4 Aug 2017 00:44:45, Noah Misch wrote:
>> --UugvWAfsgieZRqgk
>> Content-Type: text/plain; charset=us-ascii
>> Content-Disposition: inline
>> 
>> 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.
> 
> Hi Noah,
> 
> I do not think that Cygwin is the problem here; your code is the 
> problem
> here, I believe.
[snip]

> You cannot use SIG_SETMASK in that context.

You cannot use SIG_SETMASK in that context in the way you do.

--
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

  reply	other threads:[~2017-08-14  8:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04  7:45 Signal delivered while blocked Noah Misch
2017-08-04 17:02 ` Corinna Vinschen
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   ` Houder [this message]
2017-08-19  8:01   ` 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=3b48072dd1f4f1931dd7bb8b4bfc701b@xs4all.nl \
    --to=houder@xs4all.nl \
    --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).