Re: chunked_mempools - feedback needed

From: Andres Kroonmaa <andre@dont-contact.us>
Date: Sat, 28 Apr 2001 00:59:26 +0200

On 28 Apr 2001, at 0:02, Henrik Nordstrom <hno@hem.passagen.se> wrote:

> At present I have only one mempool request I'd like to bake together
> with chunked memory pools when committing this to HEAD:
>
> The compile time ability to completely disable memory pools using
> --disable-memory-pools or something similar.

 in lib/MemPool.c:
 #define DISABLE_POOLS 1

 will effectively disable pooling and will revert back to pure xcalloc/xfree

 It only disables memPoolAlloc and memPoolFree. All else is left in.
 Probably enough for debugging? It would be difficult to rip off all code
 related to pools, and I think that is not needed.
 configure options are more like for endusers, imho. Should we do that?

> Being able to disable memory pools is badly needed when debugging memory
> allocation problems. Most malloc debuggers are a lot better than memory
> pools at indicating where a thing was allocated and when, and also
> allows you to find references to freed memory or memory over/underruns.

 Yes. Even more so with chunked pools. They are very sensitive to free
 item tampering.

------------------------------------
 Andres Kroonmaa <andre@online.ee>
 CTO, Delfi Online
 Tel: 6501 731, Fax: 6501 708
 Pärnu mnt. 158, Tallinn,
 11317 Estonia
Received on Fri Apr 27 2001 - 17:03:55 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:13:50 MST