From: Mark Kettenis <kettenis@gnu.org>
To: nickrob@snap.net.nz
Cc: gdb@sourceware.org
Subject: MI-related testsuite regressions
Date: Mon, 27 Jun 2005 08:16:00 -0000 [thread overview]
Message-ID: <200506270815.j5R8FZO6026261@jop31.nfra.nl> (raw)
Nick,
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
-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. 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.
Mark
next reply other threads:[~2005-06-27 8:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 8:16 Mark Kettenis [this message]
2005-06-27 12:00 ` Nick Roberts
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=200506270815.j5R8FZO6026261@jop31.nfra.nl \
--to=kettenis@gnu.org \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/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