Since vfork() experienced spawned that baby, it returned though in fact still executing inside the parent's approach space, not simply corrupting the dad or mum's stack, but triggering two disparate sets of diagnostics to generally be printed by "downstream" code. it's not the issue OP was going through along with https://stack-ball-arcade-game94763.blue-blogs.com/44074732/indicators-on-stack-ball-arcade-game-you-should-know