[Date Prev][Date Next]
Re: (ITS#6330) slapd memory leak
> Merely increasing --num-callers isn't going to be sufficient to track this.
> Since valgrind only reports leaks after a program exits,
will check for leaks at that point in the code. The source file must
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.