About "PEM_read_privatekey, PEM_read_X509, etc" Problem

[???]

Title: Message

This document is in INSTALL.W32.   If you don't use the multithreaded DLL runtime library (/MD option) your 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. If  you want to build your openssl application on Win32 with VC++, Add '/MD' option on your project.