Package: valgrind Version: 1:3.19.0-1 Severity: normal Dear Maintainer,
trying to use valgrind on programs that contain DWARF5 debuginfo leads to an error message: ==92495== Valgrind: debuginfo reader: Possibly corrupted debuginfo file. ==92495== Valgrind: I can't recover. Giving up. Sorry. This is a problem, since e.g. for over a year now, more and more Rust programs contain DWARF5 debuginfo (see <https://github.com/rust-lang/rust/issues/98746>). They all cannot be debugged or profiled with valgrind. Reportedly, valgrind 3.20 improves the situation greatly, but unfortunately that only has an experimental package available right now. Kind regards, Ralf -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-2-amd64 (SMP w/20 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages valgrind depends on: ii libc6 2.37-7 ii libc6-dbg 2.37-7 Versions of packages valgrind recommends: ii gdb 13.2-1 ii valgrind-dbg 1:3.19.0-1 Versions of packages valgrind suggests: pn alleyoop <none> pn kcachegrind <none> pn valgrind-mpi <none> pn valkyrie <none> -- no debconf information
