https://sourceware.org/bugzilla/show_bug.cgi?id=25180
--- Comment #2 from Tim Rühsen <tim.ruehsen at gmx dot de> --- Hi Nick, no mystery. But a possible DoS vector and in the end just an example that demangling may take longer as expected (and possibly necessary). Smaller and 'real-world' input may have the same issue just on a much smaller scale - so I wonder if this an 'easy-to-fix' code flaw or an 'fixed' design (flaw). Such a CPU hog also prevents proper fuzzing, thus it prevents finding other bugs. You sound like this is a well-known behavior of the demangler and nothing can be done. If that is the case, then sorry for not knowing. Feel free to close the issue :-) -- You are receiving this mail because: You are on the CC list for the bug.
