diff options
author | Tom de Vries <tdevries@suse.de> | 2021-10-13 11:06:36 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2021-10-13 11:06:36 +0200 |
commit | 7110a5d8e8523b6ecd1d97ab3936cdea03bf7b39 (patch) | |
tree | 9b3ff082eb339e79459a6f4529d328e06a14a84b /gdb | |
parent | 777b054cf93ad2525b891ea15bbf8d5cd6a56339 (diff) | |
download | gdb-7110a5d8e8523b6ecd1d97ab3936cdea03bf7b39.zip gdb-7110a5d8e8523b6ecd1d97ab3936cdea03bf7b39.tar.gz gdb-7110a5d8e8523b6ecd1d97ab3936cdea03bf7b39.tar.bz2 |
[gdb/testsuite] Remove quit in gdb.arch/i386-mpx.exp
When running test-case gdb.arch/i386-mpx.exp with target board
native-gdbserver, I run into:
...
(gdb) PASS: gdb.arch/i386-mpx.exp: verify size for bnd0
Remote debugging from host ::1, port 42328^M
quit^M
A debugging session is active.^M
^M
Inferior 1 [process 19679] will be killed.^M
^M
Quit anyway? (y or n) monitor exit^M
Please answer y or n.^M
A debugging session is active.^M
^M
Inferior 1 [process 19679] will be killed.^M
^M
Quit anyway? (y or n) WARNING: Timed out waiting for EOF in server after monitor exit
...
The problem is that the test-case sends a quit at the end (without verifying
the result of this in any way):
...
send_gdb "quit\n"
...
Fix this by removing the quit.
Tested on x86_64-linux.
Diffstat (limited to 'gdb')
-rw-r--r-- | gdb/testsuite/gdb.arch/i386-mpx.exp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/gdb/testsuite/gdb.arch/i386-mpx.exp b/gdb/testsuite/gdb.arch/i386-mpx.exp index 520fd10..c50685c 100644 --- a/gdb/testsuite/gdb.arch/i386-mpx.exp +++ b/gdb/testsuite/gdb.arch/i386-mpx.exp @@ -134,5 +134,3 @@ if { [skip_python_tests] } { continue } # Verify if size is right set test_string ".*\\\: size 17.*" gdb_test "print /x \$bnd0 = {0x10, 0x20}" "$test_string" "verify size for bnd0" - -send_gdb "quit\n" |