Date: Sun, 21 Jul 1996 13:30:03 -0700 (PDT) From: Marc Slemko <marcs@valis.worldgate.com> To: freebsd-bugs Subject: Re: bin/1411: vi dumps core when using 'set list' Message-ID: <199607212030.NAA25310@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/1411; it has been noted by GNATS. From: Marc Slemko <marcs@valis.worldgate.com> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/1411: vi dumps core when using 'set list' Date: Sun, 21 Jul 1996 14:24:27 -0600 (MDT) On Sun, 21 Jul 1996, J Wunsch wrote: > As marcs@worldgate.com wrote: > > > >How-To-Repeat: > > > > Using version 1.36.4.5 of sys/scsi/st.c, input the following from the keyboard: > > > > vi st.c > > :set list > > 172j12jj > > > > After the last j, vi core dumps displaying line 185. Same thing > > happens when scrolling via other means, but not when you go to line > > 185 before doing a 'set list', and then do a 'set list'. > > 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. > > Which vi version are you using, and which $TERM setting? vi from RELENG_2_1_5_RELEASE. I don't doubt that the difference could be 2.1.5 vs. current; I don't have a system running current here to try it here. I checked out the vi from current as of last week and compiled it; it exhibited the same problem. I also checked out the vi from RELENG_2_1_0_RELEASE, and it had the same problem when compiled under 2.1.5. Note that the problem does not seem to be there on a 2.1.0 system using 2.1.0 vi, nor is it there when I copy the 2.1.0 binary to a 2.1.5 system; when I copy a 2.1.5 binary to a 2.1.0 system the problem is still there. It is present both on 2.1.5 compiled locally from the latest stable tree and on 2.1.5 installed via ftp from wcarchive. 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607212030.NAA25310>