From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9351 invoked by alias); 13 Jan 2011 20:59:25 -0000 Received: (qmail 9263 invoked by uid 22791); 13 Jan 2011 20:59:25 -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-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 13 Jan 2011 20:59:20 +0000 Received: from mailhost3.vmware.com (mailhost3.vmware.com [10.16.27.45]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 5EBFA4D00C; Thu, 13 Jan 2011 12:59:18 -0800 (PST) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost3.vmware.com (Postfix) with ESMTP id 356C8CD99D; Thu, 13 Jan 2011 12:59:18 -0800 (PST) Message-ID: <4D2F67A5.20000@vmware.com> Date: Thu, 13 Jan 2011 20:59:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.24 (X11/20101201) MIME-Version: 1.0 To: Joel Brobecker CC: Nathan Froyd , "gdb@sourceware.org" Subject: Re: Question re: testsuite, "isnative", "is_remote" etc. References: <4D2E35C5.60206@vmware.com> <20110113184025.GO6247@codesourcery.com> <4D2F4CA9.1010105@vmware.com> <20110113193211.GO2518@adacore.com> <4D2F5881.4020703@vmware.com> <20110113205311.GP2518@adacore.com> In-Reply-To: <20110113205311.GP2518@adacore.com> 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/msg00050.txt.bz2 Joel Brobecker wrote: >> Then what is the corresponding test for the testsuite? >> And do we need to revise some of the existing tests? > > I think what Nathan suggested was fine. I'm not an expert, though. > The thing is, the situation is the same as now. We either have to put "isremote" in our board file (as now), or replace it by putting "use_gdb_stub" in our board file. A lot of changed tests for, as I see it, no benefit.