On Fri, Jan 08, 2016 at 01:31:48PM +1100, Martin Schwenke wrote: > Package: valgrind > Version: 1:3.11.0-1 > Severity: important > > When I run valgrind against anything, I see warnings like this: > > $ valgrind -q /bin/echo > --14923-- WARNING: Serious error when reading debug info > --14923-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.21.so: > --14923-- Ignoring non-Dwarf2/3/4 block in .debug_info > --14923-- WARNING: Serious error when reading debug info > --14923-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.21.so: > --14923-- Last block truncated in .debug_info; ignoring > --14923-- WARNING: Serious error when reading debug info > --14923-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.21.so: > --14923-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 > --14923-- WARNING: Serious error when reading debug info > --14923-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.21.so: > --14923-- Ignoring non-Dwarf2/3/4 block in .debug_info > --14923-- WARNING: Serious error when reading debug info > --14923-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.21.so: > --14923-- Last block truncated in .debug_info; ignoring > --14923-- WARNING: Serious error when reading debug info > --14923-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.21.so: > --14923-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 > > This might not actually be a valgrind bug... > > $ dwarfdump -i > /usr/lib/debug/.build-id/1c/3104f034cf1caf07cdc1c4a5f342610146ebe5.debug > > .debug_info > dwarfdump ERROR: attempting to print .debug_info: DW_DLE_CU_LENGTH_ERROR > (47) (47) > attempting to continue. > > $ dpkg -S > /usr/lib/debug/.build-id/1c/3104f034cf1caf07cdc1c4a5f342610146ebe5.debug > libc6-dbg:amd64: > /usr/lib/debug/.build-id/1c/3104f034cf1caf07cdc1c4a5f342610146ebe5.debug > > So it might be a libc6 bug. > > However, I'm only seeing it causes problems in valgrind so, I guess, > this seems a good place to start... :-)
I think this may be related to https://bugs.debian.org/780173. The glibc package recently enabled compressed debug symbols but valgrind doesn't support them yet. Though I'm not sure what would be a good way to verify this. As for solutions, we can wait for valgrind to add support for compressed symbols or ask the glibc maintainers to not compress debug symbols. Either way there's not much I, as maintainer of valgrind, can do about this. Cheers
signature.asc
Description: PGP signature
