This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/2 v2] Demangler crash handler
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gbenson at redhat dot com, gdb-patches at sourceware dot org, aburgess at broadcom dot com, xdje42 at gmail dot com, fw at deneb dot enyo dot de, mark dot kettenis at xs4all dot nl, tromey at redhat dot com
- Date: Tue, 20 May 2014 05:43:44 +0300
- Subject: Re: [PATCH 2/2 v2] Demangler crash handler
- Authentication-results: sourceware.org; auth=none
- References: <20140519114801 dot GA31140 at blade dot nx> <83iop1dd8e dot fsf at gnu dot org> <20140519154822 dot GA20315 at blade dot nx> <8361l1d7yx dot fsf at gnu dot org> <20140519190530 dot GA22506 at blade dot nx> <537A6C81 dot 5040203 at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Mon, 19 May 2014 21:41:37 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: gdb-patches@sourceware.org, aburgess@broadcom.com, xdje42@gmail.com,
> fw@deneb.enyo.de, mark.kettenis@xs4all.nl, tromey@redhat.com
>
> 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?
>
> Seems like a natural and easy sell to me.
Yes, I agree.