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

RE: memory leak in libldap when handling referral -- 2.1.8

I would say that before you file such a bug, you should test this problem with a current version of OpenLDAP - 2.1.22. 2.1.8 is ancient, and there have been hundreds of problems fixed since it was released.


--On Thursday, July 31, 2003 9:55 AM -0400 Su Li <sli@rim.net> wrote:

Thanks Andreas,

I did submitted a bug report: memory leak when handle referral (ITS#2670)

I compiled the test client using libldap and liblber which passes in a
callback to rebind to new LDAP server during referral. I am not sure how
do you handle the new socket handle -- reuse or destroy?



-----Original Message----- From: Andreas [mailto:andreas@conectiva.com.br] Sent: July 31, 2003 8:32 AM To: Su Li Cc: openldap-software@OpenLDAP.org Subject: Re: memory leak in libldap when handling referral -- 2.1.8

If you believe you have found a bug, you should open a ticket at the ITS system: http://www.openldap.org/its/

On Wed, Jul 30, 2003 at 06:13:45PM -0400, Su Li wrote:
When handling referral, I saw libldap creates a new socket handle to the
new LDAP server, but after server, libldap seems did not delete the
referral socket or reuse the socket. So when I run memory leak checkor,
it shows the memory leak is in:

-- Quanah Gibson-Mount Senior Systems Administrator ITSS/TSS/Computing Systems Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html