Re: Up-to-date Valgrind suppression file for GLib/GTK+ ?

2017-01-02 Thread Bastien Nocera
On Mon, 2017-01-02 at 16:02 +0100, Stefan Sauer wrote: > On 12/30/2016 12:09 PM, jcup...@gmail.com wrote: > > On 29 December 2016 at 23:55, Emmanuele Bassi > > wrote: > > > As Philip explained earlier in the thread, Valgrind can only > > > accept a > > > single suppression file. So, if GTK+ ships

Re: Up-to-date Valgrind suppression file for GLib/GTK+ ?

2017-01-02 Thread Stefan Sauer
On 12/30/2016 12:09 PM, jcup...@gmail.com wrote: > On 29 December 2016 at 23:55, Emmanuele Bassi wrote: >> As Philip explained earlier in the thread, Valgrind can only accept a >> single suppression file. So, if GTK+ ships a suppression file, it >> would need to include suppression rules for all i

Re: Up-to-date Valgrind suppression file for GLib/GTK+ ?

2016-12-30 Thread Sébastien Wilmet
On Thu, Dec 29, 2016 at 11:55:35PM +0100, Stefan Sauer wrote: > Sorry for reviving the thread. What if upstream lib ship a suppression > file and add a pkg-config variable pointing to it? Then apps can use > $PKG_CONFIG --variable=valgrind_suppressions gtk+-3.0 > to collect those and e.g. export th

Re: Up-to-date Valgrind suppression file for GLib/GTK+ ?

2016-12-30 Thread jcupitt
On 29 December 2016 at 23:55, Emmanuele Bassi wrote: > As Philip explained earlier in the thread, Valgrind can only accept a > single suppression file. So, if GTK+ ships a suppression file, it > would need to include suppression rules for all its dependencies, and > you would still be unable to ad

Re: Up-to-date Valgrind suppression file for GLib/GTK+ ?

2016-12-29 Thread Emmanuele Bassi
Hi Stefan; On 29 December 2016 at 22:55, Stefan Sauer wrote: > Sorry for reviving the thread. What if upstream lib ship a suppression > file and add a pkg-config variable pointing to it? Then apps can use > $PKG_CONFIG --variable=valgrind_suppressions gtk+-3.0 > to collect those and e.g. export

Re: Up-to-date Valgrind suppression file for GLib/GTK+ ?

2016-12-29 Thread Stefan Sauer
On 08/02/2016 05:13 PM, Sébastien Wilmet wrote: > On Tue, Aug 02, 2016 at 01:47:41PM +0100, Philip Withnall wrote: >> On Mon, 2016-08-01 at 20:10 +0200, Sébastien Wilmet wrote: >>> So, is there an up-to-date Valgrind suppression file somewhere? Or is >>> GNOME.supp the most up-to-date? >> The one I

Re: Up-to-date Valgrind suppression file for GLib/GTK+ ?

2016-08-02 Thread Sébastien Wilmet
On Tue, Aug 02, 2016 at 01:47:41PM +0100, Philip Withnall wrote: > On Mon, 2016-08-01 at 20:10 +0200, Sébastien Wilmet wrote: > > So, is there an up-to-date Valgrind suppression file somewhere? Or is > > GNOME.supp the most up-to-date? > > The one I’ve been using is here: > > https://github.com/p

Re: Up-to-date Valgrind suppression file for GLib/GTK+ ?

2016-08-02 Thread Philip Withnall
Hey, On Mon, 2016-08-01 at 20:10 +0200, Sébastien Wilmet wrote: > GLib/GTK+ don't seem to provide a Valgrind suppression file upstream. > At > the following wiki page: > https://wiki.gnome.org/Valgrind That page is fairly outdated. I’ll give it a bit of a spruce up. > So, is there an up-to-date

Up-to-date Valgrind suppression file for GLib/GTK+ ?

2016-08-01 Thread Sébastien Wilmet
Hello, GLib/GTK+ don't seem to provide a Valgrind suppression file upstream. At the following wiki page: https://wiki.gnome.org/Valgrind I see that there is: 1) https://people.gnome.org/~johan/gtk.suppression 2) https://github.com/dtrebbien/GNOME.supp 1) is for Gtk+ 2.12, according to the commen