[Bug demangler/78944] null pointer in demangler

2017-03-09 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78944 Markus Trippelsdorf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug demangler/78944] null pointer in demangler

2017-01-11 Thread vanyacpp at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78944 --- Comment #3 from Ivan Sorokin --- I retested these cases on a more recent version of binutils 2.27. It turned out that the first three cases are fixed. The last one still causes a crash. Here is a more simple reprocase: $ c++filt

[Bug demangler/78944] null pointer in demangler

2017-01-03 Thread vanyacpp at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78944 --- Comment #2 from Ivan Sorokin --- Another very rare crash discovered by my fuzzer: _Z1fAqu4SmFG1n3_a.

[Bug demangler/78944] null pointer in demangler

2016-12-29 Thread vanyacpp at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78944 --- Comment #1 from Ivan Sorokin --- In addition to the reported crash on _Z3fooAv32pM, there are two other seeming unrelated crashes: _Z1f7729646840 and _Z1fDpDF02s4o.