rust/library/std/src/sys/unix/process, branch 1.51.0

Add setgroups to std::os::unix::process::CommandExt

2021-01-22T06:42:38+00:00

Deprecate-in-future the constants superceded by RFC 2700

2021-01-21T01:08:11+00:00

Don't use posix_spawn_file_actions_addchdir_np on macOS.

2021-01-17T17:51:02+00:00

Fix typos in Fuchsia unix_process_wait_more

2021-01-14T06:13:45+00:00

ExitStatusExt: Fix build on Fuchsia

2021-01-13T13:27:30+00:00

This is not particularly pretty but the current situation is a mess and I don't think I'm making it significantly worse. Signed-off-by: Ian Jackson

unix ExitStatus: Provide .continued()

2021-01-13T12:50:29+00:00

Signed-off-by: Ian Jackson

unix ExitStatus: Provide .stopped_signal()

2021-01-13T12:50:29+00:00

Necessary to handle WIFSTOPPED. Signed-off-by: Ian Jackson

unix ExitStatus: Provide .core_dumped

2021-01-13T12:50:29+00:00

This is essential for proper reporting of child process status on Unix. Signed-off-by: Ian Jackson

unix ExitStatus: Provide .into_raw()

2021-01-13T12:50:29+00:00

Signed-off-by: Ian Jackson

unix ExitStatus: Do not treat WIFSTOPPED as WIFSIGNALED

2021-01-13T12:50:29+00:00

A unix wait status can contain, at least, exit statuses, termination signals, and stop signals. WTERMSIG is only valid if WIFSIGNALED. https://pubs.opengroup.org/onlinepubs/9699919799/functions/wait.html It will not be easy to experience this bug with `Command`, because that doesn't pass WUNTRACED. But you could make an ExitStatus containing, say, a WIFSTOPPED, from a call to one of the libc wait functions. (In the WIFSTOPPED case, there is WSTOPSIG. But a stop signal is encoded differently to a termination signal, so WTERMSIG and WSTOPSIG are by no means the same.) Signed-off-by: Ian Jackson