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=Aw6sH8UdxbRuVyXD
	aJRkWeESKNDLVhw1fJpT6MhB6qTDCamiHX9DcXyFogdBYiTHGDHGnVpsFTuLfz9D
	rh+dgevl3EqrruZDdq++9Dlea9aOsztRPB/tNqh0LF/Uzf3mmXuJvEeyJRvucwHx
	mFu5/nxIFqlfHzV4TSDxmS1iPNM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-id: <530CBD99.5010802@cygwin.com>
Date: Tue, 25 Feb 2014 10:58:17 -0500
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
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: <f2219ce3ced8d2db57e6ad61ae95d369 AT mykolab DOT ch> <530CB834 DOT 2050009 AT cygwin DOT com> <e788505c9e25cc98142ae675f285afb3 AT mykolab DOT ch>
In-reply-to: <e788505c9e25cc98142ae675f285afb3@mykolab.ch>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 2/25/2014 10:43 AM, Thomalla, Martin wrote:
> 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.

I'd recommend sending to the VIM developers list directly.

<http://www.vim.org/maillist.php#vim-dev>

Also, checking the archives there may unearth some related discussion that
came up previously.


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