|
From: Vasanta <vt...@gm...> - 2010-01-15 21:23:02
|
also I copied all binaries and libraries into single directory, then I tried to execute "valgrind" command, I am getting same error as before. also I copied memcheck-x86-linux as memcheck. # ls -l -rwxr-xr-x 1 0 0 40959 callgrind_annotate -rwxr-xr-x 1 0 0 13662 callgrind_control -rwxr-xr-x 1 0 0 32064 cg_annotate -rwxr-xr-x 1 0 0 42942 cg_merge -rwxr-xr-x 1 0 0 24211 ms_print -rwxr-xr-x 1 0 0 8531 no_op_client_for_valgrind -rwxr-xr-x 1 0 0 30823 valgrind -rwxr-xr-x 1 0 0 18887 valgrind-listener -rwxr-xr-x 1 0 0 4636305 cachegrind-x86-linux -rwxr-xr-x 1 0 0 4891451 callgrind-x86-linux -rw-r--r-- 1 0 0 27934 default.supp -rwxr-xr-x 1 0 0 4857510 drd-x86-linux -rwxr-xr-x 1 0 0 4519362 exp-bbv-x86-linux -rwxr-xr-x 1 0 0 4729657 exp-ptrcheck-x86-linux -rwxr-xr-x 1 0 0 4837460 helgrind-x86-linux -rwxr-xr-x 1 0 0 4529944 lackey-x86-linux -rwxr-xr-x 1 0 0 4568883 massif-x86-linux -rwxr-xr-x 1 0 0 5040139 memcheck-x86-linux -rwxr-xr-x 1 0 0 4509675 none-x86-linux -rwxr-xr-x 1 0 0 6765 vgpreload_core-x86-linux.so -rwxr-xr-x 1 0 0 170657 vgpreload_drd-x86-linux.so -rwxr-xr-x 1 0 0 45354 vgpreload_exp-ptrcheck-x86-linux.so -rwxr-xr-x 1 0 0 107935 vgpreload_helgrind-x86-linux.so -rwxr-xr-x 1 0 0 37223 vgpreload_massif-x86-linux.so -rwxr-xr-x 1 0 0 72136 vgpreload_memcheck-x86-linux.so -rwxr-xr-x 1 0 0 5040139 memcheck # # valgrind /pfrm2.0/bin/pcscd valgrind: failed to start tool 'memcheck' for platform 'x86-linux': No such file or directory # On Fri, Jan 15, 2010 at 2:58 PM, Tom Hughes <to...@co...> wrote: > On 15/01/10 19:28, Vasanta wrote: > > I installed valgrind libraries and binaries on x86 based embedded >> target, I am getting "valgrind error - "failed to start tool 'memcheck' >> for platform x86-linux" no such file or directory". I can see >> memcheck-x86-linux file under lib, but it keeps reporting everytime. >> >> copied all lib and bin files which are generated after I compiled >> valgrind package, when I run my exe with valgrind, I am getting above >> error, any idea? >> > > You need to put files the same directory on the target machine that they > were in on the build machine (probably /usr/lib/valgrind) or valgrind won't > find them. > > Tom > > -- > Tom Hughes (to...@co...) > http://www.compton.nu/ > |