summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/pysh
diff options
context:
space:
mode:
authorChris Laplante <chris.laplante@agilent.com>2020-08-14 16:55:56 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-08-15 11:44:20 +0100
commitb1cd7723c4d81081c6d1935be7373c7f06ae1b97 (patch)
tree1f8d1b21b4649cb74a6354458335b601112b4593 /bitbake/lib/bb/pysh
parentbd1da2aca0bc26720f438a9c1d54f5b04084da4e (diff)
downloadpoky-b1cd7723c4d81081c6d1935be7373c7f06ae1b97.tar.gz
bitbake: build: print a backtrace when a Bash shell function fails
The trick here is to use a DEBUG trap to record the line number of each command as they execute. This is so we can report the real line number of the failing command, which is otherwise not possible in a Bash EXIT trap. See http://gnu-bash.2382.n7.nabble.com/trap-echo-quot-trap-exit-on-LINENO-quot-EXIT-gt-wrong-linenumber-td3666.html (Bitbake rev: 8366e2ad5fdad3972766b40b23188908330067ee) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/pysh')
0 files changed, 0 insertions, 0 deletions