Unexplainable deadlock detection assert in libpthread
Szabolcs Nagy
szabolcs.nagy@arm.com
Fri Nov 24 12:05:00 GMT 2017
On 24/11/17 12:01, Patrick Schlangen wrote:
> Hi Arne,
>
> can you give some more information on the involved mutex, i.e. is it a recursive
> a PTHREAD_MUTEX_ERRORCHECK_NP or a PTHREAD_MUTEX_FAST_NP mutex (the latter would
> be the default AFAIR)?
>
> If it's of 'default' PTHREAD_MUTEX_FAST_NP type, to my understanding of the code,
> it would lead to the observed assertion and the check returning EDEADLK you pointed
> out in your marker would NOT be performed.
>
_FAST_NP mutex does not check for EDEADLK errors
only error checking and recursive mutexes do.
> You don't, by any chance, lock the mutex from any signal handler?
>
> Best Regards,
>
> Patrick
>
>
More information about the Libc-help
mailing list