public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: gdb@sourceware.org
Subject: Re: Demangling in backtraces
Date: Sun, 14 Mar 2021 03:54:06 -0400	[thread overview]
Message-ID: <CAH8yC8nRcfNC2iOc+7s3yjX841LB+mSrL2A-S7ZBK6X9ntPTxg@mail.gmail.com> (raw)
In-Reply-To: <87h7le42jf.fsf@linux-m68k.org>

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

      parent reply	other threads:[~2021-03-14  7:54 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
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 [this message]

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=CAH8yC8nRcfNC2iOc+7s3yjX841LB+mSrL2A-S7ZBK6X9ntPTxg@mail.gmail.com \
    --to=noloader@gmail.com \
    --cc=gdb@sourceware.org \
    /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).