From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15198 invoked by alias); 7 Sep 2002 17:11:14 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 15190 invoked from network); 7 Sep 2002 17:11:13 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 7 Sep 2002 17:11:13 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17nk34-0006Fa-00; Sat, 07 Sep 2002 13:11:10 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17nj6o-0007Hg-00; Sat, 07 Sep 2002 13:10:58 -0400 Date: Sat, 07 Sep 2002 10:11:00 -0000 From: Daniel Jacobowitz To: Fred Fish Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] Fix inferior restart problem in gdb.base/commands.exp Message-ID: <20020907171058.GA27358@nevyn.them.org> Mail-Followup-To: Fred Fish , gdb-patches@sources.redhat.com References: <200209071404.g87E4kb19664@beeville.vert.intrinsity.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209071404.g87E4kb19664@beeville.vert.intrinsity.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-09/txt/msg00107.txt.bz2 On Sat, Sep 07, 2002 at 09:04:45AM -0500, Fred Fish wrote: > When running the gdb testsuite with an external simulator like "sid", if the > inferior is allowed to run to completion and exit, a simple gdb_run_cmd may > have problems rerunning the inferior since it doesn't do a complete restart. > > An alternative to gdb_run_cmd is to do the following prior to setting up > the test and then later do just a continue instead of gdb_run_cmd: > > gdb_exit > gdb_start > delete_breakpoints > gdb_reinitialize_dir $srcdir/$subdir > gdb_load ${binfile} > > but that is much more expensive. It is sufficient to just not allow the > inferior to run to completion. This patch does that. > > Also, to avoid having to specifically test for noinferiorio we don't > check for output from the test case, it is not relevant to the given > test anyway. I don't really like this. Isn't there some way you can make re-issuing gdb_run_cmd work for sid? It works for gdbserver, I believe, though I have to play some games to do it. (The test itself fails but due to a bad regular expression construct, I think - not sure why. The desired behavior is indeed there.) I don't like having to work around all sorts of targets in the testsuite more than necessary. I've had a kernel bug this week that only showed up when GDB ran a program multiple times. Is there anywhere else in the testsuite that continues to cover that? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer