On Wed, Dec 21, 2011 at 1:26 PM, nandan shantharaj <iamnand...@gmail.com> wrote: > Hi All, > SSL_CTX_load_verify_locations() is causing memory leak in my > application. Folowing is the function trace. > > 262 1072 bytes leaked in 4 blocks (2.25% of all bytes leaked) > 263 These range in size from 268 to 268 bytes and are allocated > 264 #0 0x800003ffefb9b6b8 in default_malloc_ex() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 265 #1 0x800003ffefb9bd10 in CRYPTO_malloc() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 266 #2 0x800003ffefc1a808 in BUF_MEM_grow() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 267 #3 0x800003ffefc715a4 in X509_NAME_oneline() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 268 #4 0x800003ffefc4af24 in x509_cb() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 269 #5 0x800003ffefc56be0 in ASN1_item_ex_d2i() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 270 #6 0x800003ffefc56730 in ASN1_item_d2i() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 271 #7 0x800003ffefc4af90 in d2i_X509() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 272 #8 0x800003ffefc68e70 in PEM_X509_INFO_read_bio() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 273 #9 0x800003ffefc7ca8c in X509_load_cert_crl_file#HLO_CL_#i2_0x1() > from /opt/omni/lib64/libcrypto.sl.0.9.8 > 274 #10 0x800003ffefc7c170 in by_file_ctrl() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 275 #11 0x800003ffefc78ff8 in X509_LOOKUP_ctrl() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 276 #12 0x800003ffefc6f6b8 in X509_STORE_load_locations() from > /opt/omni/lib64/libcrypto.sl.0.9.8 > 277 #13 0x800003ffefa9ea8c in SSL_CTX_load_verify_locations() from > /opt/omni/lib64/libssl.sl.0.9.8 > 278 #14 0x40000000000b4750 in _stub_SSL_CTX_load_verify_locations() at > ipc.c:152 > 279 #15 0x40000000000ce190 in SecIpc_SSL_ApplyCertConfig() at > ipc.c:10669 > 280 #16 0x40000000000ce7f8 in SecIpc_SSL_Accept() at ipc.c:10803 > 281 #17 0x40000000000cf9a8 in SecIpcNegotiateProtoAccept() at > ipc.c:11304 > 282 #18 0x40000000000cfd88 in SecIpcNegotiateProtoAcceptPeek() at > ipc.c:11423 > 283 #19 0x40000000000d0274 in SecIpcWaitForIpcEvent() at ipc.c:11574 > 284 #20 0x4000000000047fa8 in GetRequest() at daemon.c:1555 > 285 #21 0x4000000000046e00 in main() at daemon.c:1250 > 286 #22 0xc00000000000a784 in $START$() from /usr/lib/pa20_64/dld.sl > Both the ssl and context variables are freed in application with the > following calls > SSL_free() and SSL_CTX_free(). > > Still GDB reports memory leak. Do i have to call any other function to > release the memory or if it's actual memory leak in OpenSSL, is there a fix > for the same. If you talk with the GDB folks, they will probably recommend a dedicated leak checker such as Valgrind (http://people.redhat.com/jkratoch/DeveloperConference2011-debug.pdf).
Jeff ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
