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]

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

3 files changed, 3 insertions, 3 deletions

diff --git a/bin/bitbake-layers b/bin/bitbake-layers
index fb130444b..d47a6690e 100755
--- a/bin/bitbake-layers
+++ b/bin/bitbake-layers
@@ -1068,5 +1068,5 @@ if __name__ == "__main__":
     except Exception:
         ret = 1
         import traceback
-        traceback.print_exc(5)
+        traceback.print_exc()
     sys.exit(ret)
diff --git a/bin/bitbake-prserv b/bin/bitbake-prserv
index a8d7acb4c..03821446b 100755
--- a/bin/bitbake-prserv
+++ b/bin/bitbake-prserv
@@ -50,6 +50,6 @@ if __name__ == "__main__":
     except Exception:
         ret = 1
         import traceback
-        traceback.print_exc(5)
+        traceback.print_exc()
     sys.exit(ret)
 
diff --git a/bin/image-writer b/bin/image-writer
index 7d7116780..e30ab45e3 100755
--- a/bin/image-writer
+++ b/bin/image-writer
@@ -119,4 +119,4 @@ if __name__ == '__main__':
         gtk.main()
     except Exception:
         import traceback
-        traceback.print_exc(3)
+        traceback.print_exc()