[valgrind] [Bug 359181] Buffer Overflow during Demangling

2016-09-13 Thread Mark Wielaard via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359181

Mark Wielaard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #3 from Mark Wielaard  ---
valgrind svn r15951

-- 
You are receiving this mail because:
You are watching all bug changes.


[valgrind] [Bug 359181] Buffer Overflow during Demangling

2016-09-10 Thread Mark Wielaard via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359181

Mark Wielaard  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Assignee|jsew...@acm.org |m...@redhat.com
 Status|UNCONFIRMED |ASSIGNED
 CC||m...@redhat.com

--- Comment #2 from Mark Wielaard  ---
Created attachment 101012
  --> https://bugs.kde.org/attachment.cgi?id=101012&action=edit
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).

-- 
You are receiving this mail because:
You are watching all bug changes.


[valgrind] [Bug 359181] Buffer Overflow during Demangling

2016-04-09 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359181

Ivo Raisr  changed:

   What|Removed |Added

 CC||iv...@ivosh.net

-- 
You are receiving this mail because:
You are watching all bug changes.


[valgrind] [Bug 359181] Buffer Overflow during Demangling

2016-02-10 Thread Florian Krohm via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359181

Florian Krohm  changed:

   What|Removed |Added

 CC||flor...@eich-krohm.de

--- Comment #1 from Florian Krohm  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.