[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gtk-devel
Subject:    Re: Valgrind and GTK
From:       jcupitt () gmail ! com
Date:       2010-01-02 14:59:57
Message-ID: 522c6461001020659m399c7814l16f88636b1ec0f5a () mail ! gmail ! com
[Download RAW message or body]

2010/1/2 Erik de Castro Lopo <mle+gtk@mega-nerd.com>:
> when run as follows (suppression file from http://live.gnome.org/Valgrind):

I use the following suppression file on Ubuntu 9.10:

------------
{
   ldopen1
   Memcheck:Addr4
   obj:/lib/ld-2.6.1.so
}

{
   xwrite1
   Memcheck:Param
   write(buf)
   obj:/lib/ld-2.6.1.so
   fun:_X11TransWrite
}

{
   xwrite2
   Memcheck:Param
   writev(vector[...])
   obj:/lib/ld-2.6.1.so
   obj:/usr/lib/libX11.so.6.2.0
   fun:_X11TransWritev
}

{
   type_init
   Memcheck:Leak
   fun:*alloc
   ...
   fun:g_type_register_*
}

{
   type_init2
   Memcheck:Leak
   fun:*alloc
   ...
   fun:g_type_init_*
}

{
   type_init3
   Memcheck:Leak
   fun:*alloc
   ...
   fun:g_type_create_*
}
------------

Then run with:

$ export G_SLICE=always-malloc
$ export G_DEBUG=gc-friendly
$ valgrind --leak-check=yes nip2 > valgrind.log 2>&1

And I get no reported leaks (well, one report from selinux and one
from a getpwd call somewhere) for my 300,000 line GTK application.

John
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list
[prev in list] [next in list] [prev in thread] [next in thread]