Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 13 Jul 2004 15:05:03 -0700
From: Yitzchak Scott-Thoennes <sthoenna AT efn DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: cat /proc/registry/HKEY_PERFOMANCE_DATA/@ hangs
Message-ID: <20040713220503.GA2896@efn.org>
References: <NUTMEGUIP5RxDgQDJcu00000853 AT NUTMEG DOT CAM DOT ARTIMI DOT COM> <Pine DOT GSO DOT 4 DOT 58 DOT 0407131204160 DOT 29800 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.58.0407131204160.29800@slinky.cs.nyu.edu>
User-Agent: Mutt/1.4.1i
Organization: bs"d
X-IsSubscribed: yes

On Tue, Jul 13, 2004 at 12:21:50PM -0400, Igor Pechtchanski wrote:
>       bufalloc = 0;
>       do
>         {
> ==>       bufalloc += 1000;

> 
> I have a theory that the performance data may be added in chunks larger
> than 1000 bytes, so the fhandler just can't keep up with the amount of
> data, and loops indefinitely.  Since you intend to build the DLL from CVS,
> you're probably in the best position to check whether this theory is true
> (by either just upping the increment amount to something like 5000, or
> even doubling the buffer size on each iteration).

Perhaps bufalloc += max(bufalloc, 1000);

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/