[GitHub] [celix] jenny-cheung commented on issue #352: Potential errors due to the incorrect lock usage

[GitBox <gi...@apache.org>]

jenny-cheung commented on issue #352:
URL: https://github.com/apache/celix/issues/352#issuecomment-890486344


   @pnoltes Hi, I forgot to check the function name and made a mistake. This is in the[ pthread_cond_timedwait](https://pubs.opengroup.org/onlinepubs/009604599/functions/pthread_cond_timedwait.html) method.
   
   
   
   
   
   > These functions atomically release mutex and cause the calling thread to block on the condition variable cond; atomically here means "atomically with respect to access by another thread to the mutex and then the condition variable". 
   > That is if another thread is able to acquire the mutex after the about-to-block thread has released it, then a subsequent call to pthread_cond_broadcast() or pthread_cond_signal() in that thread shall behave as if it were issued after the about-to-block thread has blocked.
   > Upon successful return, the mutex shall have been locked and shall be owned by the calling thread.
   
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@celix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org