Search Results

I see. So, the sole presence in my environment of functions like clock_gettime should suggest to me that the 'Timers option' is actually available indeed and, therefore, something like this:
...

run time misbehavior. it did timeout much before the absolute time passed as parameter.

ps: something strange here. in my browser I read that your first reply says 'clock_gettime', but in the...

but that does not help me understand the statement in the pthread_mutex_timedlock man-page. All the examples I have seen around they use clock_gettime with option CLOCK_REALTIME before calling...

in its man-page pthread_mutex_timedlock documents that the absolute timeout parameter should be based on the CLOCK_REALTIME clock or in the system clock. All this depending on whether the 'Timers...

i see that your understanding is then the same as mine.

realizing this detail in pthread (at least for the implementation i'm using) was a bit of a surprise. i try to use timed calls (pass...

linux, glibc 2.5

Right, before waiting on a conditional variable you must hold the mutex. But once within the 'wait' method itself the mutex will be released while waiting on the conditional...

looking in pthread's source code I can see that as an epilogue both pthread_cond_timedwait and pthread_cond_wait will try to relock the mutex by means of __pthread_mutex_cond_lock.

Does this mean...