On 07/20/2011 12:24 PM, Mudric, Dusan (Dusan) 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
This does not match what "make install" produces, which is:
-----
$ cd $(configure_prefix) ## /where/you/want/it/installed
$ ls
bin include lib share
$ cd bin
$ ls
callgrind_annotate cg_diff no_op_client_for_valgrind vgdb
callgrind_control cg_merge valgrind
cg_annotate ms_print valgrind-listener
$
-----
So the correct invocation should be something like:
$ .../Valgrind/bin/valgrind ls -l
Please show the output from
strace .../Valgrind/bin/valgrind ls -l
[Adjust the pathname to valgrind before running strace, and show what
you changed it to.] It will tell the failure mechanism.
> 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
This is a symptom of not having everything that "make install" wanted to put
there,
which is lib/memcheck-arm-linux.
>
> 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.
You don't need all 80 MB to run just memcheck. Look at lib/valgrind,
and omit the obvious stuff such as any file whose name contains any one of:
cachegrind
callgrind
drd
exp
helgrind
lackey
massif
You can even do this in your build. In the top-level Makefile,
remove what you don't want from these lists:
-----
TOOLS = memcheck \
cachegrind \
callgrind \
massif \
lackey \
none \
helgrind \
drd
EXP_TOOLS = exp-sgcheck \
exp-bbv \
exp-dhat
-----
>
> Does it mean that valgrind can not run with NFS mount?
Put a copy of /bin/date (from the target) right next to (in the same directory
as)
the valgrind that you want to run, then try to run _that_ "date" program.
If you can run that "date" over NFS, then you can run valgrind over NFS;
and if that "date" won't run over NFS, then you cannot run valgrind over NFS.
--
------------------------------------------------------------------------------
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks & Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
