public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Nagmat Nazarov <nagmat@gmail.com>
To: Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: Demangling in backtraces
Date: Sun, 14 Mar 2021 17:09:42 +0900	[thread overview]
Message-ID: <CAJnvuZ_krNeoQSY55K3fBrKzBiRkVRib75mwqQZetmGmZPGNmQ@mail.gmail.com> (raw)
In-Reply-To: <83ft0ygoyi.fsf@gnu.org>

How to unsubscribe from gdb@sourceware.org ?

On Sun, Mar 14, 2021 at 5:04 PM Eli Zaretskii via Gdb <gdb@sourceware.org>
wrote:

> > 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.
>

  reply	other threads:[~2021-03-14  8:09 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 [this message]
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=CAJnvuZ_krNeoQSY55K3fBrKzBiRkVRib75mwqQZetmGmZPGNmQ@mail.gmail.com \
    --to=nagmat@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).