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 symtab/29344] New: [gdb/symtab] SUMMARY: ThreadSanitizer: data race read.c:6236 in cutu_reader::cutu_reader() Date: Sat, 09 Jul 2022 10:19:51 +0000 [thread overview] Message-ID: <bug-29344-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29344 Bug ID: 29344 Summary: [gdb/symtab] SUMMARY: ThreadSanitizer: data race read.c:6236 in cutu_reader::cutu_reader() Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- Created attachment 14201 --> https://sourceware.org/bugzilla/attachment.cgi?id=14201&action=edit gdb.log Another data race, test-case gdb.dwarf2/dw4-sig-types.exp, target board cc-with-dwz-m. Related to the per_cu->length field. AFAICT, similar to the dwarf_version case. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-07-09 10:19 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-09 10:19 vries at gcc dot gnu.org [this message] 2022-07-11 9:39 ` [Bug symtab/29344] " 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-29344-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: linkBe 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).