X-Spam-Check-By: sourceware.org
Date: Wed, 20 Dec 2006 11:15:05 +0000 (GMT)
From: Mark Fortescue <mark AT mtfhpc DOT demon DOT co DOT uk>
To: Eric Blake <ebb9 AT byu DOT net>
cc: cygwin AT cygwin DOT com
Subject: Re: Bash 3.1.17(9) $@ Expansion error
In-Reply-To: <4588BF49.1000607@byu.net>
Message-ID: <Pine.LNX.4.61.0612201048070.30142@mtfhpc.demon.co.uk>
References: <Pine DOT LNX DOT 4 DOT 61 DOT 0612200025490 DOT 29171 AT mtfhpc DOT demon DOT co DOT uk>  <4588BF49 DOT 1000607 AT byu DOT net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
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

Hi Eric,

The mensioned problems are unique to cygwin. The $@ expansion error is not 
present in cygwin bash-3.0-14.tar.bz2

For re-preduction, see the Nov 6th email. The error prevents the 
CSSC-1.0.1 test suite from operating. On Linux, it runs through without 
any failures. Using bash-2.05 and bash-3.0-14, it gets to the -y admin 
flag tests before failing.

The memory issues are reported by a windows popup reporting that 
application sh.exe has tried to write to memory that it is not alowd to. 
It gives the instruction address and the memory address but I did not make 
a note of them as I was trying to prepare a system to alow me to do some 
work on somthing else. The system is an Intel system with WinXP Home. On 
my now defunct AMD XP Pro system, I had a number of sudden blue screens 
where I was unable to read any details before automatic reboot, that only 
occoured when using bash scripts under cygwin. The blue screens may just 
have been a coincidence as the IDE chip died. Having un-installed cygwin 
and gone back to a Feb 2005 release (bash 2.05) the issue is nolonger 
present. When I have the time, I will upgrade bash on its own to 3.0-14 
and redo the test to see if it is a cygwin bash-3 issue or a cygwin core 
system error. If it is, I will note the details and pass them on.

The un-expected termination has no error messages, stack dumps or anything 
that I am aware of to aid in fault location/identification. It has only 
occoured when I have used bash in cygwin releases post November 6th. The 
issue has occoured on both the WinXP Pro and WinXP home systems.

Regards
 	Mark Fortescue.


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