> Most of the errors seem to be in one of these classes: > - Conditional jump or move depends on uninitialised value(s) > - Use of uninitialized value > > When I run it in my own code (which seems correct to me), I > see this also: > - Syscall param write(buf) contains uninitialised or > unaddressable byte(s) > > which is pretty disturbing to me, since that means it's > actually sending > uninitialized memory. >
Can't speak for all the errors you are seeing but these "uninitialised" memory errors are generally the result of OpenSSL's random number generation. Random bytes generally get xor'ed into uninitialised (freshly malloc-ed) memory and valgrind keeps track of that fact (xor-ing a known value with an uninitialised value results in an uninitialised value as far as valgrind is concerned). When it's time to use that memory (as when you call a system function), an error is reported. As I said, can't speak for your setup, but that's what I found when I tracked down similar issues on my setup. -lee ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
