On May 23, 12:27 pm, Gavin Hamill <[email protected]> wrote:
> Yep sure. I've never used valgrind before and don't want to waste an > opportunity to capture some golden information. Can you provide the > syntax for optimal valgrind usage? I haven't used valdgrind in a while (OS X memory debugging stuff is pretty good, so I've mostly been using that), but you're basically just wanting to get a clue about out of boundary issues. It's *possible* that some other condition is leading to this issue and valgrind will find it earlier. > OK.. well let's try with a combination of valgrind and 1.3.3 first. The > thing that confuses me the most is that we've had zero problems with > 1.2.6 for months on amd64 :/ That's good to know. I'll try to speculate a bit more during the day. :)
