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: gdb-patches@sourceware.org
Subject: Re: [doc] Mention accelerated watchpoint conditions in the gdb manual
Date: Tue, 17 Aug 2010 20:19:00 -0000	[thread overview]
Message-ID: <1282076384.2606.715.camel@hactar> (raw)
In-Reply-To: <83vd79qaje.fsf@gnu.org>

On Tue, 2010-08-17 at 22:55 +0300, Eli Zaretskii wrote:
> > From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> > Date: Tue, 17 Aug 2010 16:40:39 -0300
> > 
> > I mentioned this feature in the NEWS file but I just realized that it
> > would be useful to mention in the manual too. Ok to apply? For the
> > branch too?
> 
> Yes and yes.  Thanks.

Thanks!

> > +@smallexample
> > +(@value{GDBP}) watch @var{ADDRESS|VARIABLE} if  @var{ADDRESS|VARIABLE} == @var{CONSTANT EXPRESSION}
> > +@end smallexample
> 
> Please break the long line in two: it's too long and will overflow the
> page boundary in the printed manual.

I had tested this on gdb.pdf and the generated line is shorter than the
surrounding paragraphs. Though I just checked gdb.info and the line ends
at column 77, which is larger than the surrounding paragraphs...

> Also, please add a "@cindex DVC register" entry here.

Done.

What about this version? The broken line shows up nicely in both gdb.pdf
and gdb.info.
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


2010-08-17  Thiago Jung Bauermann  <bauerman@br.ibm.com>

	* gdb.texinfo (PowerPC Embedded): Mention support for the DVC register.

Index: gdb.git/gdb/doc/gdb.texinfo
===================================================================
--- gdb.git.orig/gdb/doc/gdb.texinfo	2010-08-17 17:05:08.000000000 -0300
+++ gdb.git/gdb/doc/gdb.texinfo	2010-08-17 17:09:50.000000000 -0300
@@ -18472,6 +18472,19 @@ Set suspend trace mode.
 @node PowerPC Embedded
 @subsection PowerPC Embedded
 
+@cindex DVC register
+@value{GDBN} supports using the DVC (Data Value Compare) register to
+implement in hardware simple hardware watchpoint conditions of the form:
+
+@smallexample
+(@value{GDBP}) watch @var{ADDRESS|VARIABLE} \
+  if  @var{ADDRESS|VARIABLE} == @var{CONSTANT EXPRESSION}
+@end smallexample
+
+The DVC register will be automatically used whenever @value{GDBN} detects
+such pattern in a condition expression.  This feature is available in native
+@value{GDBN} running on a Linux kernel version 2.6.34 or newer.
+
 @value{GDBN} provides the following PowerPC-specific commands:
 
 @table @code



  reply	other threads:[~2010-08-17 20:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 19:40 Thiago Jung Bauermann
2010-08-17 19:57 ` Eli Zaretskii
2010-08-17 20:19   ` Thiago Jung Bauermann [this message]
2010-08-17 20:36     ` Eli Zaretskii
2010-08-18 18:14       ` 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=1282076384.2606.715.camel@hactar \
    --to=bauerman@br.ibm.com \
    --cc=eliz@gnu.org \
    --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