On Sun, Sep 29, 2002, Cory Albrecht wrote:

> --- "Dr. Stephen Henson" <[EMAIL PROTECTED]> wrote:
> > On Sat, Sep 28, 2002, Christian Hohnstaedt wrote:
> 
> > > Same here on a WIN98 box, 
> 
> > > seems like all PEM_write_XXX functions do segfault.
> > > OpenSSL was compiled with the VC++ .dsp files provided
> > > by  http://www.iconsinc.com/~agray/ossldev/
> 
> > > the same code runs without errors on linux
> 
> > Read the FAQ.
> 
> For me it's any of the *_fp() functions which crash - something like
> PEM_write_bio_PrivateKey() or PEM_read_bio_X509() work fine. And it's
> all of the functions which use a FILE* argument instead of a BIO* which
> crash on me.
> 
> Since I already knew it wasn't the single threaded vs. multi-threaded
> problem mentioned in the FAQ, I wondered briefly if it was related to
> OPENSSL_NO_FP_API (I had seen that in the headers while lookign for
> otehr things), but since my program linked properly with nothing left
> unfound I decided it couldn't be that.
> 
> This wasn't a big problem for me since I had no overwhelming reason to
> have to use a FILE* instead of a BIO* - all I was doing was opening the
> file, reading in/writing out the certificate/key and immediately
> closing the file.
> 

Since the Win32 crashing question gets asked about once per week the initial
response is to point someone at the FAQ which covers almost all cases.

Things like FILE * crashing on Win32 only are almost always done to a runtime
library conflict of some kind. Either multi/single thread or debugging/non
debugging or some DLL linked in somewhere with a conflicting RTL.

Try compiling OpenSSL in the conventional way as mentioned in INSTALL.W32 and
see if it still happens.

Steve.
--
Dr. Stephen Henson      [EMAIL PROTECTED]            
OpenSSL Project         http://www.openssl.org/~steve/
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to