Mail Archives: djgpp-workers/1999/07/12/06:58:49
It seems that our implementation gets wrong the value returned by
getitimer and setitimer (the latter in the ovalue argument). We
return the *remaining* time until the timer expires, whereas the
Unix semantics seems to be to return the *original* timer value
passed to setitimer last time it was called.
Does Posix have any clear specification about this?
I found this when some Unix program that relied on this didn't work as
expected when compiled with DJGPP. I checked on a Sparc/Solaris
machine nearby, and it indeed returns the original timer values.
Can people please check this on Linux and maybe other platforms as well?
Changing our behavior is easy, but I'd like to know that I'm doing the
right thing...
Thanks in advance.
- Raw text -