From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] [doc] Update obsolete text about sub-blocks
Date: Thu, 14 May 2026 13:59:07 -0600 [thread overview]
Message-ID: <20260514195907.1995821-1-tromey@adacore.com> (raw)
The manual claims that there is no way to iterate over the sub-blocks
of a gdb.Block, but this hasn't been true since commit 5166ed9c
("gdb/python: add subblocks property to gdb.Block").
This patch removes the obsolete clause and rewords the paragraph.
---
gdb/doc/python.texi | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
index 6cafab78d58..663976f1877 100644
--- a/gdb/doc/python.texi
+++ b/gdb/doc/python.texi
@@ -6273,10 +6273,9 @@ The block nested just inside the global block is the @dfn{static
block}. The static block typically holds file-scoped variables and
functions.
-@value{GDBN} provides a method to get a block's superblock, but there
-is currently no way to examine the sub-blocks of a block, or to
-iterate over all the blocks in a symbol table (@pxref{Symbol Tables In
-Python}).
+There is currently no way to iterate over all the blocks in a symbol
+table (@pxref{Symbol Tables In Python}), but once a block is found,
+its super- and sub-blocks can be iterated over.
Here is a short example that should help explain blocks:
base-commit: 2ea3f3a7ac2dd6ccd42e96d496b56aa42e7cb993
--
2.54.0
next reply other threads:[~2026-05-14 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 19:59 Tom Tromey [this message]
2026-05-15 15:52 ` Jan Vrany
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=20260514195907.1995821-1-tromey@adacore.com \
--to=tromey@adacore.com \
--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