RE: Debug of Test 15

["Pierre A. Humblet" <Pierre dot Humblet at ieee dot org>]

After freezing XWin seems to keep consuming CPU at the
same rate as before (~ 70%). But the monitor itself
seems to be using a lot, so it's hard to tell. It's
surely not 100%

The time until freezing is random. Last time it happened
after ~ 1700 calls to Select().

Pierre

At 03:28 PM 4/7/2001 -0400, you wrote:
>Pierre,
>
>When Test 15 freezes in Select does it enter an infinite loop?
>
>One easy way to tell is to run Start->Programs->Accessories->System
>Tools->System Monitor and watch the CPU usage.
>
>Harold
>
>> -----Original Message-----
>> From: Pierre A. Humblet [mailto:Pierre.Humblet@ieee.org]
>> Sent: Saturday, April 07, 2001 2:17 PM
>> To: Harold Hunt
>> Cc: cygwin-xfree-help@sourceware.cygnus.com
>> Subject: Debug of Test 15
>>
>>
>> Harold,
>>
>> I have been trying to find out why Test 15
>> freezes on my WinME, even with no clients.
>> Method is simple: put ErrorF in various spots.
>>
>> 3 times out of three it has not returned from
>> Select(), in WaitFor.c
>>
>> This is when I redirect to a file. When printing
>> to screen (very slow) it doesn't freeze in many
>> minutes.
>> Is this a reliable diagnostic, or can there be
>> buffering/flushing issues?
>>
>> Pierre
>
>