Demangling in backtraces
Jeffrey Walton
noloader@gmail.com
Sun Mar 14 07:54:06 GMT 2021
On Sun, Mar 14, 2021 at 3:48 AM Andreas Schwab <schwab@linux-m68k.org> wrote:
>
> On Mär 06 2021, Eli Zaretskii via Gdb wrote:
>
> > I have built a C program linked against libgccjit. When it crashes,
> > the backtrace shows mangled names, like this:
> >
> > #0 0x70f5ac3e in libgccjit-0!_Z17gimple_build_callP9tree_nodejz ()
>
> Is this prefix part of the symbol name? A valid mangled name must start
> with _Z.
It looks like the prefix 'libgccjit-0!' is causing trouble:
$ echo '_Z17gimple_build_callP9tree_nodejz' | c++filt
gimple_build_call(tree_node*, unsigned int, ...)
$ echo 'libgccjit-0!_Z17gimple_build_callP9tree_nodejz'
libgccjit-0!_Z17gimple_build_callP9tree_nodejz
Jeff
More information about the Gdb
mailing list