From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: State of gdbsx in xen-4.0-testing.hg and debugger documentation. Date: Fri, 2 Jul 2010 07:11:19 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Bruce Edge , Mukesh Rathor Cc: "xen-devel@lists.xensource.com" , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 02/07/2010 00:51, "Bruce Edge" wrote: > Is there any reason to not build gdbsx by default? >=20 > IOW does it affect performance? There's no reason not to build it always. We could get rid of the build-tim= e option. -- Keir > -Bruce >=20 >=20 > On Thu, Jul 1, 2010 at 1:13 PM, Mukesh Rathor > wrote: >> Thanks for CC Konrad, I'm gazillions postings behind in catching up >> xen-devel. >>=20 >> Bruce, you don't need to use the ext repo anymore as gdbsx is now >> merged mainline. I should update the blog post. >>=20 >> To build a debug enabled xen image: make gdbsx=3Dy =A0is all you need >> to do. After booting with gdbsx enabled xen, you can run gdbsx in >> dom0. See tools/debugger/gdbsx/README. >>=20 >> Note, you don't need to do anything in tools/debugger/gdb and/or >> gdbbuild. =A0tools/debugger/gdb (gdbbuild) is unlreated to gdbsx. >>=20 >> Perhaps, we should just remove tools/debugger/gdb if it's not being >> maintained and no one is using it. >>=20 >> thanks, >> Mukesh >>=20 >>=20 >>=20 >> On Thu, 1 Jul 2010 10:53:31 -0400 >> Konrad Rzeszutek Wilk wrote: >>=20 >>> On Wed, Jun 30, 2010 at 10:16:10PM -0700, Bruce Edge wrote: >>>> Can one build a usable gdbsx from xen-4.0-testing.hg? >>>=20 >>> CC-ing the author - Mukesh. >>>>=20 >>>> Actually a more relevant is, is this still the preferred mechanism >>>> for domU kernel debugging? >>>>=20 >>>> The documentation on building it is a bit out of date and >>>> conflicting. >>>>=20 >>>> This post http://blog.xen.org/index.php/2009/10/21/debugging-on-xen/ >>>> States that one needs to use this repo: >>>> http://xenbits.xensource.com/ext/debuggers.hg >>>>=20 >>>> Which looks like hasn't been updated since 4.0 was released as it's >>>> still referencing 4.0-rc >>>>=20 >>>> 0 %> hg clone http://xenbits.xensource.com/ext/debuggers.hg >>>>=20 >>>> destination directory: debuggers.hg >>>> requesting all changes >>>> adding changesets >>>> adding manifests >>>> adding file changes >>>> added 20375 changesets with 117688 changes to 11049 files (+1 heads) >>>> updating working directory >>>> .hgtags@809b20f066fb, line 39: tag '4.0.0-rc1' refers to unknown >>>> node .hgtags@809b20f066fb, line 40: tag '4.0.0-rc2' refers to >>>> unknown node .hgtags@809b20f066fb, line 41: tag '4.0.0-rc3' refers >>>> to unknown node .hgtags@809b20f066fb, line 42: tag '4.0.0-rc4' >>>> refers to unknown node .hgtags@809b20f066fb, line 43: tag >>>> '4.0.0-rc5' refers to unknown node .hgtags@809b20f066fb, line 44: >>>> tag '4.0.0-rc6' refers to unknown node 3164 files updated, 0 files >>>> merged, 0 files removed, 0 files unresolved >>>>=20 >>>> This post: http://zhigang.org/wiki/XenDebugging#xend-debugging >>>> refers to magically generated Oracle images with no information on >>>> how they were created or what sources to use. >>>>=20 >>>> Other posts state that gdbsx has been integrated into >>>> xen-unstable.hg. Does that mean all that's needed to build a debug >>>> enabled xen image is: >>>>=20 >>>> (cd tools/debugger/gdb && ./gdbbuild ) ; >>>> make kdb=3Dy gdbsx=3Dy && make dist >>>>=20 >>>> Thanks >>>>=20 >>>> -Bruce >>>=20 >>>> _______________________________________________ >>>> Xen-devel mailing list >>>> Xen-devel@lists.xensource.com >>>> http://lists.xensource.com/xen-devel >>=20 >=20 >=20