From a9f158ec20ec6e6bc28e7b41c8c6e5f8853ba3f1 Mon Sep 17 00:00:00 2001 From: Jim Blandy Date: Wed, 25 Jan 2006 21:15:42 +0000 Subject: [PATCH] 2006-01-25 Jim Blandy * gdbint.texinfo (Testsuite): Explain how to run selected tests. --- gdb/doc/ChangeLog | 4 ++++ gdb/doc/gdbint.texinfo | 7 +++++++ 2 files changed, 11 insertions(+) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 531972d..a03ae63 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +2006-01-25 Jim Blandy + + * gdbint.texinfo (Testsuite): Explain how to run selected tests. + 2006-01-24 Jim Blandy * gdbint.texinfo (Frames): Document the basics of GDB's register diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index a81cc9b..b86b083 100644 --- 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 -- 2.7.4