X-Spam-Check-By: sourceware.org
Message-ID: <4588BF49.1000607@byu.net>
Date: Tue, 19 Dec 2006 21:42:49 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061025 Thunderbird/1.5.0.8 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com, mark AT mtfhpc DOT demon DOT co DOT uk
Subject: Re: Bash 3.1.17(9) $@ Expansion error
References: <Pine DOT LNX DOT 4 DOT 61 DOT 0612200025490 DOT 29171 AT mtfhpc DOT demon DOT co DOT uk>
In-Reply-To: <Pine.LNX.4.61.0612200025490.29171@mtfhpc.demon.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Mark Fortescue on 12/19/2006 5:55 PM:
> Hi,
> 
> Back in start of November (6th), I had to re-install/upgrade cygwin/bash
> to alow me to use some additional programs. At this time I found out
> that the upgraded bash had a fault in it that prevented it from
> expanding $@ correctly. Not being a subscriber to the mailing list I did
> not see the reply from Eric untill today.
> 
> I have just upgraded to bash-3.2.9(9)-release and the BUG is still
> present,

Is your bug reproducible on other platforms besides cygwin?  If so, report
it upstream.  At any rate, post more details than just 'it still doesn't
work', such as a recipe for recreating it, if you would like help in
tackling it.


> together with some more serious ones:
> 
>   When used in an Xterm under X (xinit), bash repeatedly tries to access
>   memory that it should not access and at times it terminates without
>   warning for no known reason.

Again, a formula for reproducing this would be worthwhile, since I have
never encountered this behavior.  And more details on how you arrived at
the conclusion that it is bash accessing invalid memory (such as the
address in question, or a stack trace) would be useful, in case the
problem is really a buggy Windows device driver.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
volunteer cygwin bash maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFiL9J84KuGfSFAYARAkj9AJwNqaqwV7JJgnwbO1GwYrRYd0Gg/QCbBjdb
GccPz33QudpJVrpq80OzfZI=
=BUDT
-----END PGP SIGNATURE-----

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