public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/18697] New: Demangler crash
@ 2015-07-20 16:31 hannes_weisbach at gmx dot net
2015-07-29 8:19 ` [Bug c++/18697] " qiyao at gcc dot gnu.org
0 siblings, 1 reply; 2+ messages in thread
From: hannes_weisbach at gmx dot net @ 2015-07-20 16:31 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug c++/18697] Demangler crash
2015-07-20 16:31 [Bug c++/18697] New: Demangler crash hannes_weisbach at gmx dot net
@ 2015-07-29 8:19 ` qiyao at gcc dot gnu.org
0 siblings, 0 replies; 2+ messages in thread
From: qiyao at gcc dot gnu.org @ 2015-07-29 8:19 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-07-29 8:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-20 16:31 [Bug c++/18697] New: Demangler crash hannes_weisbach at gmx dot net
2015-07-29 8:19 ` [Bug c++/18697] " qiyao at gcc dot gnu.org
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).