From owner-freebsd-bugs Sat Apr 8 20:10: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id DFBDE37B606 for ; Sat, 8 Apr 2000 20:10:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id UAA10168; Sat, 8 Apr 2000 20:10:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sat, 8 Apr 2000 20:10:02 -0700 (PDT) Message-Id: <200004090310.UAA10168@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bill Fenner Subject: Re: bin/3170: vi freaks and dump core if user doesn't exist Reply-To: Bill Fenner Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/3170; it has been noted by GNATS. From: Bill Fenner To: dhagan@cs.vt.edu Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/3170: vi freaks and dump core if user doesn't exist Date: Sat, 8 Apr 2000 20:08:08 -0700 I'm able to replicate it using the same ol' steps on a month-old 4.0-CURRENT: 1. log in as user foo 2. vi a file 3. ^Z vi 4. su 5. vipw, change user foo's uid (or delete user foo) 6. suspend the su 7. fg the vi 8. make a change; vi says: +=+=+=+=+=+=+=+ Information on user id 1000 not found. Modifications not recoverable if the session fails Segmentation fault (core dumped) (which is not surprising, since vi hasn't changed since 1996) Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message