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

Re: [Xen-devel] Debugging Xen

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Debugging Xen
From: "David Pilger" <pilger.david@xxxxxxxxx>
Date: Mon, 1 Jan 2007 11:07:54 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 01 Jan 2007 01:07:38 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=e0G4PVxLEAdswnH1eerM9gmQppS79Ipo7Kf59wHd34BAw+eGs5vQbJWpPNOz5E80BWL9vUQyTbYaiJz03zWICurtXSDITKcGXMWyh+8YRdq6gmrXPiHImjNEwTDq/WRu8qhx4FC1p6WyshWK8UOx4f19UxA4zN0CX3NKhHG7oMU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1BDA810.68FC%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <280848580612310819u77eb891au41017625fc010641@xxxxxxxxxxxxxx> <C1BDA810.68FC%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 12/31/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

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.


Isn't there a need to provide a BP mechanism that can help you PEEK
into memory, instructions, etc...?

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

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