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
Date:	Wed, 3 Jul 2002 01:28:18 -0700
From:	Clark Morgan <cmorgan AT aracnet DOT com>
To:	cygwin AT cygwin DOT com
Subject:	cygwin v1.3.11-3: flex & byacc access violation
Message-ID:	<20020703012818.B24449@aracnet.com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5.1i

For quite some time I've been using various cygwin tools (on WinME) to
build an editor called vile (a native win32 app).  The build process uses
nmake, which calls cygwin's flex to build various components.  This all works
flawlessly, or did until I upgraded to cygwin v1.3.11-3 from v1.3.10 . 
After I upgraded, flex faulted with an access violation when invoked by
nmake.  Flex did _not_ fault when invoked from the bash command line.

I experimented and also noted that:

+ byacc faulted with an access violation when invoked by nmake,
  but not when invoked from the bash command line.

+ simply reverting from the cygwin v1.3.11-3 base package to
  v1.3.10 caused the faults to disappear.

Included below are stack dumps from both faults, which were 100%
reproducible.

In closing, please note that I am a big fan of cygwin.  It's an
amazing accomplishment.

Thanks.

- Clark

BYACC.EXE.stackdump
===================
Exception: STATUS_ACCESS_VIOLATION at eip=61005558
eax=00750000 ebx=00980008 ecx=616800F0 edx=00000001 esi=00000000 edi=00000000
ebp=0074FD78 esp=0074FD30 program=C:\CYGWIN\BIN\BYACC.EXE
cs=0187 ds=018F es=018F fs=4977 gs=0000 ss=018F
Stack trace:
Frame     Function  Args
0074FD78  61005558  (610C095C, FFFFFFFE, 00000014, 610C08A0)
0074FDD8  61005D28  (00000000, 00000000, FFFFFFFF, 8179ACB4)
0074FE08  0040E017  (004048D8, 0074FC8C, BFFBB490, 0074FF68)
0074FE38  0040103D  (00000000, 8179A504, 00540000, 63617942)
0074FF78  BFF7B9E4  (8179A754, 00000008, 8179A504, 00000000)
  38223 [main] BYACC 617179 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
  38871 [main] BYACC 617179 handle_exceptions: Error while dumping state (probably corrupted stack)


FLEX.EXE.stackdump
==================
Exception: STATUS_ACCESS_VIOLATION at eip=61005558
eax=02560000 ebx=04590008 ecx=616800F0 edx=00000001 esi=00000000 edi=00000000
ebp=0255FD78 esp=0255FD30 program=C:\CYGWIN\BIN\FLEX.EXE
cs=0187 ds=018F es=018F fs=3D8F gs=0000 ss=018F
Stack trace:
Frame     Function  Args
0255FD78  61005558  (610C095C, FFFFFFFE, 00000010, 610C08A0)
0255FDD8  61005D28  (00000000, 00000000, FFFFFFFF, 817DCD0C)
0255FE08  004223C3  (004075A4, 0255FC8C, BFFBB490, 0255FF68)
0255FE38  0040103D  (00000000, 817DC554, 00550000, 78656C46)
0255FF78  BFF7B9E4  (817DC7AC, 00000008, 817DC554, 00000000)
  25881 [main] FLEX 857183 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
  26406 [main] FLEX 857183 handle_exceptions: Error while dumping state (probably corrupted stack)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -