|
From: John R. <jr...@bi...> - 2010-09-20 16:11:25
|
> But when I run "./coregrind/valgrind", I got the same error "No such
> file or directory".
Such a message might arise "mysteriously" because the Linux operating
system kernel cannot find the PT_INTERP that is requested by an executable
that is named in an execve() system call from the shell. It is the shell
which gets the ENOENT, then writes "No such file or directory."
In order to diagnose this, run "readelf --segments ./coregrind/valgrind"
and look for the PT_INTERP segment, such as this example on x86_64:
$ readelf --segments ./coregrind/valgrind
INTERP 0x0000000000000200 0x0000000000400200 0x0000000000400200
0x000000000000001c 0x000000000000001c R 1
[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]
The file "/lib64/ld-linux-x86-64.so.2" must exist on the target,
and have eXecute permissions, etc.
--
|