From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb@sourceware.org, simon.marchi@polymtl.ca, ssbssa@yahoo.de
Subject: Re: Demangling in backtraces
Date: Sun, 14 Mar 2021 09:43:33 +0200 [thread overview]
Message-ID: <83ft0ygoyi.fsf@gnu.org> (raw)
In-Reply-To: <87czw242h4.fsf@linux-m68k.org> (message from Andreas Schwab on Sun, 14 Mar 2021 08:29:59 +0100)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Simon Marchi <simon.marchi@polymtl.ca>, Hannes Domani
> <ssbssa@yahoo.de>, Eli Zaretskii <eliz@gnu.org>
> Date: Sun, 14 Mar 2021 08:29:59 +0100
>
> On Mär 14 2021, Eli Zaretskii via Gdb wrote:
>
> > Thanks. So does this mean we don't have any kind of "manual
> > demangler" in GDB that could be turned on in cases like this, when
> > "just works" doesn't? Hannes, any ideas?
>
> (gdb) help demangle
> Demangle a mangled name.
> Usage: demangle [-l LANGUAGE] [--] NAME
> If LANGUAGE is not specified, NAME is demangled in the current language.
Sure, I know. I thought there could be some "set FOO" knob that would
demangle automatically in the backtraces.
The above works, of course (one must use "-l c++", btw), but not if I
submit the "decorated" name, such as
"libgccjit-0!_Z17gimple_build_callP9tree_nodejz".
Thanks.
next prev parent reply other threads:[~2021-03-14 7:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 18:56 Eli Zaretskii
2021-03-13 8:55 ` Eli Zaretskii
2021-03-14 2:46 ` Simon Marchi
2021-03-14 5:45 ` Eli Zaretskii
2021-03-14 7:29 ` Andreas Schwab
2021-03-14 7:43 ` Eli Zaretskii [this message]
2021-03-14 8:09 ` Nagmat Nazarov
2021-03-14 7:28 ` Andreas Schwab
2021-03-14 7:36 ` Eli Zaretskii
2021-03-14 8:26 ` Andreas Schwab
2021-03-14 9:40 ` Eli Zaretskii
2021-03-14 7:54 ` Jeffrey Walton
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=83ft0ygoyi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=schwab@linux-m68k.org \
--cc=simon.marchi@polymtl.ca \
--cc=ssbssa@yahoo.de \
/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).