public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Minor fix to Python breakpoint event documentation
Date: Thu,  9 Jun 2022 18:37:31 +0000 (GMT)	[thread overview]
Message-ID: <20220609183731.D529E386DC78@sourceware.org> (raw)

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

commit 1c76a0e2a62191b7a5c0240c7178ed8a4c098fb7
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Jun 9 09:40:51 2022 -0600

    Minor fix to Python breakpoint event documentation
    
    I noticed that the Python event documentation referred to the event's
    "breakpoint" field as a function, whereas it is actually an attribute.
    This patch fixes the error.

Diff:
---
 gdb/doc/python.texi | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index ba5a9b315e1..aaf7666e0be 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -3448,9 +3448,9 @@ A sequence containing references to all the breakpoints (type
 @end defvar
 
 @defvar BreakpointEvent.breakpoint
-A reference to the first breakpoint that was hit.
-This function is maintained for backward compatibility and is now deprecated 
-in favor of the @code{gdb.BreakpointEvent.breakpoints} attribute.
+A reference to the first breakpoint that was hit.  This attribute is
+maintained for backward compatibility and is now deprecated in favor
+of the @code{gdb.BreakpointEvent.breakpoints} attribute.
 @end defvar
 
 @item events.new_objfile


                 reply	other threads:[~2022-06-09 18:37 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=20220609183731.D529E386DC78@sourceware.org \
    --to=tromey@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).