public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Guinevere Larsen <blarsen@redhat.com>
To: Mohamed Bouhaouel <mohamed.bouhaouel@intel.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] Check for zpoint support when handling watchpoints
Date: Tue, 7 Nov 2023 11:48:49 +0100	[thread overview]
Message-ID: <96089c9b-7c89-dbea-d0ae-15bfaada00ed@redhat.com> (raw)
In-Reply-To: <20230328115449.6526-1-mohamed.bouhaouel@intel.com>

On 28/03/2023 13:54, Mohamed Bouhaouel via Gdb-patches wrote:
> Hi all,
>
> This set of patches improves the flow of inserting a watchpoint or a
> hardware breakpoint.  It consists of checking whether the target
> supports the z_point before doing the actual insertion.  Having such a
> flow would avoid unnecessary too many warning messages, not
> increment the breakpoint counter when not supported, and prevent
> commands from being aborted upon resuming.
>
> Below are the behaviors, with and without the patches, of trying to
> insert a hardware watchpoint when the target does not support that.
>
> * Original behavior
>
> (gdb) awatch dim0
> Hardware watchpoint 2: dim0
> Warning:
> Could not insert hardware watchpoint 2.
> Could not insert hardware breakpoints:
> You may have requested too many hardware breakpoints/watchpoint.
>
> (gdb) continue
> Hardware watchpoint 2: dim0
> Warning:
> Could not insert hardware watchpoint 2.
> Could not insert hardware breakpoints:
> You may have requested too many hardware breakpoints/watchpoint.
>
> Command aborted.
> (gdb)
>
> The warning messages keep popping up on each resume command (`continue`,
> `step`, ...) until the user manually deletes the watchpoint.
>
> * With patches applied
>
> (gdb) awatch dim0
> Target does not support this type of hardware watchpoint.
> (gdb)
Hi Mohamed!

Thanks for working on this, and sorry for the horrible delay in getting 
a review. I read through the series, and patches 2 and 3 look fine, you 
can add my review tag to them. My comments about patch 1 were sent in 
reply to that.

I hope some maintainer looks at this soon!
Reviewed-By: Guinevere Larsen <blarsen@redhat.com>

-- 
Cheers,
Guinevere Larsen
She/Her/Hers

>
> Regards,
> Mohamed
>
> Mohamed Bouhaouel (3):
>    gdb, gdbserver, zpoint: report z_point support
>    gdb, breakpoint: add a breakpoint type converter
>    gdb, zpoint: check for target hardware breakpoint support
>
>   gdb/breakpoint.c       | 20 ++++++++++++++++++++
>   gdb/breakpoint.h       |  3 +++
>   gdb/remote.c           | 41 ++++++++++++++++++++++++++++++++++++++---
>   gdbserver/mem-break.cc |  2 +-
>   gdbserver/mem-break.h  |  4 ++++
>   gdbserver/server.cc    |  7 +++++++
>   6 files changed, 73 insertions(+), 4 deletions(-)
>


      parent reply	other threads:[~2023-11-07 10:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 11:54 Mohamed Bouhaouel
2023-03-28 11:54 ` [PATCH 1/3] gdb, gdbserver, zpoint: report z_point support Mohamed Bouhaouel
2023-11-07 10:41   ` Guinevere Larsen
2023-03-28 11:54 ` [PATCH 2/3] gdb, breakpoint: add a breakpoint type converter Mohamed Bouhaouel
2023-03-28 11:54 ` [PATCH 3/3] gdb, zpoint: check for target hardware breakpoint support Mohamed Bouhaouel
2023-11-07 10:48 ` Guinevere Larsen [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=96089c9b-7c89-dbea-d0ae-15bfaada00ed@redhat.com \
    --to=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).