Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	jorg DOT schaible AT db DOT com
Subject:	bash never ends consuming 99% of CPU
To:	cygwin AT sourceware DOT cygnus DOT com
Date:	Wed, 10 May 2000 10:47:30 +0000
Message-ID:	<OFDACF2A9E.ACCEB76F-ON002568DB.0039AF45@srv.uk.deuba.com>
X-MIMETrack:	Serialize by Router on sdbo5814/Mail/DMG UK/DeuBa(Release 5.0.3 (Intl)|21
	March 2000) at 10/05/2000 10:47:32 AM
MIME-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id EAA05207

Hi folks,

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.

Greetings,
Jörg


function e
{
    local arg
    for arg in "$@"; do
        /usr/local/bin/gvim (cygpath -w "$arg") &
    done
}



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -