On Fri, Jan 01, 2010 at 11:50:29PM -0500, Richard Salz wrote: > You're missing the point -- your comment is the height of irony, in a way. > > Use a suppression to make Valgrind shut up.
Maybe you should try to suppress that in valgrind before telling us what to do. Try running a simple program that gets a random number and then just prints it. Please also make sure you only suppress warnings caused by the PRNG and not all warnings. The standard way to suppress something in valgrind is to do that based on the stack trace. That stack trace contains no openssl functions in 99% of the time, and in the simple example above you will only see main and *printf. There is an alternative way to suppress something in valgrind and that is using the client request mechanism. This requires modifying the openssl code to embed some valgrind code at the point where you introduce the unintialised memmory and tell valgrind to ignore it. It seems very unlikely that you would like to do that. It would also be nice that someone looked at ticket 1642. Kurt ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
