Re: leaks in slapd

[Howard Chu <hyc@symas.com>]

Pierangelo Masarati wrote:
>  Howard Chu wrote:
>
> > For 64 bit builds you might try my current FunctionCheck (1.5.4)
> > instead, for leak tracing. valgrind 3.0 is still very limited on
> > AMD64, and its memory layout makes using it on large databases
> > pretty much impossible.

>  Howard,

>  one "leak" (actually, reachable memory that is not freed) which I'm
>  not sure to know how to fix is here:

I think this is taken care of now. I'm still seeing an odd one in 
back-bdb/db_open that I haven't tracked down yet.

>  ==18946== 1912 bytes in 51 blocks are still reachable in loss record
>  6 of 7 ==18946==    at 0x1B9046C1: calloc (vg_replace_malloc.c:176)
>  ==18946==    by 0x820AD43: ber_memcalloc_x (memory.c:286) ==18946==
>  by 0x80973D6: ch_calloc (ch_malloc.c:103) ==18946==    by 0x8067E68:
>  config_include (bconfig.c:2302) ==18946==    by 0x806DDDE:

--
 -- Howard Chu
 Chief Architect, Symas Corp.  http://www.symas.com
 Director, Highland Sun        http://highlandsun.com/hyc
 OpenLDAP Core Team            http://www.openldap.org/project/