X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Date:	Sun, 10 May 2009 20:32:17 -0700 (PDT)
From:	Tim Garton <tim DOT garton AT cs DOT stanford DOT edu>
To:	cygwin AT cygwin DOT com
Subject:	Bash crashes in any if statement on high compute x-large EC2 instance (cygwin 1.5.25-15)
Message-ID:	<Pine.LNX.4.64.0905102014070.8489@xenon.Stanford.EDU>
MIME-Version:	1.0
X-Spam-Score:	-101.8
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

I am able to repro this every time:

1. Launch a Windows Server 2003 x64 image (I used ami-dc4daab5) on a high 
compute x-large (c1.xlarge) instance of EC2.
2. Install the default cygwin
3. Open up a bash shell
4. Type 'if [ "1" == "1" ]; then echo hello; fi'
5. Watch bash crash

I looked through the faq and archives and couldn't see anything else about 
this.  I speculate that it has something to do with xen and the underlying 
hardware, because the above steps have no problem if you do everything 
exactly the same but launch a medium compute large (m1.large) instance. 
The main difference I can see between the two insance types is the medium 
has an AMD Opteron processor and the high compute one has a Xeon (E5345) 
processor.

-Tim

--
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/

- Raw text -