sag@lemm.ee to linuxmemes@lemmy.world · 6 months agoNo Mercyfiles.catbox.moeexternal-linkmessage-square161fedilinkarrow-up1912arrow-down170
arrow-up1842arrow-down1external-linkNo Mercyfiles.catbox.moesag@lemm.ee to linuxmemes@lemmy.world · 6 months agomessage-square161fedilink
minus-squaresenkoralinkfedilinkarrow-up3·6 months agoI haven’t tried this, but if you just need the parent to call waitpid on the child’s pid then you should be able to do that by attaching to the process via gdb, breaking, and then manually invoking waitpid and continuing.
minus-squareCameronDev@programming.devlinkfedilinkarrow-up8·edit-26 months agoI think that should do it. I’ll try later today and report back. Of course, this risks getting into an even worse state, because if the parent later tries to correctly wait for its child, the call will hang. Edit: Will clean up the orphan/defunct process. If the parent ever tried to wait, they would either get ECHILD if there are no children, or it would block until a child exited. Will likely cause follow on issues - reaping someone elses children is generally frowned upon :D.
I haven’t tried this, but if you just need the parent to call waitpid on the child’s pid then you should be able to do that by attaching to the process via gdb, breaking, and then manually invoking waitpid and continuing.
I think that should do it. I’ll try later today and report back.
Of course, this risks getting into an even worse state, because if the parent later tries to correctly wait for its child, the call will hang.
Edit: Will clean up the orphan/defunct process.
If the parent ever tried to wait, they would either get ECHILD if there are no children, or it would block until a child exited.
Will likely cause follow on issues - reaping someone elses children is generally frowned upon :D.