On Thu, Mar 21, 2002 at 05:27:16PM +0000, Austin Donnelly wrote: > I've just heard about Valgrind, a memory debugger much like Purify, > but which works on Linux.
Better/ Different than Purify because it treats the code as a black box, and so it finds bugs in your compiler, libraries and so on. It has a KDE bias, but I'm sure some loving from the right people will help it learn about glib 1.2 and 2.0 objects, memory allocators etc. to give more helpful diagnostics when you scribble all over a MemChunk :) > I've given it a quick spin on gimp-1.2.2, and it picked up a couple of > bugs. It's really quite a good tool! I didn't see any problems with 1.2 CVS when I tried it a few weeks ago, except for shared mem stuff at startup (which I put down to Valgrind not knowing about shared mem at that point). Maybe I didn't try the right tools/ features/ whatever ? Nick. _______________________________________________ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
