Subject: Re: vi core dump
To: Patrick Welche <>
From: Aymeric Vincent <>
List: current-users
Date: 12/29/2001 14:11:21
Patrick Welche <> writes:

> Can any of you reproduce this or is it just me? XF3/i386. Pop up a ordinary
> 80x24 xterm. cd /tmp. vi foo. Then resize the xterm to 80xmore. Press the
> downward cursor key. vi now says something like Error: move: l(25) c(79)
> o(0)
> Press any key to continue:

I can reproduce this (even without loading a file), but I don't get
the core dump you're refering to below.

After diffing around and digging up old versions of nvi, I can't see
any change that would have introduced this bug. The only thing I can
think of is the recent switch to using newterm() instead of initscr(),
but I'm not a curses expert. I'll try to see if I can do something in
this direction.

Can you tell when it last worked for you? And which precise version of
nvi and libcurses are you using?

> Then you get a SEGV in vi/common/line.c:157
> switch (ep->db->get(ep->db, &key, &data, 0)) {
> which essentially is ? /usr/src/lib/libc/db/recno/rec_get.c ?

Yes, that's what it essentially is, but you shouldn't get this kind of
core dump on some file which is not a broken recovery file.
What did your /tmp/foo file contain?