From: Johan Sternerup <johan.sternerup@gmail.com>
To: gdb-patches@sourceware.org
Cc: tom@tromey.com, Johan Sternerup <johan.sternerup@gmail.com>
Subject: [PATCH v3 0/3] DAP: Handle "stepOut" request in outermost frame
Date: Sat, 1 Jun 2024 18:16:29 +0200 [thread overview]
Message-ID: <20240601161632.232516-1-johan.sternerup@gmail.com> (raw)
Add support for stepping commands to be run as background tasks so that
immediate errors can be caught and reported back to the client.
Specifically, make use of this for "stepOut" so that in the case of trying to
send a "stepOut" request in the outermost frame we can now report the error back
to the client. Then the client knows that it should still expect the inferior to
be stopped and should not wait for a stoppedEvent.
Johan Sternerup (3):
DAP: Allow for deferring stop events from gdb thread
DAP: Allow gdb exception in exec_and_log to propagate
DAP: Handle "stepOut" request in outermost frame
gdb/python/lib/gdb/dap/events.py | 8 ++---
gdb/python/lib/gdb/dap/next.py | 4 +--
gdb/python/lib/gdb/dap/server.py | 54 +++++++++++++++++++++++++++---
gdb/python/lib/gdb/dap/startup.py | 9 +++--
gdb/testsuite/gdb.dap/step-out.exp | 11 ++++++
5 files changed, 72 insertions(+), 14 deletions(-)
--
2.34.1
next reply other threads:[~2024-06-01 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 16:16 Johan Sternerup [this message]
2024-06-01 16:16 ` [PATCH 1/3] DAP: Allow for deferring stop events from gdb thread Johan Sternerup
2024-06-01 16:16 ` [PATCH 2/3] DAP: Allow gdb exception in exec_and_log to propagate Johan Sternerup
2024-06-01 16:16 ` [PATCH 3/3] DAP: Handle "stepOut" request in outermost frame Johan Sternerup
2024-06-04 14:01 ` [PATCH v3 0/3] " Tom Tromey
2024-06-05 13:54 ` Johan Sternerup
2024-06-05 16:01 ` Tom Tromey
2024-06-06 17:03 ` 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=20240601161632.232516-1-johan.sternerup@gmail.com \
--to=johan.sternerup@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).