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?

Thanks,
Dusan.

-----Original Message-----
From: John Reiser [mailto:jrei...@bitwagon.com] 
Sent: Wednesday, July 20, 2011 3:03 PM
To: valgrind-users@lists.sourceforge.net
Subject: Re: [Valgrind-users] Valgrind for ARM 1176 for linux

On 07/20/2011 10:41 AM, Mudric, Dusan (Dusan) wrote:
> I did something similar. However, "valgrind ls -l" does nothing. It never 
> completes this instruction. 

"valgrind ls -l" does _something_, if nothing other than "Cannot exec", or 
SIGSEGV,
or some other complaint.  ("Normal exit" is a [silent] complaint.)

Please show the entire output from:
        valgrind ls -l
        echo $?
Then show the output from:
        strace valgrind ls -l
The show the output from
        $ gdb valgrind
        (gdb) run ls -l
        (gdb) bt
        (gdb) info reg
        (gdb) x/i $pc
        (gdb) x/8i $pc-4*4


> 1. I fixed configure.in
> 
> http://old.nabble.com/building-for-arm-td29791500.html#a29791500
> 
> 2. I used:
> 
> . ./mybuild.sh
> ./configure --host=armv7-unknown-linux-gnu --prefix=/exports/Valgrind

Cross-compiling and cross-linking is significantly different from
native compiling and native linking.  You should have mentioned this
in your first message.  You must insure that the cross-linking environment
matches the actual target environment; it is surprisingly easy and common
to make errors here.

-- 

------------------------------------------------------------------------------
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

------------------------------------------------------------------------------
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

Reply via email to