This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/70909] Libiberty Demangler segfaults (4)
- From: "mark at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 19 Nov 2016 18:43:26 +0000
- Subject: [Bug c++/70909] Libiberty Demangler segfaults (4)
- Auto-submitted: auto-generated
- References: <bug-70909-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70909
--- Comment #11 from Mark Wielaard <mark at gcc dot gnu.org> ---
(In reply to Markus Trippelsdorf from comment #10)
> The symbol was demangled with libcxxabi's demangler.
> The other two demanglers reject it.
Thanks. Do you know which demangler is correct for this input string?
The question is whether this symbol was incorrectly generated. If so then
rejecting it is it the right thing to do. If it is correct then there is still
the question whether the produced output is correct. Which is slightly hard
given how big this input/output pair is.
Does anybody have a smaller (valid) reproducer?