Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Jul 1996 23:41:12 +0200 (MET DST)
From:      J Wunsch <j@uriah.heep.sax.de>
To:        marcs@valis.worldgate.com
Cc:        freebsd-bugs@freefall.freebsd.org
Subject:   Re: bin/1411: vi dumps core when using 'set list'
Message-ID:  <199607212141.XAA01730@uriah.heep.sax.de>
In-Reply-To: <199607212030.NAA25310@freefall.freebsd.org> from Marc Slemko at "Jul 21, 96 01:30:03 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
As Marc Slemko wrote:

>  > It works for me, in a -current as of about one week old, and in an
>  > (24x80) xterm.
>  
>  I was doing the testing both from the sc console (with a $TERM of cons25),
>  rlogin from various boxes ($TERM=vt100) and a remote xterm ($TERM=xterm,
>  80x24); all had the same result for me.

>  It appears that the bug is coming from somewhere other than the vi source
>  (although the vi source still could be the thing that is broken) that is
>  linked into the binary at compile time, not run time. 
>  
>  If you don't have a 2.1.5 system handy to try it on, try pulling the 2.1.5
>  binary and running it under current.

Sorry, again: nothing.  I've compiled the vi from 2.1.5, and it works
flawlessly.  (And yes, i'm picking the correct st.c version, i can
clearly see the spot where it has to jump two lines when typing the
last `j'.)  I've tested with a 24x80 xterm, and with a 25x80 virtual
console (but pcvt).

Can you compile the vi with debug information, and try to analyze the
core dump?  Can you strip down your environment to the bare minimum
and see whether this would change something?  You are suspecting an
error somewhere else... well, recompiling the binary was easy for me,
but tweaking my system to use the 2.1.5 shared libs would be harder.
*** Nope.  I've just diffed the sources for libtermcap and libcurses,
there are only cosmetic changes between 2.1.5 and -current (additional
paren's to avoid compiler warnings).  libutil has a few more changes,
but nothing i think vi will use (setproctitle, openpty and logwtmp).

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607212141.XAA01730>