From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wei Huang <huangwei@gmail.com>
Subject: Debugging Xen and Dom0
Date: Fri, 24 Jun 2005 15:27:14 -0500
Message-ID: <60b16eff0506241327ddb6e49@mail.gmail.com>
Reply-To: Wei Huang <huangwei@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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