FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* gdbint.texinfo (Testsuite): Add a new section to document the

Browse source 
various DejaGnu variables that may be overridden.
This commit is contained in:
Doug Evans 2010-02-05 18:30:44 +00:00
parent 4c34844242
commit c5f80513ff
2 changed files with 51 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
gdb/doc/ChangeLog
View file

@ -1,3 +1,8 @@
2010-02-05 Doug Evans <dje@google.com>
* gdbint.texinfo (Testsuite): Add a new section to document the
various DejaGnu variables that may be overridden.
2010-02-04 Tom Tromey <tromey@redhat.com> 2010-02-04 Tom Tromey <tromey@redhat.com>
PR cli/8830: PR cli/8830:

46
gdb/doc/gdbint.texinfo
View file

@ -7599,6 +7599,14 @@ will give a result of ``UNRESOLVED'', like this:
UNRESOLVED: gdb.base/example.exp: This test script does not work on a remote host. UNRESOLVED: gdb.base/example.exp: This test script does not work on a remote host.
@end smallexample @end smallexample
@section Testsuite Parameters
Several variables exist to modify the behavior of the testsuite.
@itemize @bullet
@item @code{TRANSCRIPT}
Sometimes it is convenient to get a transcript of the commands which Sometimes it is convenient to get a transcript of the commands which
the testsuite sends to @value{GDBN}. For example, if @value{GDBN} the testsuite sends to @value{GDBN}. For example, if @value{GDBN}
crashes during testing, a transcript can be used to more easily crashes during testing, a transcript can be used to more easily
@ -7620,6 +7628,44 @@ make check RUNTESTFLAGS=TRANSCRIPT=y
Note that the transcript is not always complete. In particular, tests Note that the transcript is not always complete. In particular, tests
of completion can yield partial command lines. of completion can yield partial command lines.
@item @code{GDB}
Sometimes one wishes to test a different @value{GDBN} than the one in the build
directory. For example, one may wish to run the testsuite on
@file{/usr/bin/gdb}.
@smallexample
make check RUNTESTFLAGS=GDB=/usr/bin/gdb
@end smallexample
@item @code{GDBSERVER}
When testing a different @value{GDBN}, it is often useful to also test a
different gdbserver.
@smallexample
make check RUNTESTFLAGS="GDB=/usr/bin/gdb GDBSERVER=/usr/bin/gdbserver"
@end smallexample
@end itemize
There are two ways to run the testsuite and pass additional parameters
to DejaGnu. The first is with @kbd{make check} and specifying the
makefile variable @samp{RUNTESTFLAGS}.
@smallexample
make check RUNTESTFLAGS=TRANSCRIPT=y
@end smallexample
The second is to cd to the @file{testsuite} directory and invoke the DejaGnu
@command{runtest} command directly.
@smallexample
cd testsuite
make site.exp
runtest TRANSCRIPT=y
@end smallexample
@section Testsuite Organization @section Testsuite Organization
@cindex test suite organization @cindex test suite organization