Daniel, I still get SIGSEGV in memcheck when analysing pretty much _any_ program using valgrind on a x64 with intrepid. Upstream says valgrind should be working on x64 so this is likely an ubuntu bug and not a general valgrind bug.
The specific crash I am seeing is the exact one that D3m0n1q_733rz report about above, i.e. a crash in do_syscall_WR. My auto submitted crash report is here: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/278542 I found found another duplicate of my bug here: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/162933 And of course my bug report closed as a duplicate of a third report (bug id 208120) however this bug is not accessible by the community. I think getting valgrind to work on intrepid/x64 should be fairly high priority seeing as how valgrind is used for finding and analyzing many other bugs. -- valgrind crashes on memcheck for a given program https://bugs.launchpad.net/bugs/78081 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
