2006-01-25 Jim Blandy <jimb@redhat.com>

	* gdbint.texinfo (Testsuite): Explain how to run selected tests.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 531972d0eaa64c4f9ee81a9916706e147235349c..a03ae63d76151c3ddf040c609d7735b7a1d1b31c 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2006-01-25  Jim Blandy  <jimb@redhat.com>
+
+       * gdbint.texinfo (Testsuite): Explain how to run selected tests.
+
 2006-01-24  Jim Blandy  <jimb@redhat.com>
 
        * gdbint.texinfo (Frames): Document the basics of GDB's register

diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index a81cc9b9a4bc5adba9b919d0a277b9c77bd64be9..b86b083e23dea06d74d657b881047281ee2b08e4 100644 (file)
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -6474,6 +6474,13 @@ finished, you'll get a summary that looks like this:
 # of untested testcases         5
 @end smallexample
 
+To run a specific test script, type:
+@example
+make check RUNTESTFLAGS='@var{tests}'
+@end example
+where @var{tests} is a list of test script file names, separated by
+spaces.
+
 The ideal test run consists of expected passes only; however, reality
 conspires to keep us from this ideal.  Unexpected failures indicate
 real problems, whether in @value{GDBN} or in the testsuite.  Expected