From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ryan Harper <ryanh@us.ibm.com>
Subject: Re: libxc printfs and debugging
Date: Wed, 7 Mar 2007 10:29:43 -0600
Message-ID: <20070307162943.GP6768@us.ibm.com>
References: <280848580703070816j53f9faa8p4633f659ad61a579@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <280848580703070816j53f9faa8p4633f659ad61a579@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: David Pilger <pilger.david@gmail.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

* 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