diff options
author | Tom de Vries <tdevries@suse.de> | 2023-03-13 17:20:09 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2023-03-13 17:20:09 +0100 |
commit | ed7d5797b56e8b771d5f7553738f790819d96b6f (patch) | |
tree | 9abe25130b8e931a3fd042c6fef42aaa21bb9a85 /gdb/python | |
parent | 275589d9a0fda6fe898aae678588bb3841d3fed1 (diff) | |
download | binutils-ed7d5797b56e8b771d5f7553738f790819d96b6f.zip binutils-ed7d5797b56e8b771d5f7553738f790819d96b6f.tar.gz binutils-ed7d5797b56e8b771d5f7553738f790819d96b6f.tar.bz2 |
[gdb/testsuite] Fix untested message in gdb.tui/corefile-run.exp
In test-case gdb.tui/corefile-run.exp, we have this bit:
...
require !use_gdb_stub
if { [target_info gdb_protocol] == "extended-remote" } {
untested "not supported"
return
}
...
So with target board native-gdbserver we get:
...
UNSUPPORTED: gdb.tui/corefile-run.exp: require failed: !use_gdb_stub
...
and with target board native-extended-gdbserver instead:
...
UNTESTED: gdb.tui/corefile-run.exp: not supported
...
Fix this by:
- adding an optional argument target_description to proc
target_can_use_run_cmd
- handling the target_description == core &&
[target_info gdb_protocol] == "extended-remote" case in the proc
- using require {target_can_use_run_cmd core}
such that now in both cases we have:
...
UNSUPPORTED: gdb.tui/corefile-run.exp: require failed: \
target_can_use_run_cmd core
...
Tested on x86_64-linux.
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions