> can you tell me what the new glibc does for different "clone()" system
> calls?
clone() and vfork() both use int $0x80. The vfork() problem is obvious.
And the way we use clone() with a separate stack for the child it is
easy to see that we cannot prepare the stack appropriately for both
situations. When the child is started it returns with a carefully
crafted stack which among other values find the start functions address
on the stack.
There might be a way to make this use int and vsyscall at the same time
but I don't think it is worth it.
-- --------------. ,-. 444 Castro Street Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA Red Hat `--' drepper at redhat.com `---------------------------- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/