public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "luis.machado at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/26228] FAIL: gdb.threads/create-fail.exp: iteration x: run till end (SIG32)
Date: Tue, 02 Feb 2021 11:55:49 +0000	[thread overview]
Message-ID: <bug-26228-4717-UKZt6HXBFr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26228-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Luis Machado <luis.machado at linaro dot org> ---
While investigating this, I noticed something else that may indicate a
kernel-side counterpart.

Although this doesn't FAIL for x86_64-linux/Ubuntu 20.04, I can trigger FAIL's
manually if I produce enough noise (by, for example, enabling infrun debugging)
while the testcase is running.

So it seems that this test passes if GDB runs the test undisturbed (and
quickly). If there is considerable noise going on during GDB's execution of the
test, we will run into the SIG32.

It is almost as if the kernel misses sending the signal notification for SIG32
in some cases. Adhemerval, a glibc maintainer, mentioned there might be a race
going on somewhere.

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

  parent reply	other threads:[~2021-02-02 11:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11  8:35 [Bug threads/26228] New: " vries at gcc dot gnu.org
2020-07-11  8:52 ` [Bug threads/26228] " vries at gcc dot gnu.org
2020-07-11  9:11 ` vries at gcc dot gnu.org
2020-07-24 13:59 ` vries at gcc dot gnu.org
2021-02-01 21:44 ` vries at gcc dot gnu.org
2021-02-02 11:55 ` luis.machado at linaro dot org [this message]
2021-02-04 13:27 ` vries at gcc dot gnu.org
2021-02-04 14:11 ` luis.machado at linaro dot org
2021-02-04 14:15 ` vries at gcc dot gnu.org
2021-02-04 14:24 ` luis.machado at linaro dot org
2021-02-04 17:27 ` vries at gcc dot gnu.org
2021-02-12 19:12 ` cvs-commit at gcc dot gnu.org
2021-02-12 19:13 ` 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-26228-4717-UKZt6HXBFr@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).