public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug dap/30681] gdb does not send "terminated" event
Date: Tue, 01 Aug 2023 18:58:18 +0000 [thread overview]
Message-ID: <bug-30681-4717-wkcjj4367y@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30681-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30681
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=21db866dc69c481cd79b4d739c2170a7ef9b98fd
commit 21db866dc69c481cd79b4d739c2170a7ef9b98fd
Author: Tom Tromey <tromey@adacore.com>
Date: Tue Jul 25 09:16:35 2023 -0600
Implement DAP 'terminated' event
This implements the DAP 'terminated' event. Vladimir Makaev noticed
that VSCode will not report the debug session as over unless this is
sent.
It's not completely clear when exactly this event ought to be sent.
Here I've done it when the inferior exits.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30681
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-01 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 12:47 [Bug dap/30681] New: " tromey at sourceware dot org
2023-07-25 13:15 ` [Bug dap/30681] " vmakaev at gmail dot com
2023-07-25 14:42 ` tromey at sourceware dot org
2023-07-25 14:42 ` tromey at sourceware dot org
2023-07-25 21:59 ` vmakaev at gmail dot com
2023-07-26 15:38 ` tromey at sourceware dot org
2023-07-26 15:58 ` tromey at sourceware dot org
2023-07-27 15:27 ` tromey at sourceware dot org
2023-08-01 18:58 ` cvs-commit at gcc dot gnu.org [this message]
2023-08-01 18:58 ` tromey at sourceware dot org
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=bug-30681-4717-wkcjj4367y@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).