hew Allen
To: openssl-users@openssl.org
Sent: Wed, April 21, 2010 4:00:10 PM
Subject: Re: Socket left in CLOSE_WAIT state...
-- Original Message --
To: (openssl-users@openssl.org)
From: Stuart Weatherby (stuart_weathe...@yahoo.ca)
Subject: Re: Socket left in CLOSE_WAIT state...
Date: 2
Shutdown disables the ability to read, write (or both) on a socket. However,
shutdown() does not close the socket. to release the socket descriptor back to
the OS you also need to call closesocket();
- Original Message
From: Matthew Allen
To: openssl-users@openssl.org
Sent: Wed, Apr
2010, Stuart Weatherby wrote:
> Thanks Steve,
>
> After commenting out lines 24 & 25 there is still unfree'd memory:
>
http://www.openssl.org/support/faq.html#PROG13
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available se
enssl.org
Sent: Mon, April 19, 2010 3:12:53 PM
Subject: Re: possible user error / memory leak using RSA_new() and RSA_free();
On Mon, Apr 19, 2010, Stuart Weatherby wrote:
> Hi List,
>
> I am trying to figure out why there is a memory leak using RSA_new & RSA_free:
> Below is
Hi List,
I am trying to figure out why there is a memory leak using RSA_new & RSA_free:
Below is a code sample (which will produce a memory leak) and the relevent
valgrind output. I have checked the documentation but I still fail to see my
error.
As I understand the docuumentation, RSA_free()
