From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: sigpending() incorrectly returns signals pending on other threads
Date: Mon, 15 Jul 2019 09:54:00 -0000 [thread overview]
Message-ID: <77b8a5c1a1217fbec1e771f0a5f1ac6c@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <20190715075327.GL3772@calimero.vinschen.de>
On Mon, 15 Jul 2019 09:53:27, Corinna Vinschen wrote:
> On Jul 14 15:19, Houder wrote:
> > .. uhm, just a note in the interest of accuracy ...
> >
> > - standard signals (which include USRSIG1 and USRSIG2) are not queued
> > (traditional signal semantics)
> > - only real-time signals should be queued ...
>
> I think queing here means just what you outline above. It's kind of a
> queue of pending signals and in Cygwin it's actually literally a queue.
> It's >>> a kind of _queue_ <<< of pending signals ...
Not a Q if it would mean that a specific signal can be inserted more than
once in this Q ...
I am fully aware that you know all about Unix/Linux, but
for the sake of clarity:
20.12 (Signals are not queued) of LPI
"The set of pending signals is only a "mask"; it indicates whether or
not a signal has occurred, but NOT how many times it has occurred. In
other words, if the same signal is generated multiple times while it
is blocked, then it is recorded in the set of pending signals, and
later delivered, just ONCE. (One of the differences between standard
and realtime signals is that realtime signals are queued, as discussed
in Section 22.8.)
Listing 20-6 and Listing 20-7 show two programs that can be used to
observe that signals are not queued. ... "
Meaning the queue in Cygwin is not really a Q ...
Regards,
Henri
--
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
next prev parent reply other threads:[~2019-07-15 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 22:46 Kenton Varda
2019-07-07 2:16 ` Kenton Varda
2019-07-12 15:34 ` Corinna Vinschen
2019-07-14 13:19 ` Houder
2019-07-15 7:53 ` Corinna Vinschen
2019-07-15 9:54 ` Houder [this message]
2019-07-12 15:31 ` 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=77b8a5c1a1217fbec1e771f0a5f1ac6c@smtp-cloud8.xs4all.net \
--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).