[BUG] Crash when demangling with libiberty
Hi, I have been given these e-mail addresses by Nick Clifton after reporting a bug on binutils here: https://sourceware.org/bugzilla/show_bug.cgi?id=19877 . The bug is in libiberty, according to him. The bug boils down to this command (and objdump, and lldb) crashing: c++filt _ZSt4moveIRZN11tconcurrent6futureIvE4thenIZ5awaitIS2_EDaOT_EUlRKS6_E_EENS1_INSt5decayIDTclfp_defpTEEE4typeEEES7_EUlvE_EONSt16remove_referenceIS6_E4typeES7_ I'm using c++filt from binutils 2.26 and have gcc 5.3.1-8 on a debian unstable if it is of any matter. Cheers, Philippe
Re: [BUG] Crash when demangling with libiberty
Filed here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70517 On 2016-03-31 15:52, Ian Lance Taylor wrote: Philippe Daouadi writes: I have been given these e-mail addresses by Nick Clifton after reporting a bug on binutils here: https://sourceware.org/bugzilla/show_bug.cgi?id=19877 . The bug is in libiberty, according to him. The bug boils down to this command (and objdump, and lldb) crashing: c++filt _ZSt4moveIRZN11tconcurrent6futureIvE4thenIZ5awaitIS2_EDaOT_EUlRKS6_E_EENS1_INSt5decayIDTclfp_defpTEEE4typeEEES7_EUlvE_EONSt16remove_referenceIS6_E4typeES7_ I'm using c++filt from binutils 2.26 and have gcc 5.3.1-8 on a debian unstable if it is of any matter. Please refile your bug report at https://gcc.gnu.org/bugzilla . If at all possible, please include the preprocessed source code that produces the symbol (you can get this by passing the --save-temps option to the compiler; we want the .ii file) and please include complete details on the compiler that produced the symbol. Thanks. Ian
