about summary refs log tree commit diff
path: root/src/libsyntax/parse
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2014-03-28 11:21:47 -0700
committerbors <bors@rust-lang.org>2014-03-28 11:21:47 -0700
commitfd4f15ea6b04fcacc8c8446c5d725c25daab0624 (patch)
treec77eb7ce115419a982d6f32f692b26f080b68ee9 /src/libsyntax/parse
parentb8601a3d8b91ad3b653d143307611f2f5c75617e (diff)
parent0e190b9a4ad92645e8f63c72c66cc89a596f1971 (diff)
downloadrust-fd4f15ea6b04fcacc8c8446c5d725c25daab0624.tar.gz
rust-fd4f15ea6b04fcacc8c8446c5d725c25daab0624.zip
auto merge of #13131 : alexcrichton/rust/issue-13124, r=brson
It turns out that on linux, and possibly other platforms, child processes will
continue to accept signals until they have been *reaped*. This means that once
the child has exited, it will succeed to receive signals until waitpid() has
been invoked on it.

This is unfortunate behavior, and differs from what is seen on OSX and windows.
This commit changes the behavior of Process::signal() to be the same across
platforms, and updates the documentation of Process::kill() to note that when
signaling a foreign process it may accept signals until reaped.

Implementation-wise, this invokes waitpid() with WNOHANG before each signal to
the child to ensure that if the child has exited that we will reap it. Other
possibilities include installing a SIGCHLD signal handler, but at this time I
believe that that's too complicated.

Closes #13124
Diffstat (limited to 'src/libsyntax/parse')
0 files changed, 0 insertions, 0 deletions