X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Date: Fri, 03 Jul 2009 10:11:20 +0200
From: "Vincent R." <forumer AT smartmobili DOT com>
To: Eric Blake <ebb9 AT byu DOT net>
Cc: <cygwin AT cygwin DOT com>
Subject: Re: [ANNOUNCEMENT] [1.7] Updated [security]: bash-3.2.49-23 and Windows   7  RC
In-Reply-To: <4A4D4BA8.8090202@byu.net>
References: <announce DOT 4A4C18B6 DOT 4000505 AT byu DOT net> <4A4D200E DOT 9050401 AT sidefx DOT com> <4A4D2342 DOT 6050400 AT sidefx DOT com> <4A4D4BA8 DOT 8090202 AT byu DOT net>
Message-ID: <ac6f02c4727a17f29edd0c723e25a5c8@mail.smartmobili.com>
X-Sender: forumer AT smartmobili DOT com
User-Agent: RoundCube Webmail/0.2
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8"
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

>> Ok, so I can confirm a problem with bash 3.2.49-23 on Windows 7 RC build
>> 7100 64-bit. Basically, bash just crashes on startup. I don't have
>> access to a Vista machine right now but it's worthwhile confirming on
it.
> 
> I don't have access to any of these (just XP, here), so I can't really
> tell where things are crashing.  It works just fine for me.
> 
>> Frame     Function  Args
>> 0028CCE8  04FF0000  (6120B808, 6120C41C, 0028CD50, 61020360)
>> 0028CD78  61020293  (00000000, 0028CDB0, 610066C0, 7EFDE000)
> 
> 61020293 looks like an address in the dll range, probably cygwin1.dll. 
It
> would be nice to know what function is dying, but doing that may require
> rebuilding a bash image with debugging symbols.  Did you by chance do any
> rebasing?  Maybe this is a case where I didn't use the correct gcc-4
flags
> for compilation, at which point an updated binutils/gcc might fix things.
> 
Same problem here (I am attaching output from msvc debugger) :

'bash.exe': Loaded 'C:\Windows\SysWOW64\usp10.dll'
cYgFFFFFFFF 61156900'bash.exe': Loaded 'C:\Windows\SysWOW64\imm32.dll'
'bash.exe': Loaded 'C:\Windows\SysWOW64\msctf.dll'
cYgstd 28ccf5 d 3First-chance exception at 0xf9350000 in bash.exe:
0xC0000005: Access violation.
cYgSiGw00f 11 0x8D0 0x28CE94First-chance exception at 0xf9350000 in
bash.exe: 0xC0000005: Access violation.
cYgSiGw00f 11 0x8D0 0x28CE94The thread 'Win32 Thread' (0xfc8) has exited
with code 0 (0x0).
'bash.exe': Loaded 'C:\Windows\SysWOW64\psapi.dll'
The program '[0xBB8] bash.exe: Native' has exited with code 35584 (0x8b00).



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