X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=vI/l7hPPa5h2pIHa DqPN91QsoucUhbMkx9RKJYwcoH7nwuC/XoRLE6Xhg5fp3YZc+vRdbOPKue8prd9g hkKdc0Y13dTUQxNuleq7vDfr+UZi3XlFAledR+NqLEzgtieHab/HWh8uelo41omd BXkKtAfFgReDCi7YA7uvJYAtFeY= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:reply-to:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=default; bh=vzsz/pZm9mxuwisqR3rLt9 yDNOw=; b=kTz7ssvGkNRpxfjprmUPRnl+hW/2FuI58OzvS5d+T8h4Pi5lBRLzt5 HqeUusS5NDQ5tshyQpErJqKY/DCRjPLmw2FDNF+qFEdgoaNm6oGROrE6XkESadyy J+q9VGTfsl8VzoCncKjzgTlGDI5CJsf3iJerKQBJseWJ4lBI2SjQQ= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-HELO: vms173017pub.verizon.net Message-id: <530CAA5C.8060505@cygwin.com> Date: Tue, 25 Feb 2014 09:36:12 -0500 From: "Larry Hall (Cygwin)" Reply-to: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.7.28 (64bit) and Vim 7.4 build from source create SEGV when writing to a file. References: <6f9492621546f3eeca905b6281314451 AT mykolab DOT ch> In-reply-to: <6f9492621546f3eeca905b6281314451@mykolab.ch> Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit 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 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? -- 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