public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30695] [gdb, tsan] FAIL: gdb.base/bg-exec-sigint-bp-cond.exp: no force memory write: SIGINT does not interrupt background execution
Date: Wed, 02 Aug 2023 00:35:15 +0000	[thread overview]
Message-ID: <bug-30695-4717-xwNufqnpqk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30695-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30695

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
From https://www.gnu.org/software/libc/manual/html_node/Merged-Signals.html:
...
If multiple signals of the same type are delivered to your process before your
signal handler has a chance to be invoked at all, the handler may only be
invoked once, as if only a single signal had arrived. In effect, the signals
merge into one. This situation can arise when the signal is blocked, or in a
multiprocessing environment where the system is busy running some other
processes while the signals are delivered. This means, for example, that you
cannot reliably use a signal handler to count signals. The only distinction you
can reliably make is whether at least one signal has arrived since a given time
in the past. 
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-08-02  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-29  7:18 [Bug gdb/30695] New: " vries at gcc dot gnu.org
2023-07-29  7:29 ` [Bug gdb/30695] " vries at gcc dot gnu.org
2023-08-02  0:35 ` vries at gcc dot gnu.org [this message]
2023-08-02 14:38 ` vries at gcc dot gnu.org

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=bug-30695-4717-xwNufqnpqk@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).