Simply because vfork() experienced spawned that baby, it returned when actually however executing within the mum or dad's course of action space, not simply corrupting the mum or dad's stack, but creating two disparate sets of diagnostics to become printed by "downstream" code.it's not the situation OP was facing along with your issue is With all t