This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Feb 24 08:57, Mike Gran via cygwin wrote: > On Sun, Feb 24, 2019 at 10:18:58AM +0100, Corinna Vinschen wrote: > > 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. > > Works for me. Thanks for your help. Thanks for testing! Expect a 3.0.2 release soon. Corinna -- Corinna Vinschen Cygwin Maintainer
Attachment:
signature.asc
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |