From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: debugging libxc / builders Date: Wed, 22 Jun 2005 20:59:01 -0700 Message-ID: References: Reply-To: Kip Macy Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tim Newsham Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I've had to do this a number of times. Build libxc with symbols, install and then restart xend. Attach to the python process with gdb. This has gotten a tad bit harder now that xend is multiple threads as you have figure out which to attach to. -Kip On 6/22/05, Tim Newsham wrote: > Hi, > I'm playing with the builders in libxc. I am having trouble > debugging the thing. I was wondering what options I have. >=20 > - When I run 'xm create', what process calls down to the > xc_builder stuff? Can I attach to it with gdb? > - Is there any way to spit out debug output (printf?)? Where > would it go? > - If I make changes and do a make install in tools, what do > I have to restart to put the new code into use? xend restart? >=20 > Any hints or tips appreciated. >=20 > Tim Newsham > http://www.lava.net/~newsham/ >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >