public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
Cc: Bruno Larsen <blarsen@redhat.com>
Subject: Re: [PATCH v2 1/2] gdb/testsuite: allowed for function_range to deal with mangled functions
Date: Wed, 09 Nov 2022 10:15:29 -0700	[thread overview]
Message-ID: <874jv82gni.fsf@tromey.com> (raw)
In-Reply-To: <20221104154744.418906-2-blarsen@redhat.com> (Bruno Larsen via Gdb-patches's message of "Fri, 4 Nov 2022 16:47:44 +0100")

>>>>> "Bruno" == Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:

Bruno> When calling get_func_info inside a test case, it would cause failures
Bruno> if the function was printed using a C++ style mangled name. The current
Bruno> patch fixes this by allowing for mangled names along with the current
Bruno> rules.

Looks good.  Thank you.

Tom

  reply	other threads:[~2022-11-09 17:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 15:47 [PATCH v2 0/2] Improve error messages with incomplete variables Bruno Larsen
2022-11-04 15:47 ` [PATCH v2 1/2] gdb/testsuite: allowed for function_range to deal with mangled functions Bruno Larsen
2022-11-09 17:15   ` Tom Tromey [this message]
2022-11-10 11:41     ` Bruno Larsen
2022-11-10 13:44       ` Tom Tromey
2022-11-10 13:52         ` Bruno Larsen
2022-11-04 15:47 ` [PATCH v2 2/2] gdb/c++: Improve error messages in overload resolution Bruno Larsen
2022-11-09 17:47   ` Tom Tromey
2022-11-10 15:19   ` Simon Marchi
2022-11-10 15:29     ` Bruno Larsen
2022-11-10 15:45       ` Simon Marchi

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=874jv82gni.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=blarsen@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).