This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch 3/3] [RFC] Add the watch-range command
- From: Thiago Jung Bauermann <bauerman at br dot ibm dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sourceware dot org, jan dot kratochvil at redhat dot com, brobecker at adacore dot com
- Date: Sat, 27 Nov 2010 11:30:42 -0200
- Subject: Re: [patch 3/3] [RFC] Add the watch-range command
- References: <1290549386.3164.52.camel@hactar> <83lj4g73a8.fsf@gnu.org>
On Fri, 2010-11-26 at 13:06 +0200, Eli Zaretskii wrote:
> > 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.
Indeed. I'll keep it then.
> > +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.
Ok.
> Okay with those changes.
Thanks!
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center