Re: Help, DejaGnu bails out on sigstep.exp

[Mark Kettenis <mark.kettenis@xs4all.nl>]

   From: Michael Chastain <mec.gnu@mindspring.com>
   Date: Wed, 22 Sep 2004 17:45:02 -0400

   Mark Kettenis <kettenis@gnu.org> wrote:
   > Running ../../../src/gdb/testsuite/gdb.base/sigstep.exp ...
   > ERROR: (DejaGnu) proc "other" does not exist.

   This smells like you are getting screwed by this code:

     gdb_test_multiple "continue" "$test" {
       -re "done = 0.*$gdb_prompt " {
	 pass $test
       }
       # other patterns can go here
     }

   There are three occurences of "# other patterns can go here".
   Try changing them to:

       # tcl_syntax_bites_1 other patterns can go here
       # tcl_syntax_bites_2 other patterns can go here
       # tcl_syntax_bites_3 other patterns can go here

   It's a quirk of TCL that comments can occur only in certain places.
   Basically, it's a side effect of the "everything is a block or
   a delayed block" syntax rules.  I bet that the problem would not
   actually happen unless all the "-re" in front of it fell through.

   If that really is the problem, you can fix it as an obvious fix,
   something like:

       # Run around to the done
       # You can add more patterns to this if you need them.
       gdb_test_multiple ...

That's indeed the case.  Thanks!  I'll check in the obvious patch.

   > FAIL: gdb.base/sigstep.exp: nexti from handleri; leave signal trampoline
   > FAIL: gdb.base/sigstep.exp: finish from handleri; continue to handler
   > FAIL: gdb.base/sigstep.exp: finish from handleri; leave handler (in main)
   > FAIL: gdb.base/sigstep.exp: finish from handleri; leave signal trampoline
   > FAIL: gdb.base/sigstep.exp: return from handleri; continue to handler
   > ERROR: Undefined command "return".
   > ERROR: Got interactive prompt.
   > ERROR: breakpoints not deleted
   > ERROR: (DejaGnu) proc "other" does not exist.
   > The error code is NONE

   Beats me.  I don't see where the "Undefined command "return"" is
   coming from.  Can you add some "-v" to the invocation of runtest
   and show a gdb.log fragment?

The return is probably the input that is intended for GDB, but doesn't
arrive there.  I'll look a bit further into it, and I'll post the
gdb.log if I don't manage to fix it.

Mark

P.S. Since you keep bugging about testsuite results (and rightly so),
     can you tell me the guidelines again?  Was it that you wanted the
     output of:

     cat gdb.sum | grep -v ^PASS

     or something a bit more difficult?