From 31681346a70d03e94ba35344ce12205b5269f451 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Thu, 31 Mar 2016 12:47:13 +0100 Subject: 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 --- bitbake/bin/image-writer | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'bitbake/bin/image-writer') diff --git a/bitbake/bin/image-writer b/bitbake/bin/image-writer index 7d7116780b..e30ab45e31 100755 --- a/bitbake/bin/image-writer +++ b/bitbake/bin/image-writer @@ -119,4 +119,4 @@ if __name__ == '__main__': gtk.main() except Exception: import traceback - traceback.print_exc(3) + traceback.print_exc() -- cgit v1.2.3-54-g00ecf