From owner-freebsd-bugs Sun Jul 21 15:27:27 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA00873 for bugs-outgoing; Sun, 21 Jul 1996 15:27:27 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA00868 for ; Sun, 21 Jul 1996 15:27:23 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA04585; Mon, 22 Jul 1996 00:27:20 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA16327; Mon, 22 Jul 1996 00:27:19 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id XAA01730; Sun, 21 Jul 1996 23:41:12 +0200 (MET DST) From: J Wunsch Message-Id: <199607212141.XAA01730@uriah.heep.sax.de> Subject: Re: bin/1411: vi dumps core when using 'set list' To: marcs@valis.worldgate.com Date: Sun, 21 Jul 1996 23:41:12 +0200 (MET DST) Cc: freebsd-bugs@freefall.freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607212030.NAA25310@freefall.freebsd.org> from Marc Slemko at "Jul 21, 96 01:30:03 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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. ;-)