Jordan Brown wrote: > Note that __pthread_once_slow is in the stack twice, called from > OPENSSL_init_crypto and CRYPTO_THREAD_run_once. > > "once" functions ensure that they call their function argument exactly > once, even if they are called multiple times in parallel while their > function is running. They do that by locking a mutex around the > execution of the function. The second call attempted to lock the mutex > to wait for the first call to complete, and deadlocked. I still don't know what to do about this. For them moment I'm continuing with my idea in the thread "Latest idea to force usage of custom engine".
