https://bugs.openldap.org/show_bug.cgi?id=10404
--- Comment #7 from Howard Chu <[email protected]> --- (In reply to tomas.bjorklund from comment #6) > > You should repeat this test using a debug build, without stripping symbols. > > We need the symbol information to get anything useful. > > I hope this is better :) Yes, that's got all the necessary info now thanks. Unfortunately the output doesn't make a lot of sense, it shows all of the leaked memory is actually owned by libsasl2, and it's all traced back to a call from slapd main.c:265 which only occurs once, at startup time. As such any of the memory allocated by that call should only be getting allocated once, not multiple times. Since BerkeleyDB hasn't been supported in 2.6, what OpenLDAP version were you using previously? And what version of Cyrus SASL have you been using? Can you test again without using SASL or GSSAPI? > > /tmp/mdump /usr/sbin/slapd ml.* > fncdump: Cant open linux-vdso.so.1 > > Memory leaks (49508 total): -- You are receiving this mail because: You are on the CC list for the issue.
