|
From: Nicholas N. <nj...@cs...> - 2005-10-17 15:16:32
|
On Mon, 17 Oct 2005, Nick Lindridge wrote: > Looking for any hints on why valgrind may be reporting hundreds of bogus > errors in some C++/C code, compared to purify working and reporting > flawlessly on the same code on the same machine. > > The code was tested with both older valgrinds and the latest valgrind 3 on > a code base with openssh, libssh2, and other code, The only thing I can think of is that I think SSL (which ssh uses?) deliberately uses uninitialised memory as a source of entropy for some random number generator, or something like that. So it's possible that these are propagating throughout the program in various ways. If it is the case, the way to fix it would be to add client requests to SSL (eg. VALGRIND_MAKE_READABLE) to mark the uninitialised memory as being initialised. Nick |