From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13411 invoked by alias); 13 Jan 2011 19:32:19 -0000 Received: (qmail 13400 invoked by uid 22791); 13 Jan 2011 19:32:18 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 13 Jan 2011 19:32:14 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 6A0352BAC3B; Thu, 13 Jan 2011 14:32:12 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id FzLvH6MxE6jw; Thu, 13 Jan 2011 14:32:12 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 3979F2BAC36; Thu, 13 Jan 2011 14:32:12 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 6E55D1459AD; Thu, 13 Jan 2011 14:32:11 -0500 (EST) Date: Thu, 13 Jan 2011 19:32:00 -0000 From: Joel Brobecker To: Michael Snyder Cc: Nathan Froyd , "gdb@sourceware.org" Subject: Re: Question re: testsuite, "isnative", "is_remote" etc. Message-ID: <20110113193211.GO2518@adacore.com> References: <4D2E35C5.60206@vmware.com> <20110113184025.GO6247@codesourcery.com> <4D2F4CA9.1010105@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D2F4CA9.1010105@vmware.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00047.txt.bz2 > >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. -- Joel