WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] BUG() shortcomings

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] BUG() shortcomings
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Tue, 07 Nov 2006 10:15:36 +0000
Delivery-date: Tue, 07 Nov 2006 02:15:07 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Having run into BUG()s a number of times recently, I realized that other than
on Linux under Xen the register state dumped in this case is mostly unrelated
to the actual registers that were in effect when the macro was invoked. This
is rather unfortunate, as without the register state it usually requires being
able to reproduce the problem after having added extra debug code. Would
it therefore be acceptable to make BUG() work more Linux-like?

Thanks, Jan

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

<Prev in Thread] Current Thread [Next in Thread>