child, and the kill happens
before the child execs (the problematic case you describe), then the
child simply enters the hypervisor's signal handler, notices that it's
not the hypervisor, and exits.
Thomas
On Fri, Nov 25, 2011 at 4:09 PM, Christian Grothoff
mailto:christ...@grothoff.o
On 11/25/2011 07:50 PM, Thomas Bushnell, BSG wrote:
Programs which depend on the special suspend-the-parent behavior of
vfork were always regarded as buggy...
So relying on the well-documented behavior of a system call is a bug?
Did you even read about the scenario I described at
https://gnune
