Re: valgrind reports failures on examples

Syscall write(buf) contains uninitialized or unaddressable bytes doesn't mean that it's sending uninitialized memory. I've run across this one a number of times when dealing with socket code. If you allocate say a 64k buffer (~ max datagram size) and then call send() with a length of 100 byt

RE: valgrind reports failures on examples

> 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 > unaddressa

Re: valgrind reports failures on examples

Scott Lamb wrote: Maybe I should also mention that my library and unit tests are multi-threaded. (I have defined the appropriate locking callbacks.) I could easily see how that'd aggravate any problems. I forgot to mention: I'm also using a debug malloc library (). So wh

Re: valgrind reports failures on examples

Michal Dobaczewski wrote: Scott Lamb wrote: Has anyone run these examples through valgrind before? Have you found similar problems? Yes, I've had similar problems with openSSL 0.9.6. I was getting this kind of error messages when runing both my appllication and openssl s_client under valgrind

Re: valgrind reports failures on examples

Scott Lamb wrote: Has anyone run these examples through valgrind before? Have you found similar problems? Yes, I've had similar problems with openSSL 0.9.6. I was getting this kind of error messages when runing both my appllication and openssl s_client under valgrind. So far I was unable to fi