* libxc printfs and debugging
@ 2007-03-07 16:16 David Pilger
2007-03-07 16:29 ` Ryan Harper
0 siblings, 1 reply; 2+ messages in thread
From: David Pilger @ 2007-03-07 16:16 UTC (permalink / raw)
To: xen-devel
Hi,
Where does all the IPRINTF output goes in libxc?
I can't find it (the INFO constant is 1 of course)...
How do you debug libxc code btw?
Thanks,
David.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: libxc printfs and debugging
2007-03-07 16:16 libxc printfs and debugging David Pilger
@ 2007-03-07 16:29 ` Ryan Harper
0 siblings, 0 replies; 2+ messages in thread
From: Ryan Harper @ 2007-03-07 16:29 UTC (permalink / raw)
To: David Pilger; +Cc: xen-devel
* 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-03-07 16:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-07 16:16 libxc printfs and debugging David Pilger
2007-03-07 16:29 ` Ryan Harper
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.