From owner-freebsd-bugs  Thu Apr 20 14:27:12 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 5E24737B521; Thu, 20 Apr 2000 14:27:11 -0700 (PDT)
	(envelope-from wilko@FreeBSD.org)
Received: (from wilko@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id OAA75161;
	Thu, 20 Apr 2000 14:27:11 -0700 (PDT)
	(envelope-from wilko@FreeBSD.org)
Date: Thu, 20 Apr 2000 14:27:11 -0700 (PDT)
From: <wilko@FreeBSD.org>
Message-Id: <200004202127.OAA75161@freefall.freebsd.org>
To: c1995207@uhura.nit.ac.jp, wilko@FreeBSD.org,
	freebsd-bugs@FreeBSD.org
Subject: Re: bin/13000: vi core dumped
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: vi core dumped

State-Changed-From-To: open->closed
State-Changed-By: wilko
State-Changed-When: Thu Apr 20 14:25:53 PDT 2000
State-Changed-Why: 
Problem is fixed in the vi that is part of 3.4-stable (maybe already
fixed in an earlier release but I don't have a system running < 3.4-stable).
Instead of a coredump a warning/error message is produced.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message