Re: Help with anormal pausing of program

[tmoran@acm.org]

>I see that we are talking about two different problems? The MSKB article
>talks about leaps forward, but your test program shows leaps back. In
>reality, more that leaps, it seems that some value is mangled because
  -- Some buggy chipsets have a counter that appears to run backwards
  -- under heavy load (see Q274323), and Windows corrects this by
  -- adding 2**24 (5-15 sec). Yuck! We need to try to detect this
So Gnat 3.14p had a clock that could jump forward several seconds.
The fix is to watch for a suspicious jump, check it against the
Windows system clock, and correct if needed.  For that you need
the system clock and the performance counter values at some base
synchronization point.  Gnat 3.15p failed to recalculate the base
when it did a resynchronization, so, IIRC, time would go into the
future, and a short "delay" would become a long one, waiting for
the future time.
  It's late, and I'm tired, so I don't guarantee this is right,
but it appears my fix for Gnat 3.15p was to add the line
      Base_Monotonic_Clock := Base_Clock;
at line 165 of s-osprim.adb, just before the line
   end Get_Base_Time;
and then to compile with
gcc -c -gnatg -O2 s-osprim.adb
Because of heavy inlining, you'll find other parts of the Gnat
run-time that also need recompiling the same way.