Date: Tue, 22 Apr 1997 21:32:05 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.ru> To: Bruce Evans <bde@zeta.org.au> Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: Recent vfork kernel changes broke csh & tcsh! Message-ID: <Pine.BSF.3.96.970422212716.363E-100000@nagual.ru> In-Reply-To: <199704221236.WAA18843@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <ache@null.net> http://www.nagual.ru/~ache/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970422212716.363E-100000>