aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2023-10-06 14:30:46 -0600
committerTom Tromey <tromey@adacore.com>2023-11-28 08:47:24 -0700
commit14e461bed44258fb872731a79ca5e82b70781d09 (patch)
tree0f45c44bf05cf747247fa72d9e061a3f938b300c /gdb/testsuite
parent1f6ce803887ac8da6d4b5903fa270dfa63c63bbf (diff)
downloadgdb-14e461bed44258fb872731a79ca5e82b70781d09.zip
gdb-14e461bed44258fb872731a79ca5e82b70781d09.tar.gz
gdb-14e461bed44258fb872731a79ca5e82b70781d09.tar.bz2
Emit DAP "process" event
DAP specifies a "process" event that is sent when a process is started or attached to. gdb was not emitting this (several DAP clients appear to ignore it entirely), but it looked easy and harmless to implement. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30473
Diffstat (limited to 'gdb/testsuite')
-rw-r--r--gdb/testsuite/gdb.dap/pause.exp2
1 files changed, 2 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.dap/pause.exp b/gdb/testsuite/gdb.dap/pause.exp
index 30ce609..1b65dca 100644
--- a/gdb/testsuite/gdb.dap/pause.exp
+++ b/gdb/testsuite/gdb.dap/pause.exp
@@ -42,6 +42,8 @@ dap_check_request_and_response "set conditional breakpoint" \
[list s $srcfile] $line]
dap_check_request_and_response "start inferior" configurationDone
+dap_wait_for_event_and_check "process event generated" process \
+ "body startMethod" process
dap_wait_for_event_and_check "inferior started" thread "body reason" started
set resp [lindex [dap_request_and_response evaluate {o expression [s 23]}] \