> > How are you sure of this ? Did you manually remove the object code from > the library, or place an abort(); call at the points -DPURIFY is listed > to you can be sure that execution never gets there. >
Actually, I am trying to create an application that has one context per thread, where each thread handles many SSL connections. Since OpenSSL can be compiled as a non-locking, single-threaded library, I'm trying to answer the question: If I have one context per thread, will these contexts trash each others data when OpenSSL is compiled with no locking. The first 4 points of my list are the trashings that could take place. Now I just need the complete list :-) -paul > > > 6. Build OpenSSL with no-threads and -DOPENSSL_NO_LOCKING > > Am I doing anything completely insane here? > > If you are rebuilding OpenSSL why don't you throw in -DPURIFY and piece > by piece undo each point you listed until the problem comes back. That > would be far more useful to the mailing-list than all this other > information. > > > If I read things correctly, "You have a hybrid threaded app" but OpenSSL > does not have any threading support. Maybe this is okay since all the > things you disabled might end up causing no thread sensitive code path > to execute. To "no-threads" option is intended for a single threaded > execution environment. > > Darryl > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List openssl-dev@openssl.org > Automated List Manager [EMAIL PROTECTED] >
