[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: memory leak in libldap when handling referral -- 2.1.8
- To: "Andreas" <andreas@conectiva.com.br>
- Subject: RE: memory leak in libldap when handling referral -- 2.1.8
- From: "Su Li" <sli@rim.net>
- Date: Thu, 31 Jul 2003 09:55:36 -0400
- Cc: <openldap-software@OpenLDAP.org>
- Content-class: urn:content-classes:message
- Thread-index: AcNXX/lsa0Kmr82gQ76gpiY/yvP9mgACwrcg
- Thread-topic: memory leak in libldap when handling referral -- 2.1.8
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?
Thanks,
Su
-----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: