Hi all,
the glibc was recently updated for 11.2. The problem is that now valgrind won’t work anymore due to missing symbols.
>uname -a
Linux linux-9b84 2.6.31.14-0.4-desktop #1 SMP PREEMPT 2010-10-25 08:45:30 +0200 x86_64 x86_64 x86_64 GNU/Linux
> valgrind …/…/…/…/…/…/…/main_bin/main
==9753== Memcheck, a memory error detector
==9753== Copyright (C) 2002-2009, and GNU GPL’d, by Julian Seward et al.
==9753== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==9753== Command: …/…/…/…/…/…/…/main_bin/main
==9753==
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-x86-64.so.2
valgrind: was not found whilst processing
valgrind: symbols from the object with soname: ld-linux-x86-64.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.
valgrind:
valgrind: Cannot continue – exiting now. Sorry.
I have glibc debuginfo installed:
rpm -qa|grep glibc
glibc-i18ndata-2.10.1-10.9.1.x86_64
glibc-info-2.10.1-10.9.1.x86_64
glibc-locale-32bit-2.10.1-10.9.1.x86_64
glibc-devel-debuginfo-32bit-2.10.1-10.4.x86_64
glibc-debuginfo-2.10.1-10.4.x86_64
glibc-profile-32bit-2.10.1-10.9.1.x86_64
glibc-32bit-2.10.1-10.9.1.x86_64
glibc-profile-2.10.1-10.9.1.x86_64
glibc-devel-32bit-2.10.1-10.9.1.x86_64
glibc-devel-debuginfo-2.10.1-10.4.x86_64
glibc-2.10.1-10.9.1.x86_64
glibc-obsolete-2.10.1-10.9.1.x86_64
glibc-locale-2.10.1-10.9.1.x86_64
glibc-debuginfo-32bit-2.10.1-10.4.x86_64
glibc-obsolete-debuginfo-2.10.1-10.4.i586
glibc-devel-2.10.1-10.9.1.x86_64
glibc-locale-debuginfo-2.10.1-10.4.x86_64
So - where is the problem? 
Anybody else observed the same problem or got a solution?
Best regards
Ralf