From owner-freebsd-current  Mon Apr 21 18:37:40 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA04372
          for current-outgoing; Mon, 21 Apr 1997 18:37:40 -0700 (PDT)
Received: from sovcom.relcom.ru (sovcom.relcom.ru [193.125.152.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA04358;
          Mon, 21 Apr 1997 18:37:25 -0700 (PDT)
Received: by sovcom.relcom.ru id AA06304
  (5.65.kiae-1 ); Tue, 22 Apr 1997 04:27:35 +0300
Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 22 Apr 97 04:27:35 +0300
Received: (from ache@localhost)
	by nagual.ru (8.8.5/8.8.5) id FAA00253;
	Tue, 22 Apr 1997 05:25:14 +0400 (MSD)
Date: Tue, 22 Apr 1997 05:25:10 +0400 (MSD)
From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.ru>
To: FreeBSD-current <current@FreeBSD.ORG>, dyson@FreeBSD.ORG
Subject: Re: Recent vfork kernel changes broke csh & tcsh!
In-Reply-To: <Pine.BSF.3.96.970422012832.2204A-100000@nagual.ru>
Message-Id: <Pine.BSF.3.96.970422052348.244A-100000@nagual.ru>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=KOI8-R
Content-Transfer-Encoding: 8BIT
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 22 Apr 1997, Андрей Чернов wrote:

> and you got SIGSEGV at the next one or two commands you'll enter
> after it started.
> 
> Both csh and tcsh affected in the similar way.

I forgot to mention that I am shure it is vfork problem because it
disappearse when I change vfork to fork in csh or tcsh.

-- 
Andrey A. Chernov
<ache@null.net>
http://www.nagual.ru/~ache/