|
From: Bart V. A. <bva...@ac...> - 2011-07-21 05:39:00
|
On Wed, Jul 20, 2011 at 9:24 PM, Mudric, Dusan (Dusan) <dm...@av...>wrote: > I forgot to mention one more fact. I am using NFS mount. > > /etc/fstab: > ------------ > 47.135.159.188:/exports /exports nfs intr,noauto,nolock 0 0 > > Here is the "valgrind ls -l" output. If started as NFS mounted, nothing > happens: > > 47.134.206.85 # pwd > /exports > 47.134.206.85 # ls > Valgrind > 47.134.206.85 # cd Valgrind/ > 47.134.206.85 # ls > bin include lib share valgrind > 47.134.206.85 # ./valgrind ls -l > > If I copy valgrind executable on the target, "valgrind ls -l" prints > something: > > 47.134.206.85 # ./valgrind ls -l > valgrind: failed to start tool 'memcheck' for platform 'arm-linux': > No such file > or directory > > Problem is that I can not put the whole Valgrind on the target. It is 80MB > big and I don't have that much RAM available. > > Does it mean that valgrind can not run with NFS mount? > It means that Valgrind has not been configured or installed correctly. Please have a look at README.android on the trunk for an example of how to configure and install Valgrind when cross-compiling. Bart. |