Win32 Debug and Release builds now succeed.
PIII -- 500mhz
Winnt4
VC++6 sp4
I've been primarily looking at rsa_test, but I figure that most of the
failing tests have the same reason within RAND_poll()
The call stack:
rand_win.c - RAND_poll()
md_rand.c - ssleay_rand_bytes(unsigned char * 0x008a13b2, int 53) line
308
rand_lib.c - RAND_bytes(unsigned char * 0x008a13b2, int 53) line 101 +
17 bytes
rsa_pk1.c - RSA_padding_add_PKCS1_type_2(unsigned char * 0x008a13b0, int
64, unsigned char * 0x004035a4 ptext_ex, int 8) line 163 + 13 bytes
rsa_eay.c - RSA_eay_public_encrypt(int 8, unsigned char * 0x004035a4
ptext_ex, unsigned char * 0x0012fc58, rsa_st * 0x008a1a60, int 1) line
118 + 21 bytes
/*RSA_public_encrypt is the offending function within rsatest*/
RSA_public_encrypt(int 8, unsigned char * 0x004035a4 ptext_ex, unsigned
char * 0x0012fc58, rsa_st * 0x008a1a60, int 1) line 221 + 29 bytes
main(int 1, char * * 0x008a1ae0) line 244 + 27 bytes
mainCRTStartup() line 338 + 17 bytes
KERNEL32! 77f1b9ea()
Rand_Poll succeeds in the sense that the function completes,
but it never returns to ssleay_rand_bytes.
That is for the release build.
but the weirdness:
The debug build of the test and libeay32 pass rsatest with flying
colors.
The release build of rsatest is the one that fails.
I guess the key question is "what is occurring within RAND_poll for the
release build, as opposed to the debug build?
This is causing numerous test failures (anything relying on rand_poll) -
hopefully those folks working on the rand_poll weirdness earlier may be
able to shed some light. rand_poll is just giving me a headache....
Andrew
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
