From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: jan.kratochvil@redhat.com, yusunn@gmail.com, gdb@sourceware.org
Subject: Re: user friendly symbol name
Date: Fri, 09 Aug 2013 14:21:00 -0000 [thread overview]
Message-ID: <834nazrllt.fsf@gnu.org> (raw)
In-Reply-To: <5204F953.4070904@redhat.com>
> Date: Fri, 09 Aug 2013 15:14:43 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: Shang Yu <yusunn@gmail.com>, gdb@sourceware.org
>
> On 08/09/2013 11:22 AM, Jan Kratochvil wrote:
> > (gdb) maintenance demangle _ZNSt16nested_exceptionD2Ev
> > std::nested_exception::~nested_exception()
>
> Interesting. It seems a pity this is a maintenance
> command. Shouldn't we "upgrade" it to a regular user command?
My vote is YAY.
Thanks.
next prev parent reply other threads:[~2013-08-09 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 1:17 Shang Yu
2013-08-09 3:22 ` Hatte John
2013-08-09 10:22 ` Andreas Schwab
2013-08-09 10:22 ` Jan Kratochvil
2013-08-09 14:14 ` Pedro Alves
2013-08-09 14:21 ` Eli Zaretskii [this message]
2013-08-09 18:23 ` Tom Tromey
2013-08-12 16:39 ` Pedro Alves
2013-08-09 17:58 ` Shang Yu
2013-08-09 18:56 ` Jan Kratochvil
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=834nazrllt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=yusunn@gmail.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