https://bugs.kde.org/show_bug.cgi?id=445916
--- Comment #3 from Mark Wielaard <m...@klomp.org> ---
(In reply to Nick Nethercote from comment #1)
> AFAIK Valgrind uses the libiberty demangler. How does that work? Is there
> scope for a Valgrind-specific fix, or would it be better to get the suffix
> trimmed in libiberty and then import updated code into Valgrind?
Best would be to fix it in libiberty (part of gcc). Then it also gets picked up
by binutils/c++filt, gdb, perf, etc.
For valgrind we have the ./auxprogs/update-demangler script to help import a
new version.
See comments at the top of the file how to run it (and which vars/refs to
tweak).
Last libiberty demangler update was:
commit a3d42a88a6ad7bdca47b4553cfa7a7a058aac186
Author: Mark Wielaard <m...@klomp.org>
Date: Sun Sep 26 14:47:17 2021 +0200
Update libiberty demangler
Update the libiberty demangler using the auxprogs/update-demangler
script to gcc git commit b3585c0836e729bed56b9afd4292177673a25ca0.
This update includes:
- prevent null dereferencing on dlang_type
- prevent buffer overflow when decoding user input
- Add support for demangling local D template declarations
- Add support for demangling D function literals as template
value parameters
- Add support for D `typeof(*null)' types
- Fix -Wundef warnings in ansidecl.h
- Fix endian bug in rust demangler
- Adjust mangling of __alignof__
- Avoid -Wstringop-truncation
--
You are receiving this mail because:
You are watching all bug changes.
