X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Sun, 5 Jul 2009 22:52:26 -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:	<20090706025226.GA3985@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>
MIME-Version:	1.0
In-Reply-To:	<4A5162B0.4010409@verizon.net>
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 07:34:24PM -0700, Jerry DeLisle wrote:
>Eric Blake wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> According to Jerry DeLisle on 7/5/2009 1:35 PM:
>>> Warning: There are multiple cygwin1.dlls on your path
>>>
>> 
>> That's probably your culprit.
>> 
>I saw that too and did a full search of the disk and there is only one cygwin1.dll
>
>I am also seeing a stack dump for id.exe and one for bash.exe. The id.exe 
>stackdump occurs when I execute cygcheck -s
>
>The other symptoms are: none of the startup scripts are being sourced (executed).
>
>I end up with a bare shell running with /usr/bin as the current working 
>directory. The only reason I can do anything at all is I added the cygwin bin 
>directory to the windows path.

You're still in the wrong thread.  Look at the subject.  Does it have
anything to do with the problem you are having?  Apparently it doesn't.

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".

My release of binutils means that Eric can respin bash.  It doesn't mean
that, if you install binutils, it will somehow fix bash.

But, I'm not sure why binutils would be to blame for bash not
initializing correctly.

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 -