From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] fix disassemble foo::bar::~bar
Date: Fri, 22 Feb 2013 19:15:00 -0000 [thread overview]
Message-ID: <87k3q088iv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5126B48A.1080903@redhat.com> (Keith Seitz's message of "Thu, 21 Feb 2013 15:58:02 -0800")
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
Keith> Another option is to use the c++ name parser:
Keith> diff --git a/gdb/valops.c b/gdb/valops.c
Keith> index 93c09d8..b006b49 100644
Keith> --- a/gdb/valops.c
Keith> +++ b/gdb/valops.c
Keith> @@ -3160,7 +3160,7 @@ destructor_name_p (const char *name, struct type
Keith> *type)
Keith> {
Keith> if (name[0] == '~')
Keith> {
Keith> - const char *dname = type_name_no_tag_or_error (type);
Keith> + const char *dname = cp_func_name (type_name_no_tag_or_error (type));
Keith> const char *cp = strchr (dname, '<');
Keith> unsigned int len;
Keith> The above patch fixes Doug's test cases and also is regression-free on
Keith> native x86_64-unknown-linux (Fedora 15).
I tend to think this is preferable. At least, as long as we have to
keep destructor_name_p.
This patch is ok with me, if it includes Doug's test case, though I'd
like to hear from Doug about it as well.
Tom
next prev parent reply other threads:[~2013-02-22 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 0:14 Doug Evans
2013-02-21 21:14 ` Tom Tromey
2013-02-21 23:58 ` Keith Seitz
2013-02-22 19:15 ` Tom Tromey [this message]
2013-02-22 19:43 ` Keith Seitz
2013-02-22 20:00 ` 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=87k3q088iv.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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