Change gdb test suite's TERM setting
This changes the gdb test suite to set TERM to "dumb" by default. This setting disables terminal styling, so that the existing tests do not need to be updated. gdb/testsuite/ChangeLog 2018-12-28 Tom Tromey <tom@tromey.com> * lib/gdb.exp (gdb_init): Set the TERM environment variable to "dumb". * gdb.base/readline.exp (operate_and_get_next): Save and restore the TERM environment variable.
This commit is contained in:
parent
eedeedd2a5
commit
9162a27c5f
|
@ -1,3 +1,10 @@
|
||||||
|
2018-12-28 Tom Tromey <tom@tromey.com>
|
||||||
|
|
||||||
|
* lib/gdb.exp (gdb_init): Set the TERM environment variable to
|
||||||
|
"dumb".
|
||||||
|
* gdb.base/readline.exp (operate_and_get_next): Save and restore
|
||||||
|
the TERM environment variable.
|
||||||
|
|
||||||
2018-12-27 Tom Tromey <tom@tromey.com>
|
2018-12-27 Tom Tromey <tom@tromey.com>
|
||||||
|
|
||||||
* gdb.python/py-cmd.exp (test_python_inline_or_multiline): Add
|
* gdb.python/py-cmd.exp (test_python_inline_or_multiline): Add
|
||||||
|
|
|
@ -141,16 +141,21 @@ proc operate_and_get_next {name args} {
|
||||||
return 1
|
return 1
|
||||||
}
|
}
|
||||||
|
|
||||||
|
save_vars { env(TERM) } {
|
||||||
|
# The arrow key test relies on the standard VT100 bindings, so
|
||||||
|
# make sure that an appropriate terminal is selected. The same
|
||||||
|
# bug doesn't show up if we use ^P / ^N instead.
|
||||||
|
setenv TERM vt100
|
||||||
|
|
||||||
gdb_start
|
gdb_start
|
||||||
gdb_reinitialize_dir $srcdir/$subdir
|
gdb_reinitialize_dir $srcdir/$subdir
|
||||||
|
|
||||||
if { ![readline_is_used] } {
|
if { ![readline_is_used] } {
|
||||||
unsupported "readline isn't used."
|
unsupported "readline isn't used."
|
||||||
return -1
|
return -1
|
||||||
}
|
}
|
||||||
|
|
||||||
save_vars { timeout env(GDBHISTSIZE) env(GDBHISTFILE) } {
|
save_vars { timeout env(GDBHISTSIZE) env(GDBHISTFILE) } {
|
||||||
set timeout 30
|
set timeout 30
|
||||||
|
|
||||||
# A simple test of operate-and-get-next.
|
# A simple test of operate-and-get-next.
|
||||||
|
@ -192,6 +197,5 @@ save_vars { timeout env(GDBHISTSIZE) env(GDBHISTFILE) } {
|
||||||
"p 7" ".* = 7" \
|
"p 7" ".* = 7" \
|
||||||
"p 8" ".* = 8" \
|
"p 8" ".* = 8" \
|
||||||
"p 9" ".* = 9"
|
"p 9" ".* = 9"
|
||||||
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
return 0
|
|
||||||
|
|
|
@ -4732,10 +4732,9 @@ proc gdb_init { test_file_name } {
|
||||||
# read from this file.
|
# read from this file.
|
||||||
setenv INPUTRC "/dev/null"
|
setenv INPUTRC "/dev/null"
|
||||||
|
|
||||||
# The gdb.base/readline.exp arrow key test relies on the standard VT100
|
# This disables style output, which would interfere with many
|
||||||
# bindings, so make sure that an appropriate terminal is selected.
|
# tests.
|
||||||
# The same bug doesn't show up if we use ^P / ^N instead.
|
setenv TERM "dumb"
|
||||||
setenv TERM "vt100"
|
|
||||||
|
|
||||||
# Some tests (for example gdb.base/maint.exp) shell out from gdb to use
|
# Some tests (for example gdb.base/maint.exp) shell out from gdb to use
|
||||||
# grep. Clear GREP_OPTIONS to make the behavior predictable,
|
# grep. Clear GREP_OPTIONS to make the behavior predictable,
|
||||||
|
|
Loading…
Reference in New Issue