Re: Valgrind questions

2011-11-29 Thread Stefan Sauer
On 10/07/2011 11:09 AM, Andrew Cowie wrote: > On Tue, 2011-09-20 at 12:48 +0100, jcup...@gmail.com wrote: > >> Ooop, thanks. I hadn't realised but I'd not updated the version on the >> website for a while. I've put my current one up now and it includes a >> thing for g_type_add_interface_static(),

RE: Valgrind questions

2011-11-23 Thread Andrew Cowie
On Wed, 2011-11-23 at 18:07 +, Thomas Harty wrote: > I'll see if I can narrow down exactly what's causing this... Still, looks like you're pretty close to a good suppression file. Where should we install it? /usr/share/suppression/glib.sup /usr/share/suppression/gtk.sup

RE: Valgrind questions

2011-11-23 Thread Thomas Harty
er 2011 17:14 To: Thomas Harty Cc: gtk-app-devel-list@gnome.org Subject: Re: Valgrind questions Hi Tom, On 23 November 2011 15:21, Thomas Harty wrote: > any suggestions for what's causing this leak report and the best way to > suppress it? That looks like a gtk/gtkmm bug to me,

Re: Valgrind questions

2011-11-23 Thread jcupitt
Hi Tom, On 23 November 2011 15:21, Thomas Harty wrote: > any suggestions for what's causing this leak report and the best way to > suppress it? That looks like a gtk/gtkmm bug to me, but it's hard to tell without some context. Could you make a tiny test program which shows this behaviour? It a

RE: Valgrind questions

2011-11-23 Thread Thomas Harty
se.cc:194) any suggestions for what's causing this leak report and the best way to suppress it? Tom From: Thomas Harty Sent: 23 November 2011 15:20 To: Andrew Cowie; gtk-app-devel-list@gnome.org Subject: RE: Valgrind questions I've been updating the supp

RE: Valgrind questions

2011-11-23 Thread Thomas Harty
devel-list-boun...@gnome.org] on behalf of Andrew Cowie [and...@operationaldynamics.com] Sent: 07 October 2011 10:09 To: gtk-app-devel-list@gnome.org Subject: Re: Valgrind questions On Tue, 2011-09-20 at 12:48 +0100, jcup...@gmail.com wrote: > Ooop, thanks. I hadn't realised but I'd

Re: Valgrind questions

2011-10-07 Thread Andrew Cowie
On Tue, 2011-09-20 at 12:48 +0100, jcup...@gmail.com wrote: > Ooop, thanks. I hadn't realised but I'd not updated the version on the > website for a while. I've put my current one up now and it includes a > thing for g_type_add_interface_static(), as you also found. Might it be a good idea to put

RE: Valgrind questions

2011-09-20 Thread Thomas Harty
com [jcup...@gmail.com] Sent: 20 September 2011 08:54 To: Thomas Harty Cc: gtk-app-devel-list@gnome.org Subject: Re: Valgrind questions I posted this the last time this subject came up (twice last year, I think), but I made this valgrind suppression file for my project: http://www.vips.ecs.soto

Re: Valgrind questions

2011-09-20 Thread jcupitt
Hi Tom, On 20 September 2011 11:38, Thomas Harty wrote: > Running like that, I still get quite a few leaks detected by valgrind. Some > of them are created by g_type_add_interface_static, which looks like another > type_init leak, which we can safely ignore. So, I've added the following to > t

Re: Valgrind questions

2011-09-20 Thread jcupitt
I posted this the last time this subject came up (twice last year, I think), but I made this valgrind suppression file for my project:  http://www.vips.ecs.soton.ac.uk/development/nip2.supp Run with: $ export G_DEBUG=gc-friendly This makes Glib clear certain memory areas after using the

Valgrind questions

2011-09-19 Thread Thomas Harty
Dear all, I've been trying to get clear on exactly what the situation between Gtk+ and Valgrind is. There is a fair amount of information out there, but it's pretty scattered and mainly fairly old, so it'd be good to get it all in one place. As far as I understand it, the situation is that memo