From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6204 invoked by alias); 27 Jun 2005 12:00:57 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 6182 invoked by uid 22791); 27 Jun 2005 12:00:53 -0000 Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 27 Jun 2005 12:00:53 +0000 Received: from farnswood.snap.net.nz (p11-tnt1.snap.net.nz [202.124.110.11]) by viper.snap.net.nz (Postfix) with ESMTP id D429B55338D; Tue, 28 Jun 2005 00:00:49 +1200 (NZST) Received: by farnswood.snap.net.nz (Postfix, from userid 501) id 7BA8B62A99; Mon, 27 Jun 2005 13:01:37 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17087.60064.541364.938844@farnswood.snap.net.nz> Date: Mon, 27 Jun 2005 12:00:00 -0000 To: Mark Kettenis Cc: gdb@sourceware.org Subject: MI-related testsuite regressions In-Reply-To: <200506270815.j5R8FZO6026261@jop31.nfra.nl> References: <200506270815.j5R8FZO6026261@jop31.nfra.nl> X-SW-Source: 2005-06/txt/msg00254.txt.bz2 > I see a fair number of new testsuite regressions: > > -PASS: gdb.mi/mi2-stack.exp: stack select same frame > +FAIL: gdb.mi/mi2-stack.exp: stack select same frame Yes. These are due to my changes. Currently the default MI interpreter *is* mi2, so these tests are just duplicated. It would seem sensible, and save effort, to have just one file (mi-stack.exp) until the MI version is bumped up one number. Then mi-stack.exp could be renamed mi2-stack.exp and a new file mi-stack.exp could be created. In reality GDB doesn't support more than one version of MI (the current one). As has been shown on the mailing list recently, even MI output from GDB 6.3 differs from MI output from GDB in CVS. > -PASS: gdb.mi/mi2-var-block.exp: step at do_block_test > -PASS: gdb.mi/mi2-var-block.exp: create local variable foo2 > +FAIL: gdb.mi/mi2-var-block.exp: step at do_block_test (stopped at wrong place) > +FAIL: gdb.mi/mi2-var-block.exp: create local variable foo2 > > -PASS: gdb.mi/mi2-var-block.exp: step at do_block_test > +FAIL: gdb.mi/mi2-var-block.exp: step at do_block_test (stopped at wrong place) > > -PASS: gdb.mi/mi2-var-block.exp: step at do_block_test > +FAIL: gdb.mi/mi2-var-block.exp: step at do_block_test (stopped at wrong place) > > -PASS: gdb.mi/mi2-var-block.exp: update cb > +FAIL: gdb.mi/mi2-var-block.exp: update cb > > -PASS: gdb.mi/mi2-var-block.exp: delete var foo2 > +FAIL: gdb.mi/mi2-var-block.exp: delete var foo2 > They seem all to be related to your recent changes. I can't see how these relate to my changes. I have submitted a patch for variable objects, but it still hasn't been approved. I don't understand why mi-var-block.exp doesn't fail at the same places. > Please make sure you run the (complete) testsuite and check for regressions > before you check things in. I usually keep an old gdb.sum around and diff it > with the new output to check for regressions. Sure. I get all kinds of spurious fails on my old computer which makes this a bit harder to do. Nick