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

List:       gtk-devel
Subject:    Re: Turning off the slice allocator
From:       Tim Janik <timj () gtk ! org>
Date:       2006-01-24 15:47:09
Message-ID: Pine.LNX.4.61.0601241646010.21690 () localhost ! localdomain
[Download RAW message or body]

On Tue, 24 Jan 2006, Federico Mena Quintero wrote:

> On Mon, 2006-01-23 at 17:22 +0100, Tim Janik wrote:
>
>> i'm currently working on a dedicated G_SLICE variable that can support
>> different checking/debugging modes, similar to MALLOC_CHECK_ as documented
>> in glibc's malloc(3).
>>
>> what i think would be great is if we reworked your patch to support
>> G_DEBUG=gc-friendly which sets a glib variable glib_mem_gc_friendly to
>> TRUE.
>> then, all the #ifdef ENABLE_GC_FRIENDLY statements in glib can be changed to
>> if (glib_mem_gc_friendly), to enable memory debugging/profiling without
>> recompilation of glib (and for stock distribution binary packages).
>
> We are already past API freeze for this release cycle in GNOME.  I'd
> rather not delay this any further.

this is not an API change. and i don't get what exactly you fear being delayed,
please explain.

> If you simply disable the slice allocator, you can already do a lot of
> checking/debugging by running valgrind.

gc-friendlyness is interesting for a bunch of other memory profilers
as well, which is why it's supported by glib.

>
>  Federico
>

---
ciaoTJ
_______________________________________________
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]