TeamForge : Post

Forum Topic - sem_timedwait_monotonic issue:

View: as

John Parker

12/04/2012 5:23 PM

post97787

I am attempting to move away from the realtime clock for my timedwait semaphores in order to fix a bug that occurs when 
the clock jumps due to a call to clock_settime.  However, when I switch to sem_timedwait_monotonic in conjunction with 
clock_gettime(CLOCK_MONOTONIC, &startTime); it is consistently timing out immediately instead of waiting until my 
timeout time.  

Has anyone else run into this?  I am running qnx6.50 SP1.

Thanks,
John Parker

Elena Laskavaia

12/06/2012 4:17 PM

post97880

Re: sem_timedwait_monotonic issue

I think there was an issue when it starts too fast the time is 0 and 
some library calls don't think it is valid time for some reason.

On 12-12-04 05:23 PM, John Parker wrote:
> I am attempting to move away from the realtime clock for my timedwait semaphores in order to fix a bug that occurs 
when the clock jumps due to a call to clock_settime.  However, when I switch to sem_timedwait_monotonic in conjunction 
with clock_gettime(CLOCK_MONOTONIC, &startTime); it is consistently timing out immediately instead of waiting until my 
timeout time.
>
> Has anyone else run into this?  I am running qnx6.50 SP1.
>
> Thanks,
> John Parker
>
>
>
> _______________________________________________
>
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post97787
> To cancel your subscription to this discussion, please e-mail momentics-community-unsubscribe@community.qnx.com

Return