From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21673 invoked by alias); 25 Jan 2012 18:22:51 -0000 Received: (qmail 21663 invoked by uid 22791); 25 Jan 2012 18:22:50 -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; Wed, 25 Jan 2012 18:22:32 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id DD55C2BB37F; Wed, 25 Jan 2012 13:22:31 -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 1Jjq3HwKsa3r; Wed, 25 Jan 2012 13:22:31 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 6BE582BB37D; Wed, 25 Jan 2012 13:22:31 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id CAA84145615; Wed, 25 Jan 2012 22:22:13 +0400 (RET) Date: Wed, 25 Jan 2012 18:25:00 -0000 From: Joel Brobecker To: Pedro Alves Cc: GDB Patches Subject: Re: New board file to run the whole testsuite with a local gdbserver in extended-remote mode Message-ID: <20120125182213.GQ31383@adacore.com> References: <4F200EB2.8080909@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F200EB2.8080909@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00872.txt.bz2 > - many tests that do "attach" assume GDB can figure out what executable > the process is running, and load it automatically > (target_pid_to_exec_file). This doesn't work in the remote > targets. I think these testcases should be fixed to avoid tis requirement. We can always have one specific testcase that test that, and skip the testcase if testing in extended-remote mode. > I think this should be good enough to check in as is, and improve as > follow-ups. I agree. This is far better than nothing. -- Joel