public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>
Cc: gdb-patches@sourceware.org,  blarsen@redhat.com,  eliz@gnu.org
Subject: Re: [PATCH v3 1/3] gdb, gdbserver, zpoint: report z_point support
Date: Tue, 14 Nov 2023 07:36:13 -0700	[thread overview]
Message-ID: <87jzqkqu5e.fsf@tromey.com> (raw)
In-Reply-To: <20231114133532.3877-2-mohamed.bouhaouel@intel.com> (Mohamed Bouhaouel's message of "Tue, 14 Nov 2023 14:35:30 +0100")

>>>>> Mohamed Bouhaouel <mohamed.bouhaouel@intel.com> writes:

> 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)

Thanks for the patch.

I suppose the idea is that this work can't really be done on the gdb
side, because gdb creates the watchpoint and such earlier, and only then
tries to communicate with the remote... so errors come too late?

> +@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}+} for supported

I think this part of the docs should mention that the 'Z' response
assumes that both of the corresponding 'z' and 'Z' packets are
supported.

> +  return (m_features.packet_support (PACKET_Z0 + packet) != PACKET_DISABLE);

Too many parens.

> +/* Returns true if Z_TYPE is supported by the target.  */
> +
> +int z_type_supported (char z_type);
>  #endif /* GDBSERVER_MEM_BREAK_H */

Should have a newline before the #endif.

Tom

  parent reply	other threads:[~2023-11-14 14:36 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
2023-11-14 14:36   ` Tom Tromey [this message]
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=87jzqkqu5e.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=blarsen@redhat.com \
    --cc=eliz@gnu.org \
    --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).