From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24596 invoked by alias); 28 Oct 2018 17:05:04 -0000 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 Received: (qmail 24586 invoked by uid 89); 28 Oct 2018 17:05:04 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=simultaneous, expectation, spawn, connections X-HELO: smtp.polymtl.ca Received: from smtp.polymtl.ca (HELO smtp.polymtl.ca) (132.207.4.11) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 28 Oct 2018 17:05:03 +0000 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id w9SH4uX2014015 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Sun, 28 Oct 2018 13:05:01 -0400 Received: by simark.ca (Postfix, from userid 112) id B9C341EA6F; Sun, 28 Oct 2018 13:04:56 -0400 (EDT) Received: from simark.ca (localhost [127.0.0.1]) by simark.ca (Postfix) with ESMTP id A2FC21E4C2; Sun, 28 Oct 2018 13:04:54 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 28 Oct 2018 17:05:00 -0000 From: Simon Marchi To: Sandra Loosemore Cc: gdb@sourceware.org Subject: Re: remote host testing expectations re multiple simultaneous connections In-Reply-To: <30184147-e912-0713-d561-8131e7f629aa@codesourcery.com> References: <30184147-e912-0713-d561-8131e7f629aa@codesourcery.com> Message-ID: X-Sender: simon.marchi@polymtl.ca User-Agent: Roundcube Webmail/1.3.6 X-IsSubscribed: yes X-SW-Source: 2018-10/txt/msg00056.txt.bz2 On 2018-10-26 15:21, Sandra Loosemore wrote: > 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. I haven't tried remote host testing in a long time, but I would expect the framework to be able to run multiple things concurrently. Just like for remote target testing, we are able to spawn multiple programs, spawn gdbserver, and attach to them. What happens currently when you try it? Simon