This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
PATCH: doc fix for gdb_test
- To: gdb-patches at sources dot redhat dot com
- Subject: PATCH: doc fix for gdb_test
- From: Jim Blandy <jimb at zwingli dot cygnus dot com>
- Date: Wed, 13 Jun 2001 19:14:30 -0500 (EST)
2001-06-13 Jim Blandy <jimb@redhat.com>
* lib/gdb.exp (gdb_test): Doc fix.
Index: gdb/testsuite/lib/gdb.exp
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.164.6.1
diff -c -r1.164.6.1 gdb.exp
*** gdb/testsuite/lib/gdb.exp 2001/06/06 02:44:54 1.164.6.1
--- gdb/testsuite/lib/gdb.exp 2001/06/14 00:01:17
***************
*** 371,377 ****
! # gdb_test COMMAND PATTERN MESSAGE -- send a command to gdb; test the result.
#
# COMMAND is the command to execute, send to GDB with send_gdb. If
# this is the null string no command is sent.
--- 371,378 ----
! # gdb_test COMMAND PATTERN MESSAGE QUESTION RESPONSE
! # Send a command to gdb; test the result.
#
# COMMAND is the command to execute, send to GDB with send_gdb. If
# this is the null string no command is sent.
***************
*** 381,386 ****
--- 382,390 ----
# omitted, then the pass/fail messages use the command string as the
# message. (If this is the empty string, then sometimes we don't
# call pass or fail at all; I don't understand this at all.)
+ # QUESTION is a question GDB may ask in response to COMMAND, like
+ # "are you sure?"
+ # RESPONSE is the response to send if QUESTION appears.
#
# Returns:
# 1 if the test failed,