public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
Cc: gdb-patches@sourceware.org, blarsen@redhat.com
Subject: Re: [PATCH v2 1/3] gdb, gdbserver, zpoint: report z_point support
Date: Tue, 14 Nov 2023 14:50:37 +0200	[thread overview]
Message-ID: <835y24ts6a.fsf@gnu.org> (raw)
In-Reply-To: <20231114092029.31205-2-mohamed.bouhaouel@intel.com> (message from Mohamed Bouhaouel on Tue, 14 Nov 2023 10:20:27 +0100)

> From: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
> Cc: blarsen@redhat.com,
> 	mohamed.bouhaouel@intel.com
> Date: Tue, 14 Nov 2023 10:20:27 +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)
> ---
>  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.

> diff --git a/gdb/NEWS b/gdb/NEWS
> index 682def44ce0..8146f695df3 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -49,6 +49,10 @@ QThreadOptions in qSupported
>    QThreadOptions packet, and the qSupported response can contain the
>    set of thread options the remote stub supports.
>  
> +qSupported
> +  Gdbserver now reports which types of breakpoints and watchpoints
> +  are supported when exchanging features using Z<type>+, Z<type>-.
> +
>  *** Changes in GDB 14

This part is OK.

> +@item Z@var{type}
> +The remote stub reports which types of breakpoints and watchpoints are
> +supported.  This is done using flags, @samp{Z}@var{type}@samp{+} for supported
                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^
This should be @samp{Z@var{type}+}.  IOW, @var can be nested inside @samp.

> +and @samp{Z}@var{type}@samp{-} for unsupported, where @var{type} is one of
       ^^^^^^^^^^^^^^^^^^^^^^^^^^
Same here.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2023-11-14 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  9:20 [PATCH v2 0/3] Check for zpoint support when handling watchpoints Mohamed Bouhaouel
2023-11-14  9:20 ` [PATCH v2 1/3] gdb, gdbserver, zpoint: report z_point support Mohamed Bouhaouel
2023-11-14 12:50   ` Eli Zaretskii [this message]
2023-11-14  9:20 ` [PATCH v2 2/3] gdb, breakpoint: add a breakpoint type converter Mohamed Bouhaouel
2023-11-14  9:20 ` [PATCH v2 3/3] gdb, zpoint: check for target hardware breakpoint support Mohamed Bouhaouel

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=835y24ts6a.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).