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!news2.google.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Jano Newsgroups: comp.lang.ada Subject: Re: timeouts Date: Mon, 30 Aug 2004 14:17:52 +0200 Message-ID: <2pgk56Fkp78aU1@uni-berlin.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.uni-berlin.de QTnsIlbbPrriseaRjBx8hgMTM6gq7x5kJq8oZRHLadAg4cV74= User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040626) X-Accept-Language: en-us, en In-Reply-To: Xref: g2news1.google.com comp.lang.ada:3159 Date: 2004-08-30T14:17:52+02:00 List-Id: Brian May wrote: > 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). According to my experience, the bug can take any arbitrary amount of time to appear. I had a test program with intensive tasking which would trigger it in much less than 12 hours, usually around an hour and sometimes in 10 minutes.