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:content-type:content-transfer-encoding:date
	:from:to:subject:message-id; q=dns; s=default; b=pG4KD5MFCrvvrWh
	PM9aGXADxHDzwAh1uzbpZ4Fmp3IYEWiXabQN4ilTi6fukqYRZkRKkN27B6xLB4L1
	nOAuQyQKsqSbL28cxDcIfgTI6QtJ76K5lVZry/MyZOzKjaVSOuVVhHAMD4g/7FlB
	ngRDWQXAtlyfwCH21XfanalMOmwY=
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:content-type:content-transfer-encoding:date
	:from:to:subject:message-id; s=default; bh=Ux4QFc7a+JlnWVuulUw1k
	8TEl0o=; b=Uz+1O4W0BjUEFiKmhsFF/p3fDIL+Ffe/cAs63TStax4V1z0LUm+Lt
	Dv8k7g93BRz/LJVj5pdKlna+XxWKu/1O+vFg8TSYn8QDzuvK3eObs2OexhN7oZ4v
	LGMUcwn7pdufSgyKFaolBNAHJjl1mKYnagoH8vHHMNvCYtBt+9onus=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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.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
X-Spam-Score:	-0.002
Date:	Tue, 25 Feb 2014 16:20:50 +0100
From:	"Thomalla, Martin" <mrt181 AT mykolab DOT ch>
To:	cygwin AT cygwin DOT 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:	<f2219ce3ced8d2db57e6ad61ae95d369@mykolab.ch>
X-Sender:	mrt181 AT mykolab DOT ch

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 <ctrl><c> and <ctrl><d> as input and to exit cygwin I 
have to input
         <ctrl><c> followed by <ctrl><d> 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

- Raw text -