Capture both stdout and stderr in Bash [duplicate]

by

There’s a really ugly way to capture stderr and stdout in two separate variables without temporary files (if you like plumbing), using process substitution, source, and declare appropriately. I’ll call your command banana. You can mimic such a command with a function:

banana() {
    echo "banana to stdout"
    echo >&2 "banana to stderr"
}

I’ll assume you want standard output of banana in variable bout and standard error of banana in variable berr. Here’s the magic that’ll achieve that (Bash≥4 only):

. <({ berr=$({ bout=$(banana); } 2>&1; declare -p bout >&2); declare -p berr; } 2>&1)

So, what’s happening here?

Let’s start from the innermost term:

bout=$(banana)

This is just the standard way to assign to bout the standard output of banana, the standard error being displayed on your terminal.

Then:

{ bout=$(banana); } 2>&1

will still assign to bout the stdout of banana, but the stderr of banana is displayed on terminal via stdout (thanks to the redirection 2>&1.

Then:

{ bout=$(banana); } 2>&1; declare -p bout >&2

will do as above, but will also display on the terminal (via stderr) the content of bout with the declare builtin: this will be reused soon.

Then:

berr=$({ bout=$(banana); } 2>&1; declare -p bout >&2); declare -p berr

will assign to berr the stderr of banana and display the content of berr with declare.

At this point, you’ll have on your terminal screen:

declare -- bout="banana to stdout"
declare -- berr="banana to stderr"

with the line

declare -- bout="banana to stdout"

being displayed via stderr.

A final redirection:

{ berr=$({ bout=$(banana); } 2>&1; declare -p bout >&2); declare -p berr; } 2>&1

will have the previous displayed via stdout.

Finally, we use a process substitution to source the content of these lines.

You mentioned the return code of the command too. Change banana to:

banana() {
    echo "banana to stdout"
    echo >&2 "banana to stderr"
    return 42
}

We’ll also have the return code of banana in the variable bret like so:

. <({ berr=$({ bout=$(banana); bret=$?; } 2>&1; declare -p bout bret >&2); declare -p berr; } 2>&1)

You can do without sourcing and a process substitution by using eval too (and it works with Bash<4 too):

eval "$({ berr=$({ bout=$(banana); bret=$?; } 2>&1; declare -p bout bret >&2); declare -p berr; } 2>&1)"

And all this is safe, because the only stuff we’re sourceing or evaling are obtained from declare -p and will always be properly escaped.

Of course, if you want the output in an array (e.g., with mapfile, if you’re using Bash≥4—otherwise replace mapfile with a while–read loop), the adaptation is straightforward.

For example:

banana() {
    printf 'banana to stdout %d\n' {1..10}
    echo >&2 'banana to stderr'
    return 42
}

. <({ berr=$({ mapfile -t bout < <(banana); } 2>&1; declare -p bout >&2); declare -p berr; } 2>&1)

and with return code:

. <({ berr=$({ mapfile -t bout< <(banana; bret=$?; declare -p bret >&3); } 3>&2 2>&1; declare -p bout >&2); declare -p berr; } 2>&1)

More Related Contents:

  1. How can I pipe stderr, and not stdout?
  2. How to redirect and append both standard output and standard error to a file with Bash
  3. Redirect stderr and stdout in Bash [duplicate]
  4. Bash script – store stderr in a variable [duplicate]
  5. How to redirect both stdout and stderr to a file [duplicate]
  6. Shell redirection i/o order
  7. Piping both stdout and stderr in bash?
  8. How to pipe stdout while keeping it on screen ? (and not to a output file)
  9. Pipe output and capture exit status in Bash
  10. How to store standard error in a variable
  11. How to trick an application into thinking its stdout is a terminal, not a pipe
  12. What is a simple explanation for how pipes work in Bash?
  13. How to pipe input to a Bash while loop and preserve variables after loop ends
  14. How can I detect if my shell script is running through a pipe?
  15. Bash variable scope
  16. Bash how do you capture stderr to a variable? [duplicate]
  17. Why piping input to “read” only works when fed into “while read …” construct? [duplicate]
  18. Piping and Redirection
  19. How to pipe multiple commands into a single command in the shell? (sh, bash, …)
  20. Pipe, standard input and command line arguments in Bash
  21. How to store the output of a command in a variable at the same time as printing the output?
  22. How do file descriptors work?
  23. pipe stdout and stderr to two different processes in shell script?
  24. Pipe output to two different commands [duplicate]
  25. Get exit code from subshell through the pipes
  26. bash piping prevents global variable assignment
  27. How to detect if a Node.js script is running through a shell pipe?
  28. What’s the difference between “here string” and echo + pipe
  29. Left side of pipe is the subshell?
  30. How to redirect a program that writes to tty?

Leave a Comment