Re: [Valgrind-users] [Need Help] Valgrind on Cavium-Octeon-3

[Tom H. <to...@co...>]

On 07/01/2021 10:54, mihir amrelia via Valgrind-users wrote:

> I am trying to get valgrind running on cavium octeon 3 processor.
> 
> 
> Couldn't find any specific build configs for this other than some hints 
> on the valgrind wiki.
> *
> *
> *
> The steps executed to build valgrind for cavium were (on x86_64 host):
> *export CC=/opt/cavium-64bit/tools-3535/bin/mips64-octeon-linux-gnu-gcc
> export CXX=/opt/cavium-64bit/tools-3535/bin/mips64-octeon-linux-gnu-g++
> export PATH=$PATH:/opt/cavium-64bit/tools-3535/bin/
> ./configure --host=mips64-linux-gnu --target=mips64-octeon-linux 
> --prefix=/home/mihira/workspace/mylab/valgrind/cavium 
> --exec-prefix=/var/tmp/cavium --disable-tls
> make && make install
> 
> *While trying to run it on target (copied the elfs to /var/tmp/cavium/ 
> dir on the target):*
> export VALGRIND_LIB=/var/tmp/cavium/lib/valgrind/
> export PATH=$PATH:/var/tmp/cavium/bin/
> valgrind -h
> -bash: /var/tmp/cavium/bin/valgrind: No such file or directory
> 
> 
> What's that blunder I am doing?

At a guess the ELF interpreter specified in the compiled
valgrind launcher doesn't exist - that can lead to that
confusing error when running a executable that exists.

Try "file /var/tmp/cavium/bin/valgrind" and see what it says
about it - part of the result should be something like this:

   interpreter /lib64/ld-linux-x86-64.so.2

which will tell what interpreter it is using.

Tom

-- 
Tom Hughes (to...@co...)
http://compton.nu/