Re: Re: Cygwin 1.7.28 (64bit) and Vim 7.4 build from source create SEGV when writing to a file.

Re: Re: Cygwin 1.7.28 (64bit) and Vim 7.4 build from source create SEGV when writing to a file.

[Thomalla, Martin]

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

Re: Cygwin 1.7.28 (64bit) and Vim 7.4 build from source create SEGV when writing to a file.

[Larry Hall (Cygwin)]

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?

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

Re: Cygwin 1.7.28 (64bit) and Vim 7.4 build from source create SEGV when writing to a file.

[Thomalla, Martin]

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

Re: Cygwin 1.7.28 (64bit) and Vim 7.4 build from source create SEGV when writing to a file.

[Larry Hall (Cygwin)]

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