On Mon, 2005-04-04 at 14:41 +0200, Christian Parpart wrote: > Okay, it's been valgrind 2.4.0 that keeps crashing. valgrind 2.2.0 keeps > running fine inside my 32bit chroot environment. Although, the maintainer > already hardmasked valgrind 2.4.0 because of exactly this crash behavior. So, > I'm happy in being not the only one getting hit by 2.4.0 ;)
That would explain why when I emerged it this morning into my chroot, it worked fine:) > > After looking at what the folks at valgrind are doing, 3.0 will support > > amd64. [snip] > > So, if you can wait a few months, you can have real amd64 support:) Or > > if you feel brave, you can follow the svn trunk (though they come right > > out and say that amd64 is pretty much useless at this point, you could > > contribute some bug reports and help them out) and maybe get it sooner. > > Yeah, I just checked it out from their svn repository. However, it's not that > little, and I didn't find a real TODO list so that I could find a good entry > point. I hadn't gone that far... I only checked their bugzilla for tracking bugs and couldn't find any there, either. I'm kinda disappointed they don't have a todo list, 'cause I was thinking I might look into helping them out... but right now, I don't have the time to do the deep reading it'd need without a guide. Greg
signature.asc
Description: This is a digitally signed message part
