Valgrind itself SIGSEGVs on ubuntu x64

Mackenzie Morgan macoafi at gmail.com
Sun Oct 5 15:54:55 UTC 2008


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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20081005/a76d90ce/attachment.sig>


More information about the Ubuntu-devel-discuss mailing list