Dror wrote:
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
From: "Dror" [EMAIL PROTECTED]
drorotmi The functions interface (defined in crtdbg.h) is as follow:
drorotmi void *_malloc_dbg( size_t size, int blockType, const char *filename,
drorotmi int linenumber );
drorotmi void *_realloc_dbg( void *userData, size_t newSize, int blockType,
drorotmi const
Oh, I see what you mean, those are so to say replacements for malloc()
and friends... Hmm... Actually, this is doable through yet another
call level, but it also adds another level of complication.
Precisely.
Dror,
I've made a change that allows for the kind of functionality you
requested. It will be available in tonights snapshot, or if you want
to rsync it immediately...
The requirements for you will be to add the following code to your
application (and remove the CRYPTO_set_mem_debug_functions()
And do what with it? It would become some kind of OpenSSLish value
You're right, I misinterpreted your previous answer.
I'll check it as soon as I can fetch it and will inform you.
TAL
Dror
__
OpenSSL Project
