public inbox for
help / color / mirror / Atom feed
From: Enze Li <>
Subject: [binutils-gdb] gdb: update ranged_breakpoint::print_one_detail in comments
Date: Tue, 30 Aug 2022 13:09:51 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=f79688953fb09dbe5c0ecf33a8db15054d49fb8d

commit f79688953fb09dbe5c0ecf33a8db15054d49fb8d
Author: Enze Li <>
Date:   Mon Aug 29 20:15:14 2022 +0800

    gdb: update ranged_breakpoint::print_one_detail in comments
    The print_one_detail_ranged_breakpoint has been renamed to
    ranged_breakpoint::print_one_detail in this commit:
      commit ec45bb676c9c69c30783bcf35ffdac8280f3b8bc
      Date:   Sat Jan 15 16:34:51 2022 -0700
        Convert ranged breakpoints to vtable ops
    So their comments should be updated as well.

 gdb/breakpoint.c | 2 +-
 gdb/breakpoint.h | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 8f0b19f8518..63feea9e9cd 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -9215,7 +9215,7 @@ ranged_breakpoint::print_one (bp_location **last_loc) const
   if (opts.addressprint)
     /* We don't print the address range here, it will be printed later
-       by print_one_detail_ranged_breakpoint.  */
+       by ranged_breakpoint::print_one_detail.  */
     uiout->field_skip ("addr");
   annotate_field (5);
   print_breakpoint_location (this, bl);
diff --git a/gdb/breakpoint.h b/gdb/breakpoint.h
index 93f30c9c13d..360fa760577 100644
--- a/gdb/breakpoint.h
+++ b/gdb/breakpoint.h
@@ -691,7 +691,7 @@ struct breakpoint
      breakpoint description in "info breakpoints".
      In the example below, the "address range" line was printed
-     by print_one_detail_ranged_breakpoint.
+     by ranged_breakpoint::print_one_detail.
      (gdb) info breakpoints
      Num     Type           Disp Enb Address    What

                 reply	other threads:[~2022-08-30 13:09 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).