Summary: | Buffer Overflow during Demangling | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Marcel Böhme <boehme.marcel> |
Component: | general | Assignee: | Mark Wielaard <mark> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | flo2030, ivosh, mark |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | All | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Update libiberty demangler |
Description
Marcel Böhme
2016-02-09 12:16:39 UTC
Thanks for letting us know. We'll watch upstream as the bug is in their shop. We just pull in the code from the GCC demangler. I believe that upstream is actually binutils rather than gcc as the demangling code is part of libiberty. If you don't get any response from gcc you might want to raise the bug there. BTW: the c++filt tool (part of binutils) has the same issue. Created attachment 101012 [details]
Update libiberty demangler
This particular bug (and many more issues) has been fixed upstream now.
Update the libiberty demangler using the auxprogs/update-demangler
script. There were various extensions and bug fixes since our last
import. Add new D language demangler file d-demangle.c and update
the vg_libciface.h header with some new constructs used (strtol,
xmalloc_failed, xmemdup, XDELETEVEC, XDUPVEC).
valgrind svn r15951 |