Alan W. Irwin writes: > However, I still don't understand why valgrind reported no issues on my > platform without your recent changes. Segfaults can come and go (although > usually a segfault does show up for one of our 31 examples if there is a > memory management issue with the device driver). Normally valgrind is > completely reliable about reporting memory management issues with device > drivers even when there is no obvious problem with segfaults. Before your > recent change, why did valgrind find many obvious memory management issues > on your system but none on mine? That result is really weird.
I might be an outlier here, but since you brought it up, I should just share that my personal opinion is that Valgrind was rendered significantly less useful in the 3.x release series. In 2.x, it did much more thorough checking. It also ran a *lot* slower. In 3.x, they speeded it up, but it catches a lot less. For some years, I used to hold onto a 2.x copy, and ran that for a long time. In that era, I found numerous occasions where bugs were caught and identified exactly with valgrind 2.x, but missed by 3.x. But you had to be prepared to wait a lot longer. I once tried to see if I could figure out a way to bring back the execution model of 2.x, in the 3.x code, as some sort of a config time option. But it was too much for me and I ultimately gave up. Valgrind is surely faster now, but it catches fewer bugs. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
