I've retested with trunk. This time I attached the output from running reinit.
I'm still getting a lot of leaks and just from glancing at your suppressions they definitely wouldn't cover everything I'm getting. To me, it looks like literally nothing is getting cleaned up, which maybe means there's an easy fix. Avery On Tue, Apr 6, 2010 at 11:05 PM, Julien Nadeau <[email protected]>wrote: > > Hi, > > Thank you for your feedback, > > Could you test this again with current SVN? A number of leaks following > AG_Destroy() have been addressed since version 1.3.4. > > You don't need anything other than AG_Destroy() at the end of your program. > > I've attached the valgrind suppression file I'm using on my Linux/amd64 > workstation. > > On Sun, Apr 04, 2010 at 05:03:49AM -0500, Avery Fay wrote: > > Hello, > > > > I usually like to start projects with clean valgrind output so that I can > > easily detect if I've inadvertently leaked memory. The problem I'm having > is > > that even the simplest agar app is causing a lot of leak warnings from > > valgrind. For example, I've attached the valgrind output from running the > > demos/minimal program. > > > > Some of it probably isn't real like the X11 stuff, but I'm not sure about > > the rest. Are these real leaks? Do I need to add something more than > > AG_Destroy at the end of the program? > > > > Thanks, > > Avery Fay > > > > _______________________________________________ > > Agar mailing list > > [email protected] > > http://libagar.org/lists.html > >
valgrind.txt.gz
Description: GNU Zip compressed data
_______________________________________________ Agar mailing list [email protected] http://libagar.org/lists.html
