From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21514 invoked by alias); 20 May 2014 02:43:46 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 21491 invoked by uid 89); 20 May 2014 02:43:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout22.012.net.il Received: from mtaout22.012.net.il (HELO mtaout22.012.net.il) (80.179.55.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 20 May 2014 02:43:41 +0000 Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0N5U00D00POBN400@a-mtaout22.012.net.il> for gdb-patches@sourceware.org; Tue, 20 May 2014 05:43:38 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N5U00DADQ8PGM60@a-mtaout22.012.net.il>; Tue, 20 May 2014 05:43:38 +0300 (IDT) Date: Tue, 20 May 2014 02:43:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH 2/2 v2] Demangler crash handler In-reply-to: <537A6C81.5040203@redhat.com> To: Pedro Alves Cc: gbenson@redhat.com, gdb-patches@sourceware.org, aburgess@broadcom.com, xdje42@gmail.com, fw@deneb.enyo.de, mark.kettenis@xs4all.nl, tromey@redhat.com Reply-to: Eli Zaretskii Message-id: <83lhtxb25b.fsf@gnu.org> References: <20140519114801.GA31140@blade.nx> <83iop1dd8e.fsf@gnu.org> <20140519154822.GA20315@blade.nx> <8361l1d7yx.fsf@gnu.org> <20140519190530.GA22506@blade.nx> <537A6C81.5040203@redhat.com> X-IsSubscribed: yes X-SW-Source: 2014-05/txt/msg00396.txt.bz2 > Date: Mon, 19 May 2014 21:41:37 +0100 > From: Pedro Alves > 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 ... > > 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.