The openssl FAQ and INSTALL.W32 warn about a corruption problem if an app does not use the multithreaded DLL option /MD, given that the build of openssl uses it. However, I am seeing the exact opposite of this problem. This is a desperate appeal for help.
I build openssl using the following steps: cd <opensslDir> vcvars32 perl Configure -DZLIB -I<zlibDir> VC-WIN32 ms\do_ms nmake -f ms\ntdll.mak This causes it to be built using /MD. I link with a ZLIB that has also been built using /MD. I get what appears to be a C++ exception upon return from SSL_write. This cannot be, since openssl is written in C. I presume that some sort of corruption occurs. When my own app links with a ZLIB that does not use /MD, the problem goes away. I notice that someone else posted that there might be memory corruptions in 0.9.7b so I tried the snapshot that was made last night. Same problem. I also tried adding a call to CRYPTO_malloc_init() as the first line in subroutine main(). Again, no effect. Any ideas? Regards, Andrew Marlow ---- There is an emerald here the size of a plover's egg! ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
