https://sourceware.org/bugzilla/show_bug.cgi?id=19571
Gaurav Gupta changed:
What|Removed |Added
CC||g.gupta at samsung dot com
--- Comment
https://sourceware.org/bugzilla/show_bug.cgi?id=19571
Markus Trippelsdorf changed:
What|Removed |Added
URL||https://gcc.gnu.org/bugzill
https://sourceware.org/bugzilla/show_bug.cgi?id=19571
--- Comment #5 from Nick Clifton ---
Hi Markus,
> I don't think it makes any sense to fuzz the demangler with arbitrary binary
> files.
The tools (nm, objdump) should be able to cope though. When I tried running nm
for example I received th
https://sourceware.org/bugzilla/show_bug.cgi?id=19571
Markus Trippelsdorf changed:
What|Removed |Added
CC||markus at trippelsdorf dot de
-
https://sourceware.org/bugzilla/show_bug.cgi?id=19571
--- Comment #3 from Marcel Böhme ---
Hi Nick,
Sure. I'll send the bug report to the gcc bugzilla.
The bug can be triggered with:
objdump -x -C
nm -C
I detected the bug with a modified version of the AFL Fuzzer w/out
sanitization.
--
You
https://sourceware.org/bugzilla/show_bug.cgi?id=19571
Nick Clifton changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://sourceware.org/bugzilla/show_bug.cgi?id=19571
--- Comment #1 from Marcel Böhme ---
Created attachment 8957
--> https://sourceware.org/bugzilla/attachment.cgi?id=8957&action=edit
Test Case #2
--
You are receiving this mail because:
You are on the CC list for the bug.
__
