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

Re: memory leak problem.



On Mon, Apr 22, 2002 at 09:54:40AM +0530, A.Gayathri wrote:
% Good day. My problem is now with the openldap api. Even when I call
% ldap_init and immediately ldap_unbind, I get the following memory leaks
% with mtrace. I'm using openldap-2.0.23 and redhat-6.2.
% 
% Memory not freed:
% -----------------
%    Address     Size     Caller
% 0x080b8848     0x28  at 	libraries/liblber/memory.c:277
% 0x080b8878      0x5  at 	libraries/liblber/memory.c:227
% 0x080b8888      0xa  at 	libraries/liblber/memory.c:227
% 0x080b8898      0x1  at 	libraries/liblber/memory.c:227  

AFAIK, ldap_init() followed by ldap_unbind() should free anything allocated.

Can your memory profiler give a backtrace for these calls? memory.c:227 is
the generic BER calloc() routine, which could be called most anywhere.

john
-- 
John Morrissey          _o            /\         ----  __o
jwm@horde.net        _-< \_          /  \       ----  <  \,
www.horde.net/    __(_)/_(_)________/    \_______(_) /_(_)__