X-Spam-Check-By: sourceware.org
Message-ID: <43FF1402.2030904@byu.net>
Date: Fri, 24 Feb 2006 07:11:14 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Nitin Agarwal <nitin DOT na AT gmail DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: Cygwin Bash shell on Windows 2003 Server not working
References: <022320061627 DOT 13535 DOT 43FDE264000A86DE000034DF22070208530A050E040D0C079D0A AT comcast DOT net> <f87d9ad40602231633k448131d9u3dbd0698333a02f8 AT mail DOT gmail DOT com>
In-Reply-To: <f87d9ad40602231633k448131d9u3dbd0698333a02f8@mail.gmail.com>
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-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

Double ugh - two times in a row, right after I already told you not to!
PLEASE follow directions, and
http://cygwin.com/acronyms/#PCYMTNQREAIYR
Otherwise, I might be disinclined to offer further advice.

> On 2/23/06, Eric Blake <ericblake AT comcast DOT net> wrote:
                                   ^^^^       ^^^^^

>
>>Ugh - topposting reformatted: http://cygwin.com/acronyms/#TOFU
>>
>>
>>>On 2/23/06, Eric Blake <ebb9 AT byu DOT net> wrote:
>>
>>                             ^^^^   ^^^^^
>>
>>Ugh - raw email: http://cygwin.com/acronyms/#PCYMTNQREAIYR
>>
>>

>>The postinstall script for the bash package effectively does
>>'cp /bin/bash /bin/sh' from inside a bash shell, so you could
>>manually do that (or the cmd.com equivalent
>>'copy c:\cygwin\bin\bash.exe c:\cygwin\bin\sh.exe').  But
>>the bigger question is WHY the postinstall script is failing,
>>and the realization that the postinstall script relies on bash
>>working.  As has been previously suggested on this list,
>>if you are having problems starting bash, a good thing to
>>try is opening a cmd.com window in c:\cygwin\bin (or
>>wherever you installed), then running ".\bash.exe -livx"
>>to start an interactive login shell with full debugging
>>statements, and see how far you get or what error
>>message is printed.
>>
>
> I tried copyinh the bash as sh.exe by running your command but it did
not work.
> And when I run .\bash.exe -livx I get the same error in stack dump -

Did you get any output before the stackdump?  Details are essential here.

>
> Exception: STATUS_ACCESS_VIOLATION at eip=00437B40
> eax=00004000 ebx=00000004 ecx=610FCE28 edx=00000000 esi=0022EED9
edi=61102C1C
> ebp=0022EEA8 esp=0022EC0C program=C:\cygwin\bin\bash.exe, pid 21516,
thread main
> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
> Stack trace:
> Frame     Function  Args
> 0022EEA8  00437B40  (00000002, 004B01C0, 004B0090, 61010EAC)
> 0022EF78  61005BC8  (0022EFD0, FFFFFFFF, 0022EFB3, 00246E40)
> 0022FF88  61005EB3  (00000000, 00000000, 00000000, 00000000)
> End of stack trace
>

Next step - in the cmd.com window, run '.\bash' without arguments, to see
if it is still crashing.  If so, run 'strace -o strace.out bash', and post
that somewhere where the list readers can see it (strace output tends to
be large, so don't send it to the list if it is larger than, say 200k or
so).  That may give the cygwin1.dll developers an idea of what is causing
the crash.

> Is there a way reinstall just BASH.exe and run the post install script?

Yes, run setup.exe, find the bash package, and cycle the button until it
says reinstall.  Then setup.exe will reinstall bash.exe and (attempt to)
run the postinstall script.  If you are lucky, then you currently have a
corrupt bash.exe, and the reinstallation will solve problems.  But my
guess is that since you are seeing crashes when trying to run bash, that
you will see the same crashes when reinstalling it via setup.exe.  The
problem now is figuring out why bash is crashing.

Others have also suggested checking for invasive programs, such as virus
scanners or firewalls, that may be interfering with cygwin's ability to run.

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

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

iD8DBQFD/xQC84KuGfSFAYARAgybAKCOqyCKzVl5GuD8UVZxjIXkzIvpaQCgxcDl
iriI438cZp0U1wS8EJ3fgB4=
=4t9M
-----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/