X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: mwoehlke <mwoehlke AT tibco DOT com>
Subject:  Re: bash 3.1.18 seems seriously broken
Date:  Wed, 27 Sep 2006 16:40:11 -0500
Lines: 22
Message-ID: <efer3r$h4h$1@sea.gmane.org>
References:  <451AEBAE DOT 6000703 AT cs DOT ucsd DOT edu>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.0
In-Reply-To: <451AEBAE.6000703@cs.ucsd.edu>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Larry Breyer wrote:
> What changed from bash 3.1.17 to 3.1.18 ?

Did you bother reading the ANNOUNCEMENT?

> I blindly performed a cygwin update, rebooted, and attempted startx.
> X came up OK but the terminals would not respond to keyboard input.
> Looking at the output of startx it became apparent something was
> seriously wrong with /bin/sh (/bin/bash).
> 
> I got syntax errors on blank lines.
> 
> I also found, by adding little debugging stuff, like 'ls $XAPPLRESDIR',
> that the shell was quoting env variables.  I was getting "no such file
> or directory" on valid paths because the shell was including single
> quotes around the path.  At least that's what it looked like.
> 
> Really odd.  I solved the problem by reverting to bash 3.1.17.

-- 
Matthew
The hippo made me do it! What? What do you mean you can't see the hippo?


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/