This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/18697] New: Demangler crash
- From: "hannes_weisbach at gmx dot net" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 20 Jul 2015 16:31:45 +0000
- Subject: [Bug c++/18697] New: Demangler crash
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18697
Bug ID: 18697
Summary: Demangler crash
Product: gdb
Version: 7.9
Status: NEW
Severity: normal
Priority: P2
Component: c++
Assignee: unassigned at sourceware dot org
Reporter: hannes_weisbach at gmx dot net
Target Milestone: ---
After experiencing segfaults on loading symbols from an executable with
gdb-7.7, I compiled gdb-7.9, which gave me the following message:
Reading symbols from ./intex/experiment...../../gdb/cp-support.c:1583:
demangler-warning: unable to demangle
'_ZN2kjmlIixNS_1_15NanosecondLabelEEENS_8QuantityIDTmlcvT_Li1EcvT0_Li1EET1_EES4_NS3_IS5_S7_EE'
(demangler failed with signal 11)
Unable to dump core, use `ulimit -c unlimited' before executing GDB next time.
../../gdb/cp-support.c:1596: demangler-warning: unable to demangle
'_ZN2kjmlIixNS_1_15NanosecondLabelEEENS_8QuantityIDTmlcvT_Li1EcvT0_Li1EET1_EES4_NS3_IS5_S7_EE'
(demangler failed with signal 11)
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n
This seems similar and/or related to bugs 16944, 17066, and 17513.
I'm running Linux 3.18.14 on armv7l, if that's somehow relevant.
Let me know, if you require more information (I'm not sure what else to
provide; I don't have the time to provide a minimal test case.).
--
You are receiving this mail because:
You are on the CC list for the bug.