public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Yuval Emek <yuval.emek@gmail.com> To: cygwin-xfree@cygwin.com Subject: frequently getting a STATUS_ACCESS_VIOLATION exception under win7 Date: Mon, 03 May 2010 15:51:00 -0000 [thread overview] Message-ID: <r2r9d1cfe481005030851qb5559440w7318240333478229@mail.gmail.com> (raw) [-- Attachment #1: Type: text/plain, Size: 3298 bytes --] A very annoying situation: I'm getting a STATUS_ACCESS_VIOLATION exception in about 2 out of 3 operations performed under cygwin/x. An operation in this context can be starting an x application (e.g., xterm) or running some command from within emacs (e.g., diff or latex). In attempt to isolate the problem, I reinstalled cygwin from scratch using the default settings of setup.exe + xorg-server, xinit, xorg-docs, and X-start-menu-icons. Next, I open a cygwin bash window and then invoke startxwin.exe . The x-server is invoked but an xterm window does not open and the following message appears: ***message begins*** 4 [main] xterm 7156 exception::handle: Exception: STATUS_ACCESS_VIOLATION 1449 [main] xterm 7156 open_stackdumpfile: Dumping stack trace to xterm.exe.s tackdump 4 [main] xterm 7996 exception::handle: Exception: STATUS_ACCESS_VIOLATION 1356 [main] xterm 7996 open_stackdumpfile: Dumping stack trace to xterm.exe.s tackdump 4 [main] xterm 5268 exception::handle: Exception: STATUS_ACCESS_VIOLATION 647 [main] xterm 5268 open_stackdumpfile: Dumping stack trace to xterm.exe.s tackdump 5 [main] xterm 4316 exception::handle: Exception: STATUS_ACCESS_VIOLATION 739 [main] xterm 4316 open_stackdumpfile: Dumping stack trace to xterm.exe.s tackdump 2 [main] xterm 2752 exception::handle: Exception: STATUS_ACCESS_VIOLATION 1123 [main] xterm 2752 open_stackdumpfile: Dumping stack trace to xterm.exe.s tackdump 5 [main] xterm 3220 exception::handle: Exception: STATUS_ACCESS_VIOLATION 1260 [main] xterm 3220 open_stackdumpfile: Dumping stack trace to xterm.exe.s tackdump 6 [main] xterm 6752 fork: child -1 - died waiting for longjmp before initi alization, retry 0, exit code 0x600, errno 11 xterm: Error 29, errno 11: Resource temporarily unavailable Reason: spawn: fork() failed ***message ends*** The content of the resulting xterm.exe.stackdump file: ***content begins*** Exception: STATUS_ACCESS_VIOLATION at eip=610202F7 eax=00C500F8 ebx=612294A4 ecx=755F783F edx=002620F0 esi=00000000 edi=0022FA14 ebp=61020A10 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 3220, thread main cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 Stack trace: Frame Function Args End of stack trace ***content ends*** This phenomenon (or a similar one where I'm getting only 1 or two lines of the exception and xterm does open) is very common: it happens in about 2 out of 3 startxwin.exe invocation attempts. The same thing happens when I'm trying to open a new xterm window from an existing one. I'm using Windows 7 (32 bits). This is probably a relevant info as my old laptop (with Windows XP) works fine (once again with a fresh installation of cygwin + cygwin/x). I'm somewhat surprised that this problem was not reported before since I know that my office mate suffers from it as well (she is also using Windows 7 32 bits). I've already tried to discuss this problem in the cygwin mailing list (see http://cygwin.com/ml/cygwin/2010-04/msg00740.html) without a positive resolution. Thinking about it some more, I now understand that this problem occurs only under x, so I hope that this is the right mailing list. Any suggestions? The output of cygcheck -s -v -r and the content of /var/log/XWin.0.log are attached. [-- Attachment #2: XWin.0.log --] [-- Type: application/octet-stream, Size: 4224 bytes --] Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.8.0.0 (10800000) Build Date: 2010-04-02 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - primary monitor w 1680 h 1050 winInitializeDefaultScreens - native DPI x 96 y 96 winInitializeDefaultScreens - Returning [695307.766] winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 [695307.766] (II) xorg.conf is not supported [695307.766] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [695307.766] LoadPreferences: /home/i-yuvale/.XWinrc not found [695307.766] LoadPreferences: Loading /etc/X11/system.XWinrc [695307.766] LoadPreferences: Done parsing the configuration file... [695307.766] winGetDisplay: DISPLAY=:0.0 [695307.766] winDetectSupportedEngines - Windows NT/2000/XP [695307.797] winDetectSupportedEngines - DirectDraw installed [695307.797] winDetectSupportedEngines - DirectDraw4 installed [695307.797] winDetectSupportedEngines - Returning, supported engines 00000007 [695307.797] winSetEngine - Multi Window or Rootless => ShadowGDI [695307.797] winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel [695307.813] winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 [695307.813] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [695307.813] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [695307.813] null screen fn ReparentWindow [695307.813] null screen fn RestackWindow [695307.813] InitQueue - Calling pthread_mutex_init [695307.813] InitQueue - pthread_mutex_init returned [695307.813] InitQueue - Calling pthread_cond_init [695307.813] InitQueue - pthread_cond_init returned [695307.813] winInitMultiWindowWM - Hello [695307.813] winInitMultiWindowWM - Calling pthread_mutex_lock () [695307.813] Screen 0 added at virtual desktop coordinate (0,0). [695307.813] winMultiWindowXMsgProc - Hello [695307.813] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [695307.813] MIT-SHM extension disabled due to lack of kernel support [695307.828] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [695307.844] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [695307.844] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [695307.844] [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [695307.844] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [695307.859] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! [695308.187] winPointerWarpCursor - Discarding first warp: 840 525 [695308.187] (--) 7 mouse buttons found [695308.187] (--) Setting autorepeat to delay=500, rate=31 [695308.187] (--) winConfigKeyboard - Layout: "00000409" (00000409) [695308.187] (--) Using preset keyboard for "English (USA)" (409), type "4" [695308.187] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" [695308.187] winInitMultiWindowWM - pthread_mutex_lock () returned. [695308.203] winInitMultiWindowWM - pthread_mutex_unlock () returned. [695308.203] winGetDisplay: DISPLAY=:0.0 [695308.203] winInitMultiWindowWM - DISPLAY=:0.0 [695308.203] winMultiWindowXMsgProc - pthread_mutex_lock () returned. [695308.203] winMultiWindowXMsgProc - pthread_mutex_unlock () returned. [695308.203] winProcEstablishConnection - Hello [695308.203] winInitClipboard () [695308.203] winClipboardProc - Hello [695308.203] DetectUnicodeSupport - Windows NT/2000/XP [695308.203] winProcEstablishConnection - winInitClipboard returned. [695308.203] winGetDisplay: DISPLAY=:0.0 [695308.203] winMultiWindowXMsgProc - DISPLAY=:0.0 [695308.203] winGetDisplay: DISPLAY=:0.0 [695308.203] winClipboardProc - DISPLAY=:0.0 [695308.203] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. [695308.218] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [695308.218] winClipboardProc - XOpenDisplay () returned and successfully opened the display. [-- Attachment #3: xterm.exe.stackdump --] [-- Type: application/octet-stream, Size: 321 bytes --] Exception: STATUS_ACCESS_VIOLATION at eip=610202F7 eax=00C500F8 ebx=612294A4 ecx=755F783F edx=002620F0 esi=00000000 edi=0022FA14 ebp=61020A10 esp=0022C7E4 program=C:\cygwin\bin\xterm.exe, pid 3220, thread main cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 Stack trace: Frame Function Args End of stack trace [-- Attachment #4: Type: text/plain, Size: 223 bytes --] -- 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/
next reply other threads:[~2010-05-03 15:51 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-03 15:51 Yuval Emek [this message] 2010-05-03 16:37 ` Christopher Faylor 2010-05-03 18:37 ` Yuval Emek 2010-05-03 18:46 ` Christopher Faylor 2010-05-24 16:30 ` Mike 2010-05-03 18:56 ` Denis Beauchemin 2010-05-03 18:59 ` Christopher Faylor 2010-05-03 19:17 ` Yuval Emek 2010-05-03 19:42 ` Reini Urban 2010-05-03 19:25 ` Christopher Faylor 2010-05-03 20:32 ` Denis Beauchemin 2010-05-22 1:10 ` yuval birnboin 2010-06-09 5:10 ` Michael 2010-06-09 5:31 ` Yaakov (Cygwin/X) 2010-06-10 2:08 ` Michael 2010-07-07 22:35 ` Simon 2010-06-11 19:30 ` Jeff 2010-09-07 3:30 ` Michael 2011-05-15 8:36 ` Whatzit Toya 2011-09-12 14:25 ` Daniel Brockman 2011-09-12 22:10 ` Larry Hall (Cygwin-X) [not found] ` <4E6E1E6A.5020501@rcf.rhic.bnl.gov> 2013-08-08 14:21 ` unable to get setup.ini Wei Xie 2013-08-08 16:06 ` David Lee Lambert 2011-11-15 19:30 ` frequently getting a STATUS_ACCESS_VIOLATION exception under win7 jenw
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=r2r9d1cfe481005030851qb5559440w7318240333478229@mail.gmail.com \ --to=yuval.emek@gmail.com \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).