Re: New GCC? (Was: Re: Vim segv'ing)

On 22 July 2011 05:16, Corinna Vinschen wrote: > Fortunately Yaakov is going to pick up gcc and will release a new > gcc-4.5.3 package set soon. Excellent news! I very much look forward to it. Thank you Yaakov! Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/i

Re: New GCC? (Was: Re: Vim segv'ing)

On Jul 20 07:05, Chris Sutcliffe wrote: > On 1 July 2011 19:00, Chris Sutcliffe wrote: > > On 1 July 2011 15:36, Chris Sutcliffe wrote: > >> I know Yaakov has asked a few times now, it would really be nice to > >> have a 4.5.x release of the native Cygwin compiler.  I'm curious if > >> the issues I

Re: New GCC? (Was: Re: Vim segv'ing)

On 1 July 2011 19:00, Chris Sutcliffe wrote: > On 1 July 2011 15:36, Chris Sutcliffe wrote: >> I know Yaakov has asked a few times now, it would really be nice to >> have a 4.5.x release of the native Cygwin compiler.  I'm curious if >> the issues I'm having with the latest rtorrent / libtorrent re

Re: Vim segv'ing

Hi Yaakov, On Jul 6 03:28, Yaakov (Cygwin/X) wrote: > On Tue, 2011-07-05 at 11:09 +0200, Corinna Vinschen wrote: > > Thank you. Unfortunately I have issues. I have updated to the above > > fedora-cygwin-release-2-1.fc14 on my F14 machine and I cleaned out my > > entire yum cache. However, what

Re: Vim segv'ing

On Tue, 2011-07-05 at 11:09 +0200, Corinna Vinschen wrote: > Thank you. Unfortunately I have issues. I have updated to the above > fedora-cygwin-release-2-1.fc14 on my F14 machine and I cleaned out my > entire yum cache. However, what happens is this: > > # yum clean all > [...] > # yum u

Re: Vim segv'ing

On Jul 4 17:29, Yaakov (Cygwin/X) wrote: > On Fri, 2011-07-01 at 11:43 +0200, Corinna Vinschen wrote: > > P.S.: Yaakov, is there any chance to get a 4.5.3 x86_64 cross compiler > > package? Yum always tries to replace my x86_64 4.5.1 package with the > > 4.5.3 package for i686, but that doesn't w

Re: Vim segv'ing

On Fri, 2011-07-01 at 11:43 +0200, Corinna Vinschen wrote: > P.S.: Yaakov, is there any chance to get a 4.5.3 x86_64 cross compiler > package? Yum always tries to replace my x86_64 4.5.1 package with the > 4.5.3 package for i686, but that doesn't work due to missing > dependencies... I have updat

Re: Vim segv'ing

On Sat, Jul 02, 2011 at 01:31:11AM -0400, Charles Wilson wrote: >On 7/1/2011 3:36 PM, Chris Sutcliffe wrote: >> Dave, any chance on a new release? > >Dave has not posted to any cygwin list since > >Mar 29, 2011 -- cygwin >http://cygwin.com/ml/cygwin/2011-03/msg00825.html > >Apr 21, 2011 -- cygwin-t

Re: Vim segv'ing

On 7/1/2011 3:36 PM, Chris Sutcliffe wrote: > Dave, any chance on a new release? Dave has not posted to any cygwin list since Mar 29, 2011 -- cygwin http://cygwin.com/ml/cygwin/2011-03/msg00825.html Apr 21, 2011 -- cygwin-talk http://cygwin.com/ml/cygwin-talk/2011-q2/msg4.html Feb 04, 2011

New GCC? (Was: Re: Vim segv'ing)

On 1 July 2011 15:36, Chris Sutcliffe wrote: > I know Yaakov has asked a few times now, it would really be nice to > have a 4.5.x release of the native Cygwin compiler.  I'm curious if > the issues I'm having with the latest rtorrent / libtorrent release > are a result of a compiler bug. I've conf

Re: Vim segv'ing

On 1 July 2011 07:44, Corinna Vinschen wrote: > On Jul  1 11:21, Andy Koppe wrote: >> On 1 July 2011 10:43, Corinna Vinschen wrote: >> > On Jul  1 10:36, Corinna Vinschen wrote: >> > And it also does not happen if I build Cygwin with gcc 4.5.1 rather than >> > with gcc 4.3.4.  Is it possible that a

Re: Vim segv'ing

On Jul 1 11:21, Andy Koppe wrote: > On 1 July 2011 10:43, Corinna Vinschen wrote: > > On Jul  1 10:36, Corinna Vinschen wrote: > >> FYI, I tracked it down to the place where the stack overwrite occurs. > >> This is most puzzeling.  When typing :wq!, the following chain of functions > >> is called:

Re: Vim segv'ing

On Jul 1 05:09, Yaakov Selkowitz wrote: > On Fri, 2011-07-01 at 11:43 +0200, Corinna Vinschen wrote: > > P.S.: Yaakov, is there any chance to get a 4.5.3 x86_64 cross compiler > > package? Yum always tries to replace my x86_64 4.5.1 package with the > > 4.5.3 package for i686, but that doesn't wo

Re: Vim segv'ing

On 1 July 2011 10:43, Corinna Vinschen wrote: > On Jul  1 10:36, Corinna Vinschen wrote: >> FYI, I tracked it down to the place where the stack overwrite occurs. >> This is most puzzeling.  When typing :wq!, the following chain of functions >> is called: >> >>   nv_colon >>    do_cmdline >>     ex_

Re: Vim segv'ing

On Fri, 2011-07-01 at 11:43 +0200, Corinna Vinschen wrote: > P.S.: Yaakov, is there any chance to get a 4.5.3 x86_64 cross compiler > package? Yum always tries to replace my x86_64 4.5.1 package with the > 4.5.3 package for i686, but that doesn't work due to missing > dependencies... Thanks for t

Re: Vim segv'ing

On Jul 1 10:36, Corinna Vinschen wrote: > FYI, I tracked it down to the place where the stack overwrite occurs. > This is most puzzeling. When typing :wq!, the following chain of functions > is called: > > nv_colon >do_cmdline > ex_exit > do_write > open

Re: Vim segv'ing

On Jun 30 21:42, Chris Sutcliffe wrote: > On 30 June 2011 16:09, Warren Young wrote: > > On 6/30/2011 6:30 AM, Nellis, Kenneth wrote: > >> > >> The strace command interferes > >> with vim so that it won't recognize ESC to allow the ":" to be > >> recognized, so I can't ":wq!" as requested. > > > >

Re: Vim segv'ing

On Jun 30 17:05, Corinna Vinschen wrote: > On Jun 30 16:23, Corinna Vinschen wrote: > > On Jun 30 07:30, Nellis, Kenneth wrote: > > > > From: Corinna Vinschen > > > > Works fine for me. If I'm admin, writing works, if I'm not admin, > > > > writing fails with permission denied. Could you please s

Re: Vim segv'ing

On 6/30/2011 6:30 AM, Nellis, Kenneth wrote: The strace command interferes with vim so that it won't recognize ESC to allow the ":" to be recognized, so I can't ":wq!" as requested. Easy fix: $ strace -o vim.trace vim-nox -c q /etc/hosts That causes it to go through the full motions of l

Re: Vim segv'ing

On Jun 30 16:23, Corinna Vinschen wrote: > On Jun 30 07:30, Nellis, Kenneth wrote: > > > From: Corinna Vinschen > > > Works fine for me. If I'm admin, writing works, if I'm not admin, > > > writing fails with permission denied. Could you please send your > > > cygcheck output per http://cygwin.co

Re: Vim segv'ing

On Jun 30 07:30, Nellis, Kenneth wrote: > > From: Corinna Vinschen > > Works fine for me. If I'm admin, writing works, if I'm not admin, > > writing fails with permission denied. Could you please send your > > cygcheck output per http://cygwin.com/problems.html as well as an > > strace which show

Re: Vim segv'ing

On Jun 29 18:27, Jeremy Hetzler wrote: > I have noticed this problem as well. > > - "vi /etc/hosts": segfaults > - "vi /c/Windows/system32/drivers/etc/hosts": works > - "cd $HOME; ln -s /c/Windows/system32/drivers/etc/hosts foo; vi foo": works > > I get similar behavior with the other symlinks in

Re: Vim segv'ing

In addition, the segfault only occurs if /etc/hosts is specified on the command line. This works: vi :e /etc/hosts :w :q -- Jeremy Hetzler On Wed, Jun 29, 2011 at 6:27 PM, Jeremy Hetzler wrote: > I have noticed this problem as well. > > - "vi /etc/hosts": segfaults > - "vi /c/Windows/system32/d

Re: Vim segv'ing

I have noticed this problem as well. - "vi /etc/hosts": segfaults - "vi /c/Windows/system32/drivers/etc/hosts": works - "cd $HOME; ln -s /c/Windows/system32/drivers/etc/hosts foo; vi foo": works I get similar behavior with the other symlinks in /etc. CYGWIN_NT-6.1-WOW64 box 1.7.9(0.237/5/3) 2011

Vim segv'ing

Just started happening recently: $ vi /etc/hosts :wq $ vi /etc/hosts :w Vim: Caught deadly signal SEGV Vim: Finished. Segmentation fault -- Andrew DeFaria Drive carefully. It's not only cars that can be "recalled" by their maker.% Cygwin Configuration Diagnostics Current Sy