AnsweredAssumed Answered

valgrind fails to run in mpc85xx

Question asked by Hemwant Rawat on Apr 30, 2020
Latest reply on May 19, 2020 by Hemwant Rawat

I am having customised board with MPC8569 processor, I have cross compiled valgrind3.10.0 for my board.

But when i run the valgrind on the board exporting proper valgrind libraries, it throws following errors-

 

 ./valgrind
valgrind: no program specified
valgrind: Use --help for more information.
[root@cscm1_mcp bin]# ./valgrind --tool=memcheck /dev/shm/mem-leak
==7950== Memcheck, a memory error detector
==7950== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==7950== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==7950== Command: /dev/shm/mem-leak
==7950==

 

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.

 

file valgrind
valgrind: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked, interpreter /lib/ld., for GNU/Linux 2.6.16, BuildID[sha1]=4badab86221348c3634daa927d21afb49a99adb1, with debug_info, not stripped.

 

Please look into the above issue.

Outcomes