This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
MI-related testsuite regressions
- From: Mark Kettenis <kettenis at gnu dot org>
- To: nickrob at snap dot net dot nz
- Cc: gdb at sourceware dot org
- Date: Mon, 27 Jun 2005 10:15:35 +0200
- Subject: MI-related testsuite regressions
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