You need to do the following in your code -
at start:
CRYPTO_malloc_debug_init();
CRYPTO_dbg_set_options(V_CRYPTO_MDEBUG_ALL);
CRYPTO_mem_ctrl(CRYPTO_MEM_CHECK_ON);
at end:
CRYPTO_mem_leaks_fp(stderr);
This produces tons of memory references that you'll have to sort out what
are valid and which you think are leaks. I found that I could reformat
the data with awk and do a diff between a number of sessions to see where
the memory was growing.
Steve
On Wed, 11 Jul 2001, C. Gould wrote:
> I've been tuning up my code and am now trying to locate sources of what
> appears to be some leaking memory. I've searched the archives and saw
> a bit of discussion about compiling with -DCRYPTO_MDEBUG set. When I did
> so there was no indication that any sort of leaks were even trying to be
> detected. Any suggestions as to how I can sort this situation out?
>
> Chris
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
