[Bug c++/87340] Stack overflow problem for c++filt

[msebor at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87340

Martin Sebor  changed:

   What|Removed |Added

 CC||msebor at gcc dot gnu.org

--- Comment #5 from Martin Sebor  ---
(In reply to Martin Liška from comment #3)
> Then it would deserve something like segfault-on-invalid-input :)
> Or should I use ice-on-invalid-code?

Let's use ice-on-invalid.  Otherwise the two will end up being used
interchangeably over time.

[Bug c++/87340] Stack overflow problem for c++filt

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87340

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2018-09-18
 Ever confirmed|0   |1

--- Comment #4 from Jonathan Wakely  ---
The __cxa_demangle function returns 2 for each of these testcases, but the
cplus_demangle function segfaults.

[Bug c++/87340] Stack overflow problem for c++filt

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87340

--- Comment #3 from Martin Liška  ---
Then it would deserve something like segfault-on-invalid-input :)
Or should I use ice-on-invalid-code?

[Bug c++/87340] Stack overflow problem for c++filt

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87340

--- Comment #2 from Jonathan Wakely  ---
No. None of them look valid.

[Bug c++/87340] Stack overflow problem for c++filt

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87340

Martin Liška  changed:

   What|Removed |Added

 CC||marxin at gcc dot gnu.org

--- Comment #1 from Martin Liška  ---
Is the input a valid C++ mangled name of not?