----- Original Message ----- > From: "marcin@xxxxxxxxxx" <marcin@xxxxxxxxxx> > To: gtk-list@xxxxxxxxx > Cc: > Sent: Thursday, November 8, 2012 12:49 AM > Subject: Debugging memleaks - valgrind suppressions & closures > > Hi all, > > I am trying to debug memleak in my software. > > 1) > > I use valgrind as a primary tool for such task but I am spammed by > tons of messages related to type initialization. I've found that both > suppression files mentioned at http://live.gnome.org/Valgrind are not > up to date. [snip] > > Marcin > _______________________________________________ "I've found that both suppression files are not up to date" - I think it was the same several years ago. And I am too lazy to check that gtk+ developers bold claim (used to be on gtk+ main website) that gtk+ has no memory leaks is still in place. It used to remain in place amid published in this list fixed bugs related to memory leaks - again, several years ago. Regards, Sergei. _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gtk-list
