Re: [openssl.org #444] Win32 crash in PEM_read_X509

2003-01-18 Thread Michael Hunley via RT
Did you build a debug version of OpenSSL to link against for the debug build? This isn't handled automatically and you need to change it so it picks up and uses the debug libraries. Nope. that would explain it. criss-crossing MS multi-threaded libs is always a problem. I was using my debug

Re: [openssl.org #444] Win32 crash in PEM_read_X509

2003-01-17 Thread Michael Hunley via RT
Oh. That could account for the problem if OpenSSL is using the release build of the multi-threaded DLL's and my build of tunala is using the debug ones. I assume that was on the release build that you changed it, right? If on the debug build it should be correct to use the debug

Re: [openssl.org #444] Win32 crash in PEM_read_X509

2003-01-16 Thread Michael Hunley via RT
At 06:02 PM 1/15/2003 +0100, you wrote: If you just can't figure out Just to clarify. The posted patch is not so to say try-your-luck thing, it *does* get me through the ms\test. Understood, but it was unclear if it fixed the bug I posted in the PEM read, which is very likely a similar

Re: [openssl.org #444] Win32 crash in PEM_read_X509

2003-01-16 Thread Michael Hunley via RT
what did you do to get tunala to compile under Win32? Oh, that. I have been meaning to send Geoff the diff so it could get merged into the code base. I'll get to it some day. I had to wrap up sockets a little and make a few mods in ip. Here is a zip of it with the DSP. Some project

Re: [openssl.org #444] Win32 crash in PEM_read_X509

2003-01-15 Thread Michael Hunley via RT
Yes, that is a common one, though it was more prevalent in early MSVC7 (.NET) than in MSVC6. Another common problem is nested for loops. If you just can't figure out why a particular function is generating bad asm code, it is also possible to use #pragma optimize(off,0) (syntax might be

Re: [openssl.org #444] Win32 crash in PEM_read_X509

2003-01-14 Thread Michael Hunley via RT
That would certainly seem like a good first step. Have you traced into it at all? I.e. have you run with debug setup and seen a stack trace s.t. you know the function that is crashing and what variable is bad (a null pointer or something)? IF so, I may be able to provide the work around

[openssl.org #444] Win32 crash in PEM_read_X509

2003-01-08 Thread Michael Hunley via RT
html body Version 0.9.7 release version from Dec 31, 2002br Compiled using MSVC6 sp6 with Masmbr OS: Windows XP Homebrbr When PEM_read_X509 is called in certain circumstances you get an unhandled exception. I thought it was universal, but I found a test case in the quot;how to reproducequot;

Re: [openssl.org #444] Win32 crash in PEM_read_X509

2003-01-08 Thread Michael Hunley via RT
At 02:14 AM 1/9/2003 +0100, you wrote: [[EMAIL PROTECTED] - Wed Jan 8 22:09:03 2003]: html body Please don't post using HTML... Sorry, I did not know that I had. Wasn't this post from the tracker on the OpenSSL site? If not, it must be some setting I have accidentally on in Eudora or

[openssl.org #441] bug in win32 test

2003-01-07 Thread Michael Hunley via RT
OpenSSl v0.9.7 on Windows XP Home Using MSVC 6 sp 5 with Masm I'm not sure this is a bug or an issue with network connections. I compiled the source and ran the test app (ms/test.exe) and got the following error: test sslv3 ERROR in SERVER 2212:error:1408F455:SSL