Re: memory profiling (was calling g_malloc & co via a vtable)

Darin Adler <darin eazel com> writes: 
> Also, there are lots of things in glib, gtk, and gnome-libs that allocate
> one-time items and don't free on exit. Given the approach of the leak
> checker, each of these has to be identified by function name so it can be
> ignored.

That's the advantage of memprof over this type of leak checker.
> What do the Gtk+ maintainers think about a policy where we provide the
> additional code to free these data structures on exit, using g_atexit? I'd
> be happy to supply patches for this as well at some point.

Tim was strongly opposed at one point. Owen and I were thinking about


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