From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-15746-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 501 invoked by alias); 19 May 2014 12:53:08 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Received: (qmail 470 invoked by uid 48); 19 May 2014 12:53:08 -0000
From: "0xd34df00d at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/16957] gdb segfaults when loading symbols in C++11-enabled
 application
Date: Mon, 19 May 2014 12:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.7
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 0xd34df00d at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-16957-4717-BWuXQhp7Bt@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16957-4717@http.sourceware.org/bugzilla/>
References: <bug-16957-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q2/txt/msg00252.txt.bz2

https://sourceware.org/bugzilla/show_bug.cgi?id=16957

--- Comment #9 from Georg Rudoy <0xd34df00d at gmail dot com> ---
(In reply to Gary Benson from comment #8)
> Georg, alternatively can you supply more of the backtrace of a crash?  I
> need to see the mangled symbol name.  http://gbenson.net/?p=422 shows an
> example, frames 9-12 have the mangled symbol mangled=0x7ffffac19ea0
> "_Z1-Av23*;cG~Wo2Vu"

Thanks, that's much faster than rebuilding with a patch. The line in backtrace
containing d_demangle_callback:

#69765 0x000000000071e518 in d_demangle_callback (mangled=<optimized out>,
mangled@entry=0xe01eb4
"_Z7ZipWithI7QStringS0_5QListZN4oral6detail16AdaptCreateTableI7AccountEES0_RKNS3_16CachedFieldsDataEEUlRKS0_SA_E_ET1_IDTclfp1_cvT__EcvT0__EEEERKT1_ISC_ERKT1_ISD_ET2_",
options=259, callback=callback@entry=0x716e70
<d_growable_string_callback_adapter>, opaque=opaque@entry=0x7fffffffd550) at
./cp-demangle.c:5890

-- 
You are receiving this mail because:
You are on the CC list for the bug.