Package: valgrind Version: 1:3.6.1-5 Severity: grave Justification: renders package unusable
Since upgrading just now to all the latest packages in unstable, running valgrind on any program (such as /bin/ls) results in the following error: derick@whisky:~/dev$ valgrind /bin/ls ==6707== Memcheck, a memory error detector ==6707== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==6707== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info ==6707== Command: /bin/ls ==6707== --6707-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x2a valgrind: m_debuginfo/readdwarf.c:2338 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed. ==6707== at 0x3802CFF6: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x3802D19C: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x3809CBFC: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x3809DC5F: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x3809E801: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x380A1C34: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x380596A8: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x38052F21: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x3806C6D0: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x38093B39: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x38069107: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x38065FBC: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x38067169: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==6707== by 0x38076C04: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==6707== at 0x4015F3A: mmap (syscall-template.S:82) ==6707== by 0x40064B7: _dl_map_object_from_fd (dl-load.c:1240) ==6707== by 0x40076B7: _dl_map_object (dl-load.c:2250) ==6707== by 0x400CF41: openaux (dl-deps.c:65) ==6707== by 0x400D905: _dl_catch_error (dl-error.c:178) ==6707== by 0x400C02B: _dl_map_object_deps (dl-deps.c:247) ==6707== by 0x40032B6: dl_main (rtld.c:1814) ==6707== by 0x40148FD: _dl_sysdep_start (dl-sysdep.c:244) ==6707== by 0x4001422: _dl_start (rtld.c:341) ==6707== by 0x4000AF7: ??? (in /lib/x86_64-linux-gnu/ld-2.13.so) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages valgrind depends on: ii libc6 2.13-9 Embedded GNU C Library: Shared lib ii libc6-dbg 2.13-9 Embedded GNU C Library: detached d Versions of packages valgrind recommends: ii gdb 7.2-1 The GNU Debugger Versions of packages valgrind suggests: pn alleyoop <none> (no description available) ii kcachegrind 4:4.6.3-1 visualisation tool for the Valgrin pn valkyrie <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
