Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: bash often consume a cpu. References: <20000224151353 DOT A5264 AT cygnus DOT com> <20000225201506 DOT A3484 AT cygnus DOT com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 26 Feb 2000 16:58:24 +0900 In-Reply-To: Chris Faylor's message of Fri, 25 Feb 2000 20:15:06 -0500 Message-ID: Lines: 21 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Fri, 25 Feb 2000 20:15:06 -0500 >>> Chris Faylor 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. ____ | AIST Kazuhiro Fujieda | HOKURIKU School of Information Science o_/ 1990 Japan Advanced Institute of Science and Technology