Home | History | Annotate | Download | only in info

Lines Matching full:testsuite

67 * Testsuite::
6190 File: gdbint.info, Node: Releasing GDB, Next: Testsuite, Prev: Start of New Year Procedure, Up: Top
6827 File: gdbint.info, Node: Testsuite, Next: Hints, Prev: Releasing GDB, Up: Top
6829 21 Testsuite
6832 The testsuite is an important component of the GDB package. While it
6838 The GDB testsuite uses the DejaGNU testing framework. The tests
6842 21.1 Using the Testsuite
6845 To run the testsuite, simply go to the GDB object directory (or to the
6846 testsuite's objdir) and type `make check'. This just sets up some
6848 the testsuite is running, you'll get mentions of which test file is in
6850 testsuite is finished, you'll get a summary that looks like this:
6866 testsuite in parallel. This can greatly reduce the amount of time it
6867 takes for the testsuite to run. In this case, if you set
6872 testsuite, so it is not compatible with some dejagnu options, like
6877 real problems, whether in GDB or in the testsuite. Expected failures
6888 testsuite before and after the change, to confirm that there are no
6890 run the testsuite with all supported configurations and a variety of
6912 21.2 Testsuite Parameters
6915 Several variables exist to modify the behavior of the testsuite.
6920 which the testsuite sends to GDB. For example, if GDB crashes
6924 You can instruct the GDB testsuite to write transcripts by setting
6941 build directory. For example, one may wish to run the testsuite on
6955 When running the testsuite normally one doesn't want whatever is in
6970 cd testsuite
6977 There are two ways to run the testsuite and pass additional
6983 The second is to cd to the `testsuite' directory and invoke the
6986 cd testsuite
6990 21.3 Testsuite Configuration
6993 It is possible to adjust the behavior of the testsuite by defining the
7012 defined to the same value as `timeout' during the testsuite
7014 the file `gdb/testsuite/config/unix.exp' that is part of the GDB
7018 21.4 Testsuite Organization
7021 The testsuite is entirely contained in `gdb/testsuite'. While the
7022 testsuite includes some makefiles and configury, these are very minimal,
7025 `testsuite/lib/gdb.exp' contains common utility procs useful for all
7026 GDB tests, while the directory `testsuite/config' contains
7030 The tests themselves are to be found in `testsuite/gdb.*' and
7043 This is the base testsuite. The tests in it should apply to all
7093 styles, it's worth having a mix of styles in the testsuite; for
7104 File: gdbint.info, Node: Hints, Next: GDB Observers, Prev: Testsuite, Up: Top
7481 testsuite/gdb.gdb/observer.exp.
8503 * running the test suite: Testsuite. (line 19)
8613 * test suite: Testsuite. (line 6)
8614 * test suite organization: Testsuite. (line 195)
8616 * Testsuite Configuration: Testsuite. (line 167)
8681 * writing tests: Testsuite. (line 247)
8758 Node: Testsuite277890
8759 Ref: Testsuite-Footnote-1289755