On Mon, Jul 6, 2009 at 2:38 PM, Alwin Leerling<[email protected]> wrote: > I might be a bit of a puritan but I am puzzled about the following. Running > valgrind over my program I noticed a lot of unfreed block on application > close. I decided to run a basic GTK program and see what happened.
I do this a lot on Chrome. First, as described in http://library.gnome.org/devel/glib/stable/glib-running.html be sure to set G_SLICE=always-malloc, else valgrind might get a bit confused. Second, there are dozens of problems in system libraries that you should probably just ignore. Try grabbing http://src.chromium.org/viewvc/chrome/trunk/src/tools/valgrind/suppressions.txt and using part 1 of that (the non-chrome-specific part); that should suppress lots of them. - Dan _______________________________________________ gtk-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtk-list
