Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org,
	       jan.kratochvil@redhat.com, brobecker@adacore.com
Subject: Re: [patch 2/3] Implement support for PowerPC BookE ranged watchpoints
Date: Thu, 23 Dec 2010 20:17:00 -0000	[thread overview]
Message-ID: <1293132697.14239.36.camel@hactar> (raw)
In-Reply-To: <83tyi4e2fk.fsf@gnu.org>

Hi Eli,

On Thu, 2010-12-23 at 21:04 +0200, Eli Zaretskii wrote:
> > From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> > Cc: gdb-patches@sourceware.org, Jan Kratochvil <jan.kratochvil@redhat.com>,
> >         Joel Brobecker <brobecker@adacore.com>, Eli Zaretskii <eliz@gnu.org>
> > Date: Thu, 23 Dec 2010 16:49:42 -0200
> > 
> > +When running on PowerPC embedded processors @value{GDBN} automatically uses
>                                               ^
> Comma here, please.

Fixed.

> > +ranged hardware watchpoints unless the @code{exact-watchpoints} option is on,
>                               ^
> And here.

Fixed

> > +@item set powerpc exact-watchpoints
> > +@itemx show powerpc exact-watchpoints
> > +Allow @value{GDBN} to use only one debug register when watching a variable
> > +of scalar type, thus assuming that all acesses that modify that variable
> > +happen at its starting address.
> 
> I suggest a slight rewording of the last sentence:
> 
>   ... thus assuming that the variable is accessed through the address
>   of its first byte.
> 
> Is that wording accurate?  If it is, the patch for the manual is okay
> with those changes.

Yes, it is accurate. Adopted your wording. Thanks for the super-quick
review!
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


  reply	other threads:[~2010-12-23 19:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 21:52 Thiago Jung Bauermann
2010-11-23 23:17 ` Pedro Alves
2010-11-24 21:06   ` Thiago Jung Bauermann
2010-11-25 17:32     ` Pedro Alves
2010-11-26 11:09       ` Eli Zaretskii
2010-11-27 13:25         ` Thiago Jung Bauermann
2010-11-27 15:28           ` Eli Zaretskii
2010-11-26 21:15       ` Thiago Jung Bauermann
2010-11-27 17:47         ` Pedro Alves
2010-11-27 18:01           ` Pedro Alves
2010-12-09  1:44           ` Thiago Jung Bauermann
2010-12-23 19:07           ` Thiago Jung Bauermann
2010-12-23 19:13             ` Eli Zaretskii
2010-12-23 20:17               ` Thiago Jung Bauermann [this message]
2010-12-23 22:18             ` Pedro Alves
2010-12-24  5:10               ` Joel Brobecker
2010-12-25 14:13               ` Eli Zaretskii
2010-12-27 20:18                 ` Thiago Jung Bauermann
2010-12-28  2:30               ` Thiago Jung Bauermann
2010-12-28  5:47                 ` Joel Brobecker
2010-12-28 16:42                   ` Pedro Alves
2010-12-28 16:10                 ` Pedro Alves
2010-12-29  1:00                   ` Thiago Jung Bauermann
2010-11-26 10:59 ` Eli Zaretskii

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=1293132697.14239.36.camel@hactar \
    --to=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pedro@codesourcery.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