From: Tom Tromey <tom@tromey.com>
To: Simon Farre via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Simon Farre <simon.farre.cx@gmail.com>
Subject: Re: [PATCH v2] gdb/dap - dataBreakpointInfo & setDataBreakpoints
Date: Tue, 12 Sep 2023 11:08:10 -0600 [thread overview]
Message-ID: <874jjzjp51.fsf@tromey.com> (raw)
In-Reply-To: <2f655b81-4496-1c07-94ab-e1046a0b2015@gmail.com> (Simon Farre via Gdb-patches's message of "Sun, 18 Jun 2023 00:47:18 +0200")
>>>>> "Simon" == Simon Farre via Gdb-patches <gdb-patches@sourceware.org> writes:
Sorry I didn't reply to this one earlier.
Simon> I'll kill the comments about breakpoints being translated - I wanted
Simon> to be able to enable/disable individual breakpoint locations created
Simon> by GDB, but that perhaps might not be the goal/scope of the
Simon> DAP-interpreters initial feature?
Unfortunately DAP doesn't really admit the possibility that a breakpoint
has multiple locations. This is here:
https://github.com/microsoft/debug-adapter-protocol/issues/114
... but it hasn't seen any action in a while.
Tom
prev parent reply other threads:[~2023-09-12 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 18:28 Simon Farre
2023-06-16 18:14 ` Tom Tromey
2023-06-17 22:47 ` Simon Farre
2023-09-12 17:08 ` 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=874jjzjp51.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.farre.cx@gmail.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).