"C. Gould" wrote:
>
> Ok, thanks a bunch. I got that working, and found what appears to be a
> decent number of memory leaks. I know my application is leaking memory,
> but the output i'm getting isn't really of much use to me. Could anyone
> assist me in interpreting the snippet of output I've attached below.
> There is more, but I left it out because of space considerations. What is
> the best way to track down the source of these leaks. Is it safe to
> assume these are my own fault, or could the OpenSSL library be leaking
> some memory?
>
[stuff deleted]
These are probably your fault :-)
The o_names.c references are usually indicative of a missing
EVP_cleanup() call.
Its hard to tell the cause of the others because of the omissions. Could
be some hefty ASN1 object not being freed such as a certificate or
something that contains it like an SSL or SSL_CTX structure.
You get to recognise these after a while. Generally you should look for
some top level structures not being freed first like SSL_CTX, SSL, X509,
EVP_PKEY and so on. After that most of the references should disappear.
Occasionally one of them is caused by an actual bug in the library at
which point I normally use gdb and conditional breakpoints to trace the
cause.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
