title: valgrind giving fatal error at launching time
body: <p>I have compiled valgrind for a embedded device, and executed the following command to check the leaks.</p>
  <pre><code>./valgrind --leak-check=full --xml=yes --xml-file=&lt;xml file path&gt; &lt;application&gt;
  </code></pre>
  <p>But it is giving the following error.</p>
  <pre><code>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.  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:  Note that if you are debugging a 32 bit process on a
  valgrind:  64 bit system, you will need a corresponding 32 bit debuginfo
  valgrind:  package (e.g. libc6-dbg:i386).
  valgrind:
  valgrind:  Cannot continue -- exiting now.  Sorry.
  </code></pre>
  <p>There is a library &quot;ld-2.19.so&quot; built along with valgrind, If I copy this library to /lib/ (replacing the existing ld-2.19.so under /lib/ with the same library built along with valgrind) then valgrind is running fine. Same tool chain was used to build rootfs for the embedded device and valgrind. Replacing existing &quot;ld-2.19.so&quot; with library built along with valgrind will not effect the report generating by valgrind?</p>