Priority: P3
Component: demangler
Assignee: unassigned at gcc dot gnu.org
Reporter: featherrain26 at gmail dot com
Target Milestone: ---
Created attachment 50107
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50107&action=edit
POC
Hi, there.
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91128
--- Comment #3 from Shadow HUANG ---
(In reply to Martin Liška from comment #1)
> How did you create the 'input' binary?
I use my fuzzer to create it. It is a new hybrid fuzzing techniques.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91128
--- Comment #2 from Shadow HUANG ---
I just download the binutils from the website and use the compilation procedure
mentioned to create the binary.
Component: demangler
Assignee: unassigned at gcc dot gnu.org
Reporter: featherrain26 at gmail dot com
Target Milestone: ---
Created attachment 50085
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50085&action=edit
POC
Hi, there.
There is a stack overflow in the newest
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: featherrain26 at gmail dot com
Target Milestone: ---
Created attachment 50084
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50084&action=edit
POC
Hi, there.
There is a stack o
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: featherrain26 at gmail dot com
Target Milestone: ---
Created attachment 50083
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50083&action=edit
POC
Hi, there.
There is
Priority: P3
Component: demangler
Assignee: unassigned at gcc dot gnu.org
Reporter: featherrain26 at gmail dot com
Target Milestone: ---
Created attachment 50082
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50082&action=edit
POC
Hi, there.
There is
: c
Assignee: unassigned at gcc dot gnu.org
Reporter: featherrain26 at gmail dot com
Target Milestone: ---
Created attachment 46582
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46582&action=edit
Poc input
Reference link:
https://sourceware.org/bugzilla/show_bug