Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Wed, 10 May 2000 10:40:46 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: bash never ends consuming 99% of CPU Message-ID: <20000510104046.B795@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cgf@cygnus.com, cygwin@sourceware.cygnus.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: ; from jorg.schaible@db.com on Wed, May 10, 2000 at 10:47:30AM +0000 On Wed, May 10, 2000 at 10:47:30AM +0000, jorg.schaible@db.com wrote: >unfortunately I had yesterday this weird error that calling the >function below (defined in my .bashrc) left a dangling bash process in >memory consuming 99% of my CPU time (in fact, gvim was never called >either). After some experiments I found the "error" that caused this >weird behaviour: My .bashrc had CRLF format. After changing format to >normal UNIX-style line endings, the problem vanished. > >Unfortunately everyone upgrading from B20.1 to V1.1 may have this >"experience", since the old Cygwin version mounted the root as text >while the new will mount it binary. This problem should be mensioned >explicitly somewhere in the README.TXT avoiding unnecessary trouble >after the upgrade. I have no problems modifying documentation, but I do like to understand the reasons for doing it. I don't understand why changing \r\n line endings to \n line endings causes bash to not consume 98% of your CPU. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com