Re: [RFA/Testsuite] help.exp

[Elena Zannoni <ezannoni@redhat.com>]

Michael Snyder writes:
 > Elena Zannoni wrote:
 > > 
 > > Fernando Nasser writes:
 > >  > Michael Snyder wrote:
 > >  > >
 > >  > > Or you could just use a parenthesis to make the
 > >  > > powerpc command output optional...
 > >  > >
 > >  >
 > >  > Good idea, more specific than my suggested '.*'.  But we don't
 > >  > need to be so stringent in this case.  As long as we see the
 > >  > generic ones the help is working.
 > >  >
 > >  > Unless Elena wants to test if these commands show up for the powerpc
 > >  > targets help.  In this case, neither my suggestion or yours are
 > >  > checking for it. :-(
 > >  >
 > > 
 > > Nah, I don't really want to be that specific.
 > > 
 > >  > If that is the case, we will have to go with Elena's original patch.
 > >  >
 > > 
 > > But you guys decide, if we got rid of the wildcards do we want them back?
 > 
 > I was only deleting them where I thought they were unnecessary.
 > In this case, I was wrong, 'cause I didn't know PPC had its own
 > variants.  So yes, it would be appropriate to put that one back.
 > 
 > Michael

OK, I committed the following:

2002-04-23  Elena Zannoni  <ezannoni@redhat.com>

	* gdb.base/help.exp: Change 'help status' to allow for target
	dependent output differences.

Index: help.exp
===================================================================
RCS file: /cvs/uberbaum/gdb/testsuite/gdb.base/help.exp,v
retrieving revision 1.10
diff -u -p -r1.10 help.exp
--- help.exp	29 Mar 2002 01:19:11 -0000	1.10
+++ help.exp	24 Apr 2002 03:05:07 -0000
@@ -535,7 +535,9 @@ gdb_test "help source" "Read commands fr
 # test help stack
 gdb_test "help stack" "Examining the stack\..*\[\r\n\]+When the program being debugged stops, gdb selects the innermost frame\.\[\r\n\]+The commands below can be used to select other frames by number or address\.\[\r\n\]+List of commands:\[\r\n\]+backtrace -- Print backtrace of all stack frames\[\r\n\]+bt -- Print backtrace of all stack frames\[\r\n\]+down -- Select and print stack frame called by this one\[\r\n\]+frame -- Select and print a stack frame\[\r\n\]+return -- Make selected stack frame return to its caller\[\r\n\]+select-frame -- Select a stack frame without printing anything\[\r\n\]+up -- Select and print stack frame that called this one\[\r\n\]+Type \"help\" followed by command name for full documentation\.\[\r\n\]+Command name abbreviations are allowed if unambiguous\." "help stack"
 # test help status
-gdb_test "help status" "Status inquiries\.\[\r\n\]+List of commands:\[\r\n\]+info -- Generic command for showing things about the program being debugged\[\r\n\]+show -- Generic command for showing things about the debugger\[\r\n\]+Type \"help\" followed by command name for full documentation\.\[\r\n\]+Command name abbreviations are allowed if unambiguous\." "help status"
+gdb_test "help status" "Status inquiries\.\[\r\n\]+List of commands:\[\r\n\]+info -- Generic command for showing things about the program being debugged.*\[\r\n\]+show -- Generic command for showing things about the debugger\[\r\n\]+Type \"help\" followed by command name for full documentation\.\[\r\n\]+Command name abbreviations are allowed if unambiguous\." "help status"
+
 # test help support
 # FIXME -- Ultrix hangs randomly on this very long output from gdb and
 # continues with its output only if something is sent to gdb.