This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/18697] Demangler crash
- From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 29 Jul 2015 08:19:12 +0000
- Subject: [Bug c++/18697] Demangler crash
- Auto-submitted: auto-generated
- References: <bug-18697-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18697
Yao Qi <qiyao at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |qiyao at gcc dot gnu.org
--- Comment #1 from Yao Qi <qiyao at gcc dot gnu.org> ---
I can reproduce this bug on FSF trunk by the following small c code
void
_ZN2kjmlIixNS_1_15NanosecondLabelEEENS_8QuantityIDTmlcvT_Li1EcvT0_Li1EET1_EES4_NS3_IS5_S7_EE
()
{}
int main (void)
{
return 0;
}
$ gcc /tmp/2.c -o /tmp/2.exe
$ ./gdb /tmp/2.exe
.....
Reading symbols from
/tmp/2.exe.../home/yao/SourceCode/gnu/gdb/git/gdb/cp-support.c:1595:
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.
/home/yao/SourceCode/gnu/gdb/git/gdb/cp-support.c:1608: 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)
--
You are receiving this mail because:
You are on the CC list for the bug.