> It should never happen in practice unless something bad has happened such as > memory corruption. For example there is a variable which simulates a > failure > of the test which might be overwritten if something writes over memory.
It is not memory corruption from what I see. I had added a log when memcmp would fail, and that's what I see. So, the memcmp is indeed failing. Is this DRBG code thread-safe? If it isn't, then that could be the cause. Thanks, Neha. -- View this message in context: http://openssl.6102.n7.nabble.com/FIPS-OpenSSL-default-DRBG-continuous-test-failing-tp46646p46711.html Sent from the OpenSSL - Dev mailing list archive at Nabble.com. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
