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 Date: Mon, 19 Jan 2004 23:36:50 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin-1.5.6-1 Vim now broken Message-ID: <20040120043650.GB22155@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin@cygwin.com 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. This is a malloc overrun. I think I have a fix but it seems to be in Corinna's code so I've alerted her and will let her make the final decision. It's incredible that in the hours and hours of testing that I did, I never saw this problem or the problem with bash, both of which are easily reproducible. Expect a 1.5.7 shortly. In the meantime, everyone, please bang on 1.5.6 and flush out any other problems so that I don't need to release a 1.5.8. And, no, screen becoming screwed up in an rxvt session is not a show stopper. Don't forget the cygcheck output... cgf -- 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/