Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Match demangled name in "skip"
Date: Wed, 16 Sep 2020 15:17:41 -0400	[thread overview]
Message-ID: <79a2552b-1231-77ee-ac77-ffae8f49899b@simark.ca> (raw)
In-Reply-To: <20200916181057.268427-1-tromey@adacore.com>

On 2020-09-16 2:10 p.m., Tom Tromey wrote:
> PR gdb/26598 notes that, before commit bcfe6157ca28 ("Use the linkage
> name if it exists"), the "skip" command would match the demangled name
> of a symbol, but now only matches the linkage name.
>
> This patch fixes this regression.  I looked at all calls to
> function_name_is_marked_for_skip, and only one used the linkage name.
>
> gdb/ChangeLog
> 2020-09-16  Tom Tromey  <tromey@adacore.com>
>
> 	PR gdb/26598:
> 	* infrun.c (fill_in_stop_func): Use find_pc_partial_function_sym.
>
> gdb/testsuite/ChangeLog
> 2020-09-16  Tom Tromey  <tromey@adacore.com>
>
> 	PR gdb/26598:
> 	* gdb.base/skipcxx.exp: New file.
> 	* gdb.base/skipcxx.cc: New file.

Thanks, that LGTM.

Since this changes stop_func_name from the mangled name to the demangled
name (like it was before your change?), I checked what else
stop_func_name was used for.  It is passed to
gdbarch_in_solib_return_trampoline.  Implementations use that name to
compare against hard-coded symbol names.  However, I would guess that
these symbol names are not prone to being mangled.  Otherwise, we'd need
to save both the demangled and linkage name.

Simon


  reply	other threads:[~2020-09-16 19:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 18:10 Tom Tromey
2020-09-16 19:17 ` Simon Marchi [this message]
2020-09-16 19:32   ` 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=79a2552b-1231-77ee-ac77-ffae8f49899b@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.com \
    /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