return value of getitimer after an alarm
Corinna Vinschen
corinna-cygwin@cygwin.com
Sun Feb 24 10:14:00 GMT 2019
On Feb 23 22:58, Mike Gran via cygwin wrote:
> Hi-
>
> There is an unusual behaviour with setitimer/getitimer and I'm not
> sure if it is a bug or not.
>
> Basically, if I call setitimer to set an SIGALRM, and then call
> getitimer *after* the alarm goes off, I rather expect the time I
> receive from getitimer should be {tv_sec = 0, tv_usec = 0}, but, in
> fact, it_value is the negative of the unix timestamp.
>
> Attached is a test case.
Thanks for the testcase. The reason for the problem is this:
I optimized a condition in Cygwin's POSIX timers "gettime" method.
I optimized it so effecively that it was practically invisible :}
I pushed a patch and uploaded new developer snapshots to
https://cygwin.com/snapshots/
Please test.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20190224/51831229/attachment.sig>
More information about the Cygwin
mailing list