From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org,
"Kévin Le Gouguec" <legouguec@adacore.com>,
"Eli Zaretskii" <eliz@gnu.org>
Subject: Re: [PATCH v2 0/6] Implement DAP cancellation
Date: Mon, 11 Dec 2023 11:53:58 -0700 [thread overview]
Message-ID: <87fs08efjt.fsf@tromey.com> (raw)
In-Reply-To: <20231211-dap-cancel-v2-0-db7b52cf0329@adacore.com> (Tom Tromey's message of "Mon, 11 Dec 2023 09:02:17 -0700")
>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:
Tom> DAP specifies a way to cancel requests. Previously, I didn't
Tom> implement this, because it didn't seem necessary. However, I realized
Tom> later that a 'repl' evaluation can cause the inferior to continue (or
Tom> gdb to invoke a long-running CLI or Python command), and a request
Tom> like this will not finish -- cancellation is necessary.
Tom> This series implements this feature. I've split it into bite-sized
Tom> pieces.
Tom> Tested on x86-64 Fedora 38.
I'm going to check this in now.
Tom
prev parent reply other threads:[~2023-12-11 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 16:02 Tom Tromey
2023-12-11 16:02 ` [PATCH v2 1/6] Clean up handling of DAP not-stopped response Tom Tromey
2023-12-11 16:02 ` [PATCH v2 2/6] Move DAP JSON reader to its own thread Tom Tromey
2023-12-11 16:02 ` [PATCH v2 3/6] Introduce gdb.interrupt Tom Tromey
2023-12-11 16:30 ` Eli Zaretskii
2023-12-11 16:02 ` [PATCH v2 4/6] Rename a couple of DAP procs in the testsuite Tom Tromey
2023-12-11 16:02 ` [PATCH v2 5/6] Catch KeyboardInterrupt in send_gdb_with_response Tom Tromey
2023-12-11 17:53 ` Kévin Le Gouguec
2023-12-11 16:02 ` [PATCH v2 6/6] Implement DAP cancellation Tom Tromey
2023-12-11 18:53 ` 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=87fs08efjt.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).