Tcl Source Code

View Ticket
Login
Ticket UUID: 204ac7df2468599bf8c82fa82a147b79a35ef1d2
Title: Incorrect handling of redirection in process piping
Type: Bug Created on: 2019-04-30 18:37:12
Submitter: euller Assigned to: nobody
Subsystem: 45. Parsing and Eval Severity: Minor
Priority: 5 Medium Last modified: 2019-04-30 18:37:12
Status: Open Closed by: nobody
Resolution: None Closed on:
Version: 8.6.9
Description:
Tcl behaves erratically when stdout and stderr are redirected in intermediate pipe stages of an exec call.

Suppose a program called "print_stderr" that prints "COUT" to stdout and "CERR" to stderr. The following works properly:
 % echo "BLA" 1>ble | ./print_stderr
 STDOUT
 STDERR
 % cat ble
 BLA

But when we remove the "1" from the redirection, this is what we get:
 % echo "BLA" >ble | ./print_stderr
 %cat ble
 STDOUT
 STDERR

The problem also happens when redirecting stderr:
 % echo "BLA" 2>ble | ./print_stderr
 STDOUT
 % cat ble
 STDERR

Notice how the redirection happens for the whole command and not only for echo.

There's a specific problem with ">file" since it redirects both stderr and stdout when it should only redirect stdout (and only for echo in the example!), according to documentation:
    > fileName
      Standard output from the last command is redirected to the file named fileName, overwriting its previous contents.

The behaviour for stderr is unexpected but maybe understandable since the documentation states:
    2> fileName
      Standard error from all commands in the pipeline is redirected to the file named fileName, overwriting its previous contents.
Still, this should only be valid in the last stage of the pipeline, in my opinion.
Consider, for example, the following scenario:
  % echo "BLA" >ble | ./print_stderr >bli
  % cat ble
  % cat bli
  STDOUT
  STDERR

All these behaviours are very different from their shell counterparts, meaning we don't get the same expressiveness we'd get from actually running a shell command.