On 18/01/10 14:27, Vasanta wrote:
> Looklike when I compile this on host, it is hardcoding the path
> into binaries like memcheck-x86-linux and all, if I copy these onto my
> embedded target, if I run there, it says "memcheck" couldn't start, on
> target, I copied to /usr/loca/lib abd /usr/local/bin directories, when I
> execute, path not correct, how can I fix this path?.

As I have now told you twice, you need to put the binaries in the same 
place on the target as they are in when you install on the build 
machine. The exact same place. Not something a bit like the same place.

The reason for that, as you have discovered, is that the paths are fixed 
in at build time so that the launcher process (the valgrind binary) will 
look in a specific place for the tools.

So the things in /usr/local/lib/valgrind on the build machine need to be 
copied to /usr/local/lib/valgrind on the target machine, not to 
/usr/local/lib or anywhere else.

Tom

-- 
Tom Hughes ([email protected])
http://www.compton.nu/

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to