This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug demangler/81684] Out of Memory in demangler
- From: "trippels at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 03 Aug 2017 07:18:30 +0000
- Subject: [Bug demangler/81684] Out of Memory in demangler
- Auto-submitted: auto-generated
- References: <bug-81684-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81684
Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-08-03
CC| |trippels at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Confirmed:
~ % c++filt __H9999999999_
c++filt: out of memory allocating 11280523256 bytes after a total of 135168
bytes
Currently the demangler is not in shape for fuzzing. For example, it contains
several quadratic algorithms, see e.g. PR80002.
Also I'm not sure if fixing all small memory leaks is really worth the effort.