I've started on a run-program library primitive, which invokes a
'shell' program. On Unix, this involves a call to fork(). I assume
fork-then-exec is safe, and will remain safe, since the forked process
will get only the thread the called fork, and exec will pretty much
reset the whole process (I'm closing fds manually), but I thought I'd
check.

Can anyone think of any problems, either now or in the future, with
this? I'm thinking of stacks switching and other funky multi-threading
techniques doing something the OS wasn't expecting.

(And what if I call fork but don't call exec? That might also be
useful at some point.)

Cheers,
Marijn
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to