Re: [Xen-devel] Debugging Xen

To:	David Pilger <pilger.david@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] Debugging Xen
From:	Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date:	Sun, 31 Dec 2006 17:46:56 +0000
Delivery-date:	Sun, 31 Dec 2006 09:46:18 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<280848580612310819u77eb891au41017625fc010641@xxxxxxxxxxxxxx>
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
Thread-index:	AcctA6nI6CpNOJj2EduBDQANk04WTA==
Thread-topic:	[Xen-devel] Debugging Xen
User-agent:	Microsoft-Entourage/11.3.2.061213

On 31/12/06 4:19 pm, "David Pilger" <pilger.david@xxxxxxxxx> wrote:

> How do you debug xen itself?
> For instance, if you want to debug a certain VMEXIT.

It depends exactly what kind of debugging you want to do. If it's a Xen
crash you might use the gdb serial stub built into Xen, or just add some
printk tracing and reproduce the bug to get more info.

 -- Keir

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