* David Pilger <pilger.david@xxxxxxxxx> [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@xxxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel