diff options
author | Tom de Vries <tdevries@suse.de> | 2024-06-12 19:15:45 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2024-06-12 19:15:45 +0200 |
commit | 9a50e260ee1cf3b7e355371f0f4248407101795d (patch) | |
tree | 196dbeee7e8f55938023114d8f08165e16cd82c0 | |
parent | 764af878259768bb70c65bdf3f3285c2d6409bbd (diff) | |
download | gdb-9a50e260ee1cf3b7e355371f0f4248407101795d.zip gdb-9a50e260ee1cf3b7e355371f0f4248407101795d.tar.gz gdb-9a50e260ee1cf3b7e355371f0f4248407101795d.tar.bz2 |
[gdb/testsuite] Fix error in gdb.server/server-kill-python.exp
With test-case gdb.server/server-kill-python.exp, I sometimes run into:
...
builtin_spawn gdb -nw -nx -q -iex set height 0 -iex set width 0 \
-data-directory data-directory^M
kill^M
(gdb) kill^M
file server-kill-python^M
The program is not being run.^M
(gdb) ERROR: Couldn't load server-kill-python into GDB.
...
The problem is that the spawn produces a prompt, but it's not explicitly
consumed.
This is a regression since commit 0f077fcae0f ("[gdb/testsuite] Simplify
gdb.server/server-kill-python.exp").
Fix this by consuming the initial prompt.
PR testsuite/31819
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31819
Fixes: 0f077fcae0f ("[gdb/testsuite] Simplify gdb.server/server-kill-python.exp"
-rw-r--r-- | gdb/testsuite/gdb.server/server-kill-python.exp | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.server/server-kill-python.exp b/gdb/testsuite/gdb.server/server-kill-python.exp index e9066ca..a771e6f 100644 --- a/gdb/testsuite/gdb.server/server-kill-python.exp +++ b/gdb/testsuite/gdb.server/server-kill-python.exp @@ -61,6 +61,12 @@ if {[gdb_spawn]} { return } +gdb_test_multiple "" "initial prompt" { + -re "^$gdb_prompt $" { + pass $gdb_test_name + } +} + gdb_load $binfile gdb_target_cmd $gdbserver_protocol $gdbserver_gdbport |