Re: GTK+ is not Valgrind-friendly

The key to making glib and gtk+ purify friendly -- and thus presumably
also valgrind friendly -- is to make sure to supply the right configuration

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.


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