This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: Valgrind on TDA4VM

Part Number: TDA4VM

Dear support,

I've been trying to get valgrind up and running to profile my application with very little success so far. I've built it on the target from source, but when trying to use it, it says the following:

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-aarch64.so.1
valgrind: was not found whilst processing
valgrind: symbols from the object with soname: ld-linux-aarch64.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

The issue is that I don't seem to have package management on the stock TDA4 image. Is there a relatively simple way to get Valgrind working on my TDA4VM board?

Kind regards,

Bence

  • Hi Bence,

    The recommended way of building the valgrind is to use the Yocto build procedure. You will need to add the required recipes/packagegroups for valgrind and compile (bitbake) it for the target filesystem.

    The package management on the Yocto is opkg and this is available on the target. If you add and generate Yocto build, you can also install the ipk (with the package manager, opkg) or copy the new filesystem.

    The default filesystem "tisdk-default-image" does not include valgrind.

    Regards
    Karthik