binutils-gdb

Files

Tom de Vries 95e592d9ab [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>

2023-03-26 13:44:58 +02:00

basic-dap.c

gdb: update some copyright years (2022 -> 2023)

2023-03-01 20:54:56 -05:00

basic-dap.exp

[gdb/testsuite] Introduce allow_dap_tests

2023-03-26 13:44:58 +02:00

bt-inner.c

Fix DAP stackTrace through frames without debuginfo

2023-03-06 08:15:04 -07:00

bt-main.c

Fix DAP stackTrace through frames without debuginfo