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

Re: [Xen-devel] Debugging Xen

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
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=
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

Follow-Ups:
- Re: [Xen-devel] Debugging Xen
  - From: Christoph Egger

Prev by Date: [Xen-devel] [PATCH]Allow the kernel to poll in the idle loop
Next by Date: Re: [Xen-devel] Timeline for migrating to newer Linux kernels?
Previous by thread: [Xen-devel] [PATCH]Allow the kernel to poll in the idle loop
Next by thread: Re: [Xen-devel] Debugging Xen
Index(es):
- Date
- Thread

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