----- Original Message ----- > Anyway, saying that OpenSSL doesn't leak *in
debug mode* is not
> entirely true. The memory debugging code does create at least one
> hash table and at most two, and it never free's them. I've been
> pondering adding a CRYPTO_mem_cleanup() or something like that, but
> how often do you run debugging code in a production? Would it really
> be worth the while? You tell me.
>
Nope. It would be a nice to have, but we can live without that.
The debugging memory is interesting when you are implementing services on
top of OpenSSL's "low level" crypto routines, which I'm planning to do, and
I want to be sure I'm not leaking memory.
One the reason of these leaks is identified, and I know they're only linked
to the debugging version, it's OK for me.
Thanks for the explanations.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
