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

[Xen-devel] Debugging Xen and Dom0


  • To: Xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Wei Huang <huangwei@xxxxxxxxx>
  • Date: Fri, 24 Jun 2005 15:27:14 -0500
  • Delivery-date: Fri, 24 Jun 2005 20:26:13 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=cvbj8ykj84X1O6aCEfDcZBjSke+HSK52/v1+LgRe13ZireCHtibIc2oqeXSTvx7p2RHifSmmdyveqm7mEcYVVjHXXyarWIkUpwNIljFrWjfhU7F+xFb+7iHYOoPUvTsMw9edy6Kfq1YTj31wMTtZyMRsgWD9DmdeTf4tOGa67Ag=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,
    I looked into the source code of Xen. It seems CDB (and printk())
is one of the choices to debug Xen and Dom0. However, the capability
of current CDB implementation seems to be limited. For instance, it
does not support Write Registers/Single Step, etc.
   Could anyone tell me what is the most effective way to debug Dom0?
printk()? Thanks a lot.

-Wei

_______________________________________________
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®.