Date: Wed, 23 Apr 1997 04:43:11 +1000 From: Bruce Evans <bde@zeta.org.au> To: ache@nagual.ru, bde@zeta.org.au Cc: current@freebsd.org, dyson@freebsd.org Subject: Re: Recent vfork kernel changes broke csh & tcsh! Message-ID: <199704221843.EAA29497@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
The procfs_mem.c fix fixed the hangs on thrd_s.
>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 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").
>Do you have some results from debugging?
Nothing interesting before now.
>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.
I haven't seen this.
Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704221843.EAA29497>