Skip to contentSkip to conversation

utils.py: Once we've printed errors messages, suppress the backtrace

PATCH New Richard Purdie 1 participant 1 message Aug 22, 2012

lore
Share & tools
lore

Richard Purdie

author
#0 lore raw

PATCH 1/1 utils.py: Once we've printed errors messages, suppress the backtrace

Adding a generic backtrace to better_compile and better_exec is pointless, therefore reraise the exception as a bb.BBHandledException so the generic code doesn't confuse the user even more.

Signed-off-by Richard Purdie <[email protected]>

---

bitbake/lib/bb/utils.py +5 -3
index e0ef63c..82dab6b 100644
@@ -216,7 +216,8 @@ def better_compile(text, file, realfile, mode = "exec"):
             for line in body:
                 logger.error(line)
 
-        raise
+        e = bb.BBHandledException(e)
+        raise e
 
 def better_exec(code, context, text = None, realfile = "<code>"):
     """

@@ -231,7 +232,7 @@ def better_exec(code, context, text = None, realfile = "<code>"):
         code = better_compile(code, realfile, realfile)
     try:
         exec(code, _context, context)
-    except Exception:
+    except Exception as e:
         (t, value, tb) = sys.exc_info()
 
         if t in [bb.parse.SkipPackage, bb.build.FuncFailed]:

@@ -280,7 +281,8 @@ def better_exec(code, context, text = None, realfile = "<code>"):
             nexttb = tb.tb_next
             level = level + 1
 
-        raise
+        e = bb.BBHandledException(e)
+        raise e
 
 def simple_exec(code, context):
     exec(code, _context, context)