Re: [Valgrind-users] Fwd: Support Request

[Tom H. <to...@co...>]

On 18/03/14 15:40, Giuseppe Assalve wrote:

> I'm trying to install Valgrind on an embedded linux platform (Angstrom
> distribution).
> I've cross-compiled it Valgrind correctly but when I try to launch it
> (valgrind ls -al) on the board I have the following error:
>
> 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:      memcpy
> valgrind:  in an object with soname matching: ld-linux.so.3
> valgrind:  was not found whilst processing
> valgrind:  symbols from the object with soname: ld-linux.so.3
> 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.
>
> Could you please tell me how I can fix this problem?

I believe the answer to your question is in the verbose message which 
valgrind printed...

To reiterate, you need to either stop your ld.so getting stripped in 
such a severe way, or you need to provide debug symbols for it.

Tom

-- 
Tom Hughes (to...@co...)
http://compton.nu/