it has been more than 2 years since I had submitted this bug (it is not a bug, it is a feature). Ubuntu when somebody installs valgrind automatically installs the glibc6 and glibc6-dbg. On Sabayon however this doesn't happen and so:
$ aptitude show valgrind
Automatically installed: no
Maintainer: Ubuntu MOTU Developers <email@example.com>
Uncompressed Size: 164 M
Depends: libc6 (>= 2.3.4), libc6-dbg
Suggests: kcachegrind, alleyoop, valkyrie (> 1.3.0)
Conflicts: valgrind-callgrind, valgrind-callgrind, valgrind
Description: A memory debugger and profiler
Valgrind is a GPL'd tool to help you find memory-management problems in your programs. When a program is
run under Valgrind's supervision, all reads and writes of memory are checked, and calls to
malloc/new/free/delete are intercepted.
Valgrind can debug more or less any dynamically-linked ELF x86/Linux, amd64/Linux and ppc/Linux
executables, without modification, recompilation, or anything.
Valgrind provides a generic infrastructure for supervising the execution of programs called "tools". This
is done by providing a way to instrument programs in very precise ways, making it relatively easy to
support activities such as dynamic error detection and profiling. The Valgrind distribution currently
includes three tools: a memory error detectors, a cache (time) profiler and a heap (space) profiler.
However in Sabayon ...
- Code: Select all
$ valgrind ls
==30502== Memcheck, a memory error detector
==30502== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==30502== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==30502== Command: ls
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: A must-be-redirected function
valgrind: whose name matches the pattern: strlen
valgrind: in an object with soname matching: ld-linux-x86-64.so.2
valgrind: was not found whilst processing
valgrind: symbols from the object with soname: ld-linux-x86-64.so.2
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.
valgrind: Cannot continue -- exiting now. Sorry.
Could you please include the debug-info for glibc6 in the entropy and have it being installed as a dependency of valgrind?
[Edit by micia 16-oct-2011] adding code tags around command output, please use code tags for long outputs to make your post more readable.