Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Implement support for PowerPC BookE masked and ranged watchpoints
Date: Tue, 02 Nov 2010 03:53:00 -0000	[thread overview]
Message-ID: <83d3qo5qkj.fsf@gnu.org> (raw)
In-Reply-To: <1288648026.3377.7.camel@hactar>

> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 01 Nov 2010 19:47:06 -0200
> 
> What about this?
> 
>   /* The watchpoint will trigger if the address of the memory access is
>      within the defined range, as follows: p.addr <= address < p.addr2.
> 
>      Note that the above sentence just documents how ptrace interprets
>      its arguments; the watchpoint is set to watch the range defined by
>      the user _inclusively_, as specified by the user interface.  */

That's fine, thanks.

> +* GDB now supports ranged watchpoints, which stop the inferior when it
> +  accesses any address within a specified memory range.  See the
> +  documentation on the watch-range command for more information.  The
> +  watchpoint is hardware-accelerated on some targets (currently only when
> +  locally debugging programs on PowerPC BookE processors running a Linux
> +  kernel version 2.6.34 or later.)

The last period should be outside the parentheses.

> +* Also on native debugging on Linux running on PowerPC BookE, GDB supports
          ^^
"for"

> +  masked hardware watchpoints, which specifiy a mask in addition to an
> +  address to watch.  The mask specifies that some bits of an address (the
> +  bits which are reset in the mask) should be ignored when matching the
> +  address accessed by the inferior against the watchpoint address.

A pointer to the corresponding section in the manual would be good
here.

> +watch
> +  The watch command now supports the mask argument which allows creation
> +  of masked watchpoints, if the current architecture supports this feature.

Instead of just "watch", I suggest to show here its form with a mask.

OK with those changes.


  reply	other threads:[~2010-11-02  3:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 19:42 Thiago Jung Bauermann
2010-10-07 14:48 ` Thiago Jung Bauermann
2010-10-23  4:23 ` Thiago Jung Bauermann
2010-10-23  9:07   ` Eli Zaretskii
2010-10-30  1:59     ` Thiago Jung Bauermann
2010-10-30  7:13       ` Eli Zaretskii
2010-11-01 21:47         ` Thiago Jung Bauermann
2010-11-02  3:53           ` Eli Zaretskii [this message]
2010-11-04 21:12             ` Thiago Jung Bauermann
2010-11-16  4:01               ` Jan Kratochvil
2010-11-18 17:26                 ` Joel Brobecker
2010-11-19 19:55                 ` Thiago Jung Bauermann
2010-11-19 23:45                   ` Joel Brobecker
2010-11-22 17:04                     ` Thiago Jung Bauermann
2010-11-22 17:38                       ` Joel Brobecker
2010-11-22 17:46                         ` Jan Kratochvil
2010-11-22 18:37                           ` Joel Brobecker
2010-11-20  5:00                   ` Joel Brobecker
2010-11-23 22:05                     ` Thiago Jung Bauermann

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=83d3qo5qkj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    /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