> <Clipped earlier communication> > >>> >>> What OS is this running on? That error can be caused by a DLL being loaded >>> to >>> an address that is already in use under Windows and relocation would >>> invalidate the signature. >>> >>> You can work around that by specifying an alternative load address when the >>> DLL is compiled. >>> >> >> This is Win2K3 on a virtual machine. I thought about the load address >> and is looking through ProcessExplorer to see where the conflict is. >> Will try a recompile. >> > > One more query: Shouldn't fips_test_suite.exe report failure as well? > That passes without any issues. >
Sorry for fragmenting my queries. Just figured out that there is another DLL loaded at 0xFAF0000 which occupies 0x44000 bytes. So I guess that explains why libeay32.dll is not getting loaded at 0xFB00000. Now my query is if I recompile it with a different base address, isn't there a rare possibility that I might see this issue in some other environment? Anyway I can be sure that this will work always? Thanks, Vivek ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
