Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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:	<6.0.1.1.0.20040206121718.03d18000@10.82.152.185>
X-Sender:	cmetcalf AT 10 DOT 82 DOT 152 DOT 185
Date:	Fri, 06 Feb 2004 12:18:14 -0500
To:	cygwin AT cygwin DOT com
From:	Chris Metcalf <Chris DOT Metcalf AT veritas DOT com>
Subject:	access violation in ash 20040127-1 with cygwin 1.5.7-1
Mime-Version:	1.0
X-OriginalArrivalTime:	06 Feb 2004 17:18:11.0259 (UTC) FILETIME=[324CD0B0:01C3ECD5]

I got the following stack trace reproducibly, though in a way that's a
little awkward to convert to a self-contained example:

Exception: STATUS_ACCESS_VIOLATION at eip=6109399B
eax=00000000 ebx=616711C4 ecx=00000018 edx=00006B6E esi=00006B6E edi=00006B6E
ebp=00212990 esp=00212948 program=C:\cygwin\bin\sh.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
Stack trace:
Frame     Function  Args
00212990  6109399B  (002129E8, 00216A38, 00000000, 00000000)
00216A00  6104FFA0  (00216AC8, 00216A38, 0022EDB8, 00000000)
00216AB0  6104F82D  (00216AC8, 00216AC8, 0021EB08, 0022EDB8)
0021EAE0  6104F73D  (0021EB08, 0022EDB8, 0022EDB8, 00000000)
00226B30  6104F528  (00226B78, 0022EDB8, 00000000, 00000000)
00226B60  6104F158  (00226B78, 0022EDB8, 00000000, 00000000)
0022EBA0  6104F07D  (0022EBC0, 00000C90, 00000000, 0022EDB8)
0022EE00  610049F0  (0022EE62, 61110010, 6111000C, 0022EE30)
0022EE40  61004DB3  (0022EF4E, 61110010, 6111000C, 00000001)
0022EF80  61005CF4  (0022EF98, 00000000, 00000000, 00245848)
0022FF90  61005EE5  (00000000, 00000000, 00000000, 00000000)
End of stack trace

I was doing a _spawnvp() of sh.exe to run a simple shell script:
actually just an "exit 0" script in this particular case.  The spawner
was an application built with Microsoft's VC7 compiler.

I backed off to ash 20031007-1 and cygwin 1.5.5-1 and the problem went
away.  Backing off just ash by itself did not fix the problem, and I
couldn't back off just cygwin by itself, because of the fcntl64 unsat
(I believe that was the symbol, or if not something similar -- fstat64?).

Chris Metcalf


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

- Raw text -