[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH][XEND] Fix yet another information-destroying backtrace in Xend



Every time you call traceback.print_exc() from an exception handler, you
throw away all the traceback information you've accumulated to get to
that spot. I'm not going to do a global find/replace without testing,
but I know the below patch works and is needed.


Fix yet another information-destroying backtrace in Xend.
Signed-off-by: Hollis Blanchard <hollisb@xxxxxxxxxx>

diff -r 343c37f11a8b tools/python/xen/xend/server/SrvDaemon.py
--- a/tools/python/xen/xend/server/SrvDaemon.py Tue Sep 05 14:44:20 2006 -0500
+++ b/tools/python/xen/xend/server/SrvDaemon.py Tue Sep 05 16:12:25 2006 -0500
@@ -293,7 +293,7 @@ class Daemon:
         except Exception, ex:
             print >>sys.stderr, 'Exception starting xend:', ex
             if XEND_DEBUG:
-                traceback.print_exc()
+                raise
             log.exception("Exception starting xend (%s)" % ex)
             if status:
                 status.write('1')



-- 
Hollis Blanchard
IBM Linux Technology Center


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.