ash: don't skip exec() if std streams are invalidHEADmaster

This didn't produce the expected output when run from ash:

   ash -c "echo abc | sed s/a/x/" <&-

In general, if the last command in the pipe read from stdin the
command didn't work; if it read from file descriptor 0 (e.g. cat)
it did.

Closing a file descriptor caused the corresponding stream to
become invalid.  For performance reasons the shell in busybox-w32
runs applets without an exec(), but that results in their seeing
the invalid stream from their parent.

Avoid the problem by calling exec() in such cases.  This causes the
child process to get a new stdin stream initialised from the file
descriptor.  The test also applies to stdout and stderr.  There's
no discernable affect on performance when running the test suite.

Adds 64-96 bytes.

(GitHub issue #558)

0 files changed, 0 insertions, 0 deletions