user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

POSIX requires async signal safety for fork in signal handlers, not in general

Browse source
This commit is contained in:
Ralf Jung 2019-02-03 11:17:59 +01:00
parent 33ee99b26a
commit e023403da2
2 changed files with 2 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

3
src/libstd/sys/redox/ext/process.rs
View file

@ -48,8 +48,7 @@ pub trait CommandExt {
/// This also means that all resources such as file descriptors and
/// memory-mapped regions got duplicated. It is your responsibility to make
/// sure that the closure does not violate library invariants by making
/// invalid use of these duplicates. Moreover, POSIX demands that you only
/// perform operations that are explicitly documented as async-signal-safe.
/// invalid use of these duplicates.
///
/// When this closure is run, aspects such as the stdio file descriptors and
/// working directory have successfully been changed, so output to these

3
src/libstd/sys/unix/ext/process.rs
View file

@ -48,8 +48,7 @@ pub trait CommandExt {
/// This also means that all resources such as file descriptors and
/// memory-mapped regions got duplicated. It is your responsibility to make
/// sure that the closure does not violate library invariants by making
/// invalid use of these duplicates. Moreover, POSIX demands that you only
/// perform operations that are explicitly documented as async-signal-safe.
/// invalid use of these duplicates.
///
/// When this closure is run, aspects such as the stdio file descriptors and
/// working directory have successfully been changed, so output to these