How to use Valgrind on WP76 to investigate memory leaks

root@swi-mdm9x28-wp:/tmp/valgrind# ls
callgrind_annotate  cg_diff             valgrind            vgdb
callgrind_control   cg_merge            valgrind-di-server
cg_annotate         ms_print            valgrind-listener
root@swi-mdm9x28-wp:/tmp/valgrind# ./valgrind ./aa 
valgrind: failed to start tool 'memcheck' for platform 'arm-linux': No such file or directory
root@swi-mdm9x28-wp:/tmp/valgrind# export VALGRIND_LIB=/tmp/valgrind
root@swi-mdm9x28-wp:/tmp/valgrind# ./valgrind ./aa 
==3054== Memcheck, a memory error detector
==3054== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==3054== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==3054== Command: ./aa

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:  A must-be-redirected function
valgrind:  whose name matches the pattern:      strcmp
valgrind:  in an object with soname matching:
valgrind:  was not found whilst processing
valgrind:  symbols from the object with soname:
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 (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:    On Debian, Ubuntu:                 libc6-dbg
valgrind:    On SuSE, openSuSE, Fedora, RHEL:   glibc-debuginfo
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:  Cannot continue -- exiting now.  Sorry.

root@swi-mdm9x28-wp:~# legato version
root@swi-mdm9x28-wp:~# cat /proc/version 
Linux version 3.18.131 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 PREEMPT Mon Jul 8 12:20:50 UTC 2019
root@swi-mdm9x28-wp:~# uname -a
Linux swi-mdm9x28-wp 3.18.131 #1 PREEMPT Mon Jul 8 12:20:50 UTC 2019 armv7l GNU/Linux

Although the final compilation did not succeed, Valgrind has been compiled successfully.According to the way you gave it before, the wrong question is the same. I don’t know what kind of success environment you have.