Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: simon.marchi@polymtl.ca
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] gdb/dwarf: fix crash when .gdb_index contains Rust legacy mangled names
Date: Wed, 14 Oct 2026 07:01:39 -0600	[thread overview]
Message-ID: <874ieo5tcc.fsf@tromey.com> (raw)
In-Reply-To: <20261005052602.1288766-3-simon.marchi@polymtl.ca> (simon marchi's message of "Mon, 5 Oct 2026 01:25:49 -0400")

>>>>> "Simon" == simon marchi <simon.marchi@polymtl.ca> writes:

Simon> Since this name does not match the C++ and Ada special cases, it falls into
Simon> the DOT_STYLE else:
Simon>     components = split_name (name, split_style::DOT_STYLE);
Simon> Because of the consecutive dots in the symbol name, `components` (an
Simon> std::vector<std::string_view>) contains some empty components.  Some code
Simon> later calls .back() on one of those empty string_views, which is invalid.

It seems to me that a "dot-style" name could never have two consecutive
dots.  So, how about changing split_name to bail out in this case?

I see I didn't write any unit tests for split-name.c, which seems like a
real oversight.

Simon> I can't think of a pretty way to fix this.  Since we don't have a flag that
Simon> tells us whether a name is a linkage name or not, we can only make some
Simon> educated guesses.

Yeah.  I think we've resisted doing this.  But maybe we should just give
in and look for a leading _Z/_R.

Tom

  parent reply	other threads:[~2026-10-14 13:02 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 [this message]
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   ` [PATCH v2 0/2] Fix " Simon Marchi
2026-10-15 15:47     ` 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=874ieo5tcc.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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