From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28713 invoked by alias); 20 Jan 2012 19:45:54 -0000 Received: (qmail 28705 invoked by uid 22791); 20 Jan 2012 19:45:53 -0000 X-SWARE-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 20 Jan 2012 19:45:37 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q0KJjXqd022106 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 20 Jan 2012 14:45:33 -0500 Received: from host2.jankratochvil.net (ovpn-116-21.ams2.redhat.com [10.36.116.21]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q0KJjTts010663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 20 Jan 2012 14:45:32 -0500 Date: Fri, 20 Jan 2012 19:51:00 -0000 From: Jan Kratochvil To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: testsuite: native/non-extended/extended modes [Re: [PATCH] PR threads/10729: x86 hw watchpoints and non-stop mode] Message-ID: <20120120194529.GA856@host2.jankratochvil.net> References: <201112051601.59664.pedro@codesourcery.com> <201112131801.20730.pedro@codesourcery.com> <20111213191858.GA30724@host2.jankratochvil.net> <201112161516.56808.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201112161516.56808.pedro@codesourcery.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes 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 X-SW-Source: 2012-01/txt/msg00740.txt.bz2 On Fri, 16 Dec 2011 16:16:56 +0100, Pedro Alves wrote: > Currently, because there's no extended-remote board, the only way to > be a bit certain that we aren't making extended-remote "attach"/"run" > support in gdbserver a brick is the gdb.server/ tests. Let's take a > look at what we're talking about: > > $ ls gdb.server/*.exp > gdb.server/ext-attach.exp > gdb.server/ext-run.exp > gdb.server/file-transfer.exp > gdb.server/server-mon.exp > gdb.server/server-run.exp > > That's it. Once we have a board that tests the whole testsuite in > extended-remote mote, the ext-*.exp tests become useless and > redundant, and so all uses of gdbserver_start_extended can be eliminated > -- we have plenty of regular tests that "run" and "attach". Meanwhile, > we don't such a board, so we live with the exception that the > tests force gdbserver, and extended-remote. This is what I mean > by revisiting later. (I don't see a point in adding a board variable > for "supports extended-remote" at this point.) As I have another testcase in archer-jankratochvil-watchpoint3 gdb.multi/watchpoint-multi.exp needing extended gdbserver and you are already working on extended-remote board could you restate what is the recommended way how to create a testcase which: * supports native mode * does not support non-extended-remote * supports extended-remote ? Thanks, Jan