From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8da181ade72859cf
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!news.glorb.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local1.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail
NNTP-Posting-Date: Thu, 26 Aug 2004 14:06:38 -0500
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
References: <sa4smakuhzq.fsf@snoopy.apana.org.au>
 <2jVUc.13319$Fg5.12445@attbi_s53> <2p63roFgloq0U1@uni-berlin.de>
Subject: Re: timeouts
Date: Thu, 26 Aug 2004 14:07:33 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Message-ID: <8PKdnU4zIcsjqbPcRVn-rA@megapath.net>
NNTP-Posting-Host: 64.32.209.38
X-Trace: 
 sv3-qe2axPq0On4kVqOZtYlL/83sWwvP6rBNPc4EF8Dxm5o1DPPtJcJY2BAZCKAV6n8A9LS/pGWGANdcRGt!aaDgjCaKZUTS4ZJ0pV/8MVRrYXKvSEiqzMsw69FAZ3nxJYQVyzgaYIZGZ6FoD0zTSC8IFkIYjKMe
X-Complaints-To: abuse@megapath.net
X-DMCA-Complaints-To: abuse@megapath.net
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint
 properly
X-Postfilter: 1.3.13
Xref: g2news1.google.com comp.lang.ada:3043
Date: 2004-08-26T14:07:33-05:00
List-Id: <comp.lang.ada>

"Jano" <notelacreas@porfavor.no> wrote in message
news:2p63roFgloq0U1@uni-berlin.de...
> Steve wrote:
> > What version of GNAT?
> > I vaguely recall a gnat bug having to do with time.  Unfortunately I
can't
> > recall the particulars.  Maybe someone else on the list will remember.
>
> I was bitten by it. It involves Gnat 3.15p on Windows. Delays can
> mis-delay for unknown periods of time, effectively suggesting that tasks
> are locked when they are not.

The problem I recall (it happened in Janus/Ada, too, because it's actually
caused by a patch in the OS for a hardware problem) is that
QueryPerformanceCounter leaps forward by large amounts. Depending on how
Ada.Calendar is written, that can have bizarre effects. I believe that Tom
Moran created a patch for GNAT's Ada.Calendar for that; I don't know if
3.15p has it, but if not, you should try applying it. (Even better is
getting a machine without the faulty chipset, but that's not always
practical!)

                            Randy.