public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-16957-4717-BWuXQhp7Bt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16957-4717@http.sourceware.org/bugzilla/>
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.
next prev parent reply other threads:[~2014-05-19 12:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 17:49 [Bug c++/16957] New: " 0xd34df00d at gmail dot com
2014-05-17 19:09 ` [Bug c++/16957] " 0xd34df00d at gmail dot com
2014-05-17 19:21 ` keiths at redhat dot com
2014-05-17 19:24 ` 0xd34df00d at gmail dot com
2014-05-17 19:27 ` keiths at redhat dot com
2014-05-17 20:01 ` 0xd34df00d at gmail dot com
2014-05-19 9:41 ` gbenson at redhat dot com
2014-05-19 9:43 ` gbenson at redhat dot com
2014-05-19 12:53 ` 0xd34df00d at gmail dot com [this message]
2014-05-19 14:04 ` gbenson at redhat dot com
2014-05-27 12:10 ` palves at redhat dot com
2021-10-21 6:49 ` bap.fayol at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-16957-4717-BWuXQhp7Bt@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).