From: Eli Zaretskii <eliz@gnu.org>
To: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
Cc: gdb-patches@sourceware.org, blarsen@redhat.com
Subject: Re: [PATCH v3 1/3] gdb, gdbserver, zpoint: report z_point support
Date: Tue, 14 Nov 2023 15:45:48 +0200 [thread overview]
Message-ID: <831qcstpmb.fsf@gnu.org> (raw)
In-Reply-To: <20231114133532.3877-2-mohamed.bouhaouel@intel.com> (message from Mohamed Bouhaouel on Tue, 14 Nov 2023 14:35:30 +0100)
> From: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
> Cc: blarsen@redhat.com,
> mohamed.bouhaouel@intel.com,
> eliz@gnu.org
> Date: Tue, 14 Nov 2023 14:35:30 +0100
>
> Make gdbserver report which types of breakpoints and watchpoints
> are supported when exchanging features. This is done by replying with
> Z<type>+ (Supported) or Z<type>- (unsupported)
>
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
> ---
> gdb/NEWS | 4 ++++
> gdb/doc/gdb.texinfo | 32 ++++++++++++++++++++++++++++++++
> gdb/remote.c | 16 ++++++++++++++++
> gdbserver/mem-break.cc | 2 +-
> gdbserver/mem-break.h | 4 ++++
> gdbserver/server.cc | 7 +++++++
> 6 files changed, 64 insertions(+), 1 deletion(-)
Thanks, the documentation parts are okay.
next prev parent reply other threads:[~2023-11-14 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 13:35 [PATCH v3 0/3] Check for zpoint support when handling watchpoints Mohamed Bouhaouel
2023-11-14 13:35 ` [PATCH v3 1/3] gdb, gdbserver, zpoint: report z_point support Mohamed Bouhaouel
2023-11-14 13:45 ` Eli Zaretskii [this message]
2023-11-14 14:36 ` Tom Tromey
2023-11-15 17:31 ` Bouhaouel, Mohamed
2023-11-14 13:35 ` [PATCH v3 2/3] gdb, breakpoint: add a breakpoint type converter Mohamed Bouhaouel
2023-11-14 14:37 ` Tom Tromey
2023-11-15 17:44 ` Bouhaouel, Mohamed
2023-11-14 13:35 ` [PATCH v3 3/3] gdb, zpoint: check for target hardware breakpoint support Mohamed Bouhaouel
2023-11-14 14:45 ` Tom Tromey
2023-11-15 18:18 ` Bouhaouel, Mohamed
2023-11-17 13:42 ` Tom Tromey
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=831qcstpmb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mohamed.bouhaouel@intel.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).