diff options
| author | Tom de Vries <tdevries@suse.de> | 2023-03-26 13:44:58 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2023-03-26 13:44:58 +0200 |
| commit | 95e592d9ab1e79272018b8b6b6821bf053cd665b (patch) | |
| tree | 03c325bb6d2f5e1603b6bc333e5347934416eca6 /elfcpp | |
| parent | bc8b216886e01cf6269b72c12e1a92f43b70efc1 (diff) | |
| download | binutils-95e592d9ab1e79272018b8b6b6821bf053cd665b.zip binutils-95e592d9ab1e79272018b8b6b6821bf053cd665b.tar.gz binutils-95e592d9ab1e79272018b8b6b6821bf053cd665b.tar.bz2 | |
[gdb/testsuite] Introduce allow_dap_tests
Simon pointed out that with gdb.dap/*.exp and target board
native-gdbserver, we run into problems.
I see for each test-case:
...
+++ run
Traceback (most recent call last):
File "startup.py", line 146, in exec_and_log
output = gdb.execute(cmd, from_tty=True, to_string=True)
gdb.error: Don't know how to run. Try "help target".
...
Likewise with target board native-extended-gdbserver.
Fix this by:
- adding a new proc allow_dap_tests,
- using it in all the gdb.dap tests, and
- bailing out if GDBFLAGS/INTERNAL_GDBFLAGS contains
"set auto-connect-native-target off".
Tested on x86_64-linux.
Reported-By: Simon Marchi <simon.marchi@efficios.com>
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'elfcpp')
0 files changed, 0 insertions, 0 deletions