--- Patrick Li <[EMAIL PROTECTED]> escreveu: > Hi Lutz,
>
> Thanks for replying my question.
>
> I used purify as I figured out it may give me some
> directions on why my SSL
> client program is failing randomly. As purify
> reported 3 places there are
> reading from memory leaks.
...
Well, I don't have Purify, but NuMega BoundsChecker
(that is a similar product for M$-Windows). NuMega
reports "Read uninitialized memory" for this simple
code:
int i, x;
char buf [256];
for (i = 0; i < 256; ++i)
buf[i] = i;
for (i = 0; i < 256; ++i)
x = buf [i]; // <<--- NuMega reports
"uninitialized memory" when i = 191 (0xBF)
NuMega instruments the code, fills all buffers with
the byte 0xBF, and checks if you read 0xBF back. When
you read 0xBF the warning is given.
I think that Purify uses a similar method for
detecting uninitialized memory. The OpenSSL buffer has
binary data, maybe Purify had found the "uninitialized
memory" magic value.
_______________________________________________________________________________________________
Yahoo! GeoCities
Tenha seu lugar na Web. Construa hoje mesmo sua home page no Yahoo! GeoCities. É fácil
e grátis!
http://br.geocities.yahoo.com/
