Yes. The issue is fairly reproducible and takes not more than 10-15mins to
occur.
--
Thanks,
Nilesh
Sent via CanvasHD
"Dr. Stephen Henson" <st...@openssl.org> wrote:
On Wed, Jan 15, 2014, Tayade, Nilesh wrote:
>
> Thanks. I have already captured the lock details in an array. Please see
> below. The leftmost digit is lock number index.
> Lock 19 was taken by same thread and it was released (lock_present = 0). And
> this is causing confusion for me.
>
> 18 {thread_id = 140003803043584, file_name = "md_rand.c", '\000' <repeats 30
> times>, file_name_len = 9, line = 384, lock_present = 1},
> 19 {thread_id = 140003803043584, file_name = "md_rand.c", '\000' <repeats 30
> times>, file_name_len = 9, line = 389, lock_present = 0},
Does it imply that thread has lock 18 but can't get 19 even though the lock
isn't present?
Does this deadlock happen almost immediately or some time later?
The way the PRNG works it's normal for lock 18 and 19 to be acquired and
released often sometimes simultaneously.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
