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
Message-ID: <42E778CA.4060409@byu.net>
Date: Wed, 27 Jul 2005 06:06:34 -0600
From: Eric Blake <ebb9 AT byu DOT net>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: Matthew Carroll <m_c_j AT bellsouth DOT net>
CC: bug-bash AT gnu DOT org, cygwin AT cygwin DOT com
Subject: Re: bash.exe.stackdump
References: <20050726181610 DOT XEBJ3347 DOT ibm60aec DOT bellsouth DOT net AT mail DOT bellsouth DOT net>
In-Reply-To: <20050726181610.XEBJ3347.ibm60aec.bellsouth.net@mail.bellsouth.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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

[Moving to cygwin list]

According to Matthew Carroll on 7/26/2005 12:16 PM:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: cygwin
> Compiler: gcc
> Compilation CFLAGS:  -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -DRECYCLES_PIDS  -I.  -I/usr/src/bash-3.0 -I/usr/src/bash-3.0/include -I/usr/src/bash-3.0/lib   -march=prescott -O2
> uname output: CYGWIN_NT-5.1 atltnscarrolm 1.5.18(0.132/4/2) 2005-07-02 20:30 i686 unknown unknown Cygwin
> Machine Type: i686-pc-cygwin

Based on the compilation CFLAGS, it looks like you built your own bash on
cygwin, instead of using the official cygwin port that I help maintain.

> 
> Bash Version: 3.0
> Patch Level: 16
> Release Status: release
> 
> Description:
> 	Below are the contents of the "bash.exe.stackdump"

And what were you doing at the time of the crash?  Any formula for
reproducing the error?  Otherwise this is a useless bug report.

> 
> Exception: STATUS_ACCESS_VIOLATION at eip=610CA495
> 
> eax=0000004B ebx=31207064 ecx=004F6338 edx=31207065 esi=004F6340 edi=316FD39C
> 
> ebp=0022E8C8 esp=0022E8B0 program=C:\cygwin\bin\bash.exe, pid 40676, thread main
> 
> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
> 
> Stack trace:
> 
> Frame     Function  Args
> 
> 0022E8C8  610CA495  (6110AFB0, 6110AFB0, 0022F084, 004F64F0)

This sort of stack trace is useless.  It shows only the locations within
bash as compiled on your machine, but no one else knows where in the code
the crash happened.

I would recommend that you try the official cygwin port of bash, first,
and if you can still reproduce the crash, provide a formula to the cygwin
list of what went wrong.  From there, I can help you decide if it is a
porting bug specific to cygwin or a true upstream bug.

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

iD8DBQFC53jK84KuGfSFAYARAk5jAJ9RGaNLh67ehn8zJwEOvKNAoyuungCgh75q
K9XWb2JuGof+sZ2siwrr/bc=
=WePi
-----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/