From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: "Eli Zaretskii" <eliz@gnu.org>,
"Kévin Le Gouguec" <legouguec@adacore.com>
Subject: [PATCH v2 0/2] Add "finish" return value to DAP
Date: Tue, 13 Feb 2024 09:58:52 -0700 [thread overview]
Message-ID: <20240213-dap-finish-v2-0-d507b889d735@adacore.com> (raw)
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.
---
Changes in v2:
- Simplified _FinishScopeReference per review
- Link to v1: https://inbox.sourceware.org/gdb-patches/20240212-dap-finish-v1-0-8e30870e8b25@adacore.com
---
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 | 39 +++++++++++++++++-
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, 205 insertions(+), 20 deletions(-)
---
base-commit: a16034bf6417dc2259fef43fd5bcc2dd1dac562f
change-id: 20240212-dap-finish-e2b2d748801e
Best regards,
--
Tom Tromey <tromey@adacore.com>
next reply other threads:[~2024-02-13 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 16:58 Tom Tromey [this message]
2024-02-13 16:58 ` [PATCH v2 1/2] Export "finish" return value to Python Tom Tromey
2024-02-13 16:58 ` [PATCH v2 2/2] Add return value to DAP scope Tom Tromey
2024-03-08 17:49 ` [PATCH v2 0/2] Add "finish" return value to DAP Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240213-dap-finish-v2-0-d507b889d735@adacore.com \
--to=tromey@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=legouguec@adacore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).