OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

* gdbint.texinfo (Testsuite): Explain how to run selected tests.
This commit is contained in:
Jim Blandy 2006-01-25 21:15:42 +00:00
parent 410dd08eb5
commit a9f158ec20
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/doc/ChangeLog
View File

@ -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> 2006-01-24 Jim Blandy <jimb@redhat.com>
* gdbint.texinfo (Frames): Document the basics of GDB's register * gdbint.texinfo (Frames): Document the basics of GDB's register

7
gdb/doc/gdbint.texinfo
View File

@ -6474,6 +6474,13 @@ finished, you'll get a summary that looks like this:
# of untested testcases 5 # of untested testcases 5
@end smallexample @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 The ideal test run consists of expected passes only; however, reality
conspires to keep us from this ideal. Unexpected failures indicate conspires to keep us from this ideal. Unexpected failures indicate
real problems, whether in @value{GDBN} or in the testsuite. Expected real problems, whether in @value{GDBN} or in the testsuite. Expected