Date: Tue, 22 Apr 1997 23:40:27 +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.970422233443.278B-100000@nagual.ru> In-Reply-To: <199704221843.EAA29497@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Apr 1997, Bruce Evans wrote:
> I think our non-simple malloc() behaviour triggers broken csh behaviour.
> csh frees things in the parent that are allocated (only) in the child,
> but this is not guaranteed to reset the malloc state. Leaving out all
> the magic frees in the parent seems to avoid the problem. Leaving them
> alone gives a next-process pointer pointing to the name of my test
> command ("/bin/ls").
BSD vfork have follwing assumption: father suspended until child exec or
exit, even manpage say that (do we broke _that_ rule?) What wrong happens
in freeing memory in father which was malloced in a child? What do you
mean by reset malloc state?
--
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.970422233443.278B-100000>