You could compile a debug version of openssl and run your application with some debugger, depending on the compiler you use for your application. It all depends on a kind of a crash you experience. If it is some memory-related error, you could try Insure++ or IBM Purify.
HTH, Marin On Thu, Dec 16, 2010 at 2:30 PM, Lutz Jaenicke <jaeni...@openssl.org> wrote: > Forwarded to openssl-users for public discussion. > > Best regards, > Lutz > > ----- Forwarded message from "Yu, Eleanor" < > eleanor...@siemens-enterprise.com> ----- > > From: "Yu, Eleanor" <eleanor...@siemens-enterprise.com> > To: "r...@openssl.org" <r...@openssl.org> > Date: Tue, 14 Dec 2010 20:46:05 +0100 > Subject: Crash inside libeay32.dll > Thread-Topic: Crash inside libeay32.dll > Thread-Index: Acubx4u+8bEwbiTnTCW6vNwui8t7fw== > Accept-Language: en-US > acceptlanguage: en-US > > Hi, > > I am currently working on sending a request from a client to a server > through gSoap 2.7.17, and OpenSSL 0.9.8o on a Window 2008. However, we > experienced a crash inside the libeay32.dll. Is there a way we can gather > more information where exactly the crash is, and to isolate the problem? > > Thanks. > > Regards, > Eleanor > > > > ----- End forwarded message ----- > -- > Lutz Jaenicke jaeni...@openssl.org > OpenSSL Project http://www.openssl.org/~jaenicke/ > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org >
