Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <400D450B.5000108@acm.org> Date: Tue, 20 Jan 2004 07:11:07 -0800 From: David Rothenberger User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: cygwin-1.5.6-1 Vim now broken References: <20040120043650.GB22155@redhat.com> In-Reply-To: <20040120043650.GB22155@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Christopher Faylor wrote: > On Mon, Jan 19, 2004 at 09:39:19PM -0500, Brian.Kelly@Empireblue.com wrote: > >>I installed the new 1.5.6-1 and rebooted. I then went to edit a file with >>vim. I changed one line of code and went to save the file. This is what >>happened: >> >>- vi FA_lib.pm >>'Vim: Caught deadly signal SEGV >>Vim: preserving files... >> >>Basically I cannot use Vim to edit files - as it now stands. > > > Editing files works fine, AFAICT. Vim seems to be dying on exit. I don't know if this will help with this problem, but I had the same issue under Windows XP Pro. The problem occurred with files on which SYSTEM was explicitly granted Full Control in the Windows security settings. When I removed that grant, I was able to edit and save the file correctly. Dave -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/