This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

MI-related testsuite regressions


 > 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]