[PATCH 0/2] Add "finish" return value to DAP

[Tom Tromey]

This short series changes the DAP code so that it can access the
return value from a "finish" ("stepOut" in DAP parlance) command.  It
turns out that the current DAP convention is to put this value into
the local variables of the outermost scope.

---
Tom Tromey (2):
      Export "finish" return value to Python
      Add return value to DAP scope

 gdb/doc/python.texi                |  6 +++
 gdb/infcmd.c                       | 17 --------
 gdb/python/lib/gdb/dap/events.py   |  3 ++
 gdb/python/lib/gdb/dap/scopes.py   | 45 ++++++++++++++++++++-
 gdb/python/py-stopevent.c          | 23 ++++++++++-
 gdb/testsuite/gdb.dap/step-out.c   | 36 +++++++++++++++++
 gdb/testsuite/gdb.dap/step-out.exp | 82 ++++++++++++++++++++++++++++++++++++++
 gdb/thread-fsm.h                   | 19 +++++++++
 8 files changed, 211 insertions(+), 20 deletions(-)
---
base-commit: 25558d2fc0e8b77d4c522c322012b048db4c1485
change-id: 20240212-dap-finish-e2b2d748801e

Best regards,
-- 
Tom Tromey <tromey@adacore.com>