From owner-freebsd-bugs Sat Aug 10 19:16:52 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA00986 for bugs-outgoing; Sat, 10 Aug 1996 19:16:52 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA00925 for ; Sat, 10 Aug 1996 19:16:43 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id SAA00274 for ; Sat, 10 Aug 1996 18:41:42 -0700 (PDT) Received: from mongoose.bostic.com (mongoose.BSDI.COM) by mail.crl.com with SMTP id AA28236 (5.65c/IDA-1.5 for ); Sat, 10 Aug 1996 17:06:36 -0700 Received: (from bostic@localhost) by mongoose.bostic.com (8.7.4/8.7.3) id UAA10846; Sat, 10 Aug 1996 20:05:04 -0400 (EDT) Date: Sat, 10 Aug 1996 20:05:04 -0400 (EDT) From: Keith Bostic Message-Id: <199608110005.UAA10846@mongoose.bostic.com> To: j@uriah.heep.sax.de Subject: Re: bin/1411: vi dumps core when using 'set list' Cc: freebsd-bugs@freebsd.org, marcs@valis.worldgate.com Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for the vi bug report! > Subject: Re: bin/1411: vi dumps core when using 'set list' > > As j wrote: > >>> Hmm. Well, I tried compiling it once again, this time with CFLAGS set to >>> "-O2 -m486 -pipe" and the problem was not there. Trying with "-O2 -m486", >>> the problem still wasn't there. With one of -O2 or -m486, it is still >>> there. Hey, I just tried -m486 again and it won't show up. Grr. Try >>> just using -O2 and see if you can make it show up. >> >> Ah, that's the key. Now i'm getting it, too! > > Well, i can now see the error. It still occurs when compiling with > -g, and happens inside function svi_line() here: > > if (scno < cols_per_screen) { > /* If didn't paint the whole line, update the cache. */ > smp->c_ecsize = smp->c_eclen = KEY_LEN(sp, ch); > ^^^^^^^^^^^^^^^ > smp->c_eboff = len - 1; I believe that this bug is fixed in more recent versions of nvi. The currently available release is version 1.71, but I hope to make version 1.73 available early next week. Thanks again, --keith