Mail Archives: cygwin/2001/07/12/12:50:47
I'm getting occasional and apparently random Signal 11 (SEGV) exceptions
while running under Cygwin.
I'm doing a cross-build of Glibc and after running for a while (sometimes
a long while) one of the programs executed by make gets an exception.
The stackdump looks like the following:
Exception: STATUS_ACCESS_VIOLATION at eip=00000000
eax=00000000 ebx=00000006 ecx=610956F8 edx=00000000 esi=610901EC edi=610901F4
ebp=0241FE34 esp=0241FE18 program=C:\cygwin\bin\rm.exe
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
End of stack trace
Note that in this case, rm got the SEGV, other times it has been
cpp0, ld or mv.
The problem is not reproducible -- running the same make a second time
will fail somewhere else. I don't have copies of the stackdump from other
executions at hand, so I can't compare, but in each of them the stack
trace is empty.
Any suggestions on (1) what might be causing this, (2) how I can avoid
the problem, and/or (3) how I can fix it?
BTW, I'm running on NT2K with the latest version of Cygwin.
--
Michael Eager Eager Consulting eager AT eagercon DOT com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
--
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 -