STATUS ACCESS VIOLATION - Transferring Flex & Bison to another machine - Advice needed

["Killion, Richard" <rkillion at harris dot com>]

I am transferring a flex/bison environment from one Win 95 machine
to mine and get a Status Access violation with the new machine.  

I would like to know what I am missing. ( The engineer just left 
& I need it on my machine to continue his development.) 

I do not have access to a B19 setup.exe program.

The Bison command (shown below) works fine on his machine but not on mine.

On my machine, I am getting STATUS ACCESS VIOLATION when I run the 
batch file with Flex and Bison commands.  It gets by the flex command
successfully  and creates the AcmLexer.c file.  

The Bison command gives the error message and the AcmParse.c command 
is not created ( the file is NOT read-only).

The two  commands are from a bat file & I have re-typed
with  the error message shown below:
 
c:\cygnus\b19\h-i386-cygwin32\bin\flex -oAcmLexer.c acm.l

c:\cygnus\b19\h-i386-cygwin32\bin\bison -oAcmParse.c -d acm.y
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) Exception: STATUS_ACC
ESS VIOLATION
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000)  Dumping stack trace
to BISON.EXE.core)
 

Both machines have the same settings & files as shown below:

1)  Same autoexec.bat and config.sys commands and path settings

2)  Same version OS -- Win95 4.00.950B

3)  Same DLLs, file size, dates & time at: 

	C:\Cygnus\B19\H-i386-cygwin32\bin 

	cygtcl80.dll
	cygtclpip80.dll
	cygtclreg80.dll
	cygwinb19.dll
	cygtk80.dll

4) The previous engineer had cygwinb19.dll in a vxworks-tornado 
directory,  I removed this extra dll, but it still fails on my machine 
(and works on his with all permutations of dlls).

5) The Dos "mem" command shows the same memory configuration.

The original setup file for B19 is not available here.  I installed the
latest flex and bison , but still get errors.  I uninstalled it & just
copied the his environment back and currently at this state.

Any clues what I need to duplicate the other machine's setup ?  I'm stumped
(and very new to flex & bison).  I went through the cygwin list archives & 
could not find anything similar to my problem.

The first third of the  BISON.EXE.core file  is as follows:

(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) Exception trapped!
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) exception C0000005 at
10011A7E
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) exception: ax 0 bx 5 cx 9 dx
4580008
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) exception: si 0 di 10011879
bp 254FA78 sp 254FA08
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) exception is:
STATUS_ACCESS_VIOLATION
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) Stack trace:
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) frame 0: sp = 0x254F71C, pc =
0x1000A26C
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) frame 1: sp = 0x254F840, pc =
0xBFF766B5
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) frame 2: sp = 0x254F864, pc =
0xBFF85E6C
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) frame 3: sp = 0x254F8F8, pc =
0xFFECBAD7

 ... this goes on with similar stack frame lines and finishes with:

(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) frame 15: sp = 0x254FE38, pc
= 0xBFF89349
(C:\CYGNUS\B19\H-I386-CYGWIN32\BIN\BISON.EXE 1000) End of stack trace (more
stack frames may be present)


Any clues would be truly appreciated.

Sincerely,

rkillion@harris.com





--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com