On Sun, 2008-10-05 at 17:14 +0200, Martin Olsson wrote: > 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)
The private one that the reporter couldn't reproduce is the only one for Hardy on there, it seems. I can't reproduce it either. I've been using valgrind, and it's been working fine on x86_64 Hardy. Did something break between 3.3.0 and 3.3.1? -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo
signature.asc
Description: This is a digitally signed message part
-- 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
