From: Eli Zaretskii <eliz@gnu.org>
To: Simon Farre <simon.farre.cx@gmail.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [PATCH v1] gdb/dap - dataBreakpointInfo & setDataBreakpoints
Date: Wed, 14 Jun 2023 14:43:59 +0300 [thread overview]
Message-ID: <83pm5yuv40.fsf@gnu.org> (raw)
In-Reply-To: <20230614103327.30289-1-simon.farre.cx@gmail.com> (message from Simon Farre via Gdb-patches on Wed, 14 Jun 2023 12:33:27 +0200)
> Cc: tom@tromey.com,
> Simon Farre <simon.farre.cx@gmail.com>
> Date: Wed, 14 Jun 2023 12:33:27 +0200
> From: Simon Farre via Gdb-patches <gdb-patches@sourceware.org>
>
> This is v1 of the implementation of these two requests.
I didn't (and cannot) review this in a useful way, but my eye caught a
few nits:
> - if bp.locations:
> + if bp.location is not None:
> # Just choose the first location, because DAP doesn't allow
> # multiple locations. See
> # https://github.com/microsoft/debug-adapter-protocol/issues/13
> + # FIXME this does not matter; GDB can translate it's understanding
^^^^
"its"
> + # frameId does not have an effect when var ref is not none,
^^^^
"None", capitalized?
> + # however, frameId really never has an effect. An issue has been filed:
^^
Two spaces there.
> + # We've resolved the "path" for the variable using varrefs. Construct it
^^
And there.
> + # Delete wps that are not found in `breakpoints` request
^^^^^^^^^^^^^
Are we okay with MD-style markup?
Thanks.
next prev parent reply other threads:[~2023-06-14 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 10:33 Simon Farre
2023-06-14 11:43 ` Eli Zaretskii [this message]
2023-06-14 13:40 ` Simon Farre
2023-06-14 13:58 ` Eli Zaretskii
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=83pm5yuv40.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.farre.cx@gmail.com \
--cc=tom@tromey.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).