Re: [Need Help] Valgrind on Cavium-Octeon-3
John Reiser <[email protected]>
| Newsgroups | gmane.comp.debugging.valgrind |
|---|---|
| Message-ID | <[email protected]> |
mihir amrelia wrote:
>> file /var/tmp/cavium/bin/valgrind
>> /var/tmp/cavium/bin/valgrind: ELF 64-bit MSB executable, MIPS, MIPS64 rel2 version 1 (SYSV), dynamically linked, interpreter /lib64-f, for GNU/Linux 2.6.32, not stripped
>>
>> How to fix this?
Tom Hughes via Valgrind-users wrote:
> No idea - that will be down to your cross build toolchain.
Diagnose by something like:
strace -f -o strace.out -e trace=execve -v -s 400 gcc hello.c
then search for "lib64-f" in strace.out.
For a native compile tool chain the relevant piece in strace.out is something like:
execve("/usr/bin/ld", ["/usr/bin/ld", ... "-dynamic-linker", "/lib64/ld-linux-x86-64.so.2", ...
which would be changed by something like
gcc -Wl,-dynamic-linker,path_to_eventual_dynamic_linker ...