> CRYPTO_set_mem_debug_functions(
> mydebug_malloc,
> mydebug_realloc,
> mydebug_free,
> NULL, NULL);
>
> (The two last are, of course, unless you want to be able to set and
> get option bits).
>
> When you write those callbacks, do not forget to check
> is_MemCheck_on().
Yes, this is what I ment with the workaround. I've done this at the
beginning.
The disadvantages (in VC environment) are:
1.) that the memory leaks report appears in two places: the leaks
occurred in the application (with the file name and line number)
together with those occurred in OpenSSL (without the file name
and line number ) on the debug output window and those of
OpenSSL in a specified BIO (even in a BIO that writes into debug
output window, it is not very convenience, since it will be written
twice).
2.) The windows programmer can not compile a debug version that
will give this quit important information per default and in a way that
he use to detect the leaks (that could be very usefull also in bug
reports).
Another alternative for this issue is to provide an interface for
malloc_func & co. that matches the CRL library, so the
programmer could assign those methods, this however, will require
more work.
Well it is a sort of *nice to have item*, as a window programmer, I
will appreciate it very much if this will be available.
Thanks for the comment.
Dror
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
