From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7708 invoked by alias); 9 Aug 2013 15:03:23 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 7613 invoked by uid 89); 9 Aug 2013 15:03:22 -0000 X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 Received: from Unknown (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 09 Aug 2013 15:03:21 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r79EU0N8009443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Aug 2013 10:30:00 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r79ETxik026526; Fri, 9 Aug 2013 10:29:59 -0400 Message-ID: <5204FCE6.60203@redhat.com> Date: Fri, 09 Aug 2013 15:03:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Eli Zaretskii CC: Pierre Muller , gdb-patches@sourceware.org Subject: Re: [RFC] Add new commands to windows native code. References: <"001f01ce9413$72450b20$56cf2160$@muller"@ics-cnrs.unistra.fr> <83d2pnrmbn.fsf@gnu.org> In-Reply-To: <83d2pnrmbn.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-08/txt/msg00268.txt.bz2 I'd be good to keep GDBserver in the loop too. We're trying to bridge the gap between GDB and GDBserver afterall, and new features in the native target that don't end up in GDBserver now just means more work later on. IOW, it'd be very good to keep the RSP and GDBserver in mind when designing the implementation for such a feature (whatever it ends up looking like). -- Pedro Alves