From: Florian Weimer <fw@deneb.enyo.de>
To: Pedro Alves <palves@redhat.com>
Cc: Gary Benson <gbenson@redhat.com>, Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org, aburgess@broadcom.com,
xdje42@gmail.com, mark.kettenis@xs4all.nl, tromey@redhat.com
Subject: Re: [PATCH 2/2 v2] Demangler crash handler
Date: Sun, 25 May 2014 12:59:00 -0000 [thread overview]
Message-ID: <871tvi6mlc.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <537A6C81.5040203@redhat.com> (Pedro Alves's message of "Mon, 19 May 2014 21:41:37 +0100")
* Pedro Alves:
> Wouldn't a new "set debug demangle on" option, that would make
> GDB output:
>
> (gdb) bt / whatever-gdb-command-that-triggers-demangling
> demangling _ZN2CV1mEi ... CV::m(int)
> demangling _Zwhatever ... <NULL>
>
> be just as helpful, and, even potentially be helpful to debug
> scenarios where GDB/libiberty might get the demangling wrong,
> but not cause a crash?
Here's another idea: You could strcpy the input string to a mapped
file (say, ~/.config/gdb/demangler) and read that on startup, printing
it and adding the offending symbol to a blacklist (say,
~/.config/gdb/demangler.blacklist).
prev parent reply other threads:[~2014-05-25 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 11:48 Gary Benson
2014-05-19 15:01 ` Eli Zaretskii
2014-05-19 15:48 ` Gary Benson
2014-05-19 16:55 ` Eli Zaretskii
2014-05-19 19:05 ` Gary Benson
2014-05-19 20:41 ` Pedro Alves
2014-05-20 2:43 ` Eli Zaretskii
2014-05-22 10:37 ` Gary Benson
2014-05-25 12:59 ` Florian Weimer [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=871tvi6mlc.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=aburgess@broadcom.com \
--cc=eliz@gnu.org \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=palves@redhat.com \
--cc=tromey@redhat.com \
--cc=xdje42@gmail.com \
/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