diff options
author | Tom de Vries <tdevries@suse.de> | 2022-10-14 19:59:26 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2022-10-14 19:59:26 +0200 |
commit | 7c635f3e61e014d713f7fc884215576187fda038 (patch) | |
tree | 0e1d46df8cc4a836b958d8df6c31d96510718713 /gdb/testsuite/lib | |
parent | c4c8c27263d2dd25647314f4897bd01ad1a78847 (diff) | |
download | gdb-7c635f3e61e014d713f7fc884215576187fda038.zip gdb-7c635f3e61e014d713f7fc884215576187fda038.tar.gz gdb-7c635f3e61e014d713f7fc884215576187fda038.tar.bz2 |
[gdb/testsuite] Fix gdb.server/unittest.exp with host board local-remote-host.exp
With test-case gdb.server/unittest.exp and host board local-remote-host.exp I
run into:
...
builtin_spawn build/gdbserver/gdbserver --selftest^M
ERROR: : spawn id exp7 not open
while executing
"expect {
-i exp7 -timeout 10
-i $server_spawn_id
-re "Ran ($decimal) unit tests, 0 failed" {
set num_ran $expect_out(1,string)
gdb_assert "..."
("uplevel" body line 1)
invoked from within
"uplevel $body" NONE : spawn id exp7 not open
UNRESOLVED: gdb.server/unittest.exp: unit tests
...
The problem is (as fixed for avr in commit df5b8876083 ("gdb/testsuite: better
handle failures in simavr board, reap simavr process")), that gdb_expect through
remote_expect adds a "-i <gdb spawn id> -timeout 10", which is the one causing
the error.
As in aforementioned commit, fix this by using expect instead.
Tested on x86_64-linux.
Diffstat (limited to 'gdb/testsuite/lib')
0 files changed, 0 insertions, 0 deletions