[Cygwin64] Flex segfault

[Cygwin64] Flex segfault

[Teemu Nätkinniemi]

I noticed during compiling Cocom that flex segfaults when it is trying 
to run a basic test. After working around the fault I tried several 
different scripts and they all fail.

%%
%%

This res

Starting program: /usr/bin/flex flextest.l
[New Thread 7436.0xff8]
[New Thread 7436.0x1ef4]

Program received signal SIGSEGV, Segmentation fault.
flexinit (argc=argc@entry=2, argv=argv@entry=0x23aaf0)
     at /usr/src/debug/flex-2.5.37-1/main.c:966
966             action_array[0] = '\0';

(gdb) t a a bt
Thread 2 (Thread 7436.0x1ef4):
#0  0x000007fcf1a32c4a in ?? ()
#1  0x000007fceeda6188 in ReadFile ()
    from /cygdrive/c/Windows/system32/KERNELBASE.dll
#2  0x0000000000000000 in ?? ()

Thread 1 (Thread 7436.0xff8):
#0  flexinit (argc=argc@entry=2, argv=argv@entry=0x23aaf0)
     at /usr/src/debug/flex-2.5.37-1/main.c:966
#1  0x000000010040b3bc in flex_main (argc=2, argv=0x23aaf0)
     at /usr/src/debug/flex-2.5.37-1/main.c:181
#2  0x0000000180047834 in _cygwin_exit_return ()
     at /usr/src/debug/cygwin-1.7.18-3/winsup/cygwin/dcrt0.cc:1029
#3  0x000000018004573b in _cygtls::call2 (this=0x23ce00,
     func=0x1800469e0 <dll_crt0_1(void*)>, arg=0x0, buf=0x23ccf0)
     at /usr/src/debug/cygwin-1.7.18-3/winsup/cygwin/cygtls.cc:99
#4  0x00000001800458ff in _cygtls::call (
     func=0x1800469e0 <dll_crt0_1(void*)>, arg=0x0)
     at /usr/src/debug/cygwin-1.7.18-3/winsup/cygwin/cygtls.cc:30
#5  0x000000010041d0c1 in cygwin_crt0 (f=<optimized out>)
     at 
/usr/src/debug/cygwin64-20130305-1/winsup/cygwin/lib/cygwin_crt0.c:22
#6  0x0000000100401010 in mainCRTStartup ()
     at /usr/src/debug/cygwin64-20130305-1/winsup/cygwin/crt0.c:29

Stackdump:

Exception: STATUS_ACCESS_VIOLATION at rip=0010040A5EF
rax=FFFFFFFFFFFE0470 rbx=0000000000000001 rcx=0000000100455560
rdx=0000000000000001 rsi=0000000000000004 rdi=000000000023AA10
r8 =000000000000F391 r9 =0000000000000000 r10=0000000180133D04
r11=00000001004186A9 r12=000000000023AB20 r13=0000000000000002
r14=0000000000000000 r15=0000000000000000
rbp=000000000023AB80 rsp=000000000023A9D0
program=G:\cygwin64\bin\flex.exe, pid 7052, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame        Function    Args
0000023AB80  0010040A5EF (0000023AB80, 00000000002, 0000023AB20, 
00200000002)
0000023AB80  0010040B3BC (00000000020, FF0700010302FF00, 001800477CA, 
00000000000)
0000023AB80  00180047834 (00000000000, 00000000000, 00000000000, 
00000000000)
00000000000  0018004573B (00000000000, 00000000000, 00000000000, 
00000000000)
00000000000  001800458FF (00000000000, 00000000000, 00000000000, 
00000000000)
00000000000  0010041D0C1 (00000000000, 00000000000, 00000000000, 
00000000000)
00000000000  00100401010 (00000000000, 00000000000, 00000000000, 
00000000000)
00000000000  7FCF18E167E (00000000000, 00000000000, 00000000000, 
00000000000)
00000000000  7FCF1A53501 (00000000000, 00000000000, 00000000000, 
00000000000)
End of stack trace

Re: [Cygwin64] Flex segfault

[Corinna Vinschen]

On Mar 11 20:30, Teemu Nätkinniemi wrote:
> I noticed during compiling Cocom that flex segfaults when it is
> trying to run a basic test. After working around the fault I tried
> several different scripts and they all fail.

Kai and I encountered the same just half an hour ago.  It crashes right
within main for some reason.  For the time being you can use my flex
package from the install area.  It doesn't crash.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Re: [Cygwin64] Flex segfault

[Teemu Nätkinniemi]

On 11.3.2013 20:38, Corinna Vinschen wrote:
> On Mar 11 20:30, Teemu Nätkinniemi wrote:
>> I noticed during compiling Cocom that flex segfaults when it is
>> trying to run a basic test. After working around the fault I tried
>> several different scripts and they all fail.
>
> Kai and I encountered the same just half an hour ago.  It crashes right
> within main for some reason.  For the time being you can use my flex
> package from the install area.  It doesn't crash.

No crashes encountered, thanks a lot!