Re: gcc problem: cygwin_except_handler STATUS_ACCESS_VIOLATION

[Jason Alan Nordwick <nordwick at graft dot XCF dot Berkeley dot EDU>]

Heinz Schweitzer, on Thu 1/15/1998, wrote the following:
> 
> (unknown) In cygwin_except_handler
> (unknown) Exception trapped!
> (unknown) exception C0000005 at 1001E4B2
> (unknown) exception: ax 0 bx 0 cx 6 dx 7
> (unknown) exception: si 6779632D di 36383369 bp 241FB30 sp 241FB30
> (unknown) exception is: STATUS_ACCESS_VIOLATION
> (unknown) Stack trace:
> (unknown) frame 0: sp = 0x241F964, pc = 0x1001282A
> (unknown) frame 1: sp = 0x241F980, pc = 0x77F94492
> (unknown) frame 2: sp = 0x241F9A4, pc = 0x77F88E93
> (unknown) frame 3: sp = 0x241FA30, pc = 0x77F76202
> (unknown) frame 4: sp = 0x241FB30, pc = 0x10011D4D
> (unknown) frame 5: sp = 0x241FB44, pc = 0x10018972
> (unknown) frame 6: sp = 0x241FB5C, pc = 0x10011615
> (unknown) frame 7: sp = 0x241FF94, pc = 0x10011BFF
> (unknown) frame 8: sp = 0x241FFA0, pc = 0x4118D5
> (unknown) frame 9: sp = 0x241FFB0, pc = 0x40103B
> (unknown) frame 10: sp = 0x241FFC0, pc = 0x77F1B26B
> (unknown) frame 11: sp = 0x241FFF0, pc = 0x0
> (unknown) End of stack trace
> (unknown) In cygwin_except_handler
> (unknown) Error while dumping state (probably corrupted stack)
> 


When I got that error yesterday, it took me two hours to
figure out that it was the same as SIGBUS.  I was being stoopid
and derefing a NULL pointer.

doesn't look like the same problem, but is that always the case ?
It has nothing to do with a stack corruption, did it ?

jay
-- 
Join the FreeBSD Revolution.
Support the FSF, buy GNU.
http://xcf.berkeley.edu/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".