|
From: Robert C. <r.c...@gs...> - 2007-10-15 10:36:15
|
I'm sorry, I realise from looking at the archives that this problem has
come up a lot, but I can't resolve it on my own even after looking
through the archives.
I don't have root privileges on the computer I'm using, so I needed to
install valgrind locally, I made its home directory:
~/bin/valgrind-3.2.3
I then ran:
./configure --prefix=$HOME/bin
then make then make install.
It all seems to work fine, but then if I run valgrind, I get the following:
valgrind: failed to start tool 'memcheck' for platform 'x86-linux': No
such file or directory
Looking at some of the archives, I then tried running strace with it,
which gives the output at the bottom of the e-mail. Obviously it is
looking for memcheck in:
/usr/local/lib/valgrind/x86-linux/memcheck
which is not what I want, however I don't know how to alter it.
On one of the old posts with a similar problem someone suggested putting
the line
tcc_add_library_path(s, "~/lib");
into /perf/tinycc.c
after the lines:
#ifdef TCC_TARGET_PE
{
char buf[1024];
snprintf(buf, sizeof(buf), "%s/lib", tcc_lib_path);
tcc_add_library_path(s, buf);
}
#else
tcc_add_library_path(s, "/usr/local/lib");
tcc_add_library_path(s, "/usr/lib");
tcc_add_library_path(s, "/lib");
which I tried but it seemed to make no difference.
I would really appreciate some help as I have tried my best to solve
this on my own.
Many thanks,
Rob.
execve("/the/cussons/bin/valgrind", ["valgrind"], [/* 45 vars */]) = 0
uname({sys="Linux", node="tplx36", ...}) = 0
brk(0) = 0x804d000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7f91000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=85986, ...}) = 0
mmap2(NULL, 85986, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f7c000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/tls/i686/cmov/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\240O\1"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=1241392, ...}) = 0
mmap2(NULL, 1247388, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0xb7e4b000
mmap2(0xb7f72000, 28672, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x127) = 0xb7f72000
mmap2(0xb7f79000, 10396, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f79000
close(3) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7e4a000
mprotect(0xb7f72000, 20480, PROT_READ) = 0
set_thread_area({entry_number:-1 -> 6, base_addr:0xb7e4a6c0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1}) = 0
munmap(0xb7f7c000, 85986) = 0
readlink("/proc/self/exe", "/the/cussons/bin/valgrind", 4096) = 25
brk(0) = 0x804d000
brk(0x806e000) = 0x806e000
execve("/usr/local/lib/valgrind/x86-linux/memcheck", ["valgrind"], [/*
46 vars */]) = -1 ENOENT (No such file or directory)
write(2, "valgrind: failed to start tool \'"..., 94valgrind: failed to
start tool 'memcheck' for platform 'x86-linux': No such file or directory
) = 94
exit_group(1) = ?
Process 29036 detached
|
|
From: Paul F. <pa...@fr...> - 2007-10-15 14:57:08
|
Quoting Robert Cussons <r.c...@gs...>: > I'm sorry, I realise from looking at the archives that this problem has > come up a lot, but I can't resolve it on my own even after looking > through the archives. > > I don't have root privileges on the computer I'm using, so I needed to > install valgrind locally, I made its home directory: > ~/bin/valgrind-3.2.3 > > I then ran: > ./configure --prefix=$HOME/bin Hi Does it make any difference if you use the explicit path? Like ./configure --prefix=/home/r.cussons/bin A+ Paul |
|
From: Robert C. <r.c...@gs...> - 2007-10-15 16:38:51
|
Paul Floyd wrote: > Quoting Robert Cussons <r.c...@gs...>: > >> I'm sorry, I realise from looking at the archives that this problem has >> come up a lot, but I can't resolve it on my own even after looking >> through the archives. >> >> I don't have root privileges on the computer I'm using, so I needed to >> install valgrind locally, I made its home directory: >> ~/bin/valgrind-3.2.3 >> >> I then ran: >> ./configure --prefix=$HOME/bin > > Hi > > Does it make any difference if you use the explicit path? Like > > ./configure --prefix=/home/r.cussons/bin > > A+ > Paul Thanks very much Paul, but that didn't make any difference. I deleted it all and started with the install again and the first time I had installed valgrind one directory deeper than I thought I had, hence the problem. Sorry, stupid mistake, but it's now working and seems to have found lots of errors that I can now debug! Many thanks, Rob. |