From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17661 invoked by alias); 13 Jan 2011 18:27:32 -0000 Received: (qmail 17651 invoked by uid 22791); 13 Jan 2011 18:27:31 -0000 X-SWARE-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 13 Jan 2011 18:27:25 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 3671B39012; Thu, 13 Jan 2011 10:27:24 -0800 (PST) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost4.vmware.com (Postfix) with ESMTP id 2BEBDC9D42; Thu, 13 Jan 2011 10:27:24 -0800 (PST) Message-ID: <4D2F440B.6020001@vmware.com> Date: Thu, 13 Jan 2011 18:27:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.24 (X11/20101201) MIME-Version: 1.0 To: Kevin Pouget CC: Joel Brobecker , "gdb@sourceware.org" Subject: Re: Question re: testsuite, "isnative", "is_remote" etc. References: <4D2E35C5.60206@vmware.com> <20110112232003.GK2518@adacore.com> <4D2E37FB.8080300@vmware.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-01/txt/msg00042.txt.bz2 Kevin Pouget wrote: > hello, > > I'm thinking that there should be some test that checks for > "use_gdb_stub" or "gdb_protocol". But of course you have to set those in your board file too. > > just the point of view of a 'gdb beginner', but why don't you rely a bit more on the target abstraction? > maybe adding a "to_is_remote_target" in the 'struct target_ops' is too complicated, > > but what about testing if the 'remote' target has been pushed on the current target stack? That would give me exactly the result that I want. Unfortunately, this test (is-remote) is done outside of gdb, in the dejagnu test suite, and is often done before gdb even starts. So that information is not available.