From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-46678-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 35548 invoked by alias); 26 Oct 2018 19:22:02 -0000
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
Received: (qmail 35507 invoked by uid 89); 26 Oct 2018 19:22:00 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:1014, expectations, H*r:0700, channel
X-HELO: relay1.mentorg.com
Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 26 Oct 2018 19:21:59 +0000
Received: from svr-orw-mbx-03.mgc.mentorg.com ([147.34.90.203])	by relay1.mentorg.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-SHA384:256)	id 1gG7gE-0001HI-3p from Sandra_Loosemore@mentor.com 	for gdb@sourceware.org; Fri, 26 Oct 2018 12:21:58 -0700
Received: from [127.0.0.1] (147.34.91.1) by svr-orw-mbx-03.mgc.mentorg.com (147.34.90.203) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 26 Oct 2018 12:21:55 -0700
To: <gdb@sourceware.org>
From: Sandra Loosemore <sandra@codesourcery.com>
Subject: remote host testing expectations re multiple simultaneous connections
Message-ID: <30184147-e912-0713-d561-8131e7f629aa@codesourcery.com>
Date: Fri, 26 Oct 2018 19:22:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2018-10/txt/msg00053.txt.bz2

I've noticed that there are several gdb.mi tests that start GDB before 
building the test program, like this bit of code from mi-cli.exp:

gdb_exit
if [mi_gdb_start] {
     continue
}

standard_testfile basics.c

if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" 
executable {debug}] != "" } {
      untested "failed to compile"
      return -1
}

mi_gdb_test "-interpreter-exec" \
   {\^error,msg="-interpreter-exec: Usage: -interpreter-exec interp 
command"} \
   "-interpreter-exec with no arguments"

E.g. there's an implicit expectation that when testing on a remote host, 
it can start GDB and leave it running and waiting to accept GDB commands 
while running some other shell commands to build the test program on a 
different channel to the same remote host.  Is this a reasonable 
expectation that is documented somewhere?  Or are the test cases that 
are structured like this just broken?  :-S  If the latter I will submit 
a patch to fix them.

-Sandra