From: Nick Roberts <nickrob@snap.net.nz>
To: Mark Kettenis <kettenis@gnu.org>
Cc: gdb@sourceware.org
Subject: MI-related testsuite regressions
Date: Mon, 27 Jun 2005 12:00:00 -0000 [thread overview]
Message-ID: <17087.60064.541364.938844@farnswood.snap.net.nz> (raw)
In-Reply-To: <200506270815.j5R8FZO6026261@jop31.nfra.nl>
> 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
next prev parent reply other threads:[~2005-06-27 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 8:16 Mark Kettenis
2005-06-27 12:00 ` Nick Roberts [this message]
2005-06-27 13:00 ` Daniel Jacobowitz
2005-06-27 13:53 ` Nick Roberts
2005-06-27 13:56 ` Bob Rossi
2005-06-27 13:59 ` Daniel Jacobowitz
2005-06-27 14:07 ` Nick Roberts
2005-06-27 14:31 ` Daniel Jacobowitz
2005-06-27 20:53 ` Nick Roberts
2005-06-27 21:03 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17087.60064.541364.938844@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sourceware.org \
--cc=kettenis@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox