On Wed, 28 Sep 2005 11:09:30 +0200 Claudio Saavedra <[EMAIL PROTECTED]> wrote:
> Hi all, > > I'm starting to use valgrind to look for leaks, but I haven't found any > resource to analyse the valgrind output in a more friendly way. I have > seen once ago in p.g.o some charts made from the valgrind output, anyone > have idea about these tools? > > Also, any other resource outside the official valgrind documentation > that you can point me to will be appreciated. > > Thanks > > Claudio > -- > Claudio Saavedra <[EMAIL PROTECTED]> > > _______________________________________________ > gnome-love mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-love for example: gcc -g -o testprog test.c valgrind --show-reachable=yes --log-file=v.log --leak-check=yes testprog // testprog is you program wait for testprog exit, you have a file name :v.log.pidXXX(xxx is the testprog's pid). at the v.log.pidxxx, you can see that: definitely lost: 9304 bytes in 18 blocks. // that say : testprog has 18 blocks leak. :P good luck ! _______________________________________________ gnome-love mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-love
