Cygwin 1.7.6-1 , Windows 7: STATUS_ACCESS_VIOLATION

[Siegmar Gross <Siegmar dot Gross at informatik dot hs-fulda dot de>]

Hi,

I have installed Cygwin 1.7.6-1 on "Windows 7" running on a
virtual machine (VMware Workstation 6.5.4). I am using TCSH instead
of BASH and I have configured  an X11 GUI which I use since 2004
with Cygwin 1.5.x (since about a year with X11R7) on Windows XP
without problems. When I use this environment with Cygwin 1.7.6, I
have the following problems. I have seen in the mailing list that
other persons have similar problems, but I have not found a solution.
Perhaps I have some additional information which can track the problem.

Sometimes I get only one xterm-window or the background color of
the root window will only be painted in the upper part or not
all. Most times I get no xterm-window, when I left-click in the
root window of the window manager "fvwm2" and choose "xterm". In
these cases I get for example the following error messages in the
original console window from Cygwin.

      8 [main] fvwm 3168 exception::handle: Exception:
        STATUS_ACCESS_VIOLATION
 101981 [main] fvwm 3168 open_stackdumpfile: Dumping stack trace
        to fvwm.exe.stackdump
      8 [main] xterm 468 exception::handle: Exception:
        STATUS_ACCESS_VIOLATION
   1591 [main] xterm 468 open_stackdumpfile: Dumping stack trace
        to xterm.exe.stackdump

I close and restart Cygwin in these cases until I get the expected
user interface with two "xterm windows". The problem remains even if
I disable "Windows Firewall". Sometimes Cygwin repaints only the upper
part of the graphical user interface when I close Cygwin to an icon and
reopen the icon. When I move with the mouse cursor over the unpainted
parts (contents of "xterm windows" or the background of the "root
window") the area under the mouse pointer will be repainted (like a
brush). Sometimes all missing parts are automatically repainted when I
execute a command. The access violation is not restricted to "xterm".


tyr x 135 cat fvwm_1.exe.stackdump 
Exception: STATUS_ACCESS_VIOLATION at eip=610200B7
eax=00C3F870 ebx=6123DC54 ecx=7514783F edx=003E4118 esi=00000000 edi=0022FA14
ebp=61020800 esp=0022C7E4 program=C:\cygwin\bin\fvwm.exe, pid 2356, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
End of stack trace

tyr x 136 diff fvwm_1.exe.stackdump fvwm_2.exe.stackdump 
2,3c2,3
< eax=00C3F870 ebx=6123DC54 ecx=7514783F edx=003E4118 esi=00000000 edi=0022FA14
< ebp=61020800 esp=0022C7E4 program=C:\cygwin\bin\fvwm.exe, pid 2356, thread main
---
> eax=00C347C0 ebx=6123DE2C ecx=7574783F edx=00264118 esi=00000000 edi=0022FA14
> ebp=61020800 esp=0022C7E4 program=C:\cygwin\bin\fvwm.exe, pid 2312, thread main


tyr x 137 cat xterm_1.exe.stackdump 
Exception: STATUS_ACCESS_VIOLATION at eip=610200B7
eax=00B900F8 ebx=6123E374 ecx=75B9783F edx=003E4118 esi=00000000 edi=0022FA14
ebp=61020800 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 2104, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
End of stack trace

tyr x 138 diff xterm_1.exe.stackdump xterm_2.exe.stackdump 
2,3c2,3
< eax=00B900F8 ebx=6123E374 ecx=75B9783F edx=003E4118 esi=00000000 edi=0022FA14
< ebp=61020800 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 2104, thread main
---
> eax=00AD00F8 ebx=6123E694 ecx=7574783F edx=003D4118 esi=00000000 edi=0022FA14
> ebp=61020800 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 4000, thread main

tyr x 139 diff xterm_1.exe.stackdump xterm_3.exe.stackdump
2,3c2,3
< eax=00B900F8 ebx=6123E374 ecx=75B9783F edx=003E4118 esi=00000000 edi=0022FA14
< ebp=61020800 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 2104, thread main
---
> eax=00D100F8 ebx=6123E50C ecx=7574783F edx=002D4118 esi=00000000 edi=0022FA14
> ebp=61020800 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 2788, thread main
tyr x 140 


tyr x 141 cat id.exe.stackdump 
Exception: STATUS_ACCESS_VIOLATION at eip=610BFE94
eax=00000000 ebx=18EC0000 ecx=00000010 edx=67F054B2 esi=67F0B000 edi=00000001
ebp=18EBFD9C esp=18EBFD74 program=C:\cygwin\bin\id.exe, pid 3944, thread unknown (0xE5C)
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
18EBFD9C  610BFE94  (67F0B000, 67F05550, 18EBFE1C, 6102001A)
18EBFDAC  67F010D9  (61161D98, 6123A424, 6123A424, 610205E0)
18EBFE1C  6102001A  (67F00000, 00000000, 00000001, 005C23A0)
18EBFE3C  76EEAFC4  (67F08920, 67F00000, 00000000, 00000001)
18EBFEE0  76EF38DA  (00000000, 00000002, 00000000, 18EBFF88)
18EBFEF4  76EF384D  (00000000, 7666D513, 00000002, C4B334DF)
18EBFF88  7666D358  (00000002, 18EBFFD4, 76EEB495, 00000002)
18EBFF94  76611194  (00000002, 6E0A380C, 00000000, 00000000)
18EBFFD4  76EEB495  (7666D35E, 00000002, 00000000, 00000000)
     12 [unknown (0xE5C)] id 3944 exception::handle: Error while dumping state (probably 
corrupted stack)


tyr x 142 cat tcsh.exe.stackdump 
Exception: STATUS_ACCESS_VIOLATION at eip=610BFE94
eax=00000000 ebx=008A0000 ecx=00000010 edx=67F054B2 esi=67F0B000 edi=00000001
ebp=0089FD9C esp=0089FD74 program=C:\cygwin\bin\tcsh.exe, pid 3240, thread unknown (0xC5C)
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0089FD9C  610BFE94  (67F0B000, 67F05550, 0089FE1C, 6102001A)
0089FDAC  67F010D9  (61161D98, 6123A424, 6123A424, 610205E0)
0089FE1C  6102001A  (67F00000, 00000000, 00000001, 005A2560)
0089FE3C  7757AFC4  (67F08920, 67F00000, 00000000, 00000001)
0089FEE0  775838DA  (00000000, 00000002, 00000000, 0089FF88)
0089FEF4  7758384D  (00000000, 76F4D513, 00000002, 812A24CF)
0089FF88  76F4D358  (00000002, 0089FFD4, 7757B495, 00000002)
0089FF94  76EF1194  (00000002, 76E2454F, 00000000, 00000000)
0089FFD4  7757B495  (76F4D35E, 00000002, 00000000, 00000000)
      8 [unknown (0xC5C)] tcsh 3240 exception::handle: Error while dumping state (probably 
corrupted stack)
tyr x 143 

If you need any other information I can try to provide it. Thank you
very much for any help to solve this problem in advance.

Kind regards

Siegmar


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/