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/31264] [gdb] ThreadSanitizer: data race format.c:132 in bfd_preserve_save
Date: Tue, 30 Jan 2024 01:35:23 +0000	[thread overview]
Message-ID: <bug-31264-4717-b6VE9bfUqN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31264-4717@http.sourceware.org/bugzilla/>

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

--- Comment #7 from Tom Tromey <tromey at sourceware dot org> ---
Some work here:
https://sourceware.org/pipermail/binutils/2024-January/132224.html

If that goes in, I'll change gdb's BFD error handler.
I'll probably have it call warning (we can already intercept
those in workers), not sure yet though.

Still haven't investigated the clash with bfd_cache_close_all.

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

  parent reply	other threads:[~2024-01-30  1:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  9:49 [Bug gdb/31264] New: " vries at gcc dot gnu.org
2024-01-22 18:49 ` [Bug gdb/31264] " vries at gcc dot gnu.org
2024-01-22 20:32 ` tromey at sourceware dot org
2024-01-23  1:10 ` tromey at sourceware dot org
2024-01-23  8:58 ` vries at gcc dot gnu.org
2024-01-23  9:38 ` vries at gcc dot gnu.org
2024-01-29 20:14 ` tromey at sourceware dot org
2024-01-29 20:15 ` tromey at sourceware dot org
2024-01-30  1:35 ` tromey at sourceware dot org [this message]
2024-02-12 19:06 ` tromey at sourceware dot org
2024-03-15  0:01 ` tromey at sourceware dot org
2024-03-24 21:13 ` tromey at sourceware dot org
2024-04-14 17:53 ` brobecker at gnat dot com
2024-04-15 12:54 ` tromey at sourceware dot org
2024-04-16 22:53 ` cvs-commit at gcc dot gnu.org
2024-04-16 22:53 ` cvs-commit at gcc dot gnu.org
2024-04-16 22:55 ` tromey at sourceware dot org
2024-05-17 14:17 ` 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-31264-4717-b6VE9bfUqN@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).