On 31-8-2010 12:45, Lukas Gebauer wrote: > First idea - are you sure if is write/writeln call thread safe? I > remember funny error in some old FPC when writeln was called inside > thread. It reset socket LastError and Synapse was mangled. So, try to > call wrie/writeln by some thread-safe way. > > Otherwise it's looks like some multithreaded problem inside Openssl. > OpenSSL provides some hooks for external locks. But synapse using it! > See InitLocks procedure inside ssl_openssl_lib.pas. > > Please, check: > > - if this procedure is called. (If not, then shared library does not > export needed functions.) > > - if is called, check TCriticalSection class implementation for your > platform.
There is a known issue under Linux, that threads created by 3rd party software don't initialize FPC specific threadvars. At least I saw something like this on the FPC maillists. There is now a workaround: 1. checkout a _recent_ trunk version (2.5.1) 2. Start a "native" FPC thread (which doesn't have to do anything just properly initialize) BEFORE the 3rd party software launches threads. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
