Here is a good one - I have a program that reads the system clock a lot to
log timestamped events; this uses the GetSystemTime function. At seemingly
random times, the timestamps show a sudden "leap" into the future (2009
already) and sometimes back again to precisely the right time for the elapsed
duration of the leap. Yes, this is a highly multi-threaded program, but the
clock is never "reset", only ever read. Whilst my program is recording
"future" times, the OS applet and file-system are still using the correct
"today" date and time. Attempts to reproduce this under controlled
circumstances are unsuccessful, but this is not limited to any one computer
and has been seen over the last few years at random times. The smallest piece
of code showing the effect is a clock read, take difference to previous clock
time and print it - this takes a sudden leap into the future, but is only a
call to GetSystemTime. Any ideas?
|
