From owner-freebsd-current Tue Apr 22 11:01:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA29240 for current-outgoing; Tue, 22 Apr 1997 11:01:17 -0700 (PDT) Received: from sovcom.relcom.ru (sovcom.relcom.ru [193.125.152.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA29203; Tue, 22 Apr 1997 11:00:57 -0700 (PDT) Received: by sovcom.relcom.ru id AA16014 (5.65.kiae-1 ); Tue, 22 Apr 1997 20:33:41 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 22 Apr 97 20:33:40 +0300 Received: (from ache@localhost) by nagual.ru (8.8.5/8.8.5) id VAA00457; Tue, 22 Apr 1997 21:32:07 +0400 (MSD) Date: Tue, 22 Apr 1997 21:32:05 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: Bruce Evans Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: Recent vfork kernel changes broke csh & tcsh! In-Reply-To: <199704221236.WAA18843@godzilla.zeta.org.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 22 Apr 1997, Bruce Evans wrote: > It may be a csh bug. csh does a lot of work to preserve the parent > state. It's not clear that this can work with an optimising compiler. > However, compiling without -O and declaring all local variables as > volatile didn't help. Yes, it may be csh & tcsh common bug, but I can't find what clobbers exactly. It finally hits process list in both csh & tcsh, but preserving process list not helps. > I think I found other bugs while attempting to debug this: Do you have some results from debugging? BTW, this bug easily cause another bug I report early (ufs lockstatus panic) when csh or tcsh is login shell. When you call a.sh from login shell, sometimes it cause lockstatus panic instead of exiting to getty. -- Andrey A. Chernov http://www.nagual.ru/~ache/