 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] debugging libxc / builders
| To: | Tim Newsham <newsham@xxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] debugging libxc / builders |
| From: | Kip Macy <kip.macy@xxxxxxxxx> |
| Date: | Wed, 22 Jun 2005 20:59:01 -0700 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx |
| Delivery-date: | Thu, 23 Jun 2005 03:58:00 +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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MR1rpZ/838jT+YRo8S7UTu/mg/JWYffoB0L+cXHdFjf/iAjxMNQm0hfqiNfatBxfcS9fNoCLCAZ0qMtEP+ufLgROaev3xiWF1VdYF0cONzLZOumHKpgEDb6YFUiFd3Xi9B1wf2bLw7q8Z0e367pXzPRNFI3o2Tz9PQQa4FxyLVk= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <Pine.BSI.4.61.0506221746100.5014@xxxxxxxxxxxxxxxxx> |
| 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: | <Pine.BSI.4.61.0506221746100.5014@xxxxxxxxxxxxxxxxx> |
| Reply-to: | Kip Macy <kip.macy@xxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
I've had to do this a number of times. Build libxc with symbols,
install and then restart xend. Attach to the python process with gdb.
This has gotten a tad bit harder now that xend is multiple threads as
you have figure out which to attach to.
-Kip
On 6/22/05, Tim Newsham <newsham@xxxxxxxx> wrote:
> Hi,
> I'm playing with the builders in libxc. I am having trouble
> debugging the thing. I was wondering what options I have.
>
> - When I run 'xm create', what process calls down to the
> xc_builder stuff? Can I attach to it with gdb?
> - Is there any way to spit out debug output (printf?)? Where
> would it go?
> - If I make changes and do a make install in tools, what do
> I have to restart to put the new code into use? xend restart?
>
> Any hints or tips appreciated.
>
> Tim Newsham
> http://www.lava.net/~newsham/
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH] fix broken ACM, aq |
|---|---|
| Next by Date: | [Xen-devel] [PATCH] libxc hardening, Anthony Liguori |
| Previous by Thread: | Re: [Xen-devel] debugging libxc / builders, Anthony Liguori |
| Next by Thread: | Re: [Xen-devel] debugging libxc / builders, Ronald G. Minnich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
