From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] [gdb] TSAN fixes
Date: Wed, 27 May 2026 21:03:41 +0200 [thread overview]
Message-ID: <65d83245-c98e-457d-9a2e-c86ae2de3b49@suse.de> (raw)
In-Reply-To: <20260527190228.3656310-1-tdevries@suse.de>
On 5/27/26 9:02 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 is a refactoring patch.
>
> The second patch removes a local lock in try_open_dwop_file.
>
I forgot to mention: this is v3.
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
>
> Changes since v2:
> - committed another approved patch [2]
> - use gdb_bfd_check_format consistently instead of just once
> - add gdb_bfd_check_format_matches, addressing the same issue as for
> gdb_bfd_check_format
> - factor out refactoring patch, to make it easier to review
>
> [1] https://sourceware.org/pipermail/gdb-patches/2026-January/224422.html
> [2] https://sourceware.org/pipermail/gdb-patches/2026-February/225028.html
>
> Versions:
> - v1 https://sourceware.org/pipermail/gdb-patches/2026-January/224424.html
> - v2 https://sourceware.org/pipermail/gdb-patches/2026-February/225027.html
>
> Tom de Vries (2):
> [gdb] Add gdb_bfd_check_format and gdb_bfd_check_format_matches
> [gdb/symtab] Fix data race in try_open_dwop_file
>
> gdb/build-id.c | 4 ++--
> gdb/cli/cli-dump.c | 2 +-
> gdb/compile/compile-object-load.c | 2 +-
> gdb/corelow.c | 8 ++++----
> gdb/dwarf2/dwz.c | 2 +-
> gdb/dwarf2/read.c | 15 ++++-----------
> gdb/exec.c | 2 +-
> gdb/gdb_bfd.c | 24 ++++++++++++++++++++++--
> gdb/gdb_bfd.h | 11 ++++++++++-
> gdb/i386-darwin-tdep.c | 2 +-
> gdb/jit.c | 2 +-
> gdb/machoread.c | 6 +++---
> gdb/minidebug.c | 2 +-
> gdb/solib-aix.c | 6 +++---
> gdb/solib-rocm.c | 2 +-
> gdb/solib.c | 4 ++--
> gdb/symfile-mem.c | 2 +-
> gdb/symfile.c | 6 +++---
> gdb/windows-nat.c | 2 +-
> 19 files changed, 63 insertions(+), 41 deletions(-)
>
>
> base-commit: d623dadc2c4ecd509359015ae5a1ac856ba89b05
next prev parent reply other threads:[~2026-05-27 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 19:02 Tom de Vries
2026-05-27 19:02 ` [PATCH 1/2] [gdb] Add gdb_bfd_check_format and gdb_bfd_check_format_matches Tom de Vries
2026-05-27 19:02 ` [PATCH 2/2] [gdb/symtab] Fix data race in try_open_dwop_file Tom de Vries
2026-05-27 19:03 ` Tom de Vries [this message]
2026-05-28 16:37 ` [PATCH 0/2] [gdb] TSAN fixes Tom Tromey
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=65d83245-c98e-457d-9a2e-c86ae2de3b49@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