From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org, eliz@gnu.org
Subject: [RFA] doc addition to gdbint.texinfo
Date: Thu, 04 Feb 2010 21:37:00 -0000 [thread overview]
Message-ID: <20100204213709.C7D4884414@ruffy.mtv.corp.google.com> (raw)
Hi.
The Testsuite section of gdbint.texinfo is missing docs on at least
two more DejaGnu variables that are available to be overridden:
GDB, GDBSERVER.
Since there's at least three of them (those two plus TRANSCRIPT),
with more to come, it seemed appropriate to create a new section to
document them all.
Ok to check in?
2010-02-04 Doug Evans <dje@google.com>
* gdbint.texinfo (Testsuite): Add a new section to document the
various DejaGnu variables that may be overridden.
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.316
diff -u -p -r1.316 gdbint.texinfo
--- gdbint.texinfo 1 Jan 2010 11:38:33 -0000 1.316
+++ gdbint.texinfo 4 Feb 2010 21:32:09 -0000
@@ -7599,6 +7599,14 @@ will give a result of ``UNRESOLVED'', li
UNRESOLVED: gdb.base/example.exp: This test script does not work on a remote host.
@end smallexample
+@section Testsuite Parameters
+
+Several variables exist to modify the behavior of the testsuite.
+
+@itemize @bullet
+
+@item TRANSCRIPT
+
Sometimes it is convenient to get a transcript of the commands which
the testsuite sends to @value{GDBN}. For example, if @value{GDBN}
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
of completion can yield partial command lines.
+@item 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 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
+@kbd{runtest} command directly.
+
+@smallexample
+cd testsuite
+make site.exp
+runtest TRANSCRIPT=y
+@end smallexample
+
@section Testsuite Organization
@cindex test suite organization
next reply other threads:[~2010-02-04 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 21:37 Doug Evans [this message]
2010-02-04 22:20 ` Eli Zaretskii
2010-02-05 18:32 ` Doug Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100204213709.C7D4884414@ruffy.mtv.corp.google.com \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox