On Tue, Aug 14, 2012 at 12:42:15PM +0800, David Xu wrote: > I simply duplicated idea from OpenSolaris, here is my patch > which has similar feature as your patch, and it also tries to > prevent vforked child from corrupting parent's data: > http://people.freebsd.org/~davidxu/patch/libthr-vfork.diff You shall not return from vfork() frame in the child. Otherwise, the same frame is appears to be destroyed in parent, and parent dies. More often on !x86, but right combination of events on x86 is deadly too. If pid or curthread local variables are spilled into stack save area, then child will override them, and e.g. parent could see pid == 0, returning it to caller.
This was the reason why I went to asm wrapper for vfork. Also, it seems that in mt process, malloc and rtld are still broken, or am I missing something ?
pgpd2EinQ1bZi.pgp
Description: PGP signature
