OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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.
This commit is contained in:
Sandra Loosemore 2019-08-15 10:17:54 -07:00
parent d59b55f095
commit 835b995b57
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,8 @@
2019-08-15 Sandra Loosemore <sandra@codesourcery.com>
* gdb.base/batch-preserve-term-settings.exp
(test_terminal_settings_preserved_after_sigterm): Skip on Windows.
2019-08-15 Christian Biesinger <cbiesinger@google.com>
* lib/gdb.exp: When running on a mingw target, replace

7
gdb/testsuite/gdb.base/batch-preserve-term-settings.exp
View File

@ -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
}