https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99763
--- Comment #8 from Ba Jinsheng ---
(In reply to Martin Liška from comment #7)
> > I got this payload by fuzzing.
>
> I see. It's unlikely we'll fix such cases, the name is complete garbage.
Even it is an invalid symbol, the c++filt will crash.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99763
Martin Liška changed:
What|Removed |Added
Status|WAITING |NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99763
Martin Liška changed:
What|Removed |Added
Keywords||ice-on-invalid-code
--- Comment #7 from M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99763
--- Comment #6 from Ba Jinsheng ---
(In reply to Martin Liška from comment #5)
> (In reply to Ba Jinsheng from comment #3)
> > Created attachment 50471 [details]
> > the payload to trigger the crash
>
> Is it a valid symbol name? How did you com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99763
--- Comment #5 from Martin Liška ---
(In reply to Ba Jinsheng from comment #3)
> Created attachment 50471 [details]
> the payload to trigger the crash
Is it a valid symbol name? How did you come up with the name?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99763
--- Comment #4 from Ba Jinsheng ---
(In reply to Martin Liška from comment #2)
> We likely miss the payload, right?
Uploaded
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99763
--- Comment #3 from Ba Jinsheng ---
Created attachment 50471
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50471&action=edit
the payload to trigger the crash
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99763
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2021-03-25
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99763
--- Comment #1 from Ba Jinsheng ---
*** Bug 99762 has been marked as a duplicate of this bug. ***
