summaryrefslogtreecommitdiffstats
path: root/bitbake/bin/bitbake-prserv
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2016-03-31 12:47:13 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-03-31 23:01:38 +0100
commit31681346a70d03e94ba35344ce12205b5269f451 (patch)
tree307de247d9b1f53bc20bc860ce09f2fcbf3149be /bitbake/bin/bitbake-prserv
parent88ea0b9613be73605dcbfb1666cde9b927d9e8b5 (diff)
downloadpoky-31681346a70d03e94ba35344ce12205b5269f451.tar.gz
bitbake: bitbake: Don't limit traceback lengths to arbitrary values
There appears to have been a lot of copy and pasting of the code which prints tracebacks upon failure and limits the stack trace to 5 entries. This obscures the real error and is very confusing to the user it look me an age to work out why some tracebacks weren't useful. This patch removes the limit, making tracebacks much more useful for debugging. [YOCTO #9230] (Bitbake rev: 5549748a200b5df259fc7352477ec59471b87b2f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/bin/bitbake-prserv')
-rwxr-xr-xbitbake/bin/bitbake-prserv2
1 files changed, 1 insertions, 1 deletions
diff --git a/bitbake/bin/bitbake-prserv b/bitbake/bin/bitbake-prserv
index a8d7acb4c2..03821446b7 100755
--- a/bitbake/bin/bitbake-prserv
+++ b/bitbake/bin/bitbake-prserv
@@ -50,6 +50,6 @@ if __name__ == "__main__":
50 except Exception: 50 except Exception:
51 ret = 1 51 ret = 1
52 import traceback 52 import traceback
53 traceback.print_exc(5) 53 traceback.print_exc()
54 sys.exit(ret) 54 sys.exit(ret)
55 55