> I must ask if you compiled OpenSSL with the 'PURIFY' option. My build is substantially silenced: only two distinct valgrind 'uninitialiased value' errors when using my custom rand replacement. This is throughout a full regression test of my software.
I did not use the purify option - there are only two purify ifdefs in all the openssl code. Both unrelated. This problem is in BM_get_flags() - flags should be initialized, surely? Thanks -paul Sent via my BlackBerry from Vodacom - let your email find you! -----Original Message----- From: Brad House <[EMAIL PROTECTED]> Date: Sat, 19 Jan 2008 15:40:12 To:openssl-dev@openssl.org Subject: Re: Two valgrind warnings in OpenSSL - possible bug??? > I compiled OpenSSL (0.9.8g) with my own random number engine - in order > to generate > pseudo random numbers that are not based on unitialized values (if you > run openssl > without doing this you get infinite warnings - of course). > > The results are as follows > The code that gives the error is the BN_get_flags() macro > (see bn_div.c extract about line 190 below): > > Could this be highlighting a bug in OpenSSL????? Without actually looking into this first, I must ask if you compiled OpenSSL with the 'PURIFY' option. That will silence valgrind significantly. -Brad ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
