Okay, the background is that I've ported OpenSSL to the Macintosh (yeah, yeah-- I know). Even stranger yet, I'm using it as a library for a code resource which is loaded by another application to do an 'https' query of a server (if it means anything to anyone reading this, I'm working on an XFCN). Things work well as long as I ensure the library is freshly reloaded every time; however, for performance reasons, it's nice to keep the code library cached in-memory and use it again later. The problem is that on the second or third usage of the library, things break. Now, obviously there is a problem with some static variables, since things work well when they're set up correctly to their compiled values. If you're curious, I drop into my debugger when I hit the this point in lh_insert(): rn=getrn(lh,data,&hash); I'm quite sure the problem is actually within getrn(), but my debugger only notices the return to that point in lh_insert(). Anyway, the question I have is whether anyone has any idea what I need to clean up or uninitialize when I'm done with OpenSSL so that the next time I enter it, things will not break. Any takers? I'm betting the answer is that it's not worth the effort. In the meantime, I'll do the obvious thing and just keep a clean copy in-memory, clone it, then use and discard the clone (and repeat....). -Roy p.s. I'm using 0.9.4 now, so I'm pretty much ready to contribute the changes back to the project-- Whoo Hoo! ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
