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/31264] [gdb] ThreadSanitizer: data race format.c:132 in bfd_preserve_save
Date: Tue, 23 Jan 2024 08:58:33 +0000 [thread overview]
Message-ID: <bug-31264-4717-Z0lQ9SEebd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31264-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31264
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #2)
> I couldn't reproduce this on Fedora 38.
I ran into this on Fedora 39, aarch64, in a full test run.
I tried reproducing in a loop like so running only the test-case:
...
$ for n in $(seq 1 25); do \
./test.sh 2>&1 | grep "# of " | sort -u; \
grep -ac ThreadSan gdb.log; \
done
...
There's grepping in gdb.log because there's no FAIL when ThreadSanitizer
triggers.
It reproduced only once out of 25 times.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-23 8:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 9:49 [Bug gdb/31264] New: " vries at gcc dot gnu.org
2024-01-22 18:49 ` [Bug gdb/31264] " vries at gcc dot gnu.org
2024-01-22 20:32 ` tromey at sourceware dot org
2024-01-23 1:10 ` tromey at sourceware dot org
2024-01-23 8:58 ` vries at gcc dot gnu.org [this message]
2024-01-23 9:38 ` vries at gcc dot gnu.org
2024-01-29 20:14 ` tromey at sourceware dot org
2024-01-29 20:15 ` tromey at sourceware dot org
2024-01-30 1:35 ` tromey at sourceware dot org
2024-02-12 19:06 ` tromey at sourceware dot org
2024-03-15 0:01 ` tromey at sourceware dot org
2024-03-24 21:13 ` tromey at sourceware dot org
2024-04-14 17:53 ` brobecker at gnat dot com
2024-04-15 12:54 ` tromey at sourceware dot org
2024-04-16 22:53 ` cvs-commit at gcc dot gnu.org
2024-04-16 22:53 ` cvs-commit at gcc dot gnu.org
2024-04-16 22:55 ` tromey at sourceware dot org
2024-05-17 14:17 ` tromey at sourceware dot 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-31264-4717-Z0lQ9SEebd@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).