Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
LynxOS 4.2 Error on pthread_mutex_unlock (but no errno value)?
9 views
Skip to first unread message
jmd...@yahoo.com
Mar 4, 2009, 10:55:58 PM3/4/09
to
We are encountering an error on a call to pthread_mutex_unlock, but
afterward the errno value is 0? How do we determine what the error is?
afterward the errno value is 0? How do we determine what the error is?
Golden California Girls
Mar 5, 2009, 2:41:57 AM3/5/09
to
jmd...@yahoo.com wrote:
> We are encountering an error on a call to pthread_mutex_unlock, but
> afterward the errno value is 0? How do we determine what the error is?
> We are encountering an error on a call to pthread_mutex_unlock, but
> afterward the errno value is 0? How do we determine what the error is?
It doesn't set errno, check the return value.
zoot51
Mar 25, 2009, 2:20:49 PM3/25/09
to
On 5 Mar, 03:55, jmd...@yahoo.com wrote:
> We are encountering an error on a call to pthread_mutex_unlock, but
> afterward the errno value is 0? How do we determine what the error is?
> We are encountering an error on a call to pthread_mutex_unlock, but
> afterward the errno value is 0? How do we determine what the error is?
Pthread_mutex_unlock returns 0 when successful.
If the following condition(s) is detected, the
pthread_mutex_unlock
will return:
EINVAL m does not refer to a valid mutex.
EPERM The mutex is not owned by the thread.
0 new messages