From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Implement the DAP "modules" request
Date: Tue, 11 Jul 2023 08:48:51 -0600 [thread overview]
Message-ID: <20230711-dap-modules-v1-0-b4f6067c1b2e@adacore.com> (raw)
This series implements the DAP "modules" request.
---
Tom Tromey (3):
Remove unused imports
Add Progspace.objfile_for_address
Implement DAP modules request
gdb/NEWS | 3 ++
gdb/data-directory/Makefile.in | 1 +
gdb/doc/python.texi | 6 +++
gdb/progspace.c | 16 ++++++
gdb/progspace.h | 4 ++
gdb/python/lib/gdb/dap/__init__.py | 1 +
gdb/python/lib/gdb/dap/bt.py | 10 ++--
gdb/python/lib/gdb/dap/evaluate.py | 1 -
gdb/python/lib/gdb/dap/events.py | 14 ++++++
gdb/python/lib/gdb/dap/modules.py | 64 ++++++++++++++++++++++++
gdb/python/py-progspace.c | 27 +++++++++++
gdb/testsuite/gdb.dap/modules-solib.c | 21 ++++++++
gdb/testsuite/gdb.dap/modules.c | 40 +++++++++++++++
gdb/testsuite/gdb.dap/modules.exp | 81 +++++++++++++++++++++++++++++++
gdb/testsuite/gdb.python/py-progspace.exp | 7 +++
15 files changed, 291 insertions(+), 5 deletions(-)
---
base-commit: 034b6bec547084b19e39b051b3dbab7f9b8b4f23
change-id: 20230711-dap-modules-a1027c03bc1c
Best regards,
--
Tom Tromey <tromey@adacore.com>
next reply other threads:[~2023-07-11 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 14:48 Tom Tromey [this message]
2023-07-11 14:48 ` [PATCH 1/3] Remove unused imports Tom Tromey
2023-07-11 14:48 ` [PATCH 2/3] Add Progspace.objfile_for_address Tom Tromey
2023-07-11 15:51 ` Eli Zaretskii
2023-07-21 15:48 ` Tom Tromey
2023-07-11 14:48 ` [PATCH 3/3] Implement DAP modules request Tom Tromey
2023-07-12 14:42 ` [PATCH 0/3] Implement the DAP "modules" request Alexandra Petlanova Hajkova
2023-07-21 18:05 ` 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=20230711-dap-modules-v1-0-b4f6067c1b2e@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).