__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
Hi,
I am having a bit of a trouble compiling the openSSL release 0.9.8e
under WinXP SP2.
The version of minGW's the gcc compiler I am using is 3.4.5-20060117-1
and the minGW32-make is 3.80.0-1.
For some reason the build tools use malformed file names such as
".\crypto\/cryptlib.h" (pay attention
> The function SSL_library_init() is observed to be introudcing
> memory leak in
> the application code. There is still some amount of memory leak left even
> after the series of cleanup calls suggested in the openssl FAQ.
>
> Can someone help understand that technically what is the problem
> in h
David Schwartz wrote:
The function SSL_library_init() is observed to be introudcing
memory leak in
the application code. There is still some amount of memory leak left even
after the series of cleanup calls suggested in the openssl FAQ.
Your first sentence is pretty funny though. How can
David Schwartz wrote:
The function SSL_library_init() is observed to be introudcing
memory leak in
the application code. There is still some amount of memory leak left even
after the series of cleanup calls suggested in the openssl FAQ.
Can someone help understand that technically what is the pr
Hi all,
In the test suite for some C++ classes I'm writing, I deliberately
invoke errors so I can test the error handling of my code. Doing
this means that I have also turned up an error in the OpenSSL
error handling.
The problem I was seeing was that I would invoke an error and
then in the nex
> diff -ru openssl-0.9.8e/ssl/ssl_rsa.c openssl-0.9.8e-hacked/ssl/ssl_rsa.c
> --- openssl-0.9.8e/ssl/ssl_rsa.c 2005-04-09 08:52:41.0 +1000
> +++ openssl-0.9.8e-hacked/ssl/ssl_rsa.c 2007-03-19
> 09:03:15.0 +1100
> @@ -728,6 +728,9 @@
> goto end;
>
David Schwartz wrote:
> Yep, this code is broken. That is not a particularly good fix though because
> errors can be lost.
I guessed as much :-).
> The simplest and probably best fix is a new function, ERR_get_count() that
> returns the number of entries on the error stack. Callers that need to
From: "David Schwartz" <[EMAIL PROTECTED]>
Reply-To: openssl-dev@openssl.org
To:
Subject: RE: Memory Leaks in SSL_Library_init()
Date: Tue, 20 Mar 2007 05:02:01 -0700
> The function SSL_library_init() is observed to be introudcing
> memory leak in
> the application code. There is still some
> Keepin it apart from the memory leak, i would like to know by
> example how a
> perfect cleanup can casue performance problems?
One common case goes like this:
1) You have an object you create very early in the library initialization.
2) The object is accessed a lot, and having to check if it
Hi! All,
Thanks very much for your inouts on this.
From: Darryl Miles <[EMAIL PROTECTED]>
Reply-To: openssl-dev@openssl.org
To: openssl-dev@openssl.org
Subject: Re: Memory Leaks in SSL_Library_init()
Date: Tue, 20 Mar 2007 17:18:40 +
David Schwartz wrote:
The function SSL_library_init()
Hi!
I have an example case where by the unused memoy allocated by
SSL_library_init when not freed, would accumulate.
There is an application which takes services from some of the libraries say
A, B and C.
These libraries are dynamically loaded and unloaded into the application as
and when
> Hi!
>
> I have an example case where by the unused memoy allocated by
> SSL_library_init when not freed, would accumulate.
>
> There is an application which takes services from some of the
> libraries say
> A, B and C.
>
> These libraries are dynamically loaded and unloaded into the
> applicatio
HI!
Thanks again for highlighting those issues. What would be the best way for
the application using those pluggins to avoid this issue of
SSL_library_init()?
regards
-Nitin
From: "David Schwartz" <[EMAIL PROTECTED]>
Reply-To: openssl-dev@openssl.org
To:
Subject: RE: Memory Leaks in SSL_
hi!
If we say that the call SSL_library_init() would initialze some data
structures which have process scope and are initialized only once.
In such case what is the problem in having a *single* function which exacly
cleans up those data structures at the time of process termination?
regards
> HI!
>
> Thanks again for highlighting those issues. What would be the
> best way for
> the application using those pluggins to avoid this issue of
> SSL_library_init()?
There are really two good ways that ensure that all problems are resolved.
Other ways just deal with problems as they crop up
16 matches
Mail list logo