From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Simplify DAP stop reason emission
Date: Tue, 14 Nov 2023 11:44:02 -0700 [thread overview]
Message-ID: <20231114-py-stop-reason-v1-0-4ff440c956a9@adacore.com> (raw)
This patch changes the DAP stop-reason emission to be simpler (on the
DAP side) and also more reliable. Rather than guessing that a stop
occurred because a "step" finished, the DAP code now relies on gdb's
own knowledge of this.
---
Tom Tromey (3):
Move py_ui_out to a new header
Emit stop reason details in Python stop events
Simplify DAP stop-reason code
gdb/NEWS | 4 +
gdb/doc/python.texi | 11 +++
gdb/python/lib/gdb/dap/events.py | 79 ++++++++++++--------
gdb/python/lib/gdb/dap/launch.py | 4 +-
gdb/python/lib/gdb/dap/next.py | 10 +--
gdb/python/lib/gdb/dap/pause.py | 4 +-
gdb/python/py-bpevent.c | 5 +-
gdb/python/py-mi.c | 131 +--------------------------------
gdb/python/py-signalevent.c | 5 +-
gdb/python/py-stopevent.c | 65 +++++++++++++++--
gdb/python/py-stopevent.h | 9 ++-
gdb/python/py-uiout.h | 153 +++++++++++++++++++++++++++++++++++++++
12 files changed, 299 insertions(+), 181 deletions(-)
---
base-commit: c748dbd95bf3305539956053c2a25ecea7b442a5
change-id: 20231114-py-stop-reason-3f141487d90e
Best regards,
--
Tom Tromey <tromey@adacore.com>
next reply other threads:[~2023-11-14 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 18:44 Tom Tromey [this message]
2023-11-14 18:44 ` [PATCH 1/3] Move py_ui_out to a new header Tom Tromey
2023-11-14 18:44 ` [PATCH 2/3] Emit stop reason details in Python stop events Tom Tromey
2023-11-14 19:12 ` Eli Zaretskii
2023-11-14 18:44 ` [PATCH 3/3] Simplify DAP stop-reason code Tom Tromey
2023-12-11 18:42 ` [PATCH 0/3] Simplify DAP stop reason emission 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=20231114-py-stop-reason-v1-0-4ff440c956a9@adacore.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
/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).