Probably the best way to figure out what's going on here is to get the C SDK source code from CVS, compile it with debugging turned on, get purify to give more detailed info about where the leak is happening, and then file a bug in Bugzilla.
Dan hedi <[EMAIL PROTECTED]> writes: > hmmm ... OUPS ! > > the stack that make a probleme is linked to ldap_simple_bind_s, > nsldapi_try_each_host, gethostbyname_r, ... malloc , this makes an amount of > 19ko ... > > ?idea ? > > Hedi. > . > > > hedi wrote: > > > Hi, > > some complementary information ... > > it seems to be the ldap_bind_s that doesn't free everything at the unbind > > call ... > > any idea ? > > > > Hedi. > > . > > > > hedi wrote: > > > > > Hi everybody, > > > > > > using CSDK 5.08 to reach a DS and read asynchronously some entries, a > > > memory leak occured (caught using purify plus) : > > > malloc rtlib.o > > > calloc rtlib.o > > > ber_alloc_t bprint.c > > > nsldapi_alloc_ber_with_options libldap50.so > > > read1msg result.c > > > wait4msg result.c > > > > > > could anyone tell me the different delete of mem free to in addition to > > > the ldap_msgfree, and the ldap_memfree for the found dns ? > > > > > > many thanks. > > > > > > Hedi. > > > . >
