Package: valgrind
Version: 1:3.1.0-1
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I just upgraded from version 3.0.1-2 and all my attempts to run this new
version end up in valgrind receiving the SIGKILL signal.
The output of 'strace -f valgrind' ends with:
readlink("/proc/self/exe", "/usr/bin/valgrind.bin", 4096) = 21
brk(0) = 0x804d000
brk(0x806e000) = 0x806e000
execve("/usr/lib/valgrind/x86-linux/memcheck", ["/usr/bin/valgrind.bin"], [/*
36 vars */]) = 0
+++ killed by SIGKILL +++
and gdb given no information whatsoever.
Running memcheck directly gives the same error, and the strace output is just
the execve line.
Note that I'm using the 1GB highmem patch that allows computers with up to 1GB
of RAM to access it as lowmem instead of using the slower highmem code in the
kernel. The previous Valgrind version didn't work with this patch, but at least
it gave some form of (not very human-readable) error message. In this regard,
this version has a regression.
Thanks,
- -- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-ck5
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Versions of packages valgrind depends on:
ii libc6 2.3.5-8 GNU C Library: Shared libraries an
Versions of packages valgrind recommends:
ii gdb 6.3.90.20051119-1 The GNU Debugger
- -- debconf-show failed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDjG/a823633cP2P8RAuApAJ49dwbpS7EYP5BwG5RFjmQCNbtWMQCgmpS2
l2aCdVj3crtyaIvbtm0grD0=
=kxYb
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
