|
From: Michael R. H. <ma...@us...> - 2013-05-13 13:34:09
|
Hello I am running Precise Puppy 5.4.2, which is built from Ubuntu Precise Pangolin 12.04.1+ binary DEB packages, hence has binary compatibility with Ubuntu and access to the vast Ubuntu package repository. I have installed the Valgrind 3.7.0 package together with the libc6-dbg package from the Ubuntu package repository. I ran the command: valgrind -v ls -l and I get: ==20396== Memcheck, a memory error detector ==20396== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==20396== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==20396== Command: ls -l ==20396== --20396-- Valgrind options: --20396-- --suppressions=/usr/lib/valgrind/debian-libc6-dbg.supp --20396-- -v --20396-- Contents of /proc/version: --20396-- Linux version 3.2.29 (root@puppypc6993) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #1 SMP Thu Sep 13 20:33:02 GMT-8 2012 --20396-- Arch and hwcaps: X86, x86-sse1-sse2 --20396-- Page sizes: currently 4096, max supported 4096 --20396-- Valgrind library directory: /usr/lib/valgrind --20396-- Reading syms from /lib/ld-2.15.so (0x4000000) --20396-- Considering /lib/ld-2.15.so .. --20396-- .. CRC mismatch (computed 405891ab wanted 9a1d2f37) --20396-- object doesn't have a symbol table valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind: On Debian, Ubuntu: libc6-dbg valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Cannot continue -- exiting now. Sorry. The filepath to the debug symbols installed by the 'libc6-dbg' package: /usr/lib/debug/lib/i386-linux-gnu Can anyone explain why Valgrind is not finding the debug symbols? TIA Michael |