From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23800 invoked by alias); 18 Jun 2010 19:36:51 -0000 Received: (qmail 23788 invoked by uid 22791); 18 Jun 2010 19:36:50 -0000 X-SWARE-Spam-Status: No, hits=2.4 required=5.0 tests=BAYES_50,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Received: from qmta11.westchester.pa.mail.comcast.net (HELO QMTA11.westchester.pa.mail.comcast.net) (76.96.59.211) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 18 Jun 2010 19:36:46 +0000 Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by QMTA11.westchester.pa.mail.comcast.net with comcast id XNUm1e0031ei1Bg5BXclS2; Fri, 18 Jun 2010 19:36:45 +0000 Received: from [192.168.1.102] ([98.244.208.99]) by omta24.westchester.pa.mail.comcast.net with comcast id XXcZ1e00529CxLa3kXckew; Fri, 18 Jun 2010 19:36:45 +0000 Message-ID: <4C1BCAC0.7040706@comcast.net> Date: Fri, 18 Jun 2010 19:36:00 -0000 From: Michael Parkinson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: xterm gvim Windows 7 STATUS_ACCESS_VIOLATION Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2010-06/txt/msg00029.txt.bz2 The same kind of problem was reported earlier by Yuval Emek on May 3, 2010. I am having a number of STATUS_ACCESS_VIOLATION issues, although most of them are intermittent, which makes me think it is some kind of timing problem. I am running Cygwin 1.75 under Windows 7 Pro. I changed the ownership of the cygwin directory and its subdirectories except for $HOME to be Administators. I disabled the User Account Control so that there would not be dropped prompts for Administrative privileges. $HOME and its subdirectories are owned by me as the Windows login user. There are a number of scripts in my own sbin directory which spawn an X Windows with a command to be executed, usually a vim invocation; e.g., "xterm -e vim $@" (opens up vim for editing whatever files I specify in a new window). Under Windows XP, this never caused any problems. Under Windows 7, it often but not always gives the STATUS_ACCESS_VIOLATION error. When running vim in the newly spawned X window, I frequently use a command like "%!fmt" in order to format the file for easier reading. When running vim in the spawned X window, this command often gives a gvim.exe.stackdump with the same STATUS_ACCESS_VIOLATION, but I discovered by accident that if I use "xterm -e vim-nox $@" instead of "xterm -e vim $@", I do not get the gvim stackdumps when using fmt. There is a related issue. If I start a new X window using the shortcut in the Start Menu, it will occasionally fail to start. But if I hit the same shortcut a second time, it usually does open a new window. This is why I think there is some kind of time-out problem while it is waiting for a response from the X server. This will happen whether or not there are any other X windows open. Is there is a way to adjust the amount of time a request for a new X window will wait? At this point, these problems are more of a nuisance than something fatal, but I would love to get the Cygwin X window system to be more reliable under Windows 7. Any comments on what might help the situation will be welcome. Mike -- 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/