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/29286] New: SUMMARY: ThreadSanitizer: data race gdb/dwarf2/read.c:4100 in dw_expand_symtabs_matching_file_matcher
Date: Sat, 25 Jun 2022 09:19:43 +0000 [thread overview]
Message-ID: <bug-29286-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29286
Bug ID: 29286
Summary: SUMMARY: ThreadSanitizer: data race
gdb/dwarf2/read.c:4100 in
dw_expand_symtabs_matching_file_matcher
Product: gdb
Version: 12.1
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Created attachment 14168
--> https://sourceware.org/bugzilla/attachment.cgi?id=14168&action=edit
gdb.log
I build gdb with -fsanitizer=thread and gcc 7.5.0, using patches:
- https://sourceware.org/pipermail/gdb-patches/2022-June/190336.html
- https://sourceware.org/pipermail/gdb-patches/2022-June/190337.html
The latter is not necessary when using gcc 8 or later. I'm guessing the former
is not necessary on a PIE-by-default system.
When running the testsuite, I run into:
...
FAIL: gdb.ada/access_to_packed_array.exp: maint expand-symtabs
...
Due to:
...
SUMMARY: ThreadSanitizer: data race
/home/vries/gdb_versions/devel/src/gdb/dwarf2/read.c:4100 in
dw_expand_symtabs_matching_file_matcher^
...
See gdb.log attachement for more detail.
I see just one FAIL sofar, but the problem seems to be quite common:
...
$ grep -c "SUMMARY: ThreadSanitizer" gdb.log
253
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-06-25 9:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 9:19 vries at gcc dot gnu.org [this message]
2022-06-25 9:19 ` [Bug gdb/29286] " vries at gcc dot gnu.org
2022-06-25 9:20 ` vries at gcc dot gnu.org
2022-06-25 9:57 ` vries at gcc dot gnu.org
2022-06-25 11:10 ` vries at gcc dot gnu.org
2022-06-25 11:29 ` vries at gcc dot gnu.org
2022-06-25 12:14 ` vries at gcc dot gnu.org
2022-06-25 12:26 ` tromey at sourceware dot org
2022-06-25 14:17 ` vries at gcc dot gnu.org
2022-06-25 16:03 ` vries at gcc dot gnu.org
2022-06-25 16:17 ` tromey at sourceware dot org
2022-06-25 16:19 ` tromey at sourceware dot org
2022-06-25 20:33 ` vries at gcc dot gnu.org
2022-06-25 21:26 ` vries at gcc dot gnu.org
2022-06-25 22:38 ` vries at gcc dot gnu.org
2022-06-26 13:16 ` vries at gcc dot gnu.org
2022-06-26 13:36 ` vries at gcc dot gnu.org
2022-06-28 5:47 ` vries at gcc dot gnu.org
2022-06-28 5:48 ` vries at gcc dot gnu.org
2022-06-28 12:38 ` vries at gcc dot gnu.org
2022-06-29 13:12 ` vries at gcc dot gnu.org
2022-06-29 15:34 ` vries at gcc dot gnu.org
2022-07-12 14:59 ` vries at gcc dot gnu.org
2022-07-13 17:01 ` tromey at sourceware dot org
2022-07-14 7:10 ` vries at gcc dot gnu.org
2022-07-14 7:13 ` vries at gcc dot gnu.org
2022-07-14 18:50 ` vries at gcc dot gnu.org
2022-07-14 18:53 ` vries at gcc dot gnu.org
2022-09-23 20:44 ` tromey at sourceware dot org
2022-09-24 5:39 ` 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-29286-4717@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).