From: "Dror" <[EMAIL PROTECTED]>
drorotmi> It works perfectly!!!
Cool!
drorotmi> Thank you very very much effort.
YW. HAND.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +4
Hi Richard,
It works perfectly!!!
I couldn't compile the snapshot (some linker errors), so I just added
the involved files into the last release version.
I had to update the DEF file with the new function
(CRYPTO_set_mem_ex_functions) as well, in order to be able to
import it into the applic
> 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
From: "Dror" <[EMAIL PROTECTED]>
drorotmi> _NORMAL_BLOCK = 1 and _CLIENT_BLOCK = 4 are the
drorotmi> options.
drorotmi>
drorotmi> Question: If you do it this way, why don't you add the block type
drorotmi> also as an argument instead of a define?
And do what with it? It would become some
Richard,
>
> 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...
I wouldn't mind to do it immediately, but I do not know what is
rsync .
>
> #define OPENSSL_BLOCKTYPE 0 /* I've n
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()
>
> 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.
>
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>
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
>
> 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
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
>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, t
Ow. Sorry list! Private mail gone awry. Fell victim to the reply-to
header.
//oscar
Oscar Jacobsson wrote:
>
> Richard Levitte - VMS Whacker wrote:
> > Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
>
> Är mitt antagande att "ex", likt tyskans motsvarighet "aus", är en
> da
Richard Levitte - VMS Whacker wrote:
> Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Är mitt antagande att "ex", likt tyskans motsvarighet "aus", är en
dativbildande preposition riktig, månne?
//oscar, ständigt på jakt efter nya sätt att märka ord. ;-)
__
From: "Dror" <[EMAIL PROTECTED]>
drorotmi> I know there are the debug callbacks and CRYPTO_dbg_xxx
drorotmi> functions one could use for workaround but still, as a window
drorotmi> programmer, I find the memory handling of the CRT library very
drorotmi> comfortable.
So, what you want to do is
Hi
First I would like to thank and complement you all for your great
product.
I'm using OpenSSL with VC++ 6.0 compiler and
have a problem with Memory leaks detecting: they are reported in
the debug output window on program exit but without the link to the
location (no file and line number de
16 matches
Mail list logo
