[pushed,1/3,gdb/testsuite] Consume output asap in gdb.server/multi-ui-errors.exp
Commit Message
With test-case gdb.server/multi-ui-errors.exp we see:
...
(gdb) PASS: multi-ui-errors.exp: main UI, prompt after gdbserver dies
continue^M
Continuing.^M
echo^M
(gdb) PASS: multi-ui-errors.exp: extra UI, prompt after gdbserver dies
...
The continue is issued earlier in the test-case, but the output has not been
consumed, which makes it show up much later.
Consume the continue output asap, to make it clear when the continue is issued:
...
(gdb) PASS: gdb.server/multi-ui-errors.exp: connect to gdbserver
continue^M
Continuing.^M
PASS: gdb.server/multi-ui-errors.exp: continue - extra UI
...
Tested on x86_64-linux.
---
gdb/testsuite/gdb.server/multi-ui-errors.exp | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
@@ -75,7 +75,13 @@ with_spawn_id $extra_spawn_id {
with_spawn_id $extra_spawn_id {
gdb_test "target $gdbserver_protocol $gdbserver_gdbport" ".*" \
"connect to gdbserver"
- send_gdb "continue\n"
+
+ # Issue a continue and consume the response. Don't expect a prompt.
+ gdb_test_multiple "continue" "continue - extra UI" {
+ -re "\r\nContinuing\.\r\n" {
+ pass $gdb_test_name
+ }
+ }
}
# We're going to kill the gdbserver, but before we do, lets make sure