aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base
diff options
context:
space:
mode:
authorSandra Loosemore <sandra@codesourcery.com>2019-08-15 10:17:54 -0700
committerSandra Loosemore <sandra@codesourcery.com>2019-08-15 10:41:58 -0700
commit835b995b576d14fa9b73fb763d5186323b1365b6 (patch)
treee719e8f125efc8a72b509729272fe2d2768242cb /gdb/testsuite/gdb.base
parentd59b55f0952e95fdbec58021cecce85f4557b485 (diff)
downloadgdb-835b995b576d14fa9b73fb763d5186323b1365b6.zip
gdb-835b995b576d14fa9b73fb763d5186323b1365b6.tar.gz
gdb-835b995b576d14fa9b73fb763d5186323b1365b6.tar.bz2
Skip batch-preserve-term-settings.exp tests that cannot work on Windows.
This group of tests assume that the gdb "shell" command launches a POSIX-compliant shell supporting the PPID environment variable, which is used to get gdb's pid for killing it from a remote_exec shell. But on Windows host "shell" launches cmd.exe, which doesn't have an equivalent query. 2019-08-15 Sandra Loosemore <sandra@codesourcery.com> gdb/testsuite/ * gdb.base/batch-preserve-term-settings.exp (test_terminal_settings_preserved_after_sigterm): Skip on Windows.
Diffstat (limited to 'gdb/testsuite/gdb.base')
-rw-r--r--gdb/testsuite/gdb.base/batch-preserve-term-settings.exp7
1 files changed, 7 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.base/batch-preserve-term-settings.exp b/gdb/testsuite/gdb.base/batch-preserve-term-settings.exp
index ebb494b..27b7a7a 100644
--- a/gdb/testsuite/gdb.base/batch-preserve-term-settings.exp
+++ b/gdb/testsuite/gdb.base/batch-preserve-term-settings.exp
@@ -273,6 +273,13 @@ proc test_terminal_settings_preserved_after_sigterm { } {
global gdb_prompt
global shell_prompt_re
+ # On Windows, GDB's "shell" command spawns cmd.exe, which does not
+ # understand PPID. So we're out of luck even if the test harness
+ # uses a remote_exec shell with a working "kill" command.
+ if [ishost *-*-mingw*] {
+ return
+ }
+
if ![spawn_shell] {
return
}