All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kip.macy@gmail.com>
To: Tim Newsham <newsham@lava.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: debugging libxc / builders
Date: Wed, 22 Jun 2005 20:59:01 -0700	[thread overview]
Message-ID: <b1fa2917050622205916d7ebe0@mail.gmail.com> (raw)
In-Reply-To: <Pine.BSI.4.61.0506221746100.5014@malasada.lava.net>

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@lava.net> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  parent reply	other threads:[~2005-06-23  3:59 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
2005-06-23  3:59 ` Kip Macy [this message]
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=b1fa2917050622205916d7ebe0@mail.gmail.com \
    --to=kip.macy@gmail.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.