X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,TW_XF,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <AANLkTinTTqUHMjCXisfzcYRlK2TI2kDX9d5AgZBOME9R@mail.gmail.com>
References: <AANLkTinTTqUHMjCXisfzcYRlK2TI2kDX9d5AgZBOME9R AT mail DOT gmail DOT com>
Date: Thu, 13 May 2010 17:45:34 -0400
Message-ID: <AANLkTilaKXeL_hpWaeRwBDVIq-j5hSdIYigmkjsvCxlO@mail.gmail.com>
Subject: Re: 1.7.5-1: execv fails in .exe compiled
From: Stephen Morton <stephen DOT c DOT morton AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
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

The problem appears to be cygwin 1.7-specific. (*)

I get a stackdump as follows. I find that I get a stackdump under a
cygwin shell (DOS terminal) but not under mintty so I'm not 100% sure
the stackdump is for the correct error.

Exception: STATUS_ACCESS_VIOLATION at eip=611131D8
eax=0022B9E4 ebx=7FF70008 ecx=00000063 edx=0022B9E4 esi=00000001 edi=00000005
ebp=0022B998 esp=0022B950
program=C:\usr\local\companytools\gcc34\x86\cc386.exe, pid 1312,
thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022B998  611131D8  (0022D000, 7FF70008, 10029448, 00000005)
0022B9F8  610C953E  (00008000, 10029448, 00000005, 00000001)
1002944D  6103413C  (68000000, 46611C2F, 68DF0DF0, 00100280)
End of stack trace

I was able to get a further stack trace from gdb from that. Again, it
would only happen on a cygwin shell and not mintty so I'm not sure I
copied the correct error:
(gdb) backtrace
#0  0x7c90120f in ?? ()
#1  0x7c951e68 in ?? ()
#2  0x00000005 in ?? ()
#3  0x00000004 in ?? ()
#4  0x00000001 in ?? ()
#5  0x006dffd0 in ?? ()
#6  0x00000246 in ?? ()
#7  0xffffffff in ?? ()
#8  0x7c90e920 in ?? ()
#9  0x7c951e88 in ?? ()
#10 0x00000000 in ?? ()

Stephen

(*) I know that doesn't mean that it's 1.7's fault. Perhaps the
problem was pre-existing and was only revealed in 1.7. But it works in
1.3 and 1.5 on WinXP and fails in 1.7 in WinXP-32, Vista-32, Win7-67.

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