Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
From: jorg DOT schaible AT db DOT com
To: cygwin AT sourceware DOT cygnus DOT com
Message-ID: <002568DC.00371B45.00@sdbo1003.srv.uk.deuba.com>
Date: Thu, 11 May 2000 10:01:30 +0000
Subject: Re: bash never ends consuming 99% of CPU
Mime-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=2apeDEOujJJ6Sm9mCIZN9eZUDXc5NPqPSZLFyU7Y1UXcHVatJkwRF6v5"
Content-Disposition: inline

--0__=2apeDEOujJJ6Sm9mCIZN9eZUDXc5NPqPSZLFyU7Y1UXcHVatJkwRF6v5
Content-type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-transfer-encoding: quoted-printable


Hi Chris,

your question is the same like mine :)

Unfortunately, the problem resists. Now the gvim starts, but there is s=
till a dangling bash with 99% CPU usage :(
The gvim in /usr/local/bin is a symbolic link to c:\\Programme\\vim\\vi=
m56\\gvim.exe. But as I stated, from the plain command line, there is n=
o problem with this link.

I also already tried to build the bash, but the configure stops complai=
ning my compiler could not build executables (un'tar'ed the bash.tar.gz=
 into root, where / is c:\\cygnus\\cygwinv1.1).

Regards,
J=F6rg


---------------------------------------- Message History --------------=
--------------------------


From: cgf AT cygnus DOT com on 10/05/2000 14:40

Please respond to cygwin AT sourceware DOT cygnus DOT com

To:   cygwin AT sourceware DOT cygnus DOT com
cc:
Subject:  Re: bash never ends consuming 99% of CPU


=

--0__=2apeDEOujJJ6Sm9mCIZN9eZUDXc5NPqPSZLFyU7Y1UXcHVatJkwRF6v5
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline


On Wed, May 10, 2000 at 10:47:30AM +0000, jorg DOT schaible AT db DOT 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 AT sourceware DOT cygnus DOT com


--0__=2apeDEOujJJ6Sm9mCIZN9eZUDXc5NPqPSZLFyU7Y1UXcHVatJkwRF6v5
Content-Type: text/plain; charset=us-ascii

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
--0__=2apeDEOujJJ6Sm9mCIZN9eZUDXc5NPqPSZLFyU7Y1UXcHVatJkwRF6v5--