From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Add more DAP launch parameters
Date: Tue, 09 May 2023 10:01:58 -0600 [thread overview]
Message-ID: <20230509-dap-args-v1-0-16b5f0aa5cd6@adacore.com> (raw)
This series adds some more Python attributes (and methods), and then
uses these to implement some new launch parameters for DAP.
Inferior.main_name is added but not used. I plan to use this to
implement a "stop at main" launch parameter, after we work out a few
details. Meanwhile it seemed harmless and potentially useful.
Tom
---
Tom Tromey (2):
Add attributes and methods to gdb.Inferior
Add "args" and "env" parameters to DAP launch request
gdb/NEWS | 10 ++
gdb/doc/gdb.texinfo | 13 ++-
gdb/doc/python.texi | 43 ++++++++
gdb/python/lib/gdb/dap/launch.py | 20 +++-
gdb/python/py-inferior.c | 168 +++++++++++++++++++++++++++++++
gdb/testsuite/gdb.ada/py_range.exp | 4 +
gdb/testsuite/gdb.dap/args-env.c | 28 ++++++
gdb/testsuite/gdb.dap/args-env.exp | 90 +++++++++++++++++
gdb/testsuite/gdb.python/py-inferior.exp | 36 +++++++
gdb/testsuite/lib/dap-support.exp | 39 +++++--
10 files changed, 439 insertions(+), 12 deletions(-)
---
base-commit: d9cc4b060dd23724e1acf974aed3d1b72c8459e5
change-id: 20230509-dap-args-596e21f0b48d
Best regards,
--
Tom Tromey <tromey@adacore.com>
next reply other threads:[~2023-05-09 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 16:01 Tom Tromey [this message]
2023-05-09 16:01 ` [PATCH 1/2] Add attributes and methods to gdb.Inferior Tom Tromey
2023-05-09 16:15 ` Eli Zaretskii
2023-05-17 15:45 ` Tom Tromey
2023-05-10 10:17 ` Andrew Burgess
2023-05-17 15:32 ` Tom Tromey
2023-05-09 16:02 ` [PATCH 2/2] Add "args" and "env" parameters to DAP launch request Tom Tromey
2023-05-09 16:10 ` Eli Zaretskii
2023-05-16 19:06 ` Tom Tromey
2023-05-16 19:10 ` Eli Zaretskii
2023-05-16 19:20 ` Eli Zaretskii
2023-05-10 12:39 ` Andrew Burgess
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=20230509-dap-args-v1-0-16b5f0aa5cd6@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).