capture fork child stderr & include in call to FAILED-CHANGE

This mirrors what we do with stderr from remote Lisp images.

Before this change, when a remote Lisp image forks, the child's stderr is sent
to the parent's stderr.  But if the parent exits successfully its stderr is
discarded (see the :SBCL connection).  So if the child failed but the
FAILED-CHANGE was handled, perhaps because the fork occurs within SEQPROPS,
the user has no way to get at the child's error output.  After this change,
the error output should be printed to stdout by WITH-SKIP-FAILED-CHANGES.

Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>

0 files changed, 0 insertions, 0 deletions