public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Pedro Alves <palves@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Improve break-range's documentation
Date: Tue, 31 May 2022 12:22:34 +0000 (GMT)	[thread overview]
Message-ID: <20220531122234.012D53857426@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e595ad4cc20a9b34fbda044b161cc7daccdfcf66

commit e595ad4cc20a9b34fbda044b161cc7daccdfcf66
Author: Pedro Alves <pedro@palves.net>
Date:   Tue May 31 12:18:49 2022 +0100

    Improve break-range's documentation
    
    Change-Id: Iac26e1d2e7d8dc8a7d9516e6bdcc5c3fc4af45c8

Diff:
---
 gdb/doc/gdb.texinfo | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 8c85c5a0c82..f94df686bab 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -25470,7 +25470,7 @@ about the @code{mask} argument in @ref{Set Watchpoints}.
 PowerPC embedded processors support hardware accelerated
 @dfn{ranged breakpoints}.  A ranged breakpoint stops execution of
 the inferior whenever it executes an instruction at any address within
-the range it specifies.  To set a ranged breakpoint in @value{GDBN},
+the range it was set at.  To set a ranged breakpoint in @value{GDBN},
 use the @code{break-range} command.
 
 @value{GDBN} provides the following PowerPC-specific commands:
@@ -25481,12 +25481,14 @@ use the @code{break-range} command.
 Set a breakpoint for an address range given by @var{start-locspec} and
 @var{end-locspec}, which are location specs.  @xref{Location
 Specifications}, for a list of all the possible forms of location
-specs.  If either @var{start-locspec} or @var{end-locspec} resolve to
-multiple addresses in the program, then the command aborts with an
-error without creating a breakpoint.  The breakpoint will stop
-execution of the inferior whenever it executes an instruction at any
-address within the specified range, including @var{start-locspec} and
-@var{end-locspec}.
+specs.  @value{GDBN} resolves both @var{start-locspec} and
+@var{end-locspec}, and uses the addresses of the resolved code
+locations as start and end addresses of the range to break at.  The
+breakpoint will stop execution of the inferior whenever it executes an
+instruction at any address between the start and end addresses,
+inclusive.  If either @var{start-locspec} or @var{end-locspec} resolve
+to multiple code locations in the program, then the command aborts
+with an error without creating a breakpoint.
 
 @kindex set powerpc
 @item set powerpc soft-float


                 reply	other threads:[~2022-05-31 12:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220531122234.012D53857426@sourceware.org \
    --to=palves@sourceware.org \
    --cc=gdb-cvs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).