|
Hi
I am using openldap 2.2.4.33 with cyrus-sasl 2.1.25 to
do a sasl bind and get the following valgrind leak message. Looking
through the source it seems to be a variable only used inside the openldap
library and not related to what I provide to ldap_sasl_interactive_bind_s.
==14039== 34 (32 direct, 2 indirect) bytes in 2 blocks are definitely lost
in loss record 561 of 666
==14039== at 0x4C2C27B: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==14039== by 0x558E764: ber_memalloc_x
(memory.c:228)
==14039== by 0x558A8B7: ber_get_stringal
(decode.c:582)
==14039== by 0x558AFF5: ber_scanf (decode.c:806)
==14039== by 0x535535D: ldap_parse_sasl_bind_result
(sasl.c:327)
==14039== by 0x5351FE1: ldap_int_sasl_bind
(cyrus.c:551)
==14039== by 0x5355810: ldap_sasl_interactive_bind
(sasl.c:474)
==14039== by 0x5355A0C: ldap_sasl_interactive_bind_s
(sasl.c:511)
==14039== by 0x44DDC9: tool_sasl_bind (ldap.c:2338)
Is that a real memory leak or is it something I did wrong ?
Thank you
Markus
|