BASH_COMMAND is incorrect when working with subshells and error traps

[Mike Frysinger]

consider this simple code:

$ cat test.sh
#!/bin/bash
trap 'echo $BASH_COMMAND; exit 1' ERR
set -e
true
(false)
true

when run, we see:
$ ./test.sh
true 1

this can be confusing when utilized with automatic backtraces :(

even when using errtrace and debugtrace, BASH_COMMAND is incorrect
-mike

signature.asc
Description: This is a digitally signed message part.