From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11865 invoked by alias); 25 May 2014 12:59:24 -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 11847 invoked by uid 89); 25 May 2014 12:59:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: albireo.enyo.de Received: from albireo.enyo.de (HELO albireo.enyo.de) (46.237.207.196) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Sun, 25 May 2014 12:59:20 +0000 Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) id 1WoY1A-00086k-6a; Sun, 25 May 2014 14:59:12 +0200 Received: from fw by deneb.enyo.de with local (Exim 4.80) (envelope-from ) id 1WoY1A-0004UG-01; Sun, 25 May 2014 14:59:12 +0200 From: Florian Weimer To: Pedro Alves Cc: Gary Benson , Eli Zaretskii , 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 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> Date: Sun, 25 May 2014 12:59:00 -0000 In-Reply-To: <537A6C81.5040203@redhat.com> (Pedro Alves's message of "Mon, 19 May 2014 21:41:37 +0100") Message-ID: <871tvi6mlc.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes X-SW-Source: 2014-05/txt/msg00619.txt.bz2 * 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 ... > > 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).