X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Mon, 6 Jul 2009 01:29:34 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: fresh 1.7, bash fails with STATUS_ACCESS_VIOLATION
Message-ID:	<20090706052934.GA13116@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4A51008E DOT 9050205 AT verizon DOT net> <4A515F2D DOT 1060907 AT byu DOT net> <4A5162B0 DOT 4010409 AT verizon DOT net> <20090706025226 DOT GA3985 AT ednor DOT casa DOT cgf DOT cx> <4A5185EA DOT 1050802 AT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<4A5185EA.1050802@gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

On Sun, Jul 05, 2009 at 10:04:42PM -0700, Ian Kelling wrote:
>Christopher Faylor wrote:
>>It sounds like you are conflating a serious STATUS_ACCESS_VIOLATION
>>which is known to occur on Windows 7 with your not-so-serious "Bash
>>initialization w/cygwin-1.7".
>
>not-so-serious?  Cygwin 1.7 install is very broken because of this bug.
>Seems serious to me.  Is anyone able to install a fresh 1.7 with the
>default settings and not have bash fail?  If so, perhaps post cygcheck
>to compare?

When I said "a serious STATUS_ACCESS_VIOLATION" I really did mean that
this was a serious problem.  It is one that I'm sure Eric will fix, too.
The workaround for now is to drop back to an older version of bash and,
you've noted that you may have some fixup to do.

There is another problem which occurs on NT4.  There is no indication
that this is related to the STATUS_ACCESS_VIOLATION since the problem is
still evident even when dropping back to previous versions.

Everyone seems to be in "confuse the issue as much as possible" mode
today by first assuming that downloading binutils will fix a bash
problem and then assuming that all bash problems are the same bash
problem.

There is not yet any reason to post cygcheck output.  We think we
understand the problem.  We just are waiting for Eric to find the time
to roll a new bash release built with the new version of binutils.

cgf

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

- Raw text -