Mainly because vfork() experienced spawned that kid, it returned while really however executing in the mother or father's system space, not simply corrupting the mother or father's stack, but resulting in two disparate sets of diagnostics to get printed by "downstream" code. At