From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15009 invoked by alias); 25 Feb 2014 15:21:10 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 14997 invoked by uid 89); 25 Feb 2014 15:21:09 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx05.mykolab.com Received: from mx01.mykolab.com (HELO mx05.mykolab.com) (95.128.36.1) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 25 Feb 2014 15:21:07 +0000 X-Spam-Score: -0.002 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 25 Feb 2014 15:35:00 -0000 From: "Thomalla, Martin" To: cygwin@cygwin.com Subject: Re: Re: Cygwin 1.7.28 (64bit) and Vim 7.4 build from source create SEGV when writing to a file. Message-ID: X-Sender: mrt181@mykolab.ch X-SW-Source: 2014-02/txt/msg00643.txt.bz2 Which vim sources that work in cygwin should I use instead? A quick review of the files you've provided and your description of what you've done doesn't raise any red flags. I'll suggest trying to remove the Cygwin-provided VIM packages to be sure there is no collision/interaction. If that doesn't work, I'd recommend debugging the problem directly with gdb. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? On 2/25/2014 3:10 AM, Thomalla, Martin wrote: Hello, in order to get additional features into vim (lua and python) I need to build it from source. So I have downloaded the source and gcc through the cygwin setup-x86_64.exe and build vim from source. $ cd /usr/src/vim74 $ ./configure --enable-luainterp --enable-pythoninterp --enable-multibyte --enable-gui=no --without-x --prefix=/usr $ make && make install When I open a file in which the lua interpreter is used by a plugin (neocomplete:[https://github.com/Shougo/neocomplete.vim]), make a change in the file and save the file with :x I get this error: Vim: Caught deadly signal SEGV Vim: Finished. The file is saved succesfully. It does not matter if I open the file from the command line or within vim $ vim ~/file.hs $ vim :edit ~/fils.hs Both lead to the error When I open the file within vim with :edit or from the command line and save the file with :w, vim crashes again Vim: Caught deadly signal SEGV Vim: Finished. but this time the cygwin bash shell does not respond anymore. It only accepts and as input and to exit cygwin I have to input followed by or close the window. I have attached the output of vim --version gcc --version cygcheck -svr -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple