| Summary: | valgrind is sigKILL'd on startup | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Andrés Roldán <aroldan> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 3.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
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