[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] libxc printfs and debugging


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "David Pilger" <pilger.david@xxxxxxxxx>
  • Date: Wed, 7 Mar 2007 18:16:22 +0200
  • Delivery-date: Wed, 07 Mar 2007 08:15:26 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=m0e4ke8Du+5ynYxSpwHvw07CW6bGpNOJteOnpQXcWMt8lx0lxmwuOG0vtOgrrmbtGpeYi1KIM6Y8SAeqF/m1c9zXw2bf3MSJaai1bRX5QUoEg1BwNQPlS5JokXBgVXFTSgm6l1hBhYIndb4uVbDB8anSqXR6lUyP8i2CeQL9XWA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.