[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#6330) slapd memory leak

hyc@symas.com writes:
> Merely increasing --num-callers isn't going to be sufficient to track this. 
> Since valgrind only reports leaks after a program exits,

The statement
will check for leaks at that point in the code.  The source file must
	#include <stdio.h>
	#include <valgrind/memcheck.h>
Then run the program under valgrind.

Regarding Cyrus SASL, I often ./configure --without-cyrus-sasl when
testing OpenLDAP, to shut valgrind up about SASL.  And I build Berkeley
DB with ../dist/configure --enable-umrw trying to shut it up about DB.