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, jan.kratochvil@redhat.com,
	brobecker@adacore.com
Subject: Re: [patch 3/3] [RFC] Add the watch-range command
Date: Fri, 26 Nov 2010 11:04:00 -0000	[thread overview]
Message-ID: <83lj4g73a8.fsf@gnu.org> (raw)
In-Reply-To: <1290549386.3164.52.camel@hactar>

> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
>         Joel Brobecker
>  <brobecker@adacore.com>, Eli Zaretskii <eliz@gnu.org>
> Date: Tue, 23 Nov 2010 19:56:26 -0200
> 
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -18720,19 +18720,26 @@ the @code{watch} command (@pxref{Set Watchpoints}), as in:
>  @end smallexample
>  
>  A @dfn{ranged watchpoint} watches a contiguous range of addresses.
> -@value{GDBN} automatically creates a ranged watchpoint when asked to watch
> -an array or struct of known size and there are enough hardware registers
> -available.  You can create an artificial array to watch an arbitrary memory
> -region using one of the following commands (@pxref{Expressions}):
> -
> -@smallexample
> -(@value{GDBP}) watch *((char *) @var{ADDRESS})@@@var{LENGTH}
> -(@value{GDBP}) watch @{char[@var{LENGTH}]@} @var{ADDRESS}
> -@end smallexample

Why remove this example?  I think it's useful.

> +Set a hardware watchpoint for an address range.
> +The watchpoint will stop execution of your program whenever the inferior
> +writes, reads, or accesses (respectively for watch-range, awatch-range
> +and rwatch-range) any address within the specified range.

Suggest to say that the range is inclusive.

Okay with those changes.

Thanks.


  reply	other threads:[~2010-11-26 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 21:56 Thiago Jung Bauermann
2010-11-26 11:04 ` Eli Zaretskii [this message]
2010-11-27 13:30   ` 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=83lj4g73a8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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