public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Demangling in backtraces
Date: Sun, 14 Mar 2021 09:26:02 +0100	[thread overview]
Message-ID: <874khe3zvp.fsf@linux-m68k.org> (raw)
In-Reply-To: <83h7legp9t.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 14 Mar 2021 09:36:46 +0200")

On Mär 14 2021, Eli Zaretskii wrote:

>> From: Andreas Schwab <schwab@linux-m68k.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>
>> Date: Sun, 14 Mar 2021 08:28:36 +0100
>> 
>> >  #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.
>
> No, that's the name of the shared library.  This is a known
> peculiarity on Windows, see "Non-debug DLL Symbols" in the GDB manual.

So it _is_ part of the symbol name?

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  reply	other threads:[~2021-03-14  8:26 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 [this message]
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=874khe3zvp.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=eliz@gnu.org \
    --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).