From: Bodo Möller <bodo@openssl.org>
Date: Thu, 13 Jan 2000 09:18:42 +0000 (+0000)
Subject: Note about CRYPTO_malloc_init
X-Git-Tag: OpenSSL_0_9_5beta1~289
X-Git-Url: https://git.openssl.org/?p=openssl.git;a=commitdiff_plain;h=22e219d90f1ea5d3b2f4abb72c846a436ea33eff;hp=036c8d7e7b68f0db9a6322599c6a5095a98670d1

Note about CRYPTO_malloc_init
---

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.