Hi, Pretty much _any_ program that I run through valgrind on x64 boxes cause memcheck itself to SIGSEGV (valgrind works great on 32-bit afaik). Would be nice to have this for intrepid because valgrind is instrumental in: * analyzing other bugs * quality checking daily builds etc
This bug only happens using ubuntu afaik, the upstream homepage says valgrind should work well on x64. I have also found a number of duplicates on this issue: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/162933 https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/97531 https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/78081 https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/278542 https://bugs.launchpad.net/bugs/208120 (non public bug report) I also noted that my apport bug on this issue was marked as a duplicate of a non-public bug. This is pretty annoying because I want add comments etc to this bug so this makes it hard to collaborate on fixing this bug. Maybe apport should have some kind of policy that it tries to find a similar public apport bug and use that instead? I also noted that there is no -dbgsym package for valgrind itself available in ddebs (there is also no valgrind-dbg)? I thought that every single package had a corresponding -dbgsym in ddebs? What am I missing here? Finally, I wonder if anyone else on x64 can confirm this bug? When you run a simple program like the one below, does memcheck itself SIGSEGV? int main(int argc, char* argv[]) { int *ptr = 0; *ptr = 0; return 0; } Martin -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
