On Friday 27 July 2001 10:04 am, you wrote:

> Hi all.
>
> I followed instructions in
> http://marc.theaimsgroup.com/?l=openssl-users&m=99494629705968&w=2
> to find memory leaks in my application.
>
> The output generated by CRYPTO_mem_leaks_fp (as show below) tells me
> that 899 bytes were leaked but the sum of all reported bytes is 1608. Is
> that a bug or I'm reading the output incorrectely?
>
> CRYPTO_mem_leaks_fp output:
>
>    32 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12D08
>   805 file=err\err.c, line=769, thread=1, number=65, address=00D136EA
>    16 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12920
>     5 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D126A2
>    60 file=lhash\lhash.c, line=119, thread=1, number=86,
> address=00D135BE
>    13 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D12872
>    61 file=lhash\lhash.c, line=121, thread=1, number=64,
> address=00D13642
>    21 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D12A42
>    29 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D12C12
>     2 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D125F4
>    10 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D127C4
>    18 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12994
>    26 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12B64
>     7 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D12716
>    15 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D128E6
>     0 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D124E6
>    23 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D12AB6
>     4 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12668
>    62 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D136B0
>    12 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12838
>    20 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12A08
>     1 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D125BA
>    28 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12BD8
>     9 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D1278A
>    31 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D12578
>    17 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D1295A
>    25 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D12B2A
>     6 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D126DC
>    14 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D128AC
>    33 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D12D42
>    22 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12A7C
>    30 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12C4C
>     3 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D1262E
>    59 file=err\err.c, line=699, thread=1, number=264, address=00D13488
>    11 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D127FE
>    19 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D129CE
>    27 file=lhash\lhash.c, line=193, thread=1, number=12,
> address=00D12B9E
>     8 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12750
>    24 file=objects\o_names.c, line=164, thread=1, number=12,
> address=00D12AF0
> 899 bytes leaked in 39 chunks
>
> []`s Gleison
> [EMAIL PROTECTED]


This isn't the answer to your question but I think I can help with your
leaks.  Make sure you are calling EVP_cleanup and ERR_remove_state(0)
before you check for leaks.  These should free the algorithms and error
information loaded at startup.


-Chris

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to