All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Tim Newsham <newsham@lava.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: debugging libxc / builders
Date: Wed, 22 Jun 2005 22:55:43 -0500	[thread overview]
Message-ID: <42BA32BF.8030105@us.ibm.com> (raw)
In-Reply-To: <Pine.BSI.4.61.0506221746100.5014@malasada.lava.net>

Tim Newsham 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?

Xend (the daemon) actually calls the xc_XXX_build function.  The C 
invocation occurs in the xc bindings.  I'm not aware of an easy way to 
attach to bindings with gdb (although I presume it's possible).

> Any hints or tips appreciated.

It would probably be significantly easier to debug builder issues with 
VM-Tools.  There's a single executable (vm-build.linux for instance) 
that only does building and can be stepped through with gdb.

Of course, you could also write your own really simple app with libxc 
that just did a few calls to create and build the domain.  You don't 
need any of the control channel stuff until the domain starts to 
actually boot.

I can give you a more detailed example if you need.

Regards,

Anthony Liguori

> Tim Newsham
> http://www.lava.net/~newsham/
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  reply	other threads:[~2005-06-23  3:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23  3:48 debugging libxc / builders Tim Newsham
2005-06-23  3:55 ` Anthony Liguori [this message]
2005-06-23  3:59 ` Kip Macy
2005-06-23  4:35 ` Ronald G. Minnich
2005-06-23 16:45 ` Mark Williamson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42BA32BF.8030105@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=newsham@lava.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.