Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Thu, 24 Feb 2000 15:13:53 -0500
To: Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
Cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: bash often consume a cpu.
Message-ID: <20000224151353.A5264@cygnus.com>
Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com
References: <s1s7lfujwed DOT fsf AT jaist DOT ac DOT jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.4i
In-Reply-To: <s1s7lfujwed.fsf@jaist.ac.jp>; from fujieda@jaist.ac.jp on Fri, Feb 25, 2000 at 03:19:38AM +0900

On Fri, Feb 25, 2000 at 03:19:38AM +0900, Kazuhiro Fujieda wrote:
>In the latest snapshot (02/23), bash often consume 100% of one
>cpu. I investigated a strace log, and I found the the following
>entries are furiously repeated in it.
>
>  223 8634753 [main] bash 1002 _read: read (0, 0x246F5BF, 1)
>  228 8634981 [main] bash 1002 _read: non-interruptible read
>  257 8636085 [main] bash 1002 set_sig_errno: errno 4
>  238 8636323 [main] bash 1002 read_handler: -1 = read (0</dev/conin>, 0x246F5BF, 1)
>
>You can get the whole of the log at the following URL:
>http://www.jaist.ac.jp/~fujieda/cygwin/bash.log.gz

Thanks for the bug report and the strace log.  I managed to duplicate
this problem but only when I ran bash with strace for some reason.

I've checked in a fix that seems to solve the problem, for me, at least.

If you can access this via CVS then you should be able to rebuild it
now.  Otherwise, tonight's snapshot will have the fix.

-chris