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

Re: leaks in slapd

--On Tuesday, July 19, 2005 4:54 PM +0200 Pierangelo Masarati <ando@sys-net.it> wrote:

I'm trying to have slapd operate with 0 leaks under valgrind.  Currently,
it appears that the only remaining leaks are in limits handling, which
lack a destroy method (and in PERL related libraries/backend, which I'm
not going to consider right now), although I didn't check all slapd
functionalities (how could I?).  I'd appreciate if anybody can point me
to (potential) leaks that I missed.  I'm working with HEAD, of course,
but I intend to backport all operation-relted leaks to RE22.

Running OpenLDAP 2.3.4 as a 64 bit build on an AMD opteron, I could core dump slapd repeatedly using SASL/GSSAPI binds. This problem only occurs on 64 bit builds (32 bit builds run for hours with no issues), and appeared to be coming from Heimdal, rather than OpenLDAP (I was using heimdal-0.7). I put it under valgrind-3.0 (you can check this out from their subversion respository), and tried to get leak data out of slapd, but was unable to find anything other than the bits you've noted as well. The heimdal folks did give me two patches for leaks they found in a 32 bit environment, but neither of those patches solved the problem. So at this point, it is not clear where specifically the problem lies (somewhere between slapd & heimdal).


-- Quanah Gibson-Mount Principal Software Developer ITSS/Shared Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and blind
faith, the imagination." -- Ursula K. Le Guin