Valgrind is unable to get its complete list of function pointers and cannot continue Reproducible: Always Steps to Reproduce: 1. run valgrind on an executable 2. valgrind dies with error 3. ? 4. Profit! Actual Results: ==21049== Memcheck, a memory error detector ==21049== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==21049== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info ==21049== Command: ./application ==21049== 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: index 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. It appears there are certain symbols missing from the aforementioned shared library. I tried rebuilding glibc with the debug USE flag but it doesn't change anything
*** This bug has been marked as a duplicate of bug 214065 ***
