Because vfork() had spawned that baby, it returned though basically still executing throughout the parent's approach space, not simply corrupting the mother or father's stack, but producing two disparate sets of diagnostics for being printed by "downstream" code.Your first is correct as-is, except you'll want to eliminate the issue mark at the end