From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-38524-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 19444 invoked by alias); 13 Jan 2011 19:54:49 -0000
Received: (qmail 19431 invoked by uid 22791); 13 Jan 2011 19:54:47 -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 19:54:43 +0000
Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124])	by smtp-outbound-2.vmware.com (Postfix) with ESMTP id B2A5350009;	Thu, 13 Jan 2011 11:54:41 -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 9D5D0C9DBE;	Thu, 13 Jan 2011 11:54:41 -0800 (PST)
Message-ID: <4D2F5881.4020703@vmware.com>
Date: Thu, 13 Jan 2011 19:54:00 -0000
From: Michael Snyder <msnyder@vmware.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101201)
MIME-Version: 1.0
To: Joel Brobecker <brobecker@adacore.com>
CC: Nathan Froyd <froydnj@codesourcery.com>,  "gdb@sourceware.org" <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>
In-Reply-To: <20110113193211.GO2518@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: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2011-01/txt/msg00048.txt.bz2

Joel Brobecker wrote:
>>> I used [target_info exists use_gdb_stub] last time I fixed a test like
>>> this (gdb.base/break-entry.exp).
>>
>> Yep, I've been tempted to use that too.  But I think "use_gdb_stub"
>> is still something different.  It was meant to refer to those old
>> stubs like i386-stub.c, not to gdbserver.  There used to be some
>> magic that you had to do, like this in break.c:
> 
> I looked at the documented procedure for testing with gdbserver,
> and everything is setup by the boards file.  So, it's basically
> a question of convention.
> 
> The boards file in the wiki do the following:
> 
>         set_board_info use_gdb_stub 1
> 
> So that might be the best solution, even if we might be abusing
> its original intent.
> 

Then what is the corresponding test for the testsuite?
And do we need to revise some of the existing tests?