X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: =?ISO-8859-1?Q?Ren=E9_Berber?= <r DOT berber AT computer DOT org>
Subject:  Re: Bash Crashes
Date:  Fri, 07 Mar 2008 16:42:52 -0600
Lines: 44
Message-ID: <fqsgcu$8u4$1@ger.gmane.org>
References:  <783235 DOT 94862 DOT qm AT web38013 DOT mail DOT mud DOT yahoo DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  quoted-printable
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
In-Reply-To: <783235.94862.qm@web38013.mail.mud.yahoo.com>
X-IsSubscribed: yes
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

Scott Webster Wood wrote:

> I saw the following posting after experiencing a similar problem.
> One of the follow ups suggested running cygwin.bat and reporting the
> result, but the result is the same whether I try to run cygwin.bat,
> call bash directly from a cmd.exe shell or call bash from something
> like /bin/sh or /bin/tcsh:
>=20
> [swood AT arena ~]$ pwd
 > /home/swood
 > [swood AT arena ~]$ /bin/bash
 > bash-3.2$
> [swood AT arena ~]$

First point: that is not a crash.  A crash shown you a message and=20
creates a .stackdump file.

Second point: have you tried other options for calling bash?  Like for=20
instance:

   bash --login -i

   bash --noprofile --norc

   bash --debug

> Here's the cute thing.  If I create a test script with #!/bin/bash at
> the beginning and throw in something like a simple 'echo' command,
> the script works just fine calling it by name or calling it with
> /bin/bash:=20
 > [swood AT arena ~]$ cat test.sh
 > #!/bin/bash echo this is a test
 > [swood AT arena ~]$ /bin/bash test.sh
 > this is a test
 > [swood AT arena ~]$ ./test.sh
 > this is a test

That shows that bash is OK, your problem is something else in your user=20
configuration (another test, run bash as a different user).  There's=20
something wrong with one of .bashrc, .bash_profile, .profile, or the=20
global ones... and is something you (or somebody with access to your=20
computer) put there.
--=20
Ren=E9 Berber


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