Re: timeouts

[Brian May <bam@snoopy.apana.org.au>]

>>>>> "Stephen" == Stephen Leake <stephen_leake@acm.org> writes:

    Stephen> I had a similar problem, and tracked it down to a "pragma
    Stephen> Debug" in the GNAT sources for Ada.Text_IO. Try compiling
    Stephen> without -gnata. Mine went away with the next release of
    Stephen> GNAT (5.02a1).

Hmmm... Interesting... That is probably my problem. Yes, I am
compiling with -gnata, too.

When it annoys me enough I will try removing the -gnata. So far, I
haven't reached this threshold.

Anyway, to followup on my original problem:

With gnat 3.15p, after approx 12 hours, my timeouts stopped working
and/or took excessively long (e.g. in the order of hours instead of
0.1 of a second).

With mingw32 3.4.1, candidate release, after 12 hours, timeouts were
still working. Unfortunately, instead of 0.1 seconds, each one was 4.6
seconds. This is on a XP computer with no other applications
running[1]. While this is OK for my application, I am concerned that
there is still something wrong...

If I restart the application, it comes good.

I have another theory, it could be a problem with my logging code
(weird theory, I know) that prints the date & time. In order to rule
this out, I am now using Ada.Text_IO.Put_Line directly without
printing the date and time immediately before the select statement,
and at the start of each event, and this should enable to be prove
that the delay really is in the select statement.

Note:

[1] Interestingly, task manager reported 50% CPU used by the msys
terminal.  After I restarted the process the CPU usage dropped to less
then 1%. To me, this makes absolutely no sense, as surely more CPU
would be required to update the screen when it is getting updated
several times a second, not when there was a 4.6 second delay?
-- 
Brian May <bam@snoopy.apana.org.au>