valgrind fails to run in mpc85xx

[hemwant]

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.

[bpe]

The software you are asking about is part of NXP Yocto SDK:

https://source.codeaurora.org/external/qoriq/qoriq-components/yocto-sdk/

This SDK includes support to MPC8548 which is a processor of the same
family as MPC8569.  The recommended way to build a valid  executable
binary for your target is by using the BSP integrator tool, Yocto.
Familiarize with the SDK documentation to see how to configure and build
software with it:

https://source.codeaurora.org/external/qoriq/qoriq-components/yocto-sdk/tree/

The name of Yocto recipe that builds valgrind software package is
'valgrind'

Have a great day,
Platon

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[hemwant]

Hello bpe‌

There is a mention in the readme you shared that

Notes: mpc8548cds and p1020rdb are not validated in this release.

will it cause any problem?

Meanwhile , I have tried to built only valgrind utility by running following command,

bitbake valgrind

After running i got valgrind utility and its dependency at

"yocto-sdk/build_mpc8548cds/tmp/work/ppce500v2-fsl-linux/valgrind/3.15.0-r0/image" compressed this complete folder and transfered to my mpc8569 card, uncompressed the file over there and ran the following command

export VALGRIND_LIB=/tftpboot/image/usr/lib/valgrind

./valgrind

resulted in killed message.

Please confirm it is the right procedure ?