From: "Dror" <[EMAIL PROTECTED]>
drorotmi> Yes, this is what I ment with the workaround. I've done this
drorotmi> at the beginning.
That is the way to work within OpenSSL as it's currently defined.
drorotmi> The disadvantages (in VC environment) are:
drorotmi> 1.) that the memory leaks report appears in two places: the
drorotmi> leaks occurred in the application (with the file name and
drorotmi> line number) together with those occurred in OpenSSL
drorotmi> (without the file name and line number ) on the debug output
drorotmi> window and those of OpenSSL in a specified BIO (even in a
drorotmi> BIO that writes into debug output window, it is not very
drorotmi> convenience, since it will be written twice).
I'm not sure I understand. Naturally, the OpenSSL-specific debugging
hooks are made for OpenSSL primarely. If you want to get the benifits
from within your application, you need to use the functions
OPENSSL_malloc(), OPENSSL_realloc() and OPENSSL_free() for memory
handling instead of malloc(), realloc() and free(). The rule of thumb
is: if you want to get OpenSSL-specific feature, you need to use the
corresponding OpenSSL functions/macros. Then I'm not really sure what
the "without file name and number" means. They're certainly provide
to the hooks/callbacks.
drorotmi> 2.) The windows programmer can not compile a debug version
drorotmi> that will give this quite important information per default
drorotmi> and in a way that he use to detect the leaks (that could be
drorotmi> very usefull also in bug reports).
Uhmm, I assume it's "a debug version" of OpenSSL. In what way can't
you do that?
drorotmi> Another alternative for this issue is to provide an
drorotmi> interface for malloc_func & co. that matches the CRL
drorotmi> library, so the programmer could assign those methods, this
drorotmi> however, will require more work.
Uhmm, exactly what kind of interface are you after? OpenSSL has hooks
all over the place basically, and just provides internal defaults.
Please assume that I know nothing about the CRT library, and am not
likely to know anything about it in the near future, but that I can
understand precise examples and code :-).
drorotmi> Well it is a sort of *nice to have item*, as a window
drorotmi> programmer, I will appreciate it very much if this will be
drorotmi> available.
Depends on what it is you want exactly.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
