These are the kinds of debugging information available from DejaGnu:
verbose procedure (which in turn uses the
variable also called verbose) to control how much output to
generate. This will make it easier for other people running the test to
debug it if necessary. Whenever possible, if `$verbose' is
0, there should be no output other than the output from
pass, fail, error, and warning. Then, to
whatever extent is appropriate for the particular test, allow
successively higher values of `$verbose' to generate more
information. Be kind to other programmers who use your tests: provide
for a lot of debugging information.
expect.
There is a command line options for each; both forms of debugging output
are recorded in the file dbg.log in the current directory.
Use `--debug' for information from the expect level; it
generates displays of the expect attempts to match the tool
output with the patterns specified (see section Logging expect internal actions). This
output can be very helpful while developing test scripts, since it shows
precisely the characters received. Iterating between the latest attempt
at a new test script and the corresponding `dbg.log' can allow you
to create the final patterns by "cut and paste". This is sometimes
the best way to write a test case.
Use `--strace' to see more detail at the Tcl level; this shows how Tcl
procedure definitions expand, as they execute. The associated number
controls the depth of definitions expanded; see the discussion of
`--strace' in section Using runtest.
runtest
turns on the expect command log_user. This command prints
all expect actions to the expect standard output, to the
detailed log file, and (if `--debug' is on) to `dbg.log'.
Go to the first, previous, next, last section, table of contents.