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/31626] New: [gdb/symtab] data races in gdb.rust/dwindex.exp
Date: Wed, 10 Apr 2024 11:27:58 +0000	[thread overview]
Message-ID: <bug-31626-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31626
           Summary: [gdb/symtab] data races in gdb.rust/dwindex.exp
           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 15457
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15457&action=edit
gdb.log

I did a run with fedora asahi 39 and -fsanitize=thread, and ran into a issues I
haven't seen before in test-case gdb.rust/dwindex.exp:
...
SUMMARY: ThreadSanitizer: data race bfd.h:2449 in bfd_get_section_limit_octets
SUMMARY: ThreadSanitizer: data race /home/vries/gdb/src/bfd/bfdio.c:514 in
bfd_seek
...

Rust compiler version:
...
$ rustc --version
rustc 1.77.0 (aedd173a2 2024-03-17) (Fedora 1.77.0-1.fc39)
...

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

             reply	other threads:[~2024-04-10 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 11:27 vries at gcc dot gnu.org [this message]
2024-04-10 15:19 ` [Bug symtab/31626] " tromey at sourceware dot org
2024-05-17 14:16 ` tromey at sourceware dot org
2024-05-17 14:25 ` 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-31626-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).