public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31261] [gdb] ThreadSanitizer: data race objfiles.c:648 in objfile_relocate1 Date: Sat, 10 Feb 2024 22:10:43 +0000 [thread overview] Message-ID: <bug-31261-4717-5ipw4Cirb8@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31261-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31261 --- Comment #3 from Tom Tromey <tromey at sourceware dot org> --- Right now the lookup is done by searching all objfiles. However, that seems weird, since surely the debuginfo could only really describe a symbol in the current objfile. I hope this is true since it's really the only way to make this work ok using unrelocated addresses. Maybe it's possible to test this on one of the MIPS machines in the compile farm. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-10 22:10 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 9:29 [Bug gdb/31261] New: " vries at gcc dot gnu.org 2024-01-22 14:30 ` [Bug gdb/31261] " vries at gcc dot gnu.org 2024-01-22 20:33 ` tromey at sourceware dot org 2024-01-31 2:24 ` tromey at sourceware dot org 2024-02-10 22:10 ` tromey at sourceware dot org [this message] 2024-02-12 19:07 ` tromey at sourceware dot org 2024-02-16 2:42 ` tromey at sourceware dot org 2024-02-23 16:10 ` tromey at sourceware dot org 2024-03-09 0:31 ` tromey at sourceware dot org 2024-04-20 18:27 ` brobecker at gnat dot com 2024-05-04 16:07 ` cvs-commit at gcc dot gnu.org 2024-05-04 16:07 ` 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-31261-4717-5ipw4Cirb8@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).