From: Simon Marchi <simon.marchi@efficios.com>
To: gcc-patches@sourceware.org, gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [PATCH v2 0/2] Fix crash when .gdb_index contains Rust legacy mangled names
Date: Wed, 14 Oct 2026 12:46:57 -0400 [thread overview]
Message-ID: <20261014164830.358677-1-simon.marchi@efficios.com> (raw)
In-Reply-To: <20261005052602.1288766-3-simon.marchi@polymtl.ca>
This is v2 of:
https://inbox.sourceware.org/gdb-patches/878q4bumgh.fsf@redhat.com/T/#mf4974aff377310db2cf24c34224fb8e5a174a905
The changes are:
- do the fix in split_name: in DOT_STYLE mode, refuse to split a name
that would lead to an empty component
- add a preparatory patch that adds selftests for split_name
Simon Marchi (2):
gdb: add selftests for split_name
gdb/dwarf: fix crash when .gdb_index contains Rust legacy mangled
names
gdb/split-name.c | 199 ++++++++++++++++++
.../gdb-index-rust-legacy-linkage-name.c | 29 +++
.../gdb-index-rust-legacy-linkage-name.exp | 98 +++++++++
3 files changed, 326 insertions(+)
create mode 100644 gdb/testsuite/gdb.dwarf2/gdb-index-rust-legacy-linkage-name.c
create mode 100644 gdb/testsuite/gdb.dwarf2/gdb-index-rust-legacy-linkage-name.exp
base-commit: 91a47f3ae9d6d494b0c794a3ccd81b242bd15b7d
--
2.56.0
next prev parent reply other threads:[~2026-10-14 16:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 5:25 [PATCH 1/3] gdb/testsuite: fix rust compiler selection in gdb_default_target_compile simon.marchi
2026-10-05 5:25 ` [PATCH 2/3] gdb/testsuite: wrap rustc in cc-with-tweaks.exp simon.marchi
2026-10-06 10:56 ` Andrew Burgess
2026-10-05 5:25 ` [PATCH 3/3] gdb/dwarf: fix crash when .gdb_index contains Rust legacy mangled names simon.marchi
2026-10-06 11:01 ` Andrew Burgess
2026-10-06 13:39 ` Simon Marchi
2026-10-14 13:01 ` Tom Tromey
2026-10-14 13:22 ` Simon Marchi
2026-10-14 14:59 ` Tom Tromey
2026-10-14 16:13 ` Tom Tromey
2026-10-14 16:26 ` Simon Marchi
2026-10-14 16:46 ` Simon Marchi [this message]
2026-10-15 15:47 ` [PATCH v2 0/2] Fix " Tom Tromey
2026-10-18 3:45 ` Simon Marchi
2026-10-14 16:46 ` [PATCH v2 1/2] gdb: add selftests for split_name Simon Marchi
2026-10-15 15:48 ` Tom Tromey
2026-10-15 18:33 ` Simon Marchi
2026-10-16 3:15 ` Tom Tromey
2026-10-14 16:46 ` [PATCH v2 2/2] gdb/dwarf: fix crash when .gdb_index contains Rust legacy mangled names Simon Marchi
2026-10-06 10:56 ` [PATCH 1/3] gdb/testsuite: fix rust compiler selection in gdb_default_target_compile Andrew Burgess
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=20261014164830.358677-1-simon.marchi@efficios.com \
--to=simon.marchi@efficios.com \
--cc=gcc-patches@sourceware.org \
--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