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.soton.ac.uk/development/nip2.supp

Run with:

$ export G_DEBUG=gc-friendly

        This makes Glib clear certain memory areas after using them, too.

$ export G_SLICE=always-malloc

        This completely disables the magazine and slab allocator in Glib,
        and makes it use plain malloc()/free() instead.

$ valgrind --suppressions=/home/john/nip2.supp \
  --leak-check=yes \
  myprog ... > myprog-vg.log 2>&1

With this, I get no reported leaks in my huge (200,000 lines of C)
application on Ubuntu with current gtk+. There are some comments in
the file explaining what the various bits do. No doubt I've made some
errors :-( but perhaps it might be useful.

John



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]