SSL_SESSION_new(). You seem to have leaked four of them.
-Original Message-
From: C. Gould [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 18 July 2001 5:07 AM
To: [EMAIL PROTECTED]
Subject: Re: finding memory leaks
Ok, thanks a bunch. I got that working, and found what appears to be a
decent number of
"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
I don't know if you're writing a client or a server, but I'll just
describe what I did:
- hack up your code with some conditional memory debugging stuff such
that it accepts (or connects) a fixed number of times and then
calls CRYPTO_mem_leaks_fp() and exits.
- run the program for one connect
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 m
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 s
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
