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: Sun, 27 Feb 2000 16:15:41 -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: <20000227161541.A7844@cygnus.com>
Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com
References: <s1s7lfujwed DOT fsf AT jaist DOT ac DOT jp> <20000224151353 DOT A5264 AT cygnus DOT com> <s1sya89iort DOT fsf AT jaist DOT ac DOT jp> <20000225201506 DOT A3484 AT cygnus DOT com> <s1ssnygiee7 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: <s1ssnygiee7.fsf@jaist.ac.jp>; from fujieda@jaist.ac.jp on Sat, Feb 26, 2000 at 04:58:24PM +0900

On Sat, Feb 26, 2000 at 04:58:24PM +0900, Kazuhiro Fujieda wrote:
>>>> On Fri, 25 Feb 2000 20:15:06 -0500
>>>> Chris Faylor <cgf AT cygnus DOT com> said:
>
>> I've made a few more changes.  Please try the next snapshot.
>
>I tried your fixes through `cvs update'. Unfortunately, the
>fixes make nothing about the problem, too. I replaced the strace
>log with one which may be more helpful for your debugging.
>
>In the strace log, I executed the bash command without any
>environment variables nor /etc/{termcap,passwd,group}, and
>simply typed `a\n' three times. The bash didn't consume a cpu
>until two times. After I typed three times, it began to do so.
>
>Anyway, my NT box has two CPU. Multi-processor systems hit
>problems about race conditions more often than uni-processor
>ones.

I do all of my debugging on an NT with two CPUs and I'm not seeing
this.

Regardless, I think I see the problem.  When things get into this
state, could you try hitting a "CTRL-C" at the bash prompt and see
if the CPU utilization goes back down?

-chris