Re: GTK+ is not Valgrind-friendly
- From: terra gnome org (Morten Welinder)
- To: gtk-devel-list gnome org
- Subject: Re: GTK+ is not Valgrind-friendly
- Date: Fri, 30 Apr 2004 11:56:40 -0400 (EDT)
The key to making glib and gtk+ purify friendly -- and thus presumably
also valgrind friendly -- is to make sure to supply the right configuration
flags.
For glib: use --disable-mem-pools --enable-gc-friendly
For ORBit2: use --enable-purify
Owen: I think you grossly underestimate the value of cleaning out memory
at exit. While exit(2) is a very good garbage collector, relying on it
can and do hide serious problems.
Right now the amount of memory in use by gtk+ at exit is so huge that
dangling pointer in there interferes with leak hunting by sometimes
making leaks appear and disappear between runs.
Morten
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]