From: Ryan Harper <ryanh@us.ibm.com>
To: David Pilger <pilger.david@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: libxc printfs and debugging
Date: Wed, 7 Mar 2007 10:29:43 -0600 [thread overview]
Message-ID: <20070307162943.GP6768@us.ibm.com> (raw)
In-Reply-To: <280848580703070816j53f9faa8p4633f659ad61a579@mail.gmail.com>
* David Pilger <pilger.david@gmail.com> [2007-03-07 10:20]:
> Hi,
>
> Where does all the IPRINTF output goes in libxc?
> I can't find it (the INFO constant is 1 of course)...
I'm not sure about the IPRINTF, but if you build the tools with debug=y
passed to the make command, the DPRINTFs go to
/var/lib/xen/xend-debug.log
>
> How do you debug libxc code btw?
>
I found uncommenting the following in tools/libxc/Makefile , and
rebuilding (cd tools; make debug=y ) very useful when debugging as it
let me attach with gdb to the xend python process and define break
points in the libxc code.
# Define this to make it possible to run valgrind on code linked with
# these
# libraries.
CFLAGS += -DVALGRIND -O0 -ggdb3
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
prev parent reply other threads:[~2007-03-07 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 16:16 libxc printfs and debugging David Pilger
2007-03-07 16:29 ` Ryan Harper [this message]
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=20070307162943.GP6768@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=pilger.david@gmail.com \
--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.