Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Thu, 15 Jan 2004 06:34:51 -0500
From:	Ashok Vadekar <avadekar AT certicom DOT com>
To:	cygwin AT cygwin DOT com
Subject:	VIM fails with SEGV after vi under telnet session
Message-ID:	<20040115113451.GA3571@certicom.com>
Reply-To:	avadekar AT certicom DOT com
Mime-Version:	1.0
User-Agent:	Mutt/1.4i
X-IsSubscribed:	yes

I seem to have the following repeatable problem since upgrading to 1.5.x
from 1.3.x:
	open bash shell (in Windows command prompt DOS box, not rxvt)
	vi foo (works fine)
		:q
	telnet remote machine (in my case a solaris 8 box)
		exit
	vi foo (works fine)
		:q
	telnet remote machine (in my case a solaris 8 box)
		run /usr/bin/vi (or vim)
			:q
		exit
	vi foo (fails with output:
[25;1HVim: Caught deadly signal SEGV
Vim: Finished.

and then leaves the shell in a state where it does not use \r, only \n such
thathitting enter at the prompt causes a staircase of output as the command
prompt continues to skew to the right.

Either 
	stty sane
or
	tset
will fix the staircsae, but running vi again puts me back in that state.
Running vi in strace or gdb from this point does not cause the SEGV.
Opening a new shell gives me a clean environment with which to use vi,
until I telnet and run a remote vi session.

So what terminal setting is the remote vi/vim adjusting that causes the local
vi to get confused?  I probably have an old 1.3.x terminfo entry on the remote
box, which might explain a remote vi session that didn't work well, but this
does not seem to me to be a good reason for a SEGV.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -