AW: slap_sl_malloc

["Guus Leeuw jr." <Guus-Leeuw@gmx.de>]

> Von: owner-openldap-devel@OpenLDAP.org 
> [mailto:owner-openldap-devel@OpenLDAP.org] Im Auftrag von 
> Kurt D. Zeilenga
> Gesendet: zondag 29 augustus 2004 4:00
> An: Howard Chu
> Cc: openldap-devel@OpenLDAP.org
> Betreff: Re: slap_sl_malloc
> 
> 
> At 05:56 PM 8/28/2004, Howard Chu wrote:
> >I'm not entirely sure there's a leak. But it's very likely 
> that things 
> >aren't being freed in order, and it's difficult to verify a proper 
> >order now. Which implies that we maybe want 
> sl_malloc/sl_free to keep a 
> >free list, coalesce blocks, etc., etc. - all the things a 
> real malloc 
> >routine does.
> 
> I rather reuse an existing, decent, thread-aware allocator
> than write our own...
> 

As a test, I would suggest linking against electric_fence, should tell you
pretty much if there is a leak...

In the long run, we might include Boehm's garbage collector in general.
Pretty good garcol, as far as I've used it (SmallEiffel, and various stress
situations).

Just my 2 cents,
Guus

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004