WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] State of gdbsx in xen-4.0-testing.hg and debugger docum

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] State of gdbsx in xen-4.0-testing.hg and debugger documentation.
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Tue, 6 Jul 2010 16:40:56 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Tue, 06 Jul 2010 16:41:48 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=7A9Xa3aqVI1IJDLIFZIDSFCekTs7GHG53OwOqi+qT2g=; b=qWYq9dzwdbDpsfWIE3IYXEbfjfx7278mIvQmImQSToNy9Jh06cSuGn96Noa1SoQrNj Wpf64Zzavcv1KGPw7WUbG8aeN2JM+JnrpD3Mbj4dUyqF5bWS59+7Jszq9IpdTvkpTEL+ y9N00oih3xv/dLYEIk/xknaekUsB81tnakV9I=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=UrK5UPnkRrhQCIeI7m84pdF3xYq4UxQNwBU3zO5vGNlpXsUTopelbGF1ZZrEWzQUqn oGA4NsIn8pyONCXGt6Z9xTlVNlODdFB2xQQ75IdLBybjWjey2jS1BgdluUdSRmHDcbUk nPwPTGNan6eHQLeHoGW+7RN4HhTc6tyH5l76M=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19507.6707.47260.44850@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTilqNc_oQ0JmUYUBHLBmNOZ-K8VklsEOEDAHvGlt@xxxxxxxxxxxxxx> <C8534197.19427%keir.fraser@xxxxxxxxxxxxx> <AANLkTimwMvuetvx6LyBvqqWkF-omqjwEvGqmvkKF6OGF@xxxxxxxxxxxxxx> <19502.6544.743563.733900@xxxxxxxxxxxxxxxxxxxxxxxx> <AANLkTilwUZcleliBYV75HLpUth_eHfbYIoLbFFKneLOI@xxxxxxxxxxxxxx> <19507.6707.47260.44850@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Jul 6, 2010 at 4:57 AM, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
Bruce Edge writes ("Re: [Xen-devel] State of gdbsx in xen-4.0-testing.hg and debugger  documentation."):
> Here is a patch to enable gdbsx by default.

Thanks.  Is it against 4.0-testing as it seems to be ?  I think we
probably want this against xen-unstable, against which your patch
doesn't apply.

Ian, here's an unstable patch:

diff -Naur xen-unstable.hg-2010-07-06/tools/Makefile xen-unstable.hg/tools/Makefile
--- xen-unstable.hg-2010-07-06/tools/Makefile   2010-07-06 14:40:54.000000000 -0700
+++ xen-unstable.hg/tools/Makefile      2010-07-06 16:15:15.000000000 -0700
@@ -35,6 +35,7 @@
 SUBDIRS-y += libxl
 SUBDIRS-y += remus
 SUBDIRS-$(CONFIG_X86) += xenpaging
+SUBDIRS-y += debugger/gdbsx
 
 # These don't cross-compile
 ifeq ($(XEN_COMPILE_ARCH),$(XEN_TARGET_ARCH))
@@ -114,3 +115,9 @@
                $(buildmakevars2shellvars); \
                $(MAKE) -C ioemu-dir clean; \
        fi
+
+subdir-clean-debugger/gdbsx:
+       $(MAKE) -C debugger/gdbsx clean
+
+subdir-install-debugger/gdbsx:
+       $(MAKE) -C debugger/gdbsx install

-------------cut----------------
 
Thanks

-Bruce


> I suppose it would be cleaner to eliminate the debugger dir as gdbsx is the
> only one under there that's used and that would enable the tools/Rules.mk
> templates to cover the
>     subdir-clean-gdbsx:
>     subdir-install-gdbsx
> targets and not require them to be explicit in tools/Makefile

Well, yes, until we got another debugger again.

> Also, I don't know if
>     SUBDIRS-y += debugger/gdbsx
> should be conditional on any type of target, CONFIG_X86 or?

I'm happy to enable it and get the people who find it breaks to
tell us what conditions mean it needs to be disabled :-).

Ian.

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