Re: [Valgrind-users] running valgrind on ppc32 and windriver linux

[John R. <jr...@Bi...>]

>    I am trying to run valgrind on a target which is ppc32 and it has wind
> river linux.
>    I am successful in getting the valgrind related files and when I run
> valgrind, I am getting the following issue.
>    Could somebody help me.

The message really is very clear!  Do what it says after "Possible fixes".
If you don't understand what it says, then find someone else who does,
and ask them to help you.  Someone who is familiar with shared libraries
and execve() on Linux probably will understand.

If you still have problems, then file a bug report against valgrind.
See the "Bug reports" link in the left column of the main web page.
Please include the name of your Linux distribution, its version number,
the version number of the Linux kernel (copy+paste the output from "uname -a"),
and the version number of the libc shared library.  For example,
on x86_64 systems the file /lib*/libc.so.6 is a symlink to another file
such as "libc-2.17.so" which means that the version of libc is 2.17.

To make the bug report even more useful, then please run
   readelf --headers /bin/date
and look for "INTERP", such as:
-----
  INTERP         0x0000000000000238 0x0000000000400238 0x0000000000400238
                 0x000000000000001c 0x000000000000001c  R      1
      [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]
-----
Then run
   readelf --symbols /lib64/ld-linux-x86-64.so.2  |  grep str
but use the filename that you see in *YOUR* output on the second line
after "INTERP".  Then copy+paste the output of all the lines containing "str"
into the bug report.


> 
> 
>      root@lc1:/lc/isan/valgrind-3.8.1/bin# valgrind
> /isan/bin/port_client(image on the target)
> ==3536== Memcheck, a memory error detector
> ==3536== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
> ==3536== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
> ==3536== Command: /isan/bin/port_client
> ==3536==
> 
> 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.so.1
> valgrind:  was not found whilst processing
> valgrind:  symbols from the object with soname: ld.so.1
> 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.