2006-01-25 Jim Blandy <jimb@redhat.com>
* gdbint.texinfo (Testsuite): Explain how to run selected tests.
This commit is contained in:
parent
410dd08eb5
commit
a9f158ec20
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue