This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/19330] demangler failed with signal 11
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 09 Aug 2016 13:32:31 +0000
- Subject: [Bug c++/19330] demangler failed with signal 11
- Auto-submitted: auto-generated
- References: <bug-19330-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19330
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #2 from Pedro Alves <palves at redhat dot com> ---
Still crashes with 7.12.50.20160809-git.
(In reply to Tomasz Grabiec from comment #0)
> I can provide the core dump on request.
All we need is the demangled name, which you're already provided:
$ gdb -ex "demangle -l c++
_ZN8futurizeI13frozen_schemaE5applyIRZN7seastar7shardedIN7service13storage_proxyEE9invoke_onIZZNS6_22init_messaging_serviceEvENKUljN5utils4UUIDEE8_clEjSA_EUlOT_E_6futureIJS0_EEEET0_jSD_EUlvE_JEEESG_SD_DpOT0_"
GNU gdb (GDB) 7.12.50.20160809-git
[...]
/home/pedro/gdb/mygit/src/gdb/cp-support.c:1600: demangler-warning: unable to
demangle
'_ZN8futurizeI13frozen_schemaE5applyIRZN7seastar7shardedIN7service13storage_proxyEE9invoke_onIZZNS6_22init_messaging_serviceEvENKUljN5utils4UUIDEE8_clEjSA_EUlOT_E_6futureIJS0_EEEET0_jSD_EUlvE_JEEESG_SD_DpOT0_'
(demangler failed with signal 11)
Attempting to dump core.
(In reply to Markus Trippelsdorf from comment #1)
> You should report this issue on the gcc bugzilla, because libiberty
> (demangler) is maintained there.
Was this ever reported to gcc?
--
You are receiving this mail because:
You are on the CC list for the bug.