[Bug c++/19330] demangler failed with signal 11

["markus at trippelsdorf dot de" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19330

--- Comment #3 from Markus Trippelsdorf <markus at trippelsdorf dot de> ---
(In reply to Pedro Alves from comment #2)
> 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_pr
> oxyEE9invoke_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_p
> roxyEE9invoke_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?

I don't think so. However no other demangler that I've tested handles this
symbol at the moment.
The source code to produce it would be interesting.

-- 
You are receiving this mail because:
You are on the CC list for the bug.