I love writing job control code

This is a scratchpad. Don't unwrap syscall stuff. It can almost always plausibly fail.

have you misspelled "prisoned"?

@Lensflare No, I put a child process in a mutex. The mutex might get poisoned if another thread panics while holding the lock. I cannot be assed to ensure panic safety, so panics just cascade across shared mutexes through checks like this one.

@lorentz I figured it should be prisoned because you locked it 😅
I didn’t know about poisoning processes or mutexes (mutexi?).

@Lensflare I personally think it's mutices

As far as I know, poisoning is a Rust-specific term, C++ and the broader community calls it unspecified or invalid state or something like that.

I like the metaphor of poison, because it hammers in the idea that unless you can prove otherwise, touching anything coming out of a crashed process breaks the current process too.