public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug dap/30681] New: gdb does not send "terminated" event Date: Tue, 25 Jul 2023 12:47:39 +0000 [thread overview] Message-ID: <bug-30681-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30681 Bug ID: 30681 Summary: gdb does not send "terminated" event Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: dap Assignee: unassigned at sourceware dot org Reporter: tromey at sourceware dot org Target Milestone: --- This comes from https://sourceware.org/bugzilla/show_bug.cgi?id=30678#c1. gdb does not send the DAP "terminated" event. Apparently VSCode needs this to know that debugging is done. The DAP spec seems a little unclear on this point, as it seems to me that the exited event should have been enough... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-07-25 12:47 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-25 12:47 tromey at sourceware dot org [this message] 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 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@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: linkBe 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).