From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eliz@gnu.org>
Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10])
 by sourceware.org (Postfix) with ESMTPS id D09E63896C0B
 for <gdb@sourceware.org>; Sat, 13 Mar 2021 08:55:41 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D09E63896C0B
Received: from fencepost.gnu.org ([2001:470:142:3::e]:59854)
 by eggs.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <eliz@gnu.org>) id 1lL03h-0001Vi-5j
 for gdb@sourceware.org; Sat, 13 Mar 2021 03:55:41 -0500
Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3342
 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@gnu.org>) id 1lL03g-0003es-60
 for gdb@sourceware.org; Sat, 13 Mar 2021 03:55:40 -0500
Date: Sat, 13 Mar 2021 10:55:47 +0200
Message-Id: <8335wzjuuk.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
In-Reply-To: <83h7loun5e.fsf@gnu.org> (message from Eli Zaretskii via Gdb on
 Sat, 06 Mar 2021 20:56:13 +0200)
Subject: Re: Demangling in backtraces
References: <83h7loun5e.fsf@gnu.org>
X-Spam-Status: No, score=1.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: gdb@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb mailing list <gdb.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb>,
 <mailto:gdb-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb>,
 <mailto:gdb-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2021 08:55:42 -0000

Ping!  Does the silence mean we don't have such a feature in GDB?

> Date: Sat, 06 Mar 2021 20:56:13 +0200
> From: Eli Zaretskii via Gdb <gdb@sourceware.org>
> 
> I have built a C program linked against libgccjit.  When it crashes,
> the backtrace shows mangled names, like this:
> 
>  #0  0x70f5ac3e in libgccjit-0!_Z17gimple_build_callP9tree_nodejz ()
>     from D:\usr\bin\libgccjit-0.dll
>  #1  0x7190fa7b in libgccjit-0!_ZN19evrp_range_analyzer5leaveEP15basic_block_def
>  () from D:\usr\bin\libgccjit-0.dll
>  #2  0x71910eef in libgccjit-0!_Z36stmt_uses_0_or_null_in_undefined_wayP6gimple
>      () from D:\usr\bin\libgccjit-0.dll
>  #3  0x710fba2c in libgccjit-0!_Z16execute_one_passP8opt_pass ()
>     from D:\usr\bin\libgccjit-0.dll
> 
> (This is because libgccjit is written in C++, and because the DLL is
> stripped.)
> 
> How can I cause GDB to demangle the function names when showing the
> backtrace in this case?  I tried setting language to c++, but that
> didn't help.
> 
> TIA
>