Assignee: unassigned at gcc dot gnu.org
Reporter: mudongliangabcd at gmail dot com
Target Milestone: ---
Created attachment 43887
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43887&action=edit
PoC to trigger segment fault
We found one segment fault in C++ Demangle Functions. F
Priority: P3
Component: demangler
Assignee: unassigned at gcc dot gnu.org
Reporter: mudongliangabcd at gmail dot com
Target Milestone: ---
Created attachment 43799
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43799&action=edit
Dockerfile for Debian
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85122
--- Comment #1 from 慕冬亮 ---
Created attachment 43800
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43800&action=edit
PoC to trigger stack exhaustion
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85122
--- Comment #2 from 慕冬亮 ---
Created attachment 43801
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43801&action=edit
Dockerfile for Debian Stable (GCC with AddressSanitizer)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85122
--- Comment #3 from 慕冬亮 ---
At first, I reported it in bugzilla of
binutils(https://sourceware.org/bugzilla/show_bug.cgi?id=23008). The developer
said it should be the issue of C++ demangle code and GCC maintains this
component. He advised me to