* 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
@ 2010-04-18 22:09 Yuval Emek
2010-04-19 1:01 ` Dave Korn
0 siblings, 1 reply; 10+ messages in thread
From: Yuval Emek @ 2010-04-18 22:09 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
Recently, when trying to run various programs (e.g., xterm, emacs,
subversion), I often get a message of the following type:
4 [main] xterm 4640 exception::handle: Exception: STATUS_ACCESS_VIOLATION
496 [main] xterm 4640 open_stackdumpfile: Dumping stack trace to
xterm.exe.stackdump
The context of the file xterm.exe.stackdump is:
Exception: STATUS_ACCESS_VIOLATION at eip=610202F7
eax=00CE00F8 ebx=61229E44 ecx=7530783F edx=002D20F0 esi=00000000 edi=0022FA14
ebp=61020A10 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 4640, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
End of stack trace
In attempt to pin down the problem, I reinstalled cygwin from scratch,
using setup.exe with noting but the default setting + xinit. When
trying to open an xterm window (from an existing one) I often get the
aforementioned message. (In fact, many times I get multiple copies of
these two lines.)
I think that this problem has nothing to do with the problem reported
to be solved in
http://sourceware.org/ml/cygwin/2010-01/msg00632.html
This is because:
(1) the tsaware flag is set for xterm; and
(2) my windows 7 is in "Turn on DEP for essential Windows programs and
services only" mode.
Any suggestions?
Thanks,
Yuval
The cygcheck.out and /var/log/XWin.0.log files are attached.
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 27961 bytes --]
Cygwin Configuration Diagnostics
Current System Time: Mon Apr 19 00:06:47 2010
Windows 7 Enterprise Ver 6.1 Build 7600
Path: C:\cygwin\usr\local\bin
C:\cygwin\bin
C:\cygwin\bin
C:\Program Files\MiKTeX 2.8\miktex\bin
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Program Files\System Center Operations Manager 2007\
C:\Program Files\Common Files\Lenovo
C:\Program Files\Windows Imaging\
Output from C:\cygwin\bin\id.exe
UID: 123982(i-yuvale) GID: 10513(mkgroup)
10513(mkgroup) 545(Users)
SysDir: C:\Windows\system32
WinDir: C:\Windows
USER = 'i-yuvale'
PWD = '/home/i-yuvale'
HOME = '/home/i-yuvale'
HOMEPATH = '\Users\i-yuvale'
MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man'
APPDATA = 'C:\Users\i-yuvale\AppData\Roaming'
HOSTNAME = 'YuvalEm-W7'
TERM = 'xterm'
PROCESSOR_IDENTIFIER = 'x86 Family 6 Model 23 Stepping 6, GenuineIntel'
WINDIR = 'C:\Windows'
TVT = 'C:\Program Files\Lenovo'
WINDOWID = '2097185'
PUBLIC = 'C:\Users\Public'
UATDATA = 'C:\Windows\system32\CCM\UATData\D9F8C395-CAB8-491d-B8AC-179A1FE1BE77'
OS = 'Windows_NT'
ALLUSERSPROFILE = 'C:\ProgramData'
XTERM_SHELL = '/bin/bash'
!:: = '::\'
COMMONPROGRAMFILES = 'c:\Program Files\Common Files'
USERNAME = 'i-yuvale'
PROCESSOR_LEVEL = '6'
PSModulePath = 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\'
FP_NO_HOST_CHECK = 'NO'
SYSTEMDRIVE = 'C:'
LANG = 'C.UTF-8'
USERPROFILE = 'C:\Users\i-yuvale'
LOGONSERVER = '\\HEZ-ME-DC-01'
PROCESSOR_ARCHITECTURE = 'x86'
LOCALAPPDATA = 'C:\Users\i-yuvale\AppData\Local'
XTERM_LOCALE = 'C.UTF-8'
XTERM_VERSION = 'Cygwin 6.8.99.903(255)'
ProgramData = 'C:\ProgramData'
SHLVL = '3'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC'
HOMEDRIVE = 'C:'
COMSPEC = 'C:\Windows\system32\cmd.exe'
LOGNAME = 'i-yuvale'
SYSTEMROOT = 'C:\Windows'
PRINTER = '\\hez-printserver\HP LaserJet M4345 MFP SafeCom'
CVS_RSH = '/bin/ssh'
PROCESSOR_REVISION = '1706'
INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:'
PROGRAMFILES = 'c:\Program Files'
DISPLAY = ':0.0'
NUMBER_OF_PROCESSORS = '2'
SESSIONNAME = 'Console'
COMPUTERNAME = 'YUVALEM-W7'
_ = '/usr/bin/cygcheck'
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
(default) = '/cygdrive'
cygdrive flags = 0x00000022
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/
(default) = 'C:\cygwin'
flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
(default) = 'C:\cygwin/bin'
flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
(default) = 'C:\cygwin/lib'
flags = 0x00000002
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Program Options
HKEY_CURRENT_USER\Software\Cygwin\setup
HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
(default) = '/cygdrive'
cygdrive flags = 0x00000022
HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options
HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Cygwin
HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Cygwin\Installations
(default) = '\??\C:\cygwin'
HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Cygwin\Program Options
HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Cygwin\setup
(default) = 'C:\cygwin'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
(default) = '/cygdrive'
cygdrive flags = 0x00000022
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
(default) = '\??\C:\cygwin'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
(default) = 'C:\cygwin'
obcaseinsensitive set to 1
Cygwin installations found in the registry:
System: Key: c5e39b7a9d22bafb Path: C:\cygwin
c: hd NTFS 152524Mb 22% CP CS UN PA FC
C:\cygwin / system binary,auto
C:\cygwin\bin /usr/bin system binary,auto
C:\cygwin\lib /usr/lib system binary,auto
cygdrive prefix /cygdrive user binary,auto
Found: C:\cygwin\bin\awk.exe
Found: C:\cygwin\bin\awk.exe
-> C:\cygwin\bin\gawk.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cp.exe
Found: C:\cygwin\bin\cp.exe
Not Found: cpp (good!)
Not Found: crontab
Found: C:\cygwin\bin\find.exe
Found: C:\cygwin\bin\find.exe
Found: C:\Windows\system32\find.exe
Warning: C:\cygwin\bin\find.exe hides C:\Windows\system32\find.exe
Not Found: gcc
Not Found: gdb
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\kill.exe
Found: C:\cygwin\bin\kill.exe
Not Found: ld
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\ls.exe
Not Found: make
Found: C:\cygwin\bin\mv.exe
Found: C:\cygwin\bin\mv.exe
Not Found: patch
Found: C:\cygwin\bin\perl.exe
Found: C:\cygwin\bin\perl.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\sed.exe
Found: C:\cygwin\bin\sed.exe
Not Found: ssh
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\tar.exe
Found: C:\cygwin\bin\tar.exe
Found: C:\cygwin\bin\test.exe
Found: C:\cygwin\bin\test.exe
Not Found: vi
Not Found: vim
61k 2009/03/02 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
"cygbz2-1.dll" v0.0 ts=2009/3/2 5:11
7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypt-0.dll" v0.0 ts=2003/10/19 9:57
1144k 2010/03/24 C:\cygwin\bin\cygcrypto-0.9.8.dll - os=4.0 img=1.0 sys=4.0
"cygcrypto-0.9.8.dll" v0.0 ts=2010/3/24 17:16
943k 2007/12/17 C:\cygwin\bin\cygdb-4.5.dll - os=4.0 img=1.0 sys=4.0
"cygdb-4.5.dll" v0.0 ts=2007/12/17 15:12
1296k 2007/12/17 C:\cygwin\bin\cygdb_cxx-4.5.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-4.5.dll" v0.0 ts=2007/12/17 15:12
118k 2008/05/09 C:\cygwin\bin\cygexpat-1.dll - os=4.0 img=1.0 sys=4.0
"cygexpat-1.dll" v0.0 ts=2008/5/9 7:03
176k 2010/01/29 C:\cygwin\bin\cygfontconfig-1.dll - os=4.0 img=1.0 sys=4.0
"cygfontconfig-1.dll" v0.0 ts=2010/1/29 0:12
21k 2009/10/14 C:\cygwin\bin\cygfontenc-1.dll - os=4.0 img=1.0 sys=4.0
"cygfontenc-1.dll" v0.0 ts=2009/10/14 3:04
43k 2010/01/02 C:\cygwin\bin\cygform-10.dll - os=4.0 img=1.0 sys=4.0
"cygform-10.dll" v0.0 ts=2010/1/2 16:49
40k 2009/03/01 C:\cygwin\bin\cygform-8.dll - os=4.0 img=1.0 sys=4.0
"cygform-8.dll" v0.0 ts=2009/3/1 8:32
43k 2009/11/20 C:\cygwin\bin\cygform-9.dll - os=4.0 img=1.0 sys=4.0
"cygform-9.dll" v0.0 ts=2009/11/20 21:14
492k 2010/03/03 C:\cygwin\bin\cygfreetype-6.dll - os=4.0 img=1.0 sys=4.0
"cygfreetype-6.dll" v0.0 ts=2010/3/2 23:24
45k 2009/12/11 C:\cygwin\bin\cyggcc_s-1.dll - os=4.0 img=1.0 sys=4.0
"cyggcc_s-1.dll" v0.0 ts=2009/12/8 2:30
449k 2010/03/17 C:\cygwin\bin\cyggcrypt-11.dll - os=4.0 img=1.0 sys=4.0
"cyggcrypt-11.dll" v0.0 ts=2010/3/17 23:45
19k 2009/02/26 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-4.dll" v0.0 ts=2009/2/26 9:58
8k 2009/02/26 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-4.dll" v0.0 ts=2009/2/26 9:58
2389k 2010/02/10 C:\cygwin\bin\cygGL-1.dll - os=4.0 img=1.0 sys=4.0
"cygGL-1.dll" v0.0 ts=2010/2/10 3:40
315k 2009/06/06 C:\cygwin\bin\cyggmp-3.dll - os=4.0 img=1.0 sys=4.0
"cyggmp-3.dll" v0.0 ts=2009/6/6 14:23
16k 2010/03/17 C:\cygwin\bin\cyggpg-error-0.dll - os=4.0 img=1.0 sys=4.0
"cyggpg-error-0.dll" v0.0 ts=2010/3/17 23:21
25k 2009/07/06 C:\cygwin\bin\cyghistory7.dll - os=4.0 img=1.0 sys=4.0
"cyghistory7.dll" v0.0 ts=2009/7/5 17:45
73k 2009/09/02 C:\cygwin\bin\cygICE-6.dll - os=4.0 img=1.0 sys=4.0
"cygICE-6.dll" v0.0 ts=2009/9/3 0:39
360k 2009/12/29 C:\cygwin\bin\cygicons-0.dll - os=4.0 img=1.4 sys=4.0
"cygicons-0.dll" v0.0 ts=2009/12/29 7:30
982k 2009/12/23 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
"cygiconv-2.dll" v0.0 ts=2009/12/23 15:25
31k 2005/11/20 C:\cygwin\bin\cygintl-3.dll - os=4.0 img=1.0 sys=4.0
"cygintl-3.dll" v0.0 ts=2005/11/20 4:04
31k 2009/04/03 C:\cygwin\bin\cygintl-8.dll - os=4.0 img=1.0 sys=4.0
"cygintl-8.dll" v0.0 ts=2009/4/3 4:15
5k 2010/04/12 C:\cygwin\bin\cyglsa.dll - os=4.0 img=1.0 sys=4.0
"cyglsa.dll" v0.0 ts=2010/4/12 20:08
9k 2010/04/12 C:\cygwin\bin\cyglsa64.dll - os=5.2 img=0.0 sys=5.2
125k 2010/04/09 C:\cygwin\bin\cyglzma-1.dll - os=4.0 img=1.0 sys=4.0
"cyglzma-1.dll" v0.0 ts=2010/4/9 18:54
25k 2010/01/02 C:\cygwin\bin\cygmenu-10.dll - os=4.0 img=1.0 sys=4.0
"cygmenu-10.dll" v0.0 ts=2010/1/2 16:48
21k 2009/03/01 C:\cygwin\bin\cygmenu-8.dll - os=4.0 img=1.0 sys=4.0
"cygmenu-8.dll" v0.0 ts=2009/3/1 8:31
25k 2009/11/20 C:\cygwin\bin\cygmenu-9.dll - os=4.0 img=1.0 sys=4.0
"cygmenu-9.dll" v0.0 ts=2009/11/20 21:13
211k 2009/06/06 C:\cygwin\bin\cygmp-3.dll - os=4.0 img=1.0 sys=4.0
"cygmp-3.dll" v0.0 ts=2009/6/6 14:23
63k 2010/01/02 C:\cygwin\bin\cygncurses++-10.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++-10.dll" v0.0 ts=2010/1/2 17:00
66k 2009/03/01 C:\cygwin\bin\cygncurses++-8.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++-8.dll" v0.0 ts=2009/3/1 8:39
63k 2009/11/20 C:\cygwin\bin\cygncurses++-9.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++-9.dll" v0.0 ts=2009/11/20 21:25
195k 2010/01/02 C:\cygwin\bin\cygncurses-10.dll - os=4.0 img=1.0 sys=4.0
"cygncurses-10.dll" v0.0 ts=2010/1/2 16:45
237k 2009/03/01 C:\cygwin\bin\cygncurses-8.dll - os=4.0 img=1.0 sys=4.0
"cygncurses-8.dll" v0.0 ts=2009/3/1 8:28
198k 2009/11/20 C:\cygwin\bin\cygncurses-9.dll - os=4.0 img=1.0 sys=4.0
"cygncurses-9.dll" v0.0 ts=2009/11/20 21:10
13k 2010/01/02 C:\cygwin\bin\cygpanel-10.dll - os=4.0 img=1.0 sys=4.0
"cygpanel-10.dll" v0.0 ts=2010/1/2 16:47
11k 2009/03/01 C:\cygwin\bin\cygpanel-8.dll - os=4.0 img=1.0 sys=4.0
"cygpanel-8.dll" v0.0 ts=2009/3/1 8:30
13k 2009/11/20 C:\cygwin\bin\cygpanel-9.dll - os=4.0 img=1.0 sys=4.0
"cygpanel-9.dll" v0.0 ts=2009/11/20 21:12
217k 2009/11/10 C:\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcre-0.dll" v0.0 ts=2009/10/25 11:42
8k 2009/11/10 C:\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcreposix-0.dll" v0.0 ts=2009/10/25 11:42
1553k 2009/12/19 C:\cygwin\bin\cygperl5_10.dll - os=4.0 img=1.0 sys=4.0
"cygperl5_10.dll" v0.0 ts=2009/12/18 16:54
377k 2010/04/02 C:\cygwin\bin\cygpixman-1-0.dll - os=4.0 img=1.0 sys=4.0
"cygpixman-1-0.dll" v0.0 ts=2010/4/2 10:44
22k 2002/06/09 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
"cygpopt-0.dll" v0.0 ts=2002/6/9 8:45
162k 2009/07/06 C:\cygwin\bin\cygreadline7.dll - os=4.0 img=1.0 sys=4.0
"cygreadline7.dll" v0.0 ts=2009/7/5 17:45
27k 2009/09/03 C:\cygwin\bin\cygSM-6.dll - os=4.0 img=1.0 sys=4.0
"cygSM-6.dll" v0.0 ts=2009/9/3 11:56
264k 2010/03/24 C:\cygwin\bin\cygssl-0.9.8.dll - os=4.0 img=1.0 sys=4.0
"cygssl-0.9.8.dll" v0.0 ts=2010/3/24 17:17
10k 2009/12/11 C:\cygwin\bin\cygssp-0.dll - os=4.0 img=1.0 sys=4.0
"cygssp-0.dll" v0.0 ts=2009/12/8 2:38
773k 2009/12/11 C:\cygwin\bin\cygstdc++-6.dll - os=4.0 img=1.0 sys=4.0
"cygstdc++-6.dll" v0.0 ts=2009/12/8 3:07
48k 2010/01/02 C:\cygwin\bin\cygtic-10.dll - os=4.0 img=1.0 sys=4.0
"cygtic-10.dll" v0.0 ts=2010/1/2 16:45
48k 2009/11/20 C:\cygwin\bin\cygtic-9.dll - os=4.0 img=1.0 sys=4.0
"cygtic-9.dll" v0.0 ts=2009/11/20 21:10
1040k 2010/02/10 C:\cygwin\bin\cygX11-6.dll - os=4.0 img=1.0 sys=4.0
"cygX11-6.dll" v0.0 ts=2010/2/10 2:42
9k 2009/09/03 C:\cygwin\bin\cygXau-6.dll - os=4.0 img=1.0 sys=4.0
"cygXau-6.dll" v0.0 ts=2009/9/3 0:47
352k 2009/10/19 C:\cygwin\bin\cygXaw-7.dll - os=4.0 img=1.0 sys=4.0
"cygXaw-7.dll" v0.0 ts=2009/10/18 23:55
76k 2009/12/14 C:\cygwin\bin\cygxcb-1.dll - os=4.0 img=1.0 sys=4.0
"cygxcb-1.dll" v0.0 ts=2009/12/14 21:17
17k 2009/10/14 C:\cygwin\bin\cygXdmcp-6.dll - os=4.0 img=1.0 sys=4.0
"cygXdmcp-6.dll" v0.0 ts=2009/10/14 0:31
51k 2009/10/22 C:\cygwin\bin\cygXext-6.dll - os=4.0 img=1.0 sys=4.0
"cygXext-6.dll" v0.0 ts=2009/10/22 5:45
66k 2009/10/15 C:\cygwin\bin\cygXft-2.dll - os=4.0 img=1.0 sys=4.0
"cygXft-2.dll" v0.0 ts=2009/10/14 22:33
122k 2009/10/15 C:\cygwin\bin\cygxkbfile-1.dll - os=4.0 img=1.0 sys=4.0
"cygxkbfile-1.dll" v0.0 ts=2009/10/14 7:57
75k 2009/10/14 C:\cygwin\bin\cygXmu-6.dll - os=4.0 img=1.0 sys=4.0
"cygXmu-6.dll" v0.0 ts=2009/10/14 9:29
11k 2009/10/14 C:\cygwin\bin\cygXmuu-1.dll - os=4.0 img=1.0 sys=4.0
"cygXmuu-1.dll" v0.0 ts=2009/10/14 9:29
53k 2009/10/14 C:\cygwin\bin\cygXpm-4.dll - os=4.0 img=1.0 sys=4.0
"cygXpm-4.dll" v0.0 ts=2009/10/14 19:01
30k 2009/10/14 C:\cygwin\bin\cygXrender-1.dll - os=4.0 img=1.0 sys=4.0
"cygXrender-1.dll" v0.0 ts=2009/10/14 9:40
279k 2010/04/02 C:\cygwin\bin\cygXt-6.dll - os=4.0 img=1.0 sys=4.0
"cygXt-6.dll" v0.0 ts=2010/4/2 8:27
64k 2009/03/02 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
"cygz.dll" v0.0 ts=2009/3/2 3:33
2547k 2010/04/12 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2010/4/12 20:07
Cygwin DLL version info:
DLL version: 1.7.5
DLL epoch: 19
DLL old termios: 5
DLL malloc env: 28
Cygwin conv: 181
API major: 0
API minor: 225
Shared data: 5
DLL identifier: cygwin1
Mount registry: 3
Cygwin registry name: Cygwin
Program options name: Program Options
Installations name: Installations
Cygdrive default prefix:
Build date:
Shared id: cygwin1S5
61k 2009/03/02 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
"cygbz2-1.dll" v0.0 ts=2009/3/2 5:11
7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
"cygcrypt-0.dll" v0.0 ts=2003/10/19 9:57
1144k 2010/03/24 C:\cygwin\bin\cygcrypto-0.9.8.dll - os=4.0 img=1.0 sys=4.0
"cygcrypto-0.9.8.dll" v0.0 ts=2010/3/24 17:16
943k 2007/12/17 C:\cygwin\bin\cygdb-4.5.dll - os=4.0 img=1.0 sys=4.0
"cygdb-4.5.dll" v0.0 ts=2007/12/17 15:12
1296k 2007/12/17 C:\cygwin\bin\cygdb_cxx-4.5.dll - os=4.0 img=1.0 sys=4.0
"cygdb_cxx-4.5.dll" v0.0 ts=2007/12/17 15:12
118k 2008/05/09 C:\cygwin\bin\cygexpat-1.dll - os=4.0 img=1.0 sys=4.0
"cygexpat-1.dll" v0.0 ts=2008/5/9 7:03
176k 2010/01/29 C:\cygwin\bin\cygfontconfig-1.dll - os=4.0 img=1.0 sys=4.0
"cygfontconfig-1.dll" v0.0 ts=2010/1/29 0:12
21k 2009/10/14 C:\cygwin\bin\cygfontenc-1.dll - os=4.0 img=1.0 sys=4.0
"cygfontenc-1.dll" v0.0 ts=2009/10/14 3:04
43k 2010/01/02 C:\cygwin\bin\cygform-10.dll - os=4.0 img=1.0 sys=4.0
"cygform-10.dll" v0.0 ts=2010/1/2 16:49
40k 2009/03/01 C:\cygwin\bin\cygform-8.dll - os=4.0 img=1.0 sys=4.0
"cygform-8.dll" v0.0 ts=2009/3/1 8:32
43k 2009/11/20 C:\cygwin\bin\cygform-9.dll - os=4.0 img=1.0 sys=4.0
"cygform-9.dll" v0.0 ts=2009/11/20 21:14
492k 2010/03/03 C:\cygwin\bin\cygfreetype-6.dll - os=4.0 img=1.0 sys=4.0
"cygfreetype-6.dll" v0.0 ts=2010/3/2 23:24
45k 2009/12/11 C:\cygwin\bin\cyggcc_s-1.dll - os=4.0 img=1.0 sys=4.0
"cyggcc_s-1.dll" v0.0 ts=2009/12/8 2:30
449k 2010/03/17 C:\cygwin\bin\cyggcrypt-11.dll - os=4.0 img=1.0 sys=4.0
"cyggcrypt-11.dll" v0.0 ts=2010/3/17 23:45
19k 2009/02/26 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm-4.dll" v0.0 ts=2009/2/26 9:58
8k 2009/02/26 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0
"cyggdbm_compat-4.dll" v0.0 ts=2009/2/26 9:58
2389k 2010/02/10 C:\cygwin\bin\cygGL-1.dll - os=4.0 img=1.0 sys=4.0
"cygGL-1.dll" v0.0 ts=2010/2/10 3:40
315k 2009/06/06 C:\cygwin\bin\cyggmp-3.dll - os=4.0 img=1.0 sys=4.0
"cyggmp-3.dll" v0.0 ts=2009/6/6 14:23
16k 2010/03/17 C:\cygwin\bin\cyggpg-error-0.dll - os=4.0 img=1.0 sys=4.0
"cyggpg-error-0.dll" v0.0 ts=2010/3/17 23:21
25k 2009/07/06 C:\cygwin\bin\cyghistory7.dll - os=4.0 img=1.0 sys=4.0
"cyghistory7.dll" v0.0 ts=2009/7/5 17:45
73k 2009/09/02 C:\cygwin\bin\cygICE-6.dll - os=4.0 img=1.0 sys=4.0
"cygICE-6.dll" v0.0 ts=2009/9/3 0:39
360k 2009/12/29 C:\cygwin\bin\cygicons-0.dll - os=4.0 img=1.4 sys=4.0
"cygicons-0.dll" v0.0 ts=2009/12/29 7:30
982k 2009/12/23 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
"cygiconv-2.dll" v0.0 ts=2009/12/23 15:25
31k 2005/11/20 C:\cygwin\bin\cygintl-3.dll - os=4.0 img=1.0 sys=4.0
"cygintl-3.dll" v0.0 ts=2005/11/20 4:04
31k 2009/04/03 C:\cygwin\bin\cygintl-8.dll - os=4.0 img=1.0 sys=4.0
"cygintl-8.dll" v0.0 ts=2009/4/3 4:15
5k 2010/04/12 C:\cygwin\bin\cyglsa.dll - os=4.0 img=1.0 sys=4.0
"cyglsa.dll" v0.0 ts=2010/4/12 20:08
9k 2010/04/12 C:\cygwin\bin\cyglsa64.dll - os=5.2 img=0.0 sys=5.2
125k 2010/04/09 C:\cygwin\bin\cyglzma-1.dll - os=4.0 img=1.0 sys=4.0
"cyglzma-1.dll" v0.0 ts=2010/4/9 18:54
25k 2010/01/02 C:\cygwin\bin\cygmenu-10.dll - os=4.0 img=1.0 sys=4.0
"cygmenu-10.dll" v0.0 ts=2010/1/2 16:48
21k 2009/03/01 C:\cygwin\bin\cygmenu-8.dll - os=4.0 img=1.0 sys=4.0
"cygmenu-8.dll" v0.0 ts=2009/3/1 8:31
25k 2009/11/20 C:\cygwin\bin\cygmenu-9.dll - os=4.0 img=1.0 sys=4.0
"cygmenu-9.dll" v0.0 ts=2009/11/20 21:13
211k 2009/06/06 C:\cygwin\bin\cygmp-3.dll - os=4.0 img=1.0 sys=4.0
"cygmp-3.dll" v0.0 ts=2009/6/6 14:23
63k 2010/01/02 C:\cygwin\bin\cygncurses++-10.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++-10.dll" v0.0 ts=2010/1/2 17:00
66k 2009/03/01 C:\cygwin\bin\cygncurses++-8.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++-8.dll" v0.0 ts=2009/3/1 8:39
63k 2009/11/20 C:\cygwin\bin\cygncurses++-9.dll - os=4.0 img=1.0 sys=4.0
"cygncurses++-9.dll" v0.0 ts=2009/11/20 21:25
195k 2010/01/02 C:\cygwin\bin\cygncurses-10.dll - os=4.0 img=1.0 sys=4.0
"cygncurses-10.dll" v0.0 ts=2010/1/2 16:45
237k 2009/03/01 C:\cygwin\bin\cygncurses-8.dll - os=4.0 img=1.0 sys=4.0
"cygncurses-8.dll" v0.0 ts=2009/3/1 8:28
198k 2009/11/20 C:\cygwin\bin\cygncurses-9.dll - os=4.0 img=1.0 sys=4.0
"cygncurses-9.dll" v0.0 ts=2009/11/20 21:10
13k 2010/01/02 C:\cygwin\bin\cygpanel-10.dll - os=4.0 img=1.0 sys=4.0
"cygpanel-10.dll" v0.0 ts=2010/1/2 16:47
11k 2009/03/01 C:\cygwin\bin\cygpanel-8.dll - os=4.0 img=1.0 sys=4.0
"cygpanel-8.dll" v0.0 ts=2009/3/1 8:30
13k 2009/11/20 C:\cygwin\bin\cygpanel-9.dll - os=4.0 img=1.0 sys=4.0
"cygpanel-9.dll" v0.0 ts=2009/11/20 21:12
217k 2009/11/10 C:\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcre-0.dll" v0.0 ts=2009/10/25 11:42
8k 2009/11/10 C:\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0
"cygpcreposix-0.dll" v0.0 ts=2009/10/25 11:42
1553k 2009/12/19 C:\cygwin\bin\cygperl5_10.dll - os=4.0 img=1.0 sys=4.0
"cygperl5_10.dll" v0.0 ts=2009/12/18 16:54
377k 2010/04/02 C:\cygwin\bin\cygpixman-1-0.dll - os=4.0 img=1.0 sys=4.0
"cygpixman-1-0.dll" v0.0 ts=2010/4/2 10:44
22k 2002/06/09 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
"cygpopt-0.dll" v0.0 ts=2002/6/9 8:45
162k 2009/07/06 C:\cygwin\bin\cygreadline7.dll - os=4.0 img=1.0 sys=4.0
"cygreadline7.dll" v0.0 ts=2009/7/5 17:45
27k 2009/09/03 C:\cygwin\bin\cygSM-6.dll - os=4.0 img=1.0 sys=4.0
"cygSM-6.dll" v0.0 ts=2009/9/3 11:56
264k 2010/03/24 C:\cygwin\bin\cygssl-0.9.8.dll - os=4.0 img=1.0 sys=4.0
"cygssl-0.9.8.dll" v0.0 ts=2010/3/24 17:17
10k 2009/12/11 C:\cygwin\bin\cygssp-0.dll - os=4.0 img=1.0 sys=4.0
"cygssp-0.dll" v0.0 ts=2009/12/8 2:38
773k 2009/12/11 C:\cygwin\bin\cygstdc++-6.dll - os=4.0 img=1.0 sys=4.0
"cygstdc++-6.dll" v0.0 ts=2009/12/8 3:07
48k 2010/01/02 C:\cygwin\bin\cygtic-10.dll - os=4.0 img=1.0 sys=4.0
"cygtic-10.dll" v0.0 ts=2010/1/2 16:45
48k 2009/11/20 C:\cygwin\bin\cygtic-9.dll - os=4.0 img=1.0 sys=4.0
"cygtic-9.dll" v0.0 ts=2009/11/20 21:10
1040k 2010/02/10 C:\cygwin\bin\cygX11-6.dll - os=4.0 img=1.0 sys=4.0
"cygX11-6.dll" v0.0 ts=2010/2/10 2:42
9k 2009/09/03 C:\cygwin\bin\cygXau-6.dll - os=4.0 img=1.0 sys=4.0
"cygXau-6.dll" v0.0 ts=2009/9/3 0:47
352k 2009/10/19 C:\cygwin\bin\cygXaw-7.dll - os=4.0 img=1.0 sys=4.0
"cygXaw-7.dll" v0.0 ts=2009/10/18 23:55
76k 2009/12/14 C:\cygwin\bin\cygxcb-1.dll - os=4.0 img=1.0 sys=4.0
"cygxcb-1.dll" v0.0 ts=2009/12/14 21:17
17k 2009/10/14 C:\cygwin\bin\cygXdmcp-6.dll - os=4.0 img=1.0 sys=4.0
"cygXdmcp-6.dll" v0.0 ts=2009/10/14 0:31
51k 2009/10/22 C:\cygwin\bin\cygXext-6.dll - os=4.0 img=1.0 sys=4.0
"cygXext-6.dll" v0.0 ts=2009/10/22 5:45
66k 2009/10/15 C:\cygwin\bin\cygXft-2.dll - os=4.0 img=1.0 sys=4.0
"cygXft-2.dll" v0.0 ts=2009/10/14 22:33
122k 2009/10/15 C:\cygwin\bin\cygxkbfile-1.dll - os=4.0 img=1.0 sys=4.0
"cygxkbfile-1.dll" v0.0 ts=2009/10/14 7:57
75k 2009/10/14 C:\cygwin\bin\cygXmu-6.dll - os=4.0 img=1.0 sys=4.0
"cygXmu-6.dll" v0.0 ts=2009/10/14 9:29
11k 2009/10/14 C:\cygwin\bin\cygXmuu-1.dll - os=4.0 img=1.0 sys=4.0
"cygXmuu-1.dll" v0.0 ts=2009/10/14 9:29
53k 2009/10/14 C:\cygwin\bin\cygXpm-4.dll - os=4.0 img=1.0 sys=4.0
"cygXpm-4.dll" v0.0 ts=2009/10/14 19:01
30k 2009/10/14 C:\cygwin\bin\cygXrender-1.dll - os=4.0 img=1.0 sys=4.0
"cygXrender-1.dll" v0.0 ts=2009/10/14 9:40
279k 2010/04/02 C:\cygwin\bin\cygXt-6.dll - os=4.0 img=1.0 sys=4.0
"cygXt-6.dll" v0.0 ts=2010/4/2 8:27
64k 2009/03/02 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
"cygz.dll" v0.0 ts=2009/3/2 3:33
2547k 2010/04/12 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2010/4/12 20:07
Cygwin DLL version info:
DLL version: 1.7.5
DLL epoch: 19
DLL old termios: 5
DLL malloc env: 28
Cygwin conv: 181
API major: 0
API minor: 225
Shared data: 5
DLL identifier: cygwin1
Mount registry: 3
Cygwin registry name: Cygwin
Program options name: Program Options
Installations name: Installations
Cygdrive default prefix:
Build date:
Shared id: cygwin1S5
Can't find the cygrunsrv utility, skipping services check.
Cygwin Package Information
Last downloaded files to: ”"
Last downloaded files from: ”"
Package Version
_update-info-dir 00884-1
alternatives 1.3.30c-10
base-cygwin 2.1-1
base-files 3.9-3
base-passwd 3.1-1
bash 3.2.49-23
bzip2 1.0.5-10
coreutils 8.4-2
crypt 1.1-1
cygutils 1.4.2-1
cygwin 1.7.5-1
cygwin-doc 1.7-1
dash 0.5.5.1-2
diffutils 2.9-1
e2fsprogs 1.35-3
editrights 1.01-2
findutils 4.5.5-1
font-adobe-dpi75 1.0.1-1
font-alias 1.0.2-1
font-encodings 1.0.3-1
font-misc-misc 1.1.0-1
fontconfig 2.8.0-1
gawk 3.1.7-1
gettext 0.17-11
grep 2.5.4-2
groff 1.19.2-2
gzip 1.3.12-2
ipc-utils 1.0-1
less 436-1
libbz2_1 1.0.5-10
libdb4.5 4.5.20.2-2
libexpat1 2.0.1-1
libfontconfig1 2.8.0-1
libfontenc1 1.0.5-1
libfreetype6 2.3.12-1
libgcc1 4.3.4-3
libgcrypt11 1.4.5-1
libgdbm4 1.8.3-20
libGL1 7.6.1-1
libgmp3 4.3.1-3
libgpg-error0 1.7-1
libICE6 1.0.6-1
libiconv2 1.13.1-1
libintl3 0.14.5-1
libintl8 0.17-11
liblzma1 4.999.9beta-11
libncurses10 5.7-18
libncurses8 5.5-10
libncurses9 5.7-16
libpcre0 8.00-1
libpixman1_0 0.18.0-1
libpopt0 1.6.4-4
libreadline7 6.0.3-2
libSM6 1.1.1-1
libssp0 4.3.4-3
libstdc++6 4.3.4-3
libX11_6 1.3.3-1
libXau6 1.0.5-1
libXaw7 1.0.7-1
libxcb1 1.5-1
libXdmcp6 1.0.3-1
libXext6 1.1.1-1
libXft2 2.1.14-1
libxkbfile1 1.0.6-1
libXmu6 1.0.5-1
libXmuu1 1.0.5-1
libXpm4 3.5.8-1
libXrender1 0.9.5-1
libXt6 1.0.8-1
login 1.10-10
luit 1.0.5-1
man 1.6e-1
mkfontdir 1.0.5-1
mkfontscale 1.0.7-1
openssl 0.9.8n-1
perl 5.10.1-3
rebase 3.0.1-1
run 1.1.12-11
sed 4.2.1-1
tar 1.22.90-1
terminfo 5.7_20091114-14
terminfo0 5.5_20061104-12
texinfo 4.13-3
tzcode 2009k-1
util-linux 2.14.1-1
which 2.20-2
xauth 1.0.4-1
xcursor-themes 1.0.2-1
xinit 1.2.1-1
xkbcomp 1.1.1-1
xkeyboard-config 1.8-1
xmodmap 1.0.4-1
xorg-server 1.7.6-2
xrdb 1.0.6-1
xterm 255-1
xz 4.999.9beta-11
zlib 1.2.3-10
zlib-devel 1.2.3-10
zlib0 1.2.3-10
Use -h to see help about each section
[-- Attachment #3: XWin.0.log --]
[-- Type: application/octet-stream, Size: 4554 bytes --]
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.7.6.0 (10706000)
Build Date: 2010-03-22
Contact: cygwin-xfree@cygwin.com
XWin was started with the following command line:
X :0 -multiwindow
ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1024 h 768
winInitializeDefaultScreens - Returning
2010-04-19 00:46:57 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
2010-04-19 00:46:57 (II) xorg.conf is not supported
2010-04-19 00:46:57 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
2010-04-19 00:46:57 LoadPreferences: /home/i-yuvale/.XWinrc not found
2010-04-19 00:46:57 LoadPreferences: Loading /etc/X11/system.XWinrc
2010-04-19 00:46:57 LoadPreferences: Done parsing the configuration file...
2010-04-19 00:46:57 winGetDisplay: DISPLAY=:0.0
2010-04-19 00:46:57 winDetectSupportedEngines - Windows NT/2000/XP
2010-04-19 00:46:57 winDetectSupportedEngines - DirectDraw installed
2010-04-19 00:46:57 winDetectSupportedEngines - DirectDraw4 installed
2010-04-19 00:46:57 winDetectSupportedEngines - Returning, supported engines 00000007
2010-04-19 00:46:57 winSetEngine - Multi Window or Rootless => ShadowGDI
2010-04-19 00:46:57 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
2010-04-19 00:46:57 winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 768 depth: 32
2010-04-19 00:46:57 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
2010-04-19 00:46:57 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32
2010-04-19 00:46:57 null screen fn ReparentWindow
2010-04-19 00:46:57 null screen fn RestackWindow
2010-04-19 00:46:57 InitQueue - Calling pthread_mutex_init
2010-04-19 00:46:57 InitQueue - pthread_mutex_init returned
2010-04-19 00:46:57 InitQueue - Calling pthread_cond_init
2010-04-19 00:46:57 InitQueue - pthread_cond_init returned
2010-04-19 00:46:57 winInitMultiWindowWM - Hello
2010-04-19 00:46:57 winInitMultiWindowWM - Calling pthread_mutex_lock ()
2010-04-19 00:46:57 Screen 0 added at XINERAMA coordinate (0,0).
2010-04-19 00:46:57 winMultiWindowXMsgProc - Hello
2010-04-19 00:46:57 winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
2010-04-19 00:46:57 MIT-SHM extension disabled due to lack of kernel support
2010-04-19 00:46:57 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
2010-04-19 00:46:57 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
2010-04-19 00:46:57 (II) GLX: Initialized DRISWRAST GL provider for screen 0
2010-04-19 00:46:57 [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list!
2010-04-19 00:46:57 [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list!
2010-04-19 00:46:57 [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list!
2010-04-19 00:46:58 winPointerWarpCursor - Discarding first warp: 512 384
2010-04-19 00:46:58 (--) 3 mouse buttons found
2010-04-19 00:46:58 (--) Setting autorepeat to delay=500, rate=31
2010-04-19 00:46:58 (--) winConfigKeyboard - Layout: "00000409" (00000409)
2010-04-19 00:46:58 (--) Using preset keyboard for "English (USA)" (409), type "7"
2010-04-19 00:46:58 Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none"
2010-04-19 00:46:58 winInitMultiWindowWM - pthread_mutex_lock () returned.
2010-04-19 00:46:58 winInitMultiWindowWM - pthread_mutex_unlock () returned.
2010-04-19 00:46:58 winMultiWindowXMsgProc - pthread_mutex_lock () returned.
2010-04-19 00:46:58 winGetDisplay: DISPLAY=:0.0
2010-04-19 00:46:58 winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
2010-04-19 00:46:58 winInitMultiWindowWM - DISPLAY=:0.0
2010-04-19 00:46:58 winGetDisplay: DISPLAY=:0.0
2010-04-19 00:46:58 winMultiWindowXMsgProc - DISPLAY=:0.0
2010-04-19 00:46:58 winProcEstablishConnection - Hello
2010-04-19 00:46:58 winInitClipboard ()
2010-04-19 00:46:58 winClipboardProc - Hello
2010-04-19 00:46:58 DetectUnicodeSupport - Windows NT/2000/XP
2010-04-19 00:46:58 winProcEstablishConnection - winInitClipboard returned.
2010-04-19 00:46:58 winGetDisplay: DISPLAY=:0.0
2010-04-19 00:46:58 winClipboardProc - DISPLAY=:0.0
2010-04-19 00:46:58 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display.
2010-04-19 00:46:58 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display.
2010-04-19 00:46:58 winClipboardProc - XOpenDisplay () returned and successfully opened the display.
[-- Attachment #4: Type: text/plain, Size: 218 bytes --]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
2010-04-18 22:09 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions Yuval Emek
@ 2010-04-19 1:01 ` Dave Korn
2010-04-19 6:32 ` Christopher Faylor
0 siblings, 1 reply; 10+ messages in thread
From: Dave Korn @ 2010-04-19 1:01 UTC (permalink / raw)
To: cygwin
On 18/04/2010 23:09, Yuval Emek wrote:
> The context of the file xterm.exe.stackdump is:
> Exception: STATUS_ACCESS_VIOLATION at eip=610202F7
> eax=00CE00F8 ebx=61229E44 ecx=7530783F edx=002D20F0 esi=00000000 edi=0022FA14
> ebp=61020A10 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 4640, thread main
> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
> Stack trace:
> Frame Function Args
> End of stack trace
$ addr2line --exe cygwin-1.7.5-1/winsup/cygwin/cygwin1.dbg
610202F7
/ext/build/netrel/src/cygwin-1.7.5-1/winsup/cygwin/dll_init.cc:78
71 /* Initialize an individual DLL */
72 int
73 dll::init ()
74 {
75 int ret = 1;
76
77 /* Why didn't we just import this variable? */
78 *(p.envptr) = __cygwin_environ;
79
Ah. Hmm. That certainly does look like it's nothing to do with the DEP or
anything else; either we're missing a null pointer check here, or there's some
reason why that pointer's never supposed to be null at this point in the code
but somehow it is.
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
2010-04-19 1:01 ` Dave Korn
@ 2010-04-19 6:32 ` Christopher Faylor
2010-04-19 11:44 ` Yuval Emek
0 siblings, 1 reply; 10+ messages in thread
From: Christopher Faylor @ 2010-04-19 6:32 UTC (permalink / raw)
To: cygwin
On Mon, Apr 19, 2010 at 02:20:48AM +0100, Dave Korn wrote:
>On 18/04/2010 23:09, Yuval Emek wrote:
>
>> The context of the file xterm.exe.stackdump is:
>> Exception: STATUS_ACCESS_VIOLATION at eip=610202F7
>> eax=00CE00F8 ebx=61229E44 ecx=7530783F edx=002D20F0 esi=00000000 edi=0022FA14
>> ebp=61020A10 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 4640, thread main
>> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
>> Stack trace:
>> Frame Function Args
>> End of stack trace
>
>$ addr2line --exe cygwin-1.7.5-1/winsup/cygwin/cygwin1.dbg
>610202F7
>/ext/build/netrel/src/cygwin-1.7.5-1/winsup/cygwin/dll_init.cc:78
>
> 71 /* Initialize an individual DLL */
> 72 int
> 73 dll::init ()
> 74 {
> 75 int ret = 1;
> 76
> 77 /* Why didn't we just import this variable? */
> 78 *(p.envptr) = __cygwin_environ;
> 79
>
> Ah. Hmm. That certainly does look like it's nothing to do with the DEP or
>anything else; either we're missing a null pointer check here, or there's some
>reason why that pointer's never supposed to be null at this point in the code
>but somehow it is.
p.envptr is supposed to be filled in by the call to _cygwin_crt0_common
in cygwin_attach_dll. It is supposed to be set to the address of the
"environ" variable in the DLL. It is not supposed to be NULL. That
assignment should actually not even be necessary but the fact that
envptr may be NULL is a problem. Of course, it could just be some
non-NULL garbage too. Running in gdb and getting a stack trace would be
instructive.
The handling of the environ pointer has always made my head hurt. In
retrospect, I wish I'd simplified it for 1.7.x.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
2010-04-19 6:32 ` Christopher Faylor
@ 2010-04-19 11:44 ` Yuval Emek
2010-04-19 14:48 ` Larry Hall (Cygwin)
0 siblings, 1 reply; 10+ messages in thread
From: Yuval Emek @ 2010-04-19 11:44 UTC (permalink / raw)
To: cygwin
On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
<cgf-use-the-mailinglist-please@cygwin.com> wrote:
> On Mon, Apr 19, 2010 at 02:20:48AM +0100, Dave Korn wrote:
>>On 18/04/2010 23:09, Yuval Emek wrote:
>>
>>> The context of the file xterm.exe.stackdump is:
>>> Exception: STATUS_ACCESS_VIOLATION at eip=610202F7
>>> eax=00CE00F8 ebx=61229E44 ecx=7530783F edx=002D20F0 esi=00000000 edi=0022FA14
>>> ebp=61020A10 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 4640, thread main
>>> cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
>>> Stack trace:
>>> Frame Function Args
>>> End of stack trace
>>
>>$ addr2line --exe cygwin-1.7.5-1/winsup/cygwin/cygwin1.dbg
>>610202F7
>>/ext/build/netrel/src/cygwin-1.7.5-1/winsup/cygwin/dll_init.cc:78
>>
>> 71 /* Initialize an individual DLL */
>> 72 int
>> 73 dll::init ()
>> 74 {
>> 75 int ret = 1;
>> 76
>> 77 /* Why didn't we just import this variable? */
>> 78 *(p.envptr) = __cygwin_environ;
>> 79
>>
>> Ah. Hmm. That certainly does look like it's nothing to do with the DEP or
>>anything else; either we're missing a null pointer check here, or there's some
>>reason why that pointer's never supposed to be null at this point in the code
>>but somehow it is.
>
> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common
> in cygwin_attach_dll. It is supposed to be set to the address of the
> "environ" variable in the DLL. It is not supposed to be NULL. That
> assignment should actually not even be necessary but the fact that
> envptr may be NULL is a problem. Of course, it could just be some
> non-NULL garbage too. Running in gdb and getting a stack trace would be
> instructive.
Can you be more specific? (I have been using cygwin for a while, but I
never debugged it beforehand.)
I can install gdb using setup.exe . What should I do then in order to
obtain a stack trace?
Thanks,
Yuval
>
> The handling of the environ pointer has always made my head hurt. In
> retrospect, I wish I'd simplified it for 1.7.x.
>
> cgf
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
2010-04-19 11:44 ` Yuval Emek
@ 2010-04-19 14:48 ` Larry Hall (Cygwin)
2010-04-19 17:48 ` Christopher Faylor
0 siblings, 1 reply; 10+ messages in thread
From: Larry Hall (Cygwin) @ 2010-04-19 14:48 UTC (permalink / raw)
To: cygwin
On 4/19/2010 7:44 AM, Yuval Emek wrote:
> On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
> <cgf-use-the-mailinglist-please...> wrote:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Feeding spammers just makes
them hungry.
<snip>
>> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common
>> in cygwin_attach_dll. It is supposed to be set to the address of the
>> "environ" variable in the DLL. It is not supposed to be NULL. That
>> assignment should actually not even be necessary but the fact that
>> envptr may be NULL is a problem. Of course, it could just be some
>> non-NULL garbage too. Running in gdb and getting a stack trace would be
>> instructive.
>
> Can you be more specific? (I have been using cygwin for a while, but I
> never debugged it beforehand.)
> I can install gdb using setup.exe . What should I do then in order to
> obtain a stack trace?
Grab a snapshot from <http://cygwin.com/snapshots/>. You want the DLL
and debugging info at least.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
2010-04-19 14:48 ` Larry Hall (Cygwin)
@ 2010-04-19 17:48 ` Christopher Faylor
2010-04-20 6:19 ` Yuval Emek
0 siblings, 1 reply; 10+ messages in thread
From: Christopher Faylor @ 2010-04-19 17:48 UTC (permalink / raw)
To: cygwin
On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
>On 4/19/2010 7:44 AM, Yuval Emek wrote:
>> On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
>> <cgf-use-the-mailinglist-please...> wrote:
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
><http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Feeding spammers just makes
>them hungry.
>
><snip>
>
>>> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common
>>> in cygwin_attach_dll. It is supposed to be set to the address of the
>>> "environ" variable in the DLL. It is not supposed to be NULL. That
>>> assignment should actually not even be necessary but the fact that
>>> envptr may be NULL is a problem. Of course, it could just be some
>>> non-NULL garbage too. Running in gdb and getting a stack trace would be
>>> instructive.
>>
>> Can you be more specific? (I have been using cygwin for a while, but I
>> never debugged it beforehand.)
>> I can install gdb using setup.exe . What should I do then in order to
>> obtain a stack trace?
>
>Grab a snapshot from <http://cygwin.com/snapshots/>. You want the DLL
>and debugging info at least.
And, assuming that you can actually run gdb, just "gdb bash" and then "r".
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
2010-04-19 17:48 ` Christopher Faylor
@ 2010-04-20 6:19 ` Yuval Emek
2010-04-20 13:41 ` Yuval Emek
2010-04-20 14:26 ` Christopher Faylor
0 siblings, 2 replies; 10+ messages in thread
From: Yuval Emek @ 2010-04-20 6:19 UTC (permalink / raw)
To: cygwin
On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
> On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
>>On 4/19/2010 7:44 AM, Yuval Emek wrote:
>>> On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
>>> <cgf-use-the-mailinglist-please...> wrote:
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>><http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Feeding spammers just makes
>>them hungry.
>>
>><snip>
>>
>>>> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common
>>>> in cygwin_attach_dll. It is supposed to be set to the address of the
>>>> "environ" variable in the DLL. It is not supposed to be NULL. That
>>>> assignment should actually not even be necessary but the fact that
>>>> envptr may be NULL is a problem. Of course, it could just be some
>>>> non-NULL garbage too. Running in gdb and getting a stack trace would be
>>>> instructive.
>>>
>>> Can you be more specific? (I have been using cygwin for a while, but I
>>> never debugged it beforehand.)
>>> I can install gdb using setup.exe . What should I do then in order to
>>> obtain a stack trace?
>>
>>Grab a snapshot from <http://cygwin.com/snapshots/>. You want the DLL
>>and debugging info at least.
>
> And, assuming that you can actually run gdb, just "gdb bash" and then "r".
I installed gdb and then downloaded the (latest) snapshots of
cygwin1.dll and cygwin1.dbg and extracted then to /bin/ (replacing the
previous cygwin1.dll) .
Running gdb bash seems to fail since there are no debugging symbols.
In particular, when typing r in the gdb prompt, I get the following
output:
Starting program: /usr/bin/bash
[New thread 3800.0x15b4]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New thread 3800.0x13f4]
[1]+ Stopped gdb bash
(Makes sense, I guess, as bash was not compiled with debugging info.)
Can I download debugging info for bash from somewhere? (As far as I
understand, I don't even have the source code for bash.)
Is there something else I can do?
>
> cgf
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
2010-04-20 6:19 ` Yuval Emek
@ 2010-04-20 13:41 ` Yuval Emek
2010-04-20 14:26 ` Christopher Faylor
1 sibling, 0 replies; 10+ messages in thread
From: Yuval Emek @ 2010-04-20 13:41 UTC (permalink / raw)
To: cygwin
Is it possible that this problem is somehow related to another problem
I'm experiencing, reported in
http://cygwin.com/ml/cygwin/2010-04/msg00797.html ?
On Tue, Apr 20, 2010 at 09:19, Yuval Emek wrote:
> On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
>> On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
>>>On 4/19/2010 7:44 AM, Yuval Emek wrote:
>>>> On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
>>>> <cgf-use-the-mailinglist-please...> wrote:
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>><http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Feeding spammers just makes
>>>them hungry.
>>>
>>><snip>
>>>
>>>>> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common
>>>>> in cygwin_attach_dll. It is supposed to be set to the address of the
>>>>> "environ" variable in the DLL. It is not supposed to be NULL. That
>>>>> assignment should actually not even be necessary but the fact that
>>>>> envptr may be NULL is a problem. Of course, it could just be some
>>>>> non-NULL garbage too. Running in gdb and getting a stack trace would be
>>>>> instructive.
>>>>
>>>> Can you be more specific? (I have been using cygwin for a while, but I
>>>> never debugged it beforehand.)
>>>> I can install gdb using setup.exe . What should I do then in order to
>>>> obtain a stack trace?
>>>
>>>Grab a snapshot from <http://cygwin.com/snapshots/>. You want the DLL
>>>and debugging info at least.
>>
>> And, assuming that you can actually run gdb, just "gdb bash" and then "r".
>
> I installed gdb and then downloaded the (latest) snapshots of
> cygwin1.dll and cygwin1.dbg and extracted then to /bin/ (replacing the
> previous cygwin1.dll) .
> Running gdb bash seems to fail since there are no debugging symbols.
> In particular, when typing r in the gdb prompt, I get the following
> output:
>
> Starting program: /usr/bin/bash
> [New thread 3800.0x15b4]
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [New thread 3800.0x13f4]
>
> [1]+ Stopped gdb bash
>
> (Makes sense, I guess, as bash was not compiled with debugging info.)
> Can I download debugging info for bash from somewhere? (As far as I
> understand, I don't even have the source code for bash.)
> Is there something else I can do?
>
>>
>> cgf
>>
>> --
>> Problem reports: http://cygwin.com/problems.html
>> FAQ: http://cygwin.com/faq/
>> Documentation: http://cygwin.com/docs.html
>> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>>
>>
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
2010-04-20 6:19 ` Yuval Emek
2010-04-20 13:41 ` Yuval Emek
@ 2010-04-20 14:26 ` Christopher Faylor
2010-04-25 15:06 ` Yuval Emek
1 sibling, 1 reply; 10+ messages in thread
From: Christopher Faylor @ 2010-04-20 14:26 UTC (permalink / raw)
To: cygwin
On Tue, Apr 20, 2010 at 09:19:28AM +0300, Yuval Emek wrote:
>On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
>> On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
>>>On 4/19/2010 7:44 AM, Yuval Emek wrote:
>>>> On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
>>>> <cgf-use-the-mailinglist-please...> ?wrote:
>>> ? ?^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>><http://cygwin.com/acronyms/#PCYMTNQREAIYR>. ?Feeding spammers just makes
>>>them hungry.
>>>
>>><snip>
>>>
>>>>> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common
>>>>> in cygwin_attach_dll. ?It is supposed to be set to the address of the
>>>>> "environ" variable in the DLL. ?It is not supposed to be NULL. ?That
>>>>> assignment should actually not even be necessary but the fact that
>>>>> envptr may be NULL is a problem. ?Of course, it could just be some
>>>>> non-NULL garbage too. ?Running in gdb and getting a stack trace would be
>>>>> instructive.
>>>>
>>>> Can you be more specific? (I have been using cygwin for a while, but I
>>>> never debugged it beforehand.)
>>>> I can install gdb using setup.exe . What should I do then in order to
>>>> obtain a stack trace?
>>>
>>>Grab a snapshot from <http://cygwin.com/snapshots/>. ?You want the DLL
>>>and debugging info at least.
>>
>> And, assuming that you can actually run gdb, just "gdb bash" and then "r".
>
>I installed gdb and then downloaded the (latest) snapshots of
>cygwin1.dll and cygwin1.dbg and extracted then to /bin/ (replacing the
>previous cygwin1.dll) .
>Running gdb bash seems to fail since there are no debugging symbols.
>In particular, when typing r in the gdb prompt, I get the following
>output:
>
>Starting program: /usr/bin/bash
>[New thread 3800.0x15b4]
>(no debugging symbols found)
>(no debugging symbols found)
>(no debugging symbols found)
>[New thread 3800.0x13f4]
>
>[1]+ Stopped gdb bash
>
>(Makes sense, I guess, as bash was not compiled with debugging info.)
>Can I download debugging info for bash from somewhere? (As far as I
>understand, I don't even have the source code for bash.)
>Is there something else I can do?
I'm not interested in bash symbols.
In the above it sounds like you may actually be running gdb from bash.
I suggested bash because I thought most cygwin programs were dying but,
on rereading the original report, you only mentioned xterm, emacs, and
subversion. So, the thing to try would be to run gdb on one of those
from a c:\> prompt. And, it really would be as simple as just typing:
gdb svn
r
bt
and reporting the backtrace.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions
2010-04-20 14:26 ` Christopher Faylor
@ 2010-04-25 15:06 ` Yuval Emek
0 siblings, 0 replies; 10+ messages in thread
From: Yuval Emek @ 2010-04-25 15:06 UTC (permalink / raw)
To: cygwin
On Tue, Apr 20, 2010 at 17:26, Christopher Faylor wrote:
>
> On Tue, Apr 20, 2010 at 09:19:28AM +0300, Yuval Emek wrote:
> >On Mon, Apr 19, 2010 at 20:48, Christopher Faylor wrote:
> >> On Mon, Apr 19, 2010 at 10:48:18AM -0400, Larry Hall (Cygwin) wrote:
> >>>On 4/19/2010 7:44 AM, Yuval Emek wrote:
> >>>> On Mon, Apr 19, 2010 at 09:32, Christopher Faylor
> >>>> <cgf-use-the-mailinglist-please...> ?wrote:
> >>> ? ?^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >>><http://cygwin.com/acronyms/#PCYMTNQREAIYR>. ?Feeding spammers just makes
> >>>them hungry.
> >>>
> >>><snip>
> >>>
> >>>>> p.envptr is supposed to be filled in by the call to _cygwin_crt0_common
> >>>>> in cygwin_attach_dll. ?It is supposed to be set to the address of the
> >>>>> "environ" variable in the DLL. ?It is not supposed to be NULL. ?That
> >>>>> assignment should actually not even be necessary but the fact that
> >>>>> envptr may be NULL is a problem. ?Of course, it could just be some
> >>>>> non-NULL garbage too. ?Running in gdb and getting a stack trace would be
> >>>>> instructive.
> >>>>
> >>>> Can you be more specific? (I have been using cygwin for a while, but I
> >>>> never debugged it beforehand.)
> >>>> I can install gdb using setup.exe . What should I do then in order to
> >>>> obtain a stack trace?
> >>>
> >>>Grab a snapshot from <http://cygwin.com/snapshots/>. ?You want the DLL
> >>>and debugging info at least.
> >>
> >> And, assuming that you can actually run gdb, just "gdb bash" and then "r".
> >
> >I installed gdb and then downloaded the (latest) snapshots of
> >cygwin1.dll and cygwin1.dbg and extracted then to /bin/ (replacing the
> >previous cygwin1.dll) .
> >Running gdb bash seems to fail since there are no debugging symbols.
> >In particular, when typing r in the gdb prompt, I get the following
> >output:
> >
> >Starting program: /usr/bin/bash
> >[New thread 3800.0x15b4]
> >(no debugging symbols found)
> >(no debugging symbols found)
> >(no debugging symbols found)
> >[New thread 3800.0x13f4]
> >
> >[1]+ Stopped gdb bash
> >
> >(Makes sense, I guess, as bash was not compiled with debugging info.)
> >Can I download debugging info for bash from somewhere? (As far as I
> >understand, I don't even have the source code for bash.)
> >Is there something else I can do?
>
> I'm not interested in bash symbols.
>
> In the above it sounds like you may actually be running gdb from bash.
>
> I suggested bash because I thought most cygwin programs were dying but,
> on rereading the original report, you only mentioned xterm, emacs, and
> subversion. So, the thing to try would be to run gdb on one of those
> from a c:\> prompt. And, it really would be as simple as just typing:
>
> gdb svn
> r
> bt
>
> and reporting the backtrace.
>
> cgf
>
I cannot produce a backtrace:
I run gdb on emacs (from a dos command prompt). Then I set the
arguments of emacs to --batch -l bar.el (which causes the
aforementioned exception many times) and type run.
In 2 out of three runs, I get a message that looks like:
***message begins***
Starting program: /cygdrive/c/cygwin/bin/emacs --batch -l bar.el
[New thread 4980.0x14dc]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New thread 4980.0x1600]
warning: ERROR !!! HeapSetInformation failed to set g_Heap to LFH
warning: ERROR !!! HeapSetInformation failed to set g_SpyHeap to LFH
[New thread 4980.0x798]
[New thread 4980.0xdc0]
warning: Lowest section in /cygdrive/c/Windows/system32/security.dll is .text at
00401000
[New thread 4980.0x1410]
[New thread 4980.0x1700]
(No files need saving)
[New thread 4980.0xe24]
5 [main] emacs-X11 4040 exception::handle: Exception: STATUS_ACCESS_VIOLAT
ION
723 [main] emacs-X11 4040 open_stackdumpfile: Dumping stack trace to emacs-X
11.exe.stackdump
8 [main] emacs-X11 2056 exception::handle: Exception: STATUS_ACCESS_VIOLAT
ION
743 [main] emacs-X11 2056 open_stackdumpfile: Dumping stack trace to emacs-X
11.exe.stackdump
6 [main] emacs-X11 2948 exception::handle: Exception: STATUS_ACCESS_VIOLAT
ION
719 [main] emacs-X11 2948 open_stackdumpfile: Dumping stack trace to emacs-X
11.exe.stackdump
6 [main] emacs-X11 1100 exception::handle: Exception: STATUS_ACCESS_VIOLAT
ION
739 [main] emacs-X11 1100 open_stackdumpfile: Dumping stack trace to emacs-X
11.exe.stackdump
[New thread 4980.0x12b8]
Program exited normally.
***message ends***
Afterward, when typing bt, I receive a "No stack" message.
A piece of info that may help:
The message
6 [main] emacs-X11 4832 exception::handle: Exception: STATUS_ACCESS_VIOLAT
ION
1113 [main] emacs-X11 4832 open_stackdumpfile: Dumping stack trace to emacs-X
11.exe.stackdump
that accompanies about 50% of the emacs, xterm, svn invocations is
sometimes followed by the following message:
6 [main] emacs 6076 fork: child -1 - died waiting for longjmp before initi
alization, retry 0, exit code 0x600, errno 11
I don't know why but I cannot produce this latter message from within dbg.
Any suggestions?
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2010-04-25 15:06 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-04-18 22:09 1.7.5: cygwin programs throw STATUS_ACCESS_VIOLATION exceptions Yuval Emek
2010-04-19 1:01 ` Dave Korn
2010-04-19 6:32 ` Christopher Faylor
2010-04-19 11:44 ` Yuval Emek
2010-04-19 14:48 ` Larry Hall (Cygwin)
2010-04-19 17:48 ` Christopher Faylor
2010-04-20 6:19 ` Yuval Emek
2010-04-20 13:41 ` Yuval Emek
2010-04-20 14:26 ` Christopher Faylor
2010-04-25 15:06 ` Yuval Emek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).