Well, I am definiately leaking stuff related to BIOs, among other things. But, why, is what I'm wondering.
________________________________ From: owner-openssl-us...@openssl.org on behalf of Dr. Stephen Henson Sent: Sun 4/19/2009 1:53 PM To: openssl-users@openssl.org Subject: Re: tracking down memory leaks On Sun, Apr 19, 2009, Rene Hollan wrote: > Well, I tried what you suggested and it still makes no difference. > > One thing I am doing is creating a single SSL_CTX and using it for multiple > SSL sessions. I presume the SSL_CTX is reference counted. > > I will try with a debug version of the SSL libraries thart include symbols > with default_malloc_ex replaced with malloc and see where these things are > getting allocated. > Have you tried OpenSSL's builtin leak checker? You basically call: CRYPTO_malloc_debug_init(); CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_ON); at the start and then: CRYPTO_mem_leaks(bio_err); or CRYPTO_mem_leaks_fp(stderr); after everything has been freed up. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Homepage: http://www.drh-consultancy.demon.co.uk <http://www.drh-consultancy.demon.co.uk/> ______________________________________________________________________ OpenSSL Project http://www.openssl.org <http://www.openssl.org/> User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
<<winmail.dat>>
