From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org, "Eli Zaretskii" <eliz@gnu.org>,
"Kévin Le Gouguec" <legouguec@adacore.com>
Subject: Re: [PATCH v2 0/2] Add "finish" return value to DAP
Date: Fri, 08 Mar 2024 10:49:33 -0700 [thread overview]
Message-ID: <878r2sr4uq.fsf@tromey.com> (raw)
In-Reply-To: <20240213-dap-finish-v2-0-d507b889d735@adacore.com> (Tom Tromey's message of "Tue, 13 Feb 2024 09:58:52 -0700")
>>>>> Tom Tromey <tromey@adacore.com> writes:
> 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.
I'm checking this in now.
Tom
prev parent reply other threads:[~2024-03-08 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 16:58 Tom Tromey
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 ` Tom Tromey [this message]
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=878r2sr4uq.fsf@tromey.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).