Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Sent: 25 Jun 2002 22:59:10 GMT Message-Id: <5.1.0.14.0.20020625164942.00b31578@mail.januslogix.com> X-Sender: jsumsion AT januslogix DOT com@mail.januslogix.com Date: Tue, 25 Jun 2002 16:59:06 -0600 To: cygwin AT cygwin DOT com From: John Sumsion Subject: Problem with cygwin 1.3.11-3 / WinCVS / vim Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed I'm using Problem with cygwin 1.3.11-3 / WinCVS 1.3 beta / vim 6.1-2. Here is the command that fails: cvs ci NameParser.java NOTE: the WinCVS cvs executable is being run, NOT the cygwin cvs executable. The following variables are set for the CVS executable CVSHOME=:sspi:1.2.3.4:d:/dev ; CVSEDITOR=vim -n . And the ~/.cvsrc file contains one line: 'cvs -x' Here is the result: *** BEGIN *** 6 [main] vim 2064 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 36228 [main] vim 2064 open_stackdumpfile: Dumping stack trace to vim.exe.stack dump cvs commit: warning: editor session failed Log message unchanged or not specified a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining dirs Action: (continue) a cvs [commit aborted]: aborted by user *** END *** The stack dump looks like: *** BEGIN *** Exception: STATUS_ACCESS_VIOLATION at eip=61005558 eax=00000000 ebx=10020008 ecx=616800F0 edx=00000001 esi=00000000 edi=00000000 ebp=0022FF00 esp=0022FEB8 program=C:\cygwin\bin\vim.exe cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023 Stack trace: Frame Function Args 0022FF00 61005558 (610C095C, FFFFFFFE, 000007E0, 610C08A0) 0022FF60 61005D28 (00000000, 00000000, 0000000F, F7732C94) 0022FF90 004C49AB (00450898, 00000001, 00000000, 805B406F) 0022FFC0 0040103D (00000000, 00000000, 7FFDF000, F7732CF4) 0022FFF0 77E7EB69 (00401000, 00000000, 78746341, 00000020) End of stack trace *** END *** I've tried the snapshot for Jun 25, 2002 - the problem doesn't go away. When I revert back to cygwin 1.3.10-1, everything works fine - vim comes up and I'm able to type in a comment and commit the file. John... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/