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:in-reply-to:references:message-id; q=dns; s=
	default; b=EB8zRMNvTMaEeNvW48LCx0xT+/fyi/K+KLx9I1/rass6CVOafYkws
	YMxDJa3SxVRi98gzwEegtdFOgYaznN5BhEz2Z1xoVPKYfggZb/OCA1iGIafZp7jv
	RUxdFbE3iAdtDmcU9eeFhZojiJRr7Gh4aShMDsmoUJ+sUaPAkcE1oI=
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:in-reply-to:references:message-id; s=default;
	 bh=IojVvMQ9sj+B0jJnTkyuNhMgtrQ=; b=mN9zJVR1KpWSdrSu5XnNpwdT2ed6
	wESoFfHaEZJzLqLUahl4v5YIFyI3sT1RjIjkS7uXwjp50ux1le8StBy44Lnepae9
	rvoII7V/7P3S4EJiEFRMXrI9UAJKwXwrQ2AdWhgiyJTuIoM9YRhVmlfP3waT3lyk
	8khJCGSqioL4yXI=
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=1.3 required=5.0 tests=AWL,BAYES_05,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mx03.mykolab.com
X-Spam-Score: -0.002
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 25 Feb 2014 16:43:21 +0100
From: "Thomalla, Martin" <mrt181 AT mykolab DOT ch>
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.
In-Reply-To: <530CB834.2050009@cygwin.com>
References: <f2219ce3ced8d2db57e6ad61ae95d369 AT mykolab DOT ch> <530CB834 DOT 2050009 AT cygwin DOT com>
Message-ID: <e788505c9e25cc98142ae675f285afb3@mykolab.ch>
X-Sender: mrt181 AT mykolab DOT ch
X-IsSubscribed: yes

On 2014-02-25 16:35, Larry Hall (Cygwin) wrote:
> On 2/25/2014 10:20 AM, Thomalla, Martin wrote:
>>>      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.
>> Which vim sources that work in cygwin should I use instead?
> 
> If you didn't use source package that you can download through setup, 
> you
> can rerun setup and select it by checking the "Src?" checkbox.  But I
> think you misunderstand my response.  You said that you built from 
> source
> yourself and added features that aren't built into the binary package 
> that
> you can install via setup.  When using those features in your binary, 
> you
> experienced SEGVs.  Since you are using features that aren't supported 
> in
> the Cygwin version, there's no guarantee that they will work as 
> expected.
> In other words, you're blazing a new trail under Cygwin so you'll be 
> the
> first to encounter any problems that may come from doing so.
> 
> Another possible avenue to check is whether the upstream VIM package 
> has
> received any reports of problems with python and lua.  If so, there may 
> be
> patches or other solutions that could also be applied to Cygwin.
> 
> 
> --
> Larry
> 
> _____________________________________________________________________
> 
> A: Yes.
>> Q: Are you sure?
>>> A: Because it reverses the logical flow of conversation.
>>>> Q: Why is top posting annoying in email?
> 

Ok, I have already used the source packages I get through setup and 
encountered the problem.
I have send the initial email also to the 
https://groups.google.com/forum/#!forum/vim_dev list but haven't heard 
anything from there yet.

Martin

--
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