|
From: wwp <sub...@fr...> - 2006-06-03 09:05:21
Attachments:
signature.asc
kernel-2.6.16-i686.config.gz
|
Hi there,
I'm running valgrind on a Fedora Core 5 box, no problem w/ 3.1.1 from the
sources or the FC5 valgrind-3.1.0-2 package, if only use the Fedora kernels. I
recently set up a custom kernel, which config is stripped down from the
2.6.16-1.2122_FC5's one (get rid of tons of unnecessary stuff, best fit my
hardware).
Unfortunately, when I use this custom kernel, running valgrind is impossible
(whatever command-line I try), I get:
$ valgrind --help
Killed
With root or non-root, still the same. I tried using strace, but can get any
clue from the output:
$ strace valgrind --help
execve("/usr/bin/valgrind", ["valgrind", "--help"], [/* 40 vars */]) = 0
brk(0) = 0x9bd7000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa7f76000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/usr/local/lib/tls/i686/sse2/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/lib/tls/i686/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/lib/tls/sse2/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/lib/tls/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/lib/i686/sse2/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/lib/i686/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/lib/sse2/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/lib/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=121122, ...}) = 0
mmap2(NULL, 121122, PROT_READ, MAP_PRIVATE, 4, 0) = 0xa7f58000
close(4) = 0
open("/lib/libc.so.6", O_RDONLY) = 4
read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0J\330c\000"..., 512) = 512
fstat64(4, {st_mode=S_IFREG|0755, st_size=1532536, ...}) = 0
mmap2(0x628000, 1254780, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = 0x628000
mmap2(0x755000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x12d) = 0x755000
mmap2(0x758000, 9596, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x758000
close(4) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa7f57000
set_thread_area({entry_number:-1 -> 6, base_addr:0xa7f576c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0
mprotect(0x755000, 8192, PROT_READ) = 0
mprotect(0x624000, 4096, PROT_READ) = 0
munmap(0xa7f58000, 121122) = 0
readlink("/proc/self/exe", "/usr/bin/valgrind", 4096) = 17
brk(0) = 0x9bd7000
brk(0x9bf8000) = 0x9bf8000
execve("/usr/lib/valgrind/x86-linux/memcheck", ["valgrind", "--help"], [/* 41 vars */]) = 0
+++ killed by SIGKILL +++
Process 21593 detached
Are there any kernel setting that might explain this problem? (I've attached
my kernel config)
Regards,
--
wwp
|
|
From: Julian S. <js...@ac...> - 2006-06-03 12:03:24
|
> execve("/usr/lib/valgrind/x86-linux/memcheck", ["valgrind", "--help"], [/*
> 41 vars */]) = 0 +++ killed by SIGKILL +++
I believe this will be fixed in 3.2.0. Try the release candidate and
see if it works:
http://www.valgrind.org/downloads/valgrind-3.2.0rc1.tar.bz2
(MD5 = 200bdc9bfb3a6b4f74c797b12a91a402)
J
|
|
From: wwp <sub...@fr...> - 2006-06-03 12:30:58
Attachments:
signature.asc
|
Hello Julian,
On Sat, 3 Jun 2006 13:03:04 +0100 Julian Seward <js...@ac...> wrote:
>=20
> > execve("/usr/lib/valgrind/x86-linux/memcheck", ["valgrind", "--help"], =
[/*
> > 41 vars */]) =3D 0 +++ killed by SIGKILL +++
>=20
> I believe this will be fixed in 3.2.0. Try the release candidate and
> see if it works:
>=20
> http://www.valgrind.org/downloads/valgrind-3.2.0rc1.tar.bz2
> (MD5 =3D 200bdc9bfb3a6b4f74c797b12a91a402)
Well, it seems to work! At least it doesn't get Killed at startup ;-). Than=
ks
a ton!
Is there any link I could follow to know why 3.1.x don't work with my kernel
(to feed a thread on fedora users mailing-list, for the archives)?
Regards,
--=20
wwp
|
|
From: Michael S. <ms...@xi...> - 2006-06-03 12:36:18
|
On 6/3/06, wwp <sub...@fr...> wrote: > Well, it seems to work! At least it doesn't get Killed at startup ;-). Thanks > a ton! > > Is there any link I could follow to know why 3.1.x don't work with my kernel > (to feed a thread on fedora users mailing-list, for the archives)? See the thread starting here: http://sourceforge.net/mailarchive/message.php?msg_id=14946071 Mike |
|
From: Julian S. <js...@ac...> - 2006-06-03 12:46:51
|
On Saturday 03 June 2006 13:36, Michael Smith wrote: > On 6/3/06, wwp <sub...@fr...> wrote: > > Well, it seems to work! At least it doesn't get Killed at startup ;-). > > Thanks a ton! > > > > Is there any link I could follow to know why 3.1.x don't work with my > > kernel (to feed a thread on fedora users mailing-list, for the archives)? > > See the thread starting here: > http://sourceforge.net/mailarchive/message.php?msg_id=14946071 We tracked this bug as #117290. http://bugs.kde.org/117290 should make the problem clear. J |
|
From: wwp <sub...@fr...> - 2006-06-03 12:46:58
Attachments:
signature.asc
|
Hello Michael, On Sat, 3 Jun 2006 14:36:08 +0200 "Michael Smith" <ms...@xi...> wrote: > On 6/3/06, wwp <sub...@fr...> wrote: >=20 > > Well, it seems to work! At least it doesn't get Killed at startup ;-). > > Thanks a ton! > > > > Is there any link I could follow to know why 3.1.x don't work with my > > kernel (to feed a thread on fedora users mailing-list, for the archives= )? >=20 > See the thread starting here: > http://sourceforge.net/mailarchive/message.php?msg_id=3D14946071 I could also see (NEWS file helps) that it was bug 117290. I'll unsubscribe now, thanks to all. Regards, --=20 wwp |