Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PING][PATCH v2 0/2] [gdb] TSAN fixes
Date: Tue, 3 Mar 2026 16:34:39 +0100	[thread overview]
Message-ID: <0ebdbd06-3b67-4852-8e39-8467a8afdb4c@suse.de> (raw)
In-Reply-To: <20260216180925.3174052-1-tdevries@suse.de>

On 2/16/26 7:09 PM, Tom de Vries wrote:
> I build gdb with TSAN at -O0, ran the testsuite and found a few problems.
> 
> This series fixes those.
> 
> The first patch changes the locking scheme.
> 
> The second patch removes a local lock in try_open_dwop_file.
> 

Ping.

Thanks,
- Tom

> Changes since v1:
> - commited an approved patch [1]
> - combined two patches related to the local lock in try_open_dwop_file
> - replaced last patch by new patch changing the locking scheme
> 
> [1] https://sourceware.org/pipermail/gdb-patches/2026-January/224422.html
> 
> Tom de Vries (2):
>    [gdb/symtab] Replace per-BFD lock with global BFD lock
>    [gdb/symtab] Fix data race in try_open_dwop_file
> 
>   gdb/dwarf2/read.c | 15 ++++-----------
>   gdb/gdb_bfd.c     | 37 ++++++++++++++++---------------------
>   gdb/gdb_bfd.h     |  4 ++++
>   3 files changed, 24 insertions(+), 32 deletions(-)
> 
> 
> base-commit: 2d306bf8a70e4ef9d6cd6eeecf17a8e6f4f04151


      parent reply	other threads:[~2026-03-03 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 18:09 [PATCH " Tom de Vries
2026-02-16 18:09 ` [PATCH v2 1/2] [gdb/symtab] Replace per-BFD lock with global BFD lock Tom de Vries
2026-03-04 20:20   ` Tom Tromey
2026-03-05 21:13     ` Tom de Vries
2026-02-16 18:09 ` [PATCH v2 2/2] [gdb/symtab] Fix data race in try_open_dwop_file Tom de Vries
2026-03-04 20:29   ` Tom Tromey
2026-05-27 19:16     ` Tom de Vries
2026-05-27 20:48       ` Tom Tromey
2026-05-27 21:55         ` Tom de Vries
2026-03-03 15:34 ` Tom de Vries [this message]

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=0ebdbd06-3b67-4852-8e39-8467a8afdb4c@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@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