Re: Demangling in backtraces
Nagmat Nazarov via Gdb <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <CAJnvuZ_krNeoQSY55K3fBrKzBiRkVRib75mwqQZetmGmZPGNmQ@mail.gmail.com> |
How to unsubscribe from [email protected] ? On Sun, Mar 14, 2021 at 5:04 PM Eli Zaretskii via Gdb <[email protected]> wrote: > > From: Andreas Schwab <[email protected]> > > Cc: Simon Marchi <[email protected]>, Hannes Domani > > <[email protected]>, Eli Zaretskii <[email protected]> > > 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. >