summaryrefslogtreecommitdiff
path: root/gdb/testsuite/README
diff options
context:
space:
mode:
Diffstat (limited to 'gdb/testsuite/README')
-rw-r--r--gdb/testsuite/README25
1 files changed, 18 insertions, 7 deletions
diff --git a/gdb/testsuite/README b/gdb/testsuite/README
index 7552774c78b..3a34dcdd154 100644
--- a/gdb/testsuite/README
+++ b/gdb/testsuite/README
@@ -164,15 +164,23 @@ instance
checks both the installed GDB and GDBserver.
-INTERNAL_GDBFLAGS
+GDB_DATA_DIRECTORY
-Command line options passed to all GDB invocations.
+If you set GDB, then by default the testsuite assumes you are
+exercising an installed GDB, and thus the testsuite lets GDB use its
+configured data directory. Otherwise, if you don't set GDB, then by
+default the tested GDB uses the data directory found under the GDB
+build directory. You can override this by setting GDB_DATA_DIRECTORY.
+For instance:
+
+ make check \
+ RUNTESTFLAGS="GDB=/path/to/other/build/gdb \
+ GDB_DATA_DIRECTORY=/path/to/other/build/gdb/data-directory"
-The default is "-nw -nx".
+INTERNAL_GDBFLAGS
-`-nw' disables any of the windowed interfaces.
-`-nx' disables ~/.gdbinit, so that it doesn't interfere with
-the tests.
+Command line options passed to all GDB invocations.
+The default is set in lib/gdb.exp.
This is actually considered an internal variable, and you
won't normally want to change it. However, in some situations,
@@ -193,7 +201,10 @@ a .gdbinit. For example:
HOME=`pwd` runtest \
GDB=/usr/bin/gdb \
GDBSERVER=/usr/bin/gdbserver \
- INTERNAL_GDBFLAGS=-nw
+ INTERNAL_GDBFLAGS="-nw -iex 'set height 0' -iex 'set width 0'"
+
+Note that we do not need to specify '-data-directory' here
+as we are testing an installed GDB.
GDB_PARALLEL