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/30473] Emit DAP Process event
Date: Tue, 28 Nov 2023 15:56:20 +0000 [thread overview]
Message-ID: <bug-30473-4717-Pe4sQSvuK1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30473-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30473
--- Comment #4 from Sourceware Commits <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=14e461bed44258fb872731a79ca5e82b70781d09
commit 14e461bed44258fb872731a79ca5e82b70781d09
Author: Tom Tromey <tromey@adacore.com>
Date: Fri Oct 6 14:30:46 2023 -0600
Emit DAP "process" event
DAP specifies a "process" event that is sent when a process is started
or attached to. gdb was not emitting this (several DAP clients appear
to ignore it entirely), but it looked easy and harmless to implement.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30473
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-28 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 15:07 [Bug dap/30473] New: " tromey at sourceware dot org
2023-10-06 15:55 ` [Bug dap/30473] " tromey at sourceware dot org
2023-10-06 20:30 ` tromey at sourceware dot org
2023-11-14 19:25 ` tromey at sourceware dot org
2023-11-28 15:56 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-28 15:57 ` tromey at sourceware dot org
2023-12-11 15:45 ` cvs-commit at gcc dot gnu.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-30473-4717-Pe4sQSvuK1@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).