sag@lemm.ee to linuxmemes@lemmy.world · 4 months agoNo Mercyfiles.catbox.moeimagemessage-square159fedilinkarrow-up1756arrow-down162
arrow-up1694arrow-down1imageNo Mercyfiles.catbox.moesag@lemm.ee to linuxmemes@lemmy.world · 4 months agomessage-square159fedilink
minus-squaresenkora@lemmy.ziplinkfedilinkarrow-up3·4 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·4 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.
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.