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/
Home Products Support Community News


[Xen-devel] Tips for debugging Xend?

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Tips for debugging Xend?
From: Randy Thelen <rthelen@xxxxxxxxxx>
Date: Tue, 25 Apr 2006 17:11:49 -0700
Delivery-date: Tue, 25 Apr 2006 17:12:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
Folks --

I'm walking through Xend and am having trouble figuring out where new commands that come in from xm via the UnixHttp interface are actually parsed and run. There are sort of three ways to tackle this.

First: Is there any documentation that explains the inner workings of xend?

Second: Is there an obvious way to convert SrvDaemon.start() to not fork so that I can run Xend on top of pdb?

Third: Is there a Python debugger that allows me to connect to a running application?

Any pointers to do any of the above would be welcome.

-- Randy

Xen-devel mailing list

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