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, 09 Mar 2024 00:31:50 +0000 [thread overview]
Message-ID: <bug-31261-4717-nLZ0Qzn7GD@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 #6 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Tom Tromey from comment #5)
> https://sourceware.org/pipermail/gdb-patches/2024-February/206633.html
>
> However last night I was wondering if this complicated
> stuff is even necessary. It seems to me that this MIPS16
> special case can't really affect the index anyway.
The way the code is shared in the DWARF reader makes this a
little trickier than I thought. It still might be better though.
I wonder why MIPS16 has to work this weird way.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-09 0:31 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
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 [this message]
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-nLZ0Qzn7GD@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).