espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-10-17 04:43:17 +08:00
Code Issues Packages Projects Releases Wiki Activity

testsuite/

Browse Source 
* lib/gdb.exp (INTERNAL_GDBFLAGS): Don't override value provided by
	user.
	doc/
	* gdbint.texinfo (Testsuite): Document INTERNAL_GDBFLAGS.
This commit is contained in:
Doug Evans
2010-02-05 21:51:38 +00:00
parent 8285698016
commit 1be008824d
4 changed files with 37 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
gdb/doc/ChangeLog
View File

@ -2,6 +2,7 @@
* gdbint.texinfo (Testsuite): Add a new section to document the * gdbint.texinfo (Testsuite): Add a new section to document the
various DejaGnu variables that may be overridden. various DejaGnu variables that may be overridden.
Document INTERNAL_GDBFLAGS.
2010-02-04 Tom Tromey <tromey@redhat.com> 2010-02-04 Tom Tromey <tromey@redhat.com>

27
gdb/doc/gdbint.texinfo
View File

@ -7647,6 +7647,33 @@ different gdbserver.
make check RUNTESTFLAGS="GDB=/usr/bin/gdb GDBSERVER=/usr/bin/gdbserver" make check RUNTESTFLAGS="GDB=/usr/bin/gdb GDBSERVER=/usr/bin/gdbserver"
@end smallexample @end smallexample
@item @code{INTERNAL_GDBFLAGS}
When running the testsuite normally one doesn't want whatever is in
@file{~/.gdbinit} to interfere with the tests, therefore the test harness
passes @option{-nx} to @value{GDBN}. One also doesn't want any windowed
version of @value{GDBN}, e.g., @command{gdbtui}, to run.
This is achieved via @code{INTERNAL_GDBFLAGS}.
@smallexample
set INTERNAL_GDBFLAGS "-nw -nx"
@end smallexample
This is all well and good, except when testing an installed @value{GDBN}
that has been configured with @option{--with-system-gdbinit}. Here one
does not want @file{~/.gdbinit} loaded but one may want the system
@file{.gdbinit} file loaded. This can be achieved by pointing @code{$HOME}
at a directory without a @file{.gdbinit} and by overriding
@code{INTERNAL_GDBFLAGS} and removing @option{-nx}.
@smallexample
cd testsuite
HOME=`pwd` runtest \
GDB=/usr/bin/gdb \
GDBSERVER=/usr/bin/gdbserver \
INTERNAL_GDBFLAGS=-nw
@end smallexample
@end itemize @end itemize
There are two ways to run the testsuite and pass additional parameters There are two ways to run the testsuite and pass additional parameters

5
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,8 @@
2010-02-05 Doug Evans <dje@google.com>
* lib/gdb.exp (INTERNAL_GDBFLAGS): Don't override value provided by
user.
2010-02-05 Sami Wagiaalla <swagiaal@redhat.com> 2010-02-05 Sami Wagiaalla <swagiaal@redhat.com>
PR c++/7935: PR c++/7935:

5
gdb/testsuite/lib/gdb.exp
View File

@ -54,7 +54,10 @@ if ![info exists GDBFLAGS] {
verbose "using GDBFLAGS = $GDBFLAGS" 2 verbose "using GDBFLAGS = $GDBFLAGS" 2
# INTERNAL_GDBFLAGS contains flags that the testsuite requires. # INTERNAL_GDBFLAGS contains flags that the testsuite requires.
set INTERNAL_GDBFLAGS "-nw -nx" global INTERNAL_GDBFLAGS
if ![info exists INTERNAL_GDBFLAGS] {
set INTERNAL_GDBFLAGS "-nw -nx"
}
# The variable gdb_prompt is a regexp which matches the gdb prompt. # The variable gdb_prompt is a regexp which matches the gdb prompt.
# Set it if it is not already set. # Set it if it is not already set.