diff options
author | Bodo Möller <bodo@openssl.org> | 2000-01-13 09:18:42 +0000 |
---|---|---|
committer | Bodo Möller <bodo@openssl.org> | 2000-01-13 09:18:42 +0000 |
commit | 22e219d90f1ea5d3b2f4abb72c846a436ea33eff (patch) | |
tree | a370818ed688bf8cf0db18810c8ab6d5ee393667 | |
parent | 036c8d7e7b68f0db9a6322599c6a5095a98670d1 (diff) | |
download | openssl-22e219d90f1ea5d3b2f4abb72c846a436ea33eff.tar.gz |
Note about CRYPTO_malloc_init
-rw-r--r-- | INSTALL.W32 | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/INSTALL.W32 b/INSTALL.W32 index 4f30700885..a54ea11cb8 100644 --- a/INSTALL.W32 +++ b/INSTALL.W32 @@ -165,6 +165,13 @@ One final comment about compiling applications linked to the OpenSSL library. If you don't use the multithreaded DLL runtime library (/MD option) your - program will almost certainly crash: see the original SSLeay description - below for more details. - + program will almost certainly crash because malloc gets confused -- the + OpenSSL DLLs are statically linked to one version, the application must + not use a different one. You might be able to work around such problems + by adding CRYPTO_malloc_init() to your program before any calls to the + OpenSSL libraries: This tells the OpenSSL libraries to use the same + malloc(), free() and realloc() as the application. However there are many + standard library functions used by OpenSSL that call malloc() internally + (e.g. fopen()), and OpenSSL cannot change these; so in general you cannot + rely on CYRPTO_malloc_init() solving your problem, and you should + consistently use the multithreaded library. |