From: Siva Chandra <sivachandra@google.com>
To: gdb-patches@sourceware.org
Subject: [RFC - doc] Add note about the possibility of symbols getting moved across blocks
Date: Wed, 25 Apr 2012 08:13:00 -0000 [thread overview]
Message-ID: <CAGyQ6gyV9+jn1f6Vcqt+8PtzqZG2CZi8bZ_tW21+_21M+26DUQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
Hello,
This patch is in response to the discussion here:
http://sourceware.org/ml/gdb-patches/2012-04/msg00845.html
2012-04-25 Siva Chandra Reddy <sivachandra@google.com>
* gdb.texinfo (Blocks In Python): Add a note saying that future
improvements to symbol and symbol table representations can move
symbols across blocks within a symbol table.
Thanks,
Siva Chandra
[-- Attachment #2: blocks_doc_patch_v1.txt --]
[-- Type: text/plain, Size: 794 bytes --]
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.948
diff -u -p -r1.948 gdb.texinfo
--- gdb.texinfo 23 Apr 2012 17:26:01 -0000 1.948
+++ gdb.texinfo 25 Apr 2012 07:53:58 -0000
@@ -24530,7 +24530,10 @@ detailed technical information on @value
stack.
A @code{gdb.Block} is iterable. The iterator returns the symbols
-(@pxref{Symbols In Python}) local to the block.
+(@pxref{Symbols In Python}) local to the block. Users using this
+feature should keep in mind that future improvements to the internal
+representation, of symbols and symbol tables, can move symbols across
+blocks within a symbol table.
The following block-related functions are available in the @code{gdb}
module:
next reply other threads:[~2012-04-25 8:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 8:13 Siva Chandra [this message]
2012-04-25 9:02 ` Eli Zaretskii
2012-04-25 20:02 ` Tom Tromey
2012-04-25 21:02 ` Eli Zaretskii
2012-04-26 14:04 ` Tom Tromey
2012-04-26 14:17 ` Eli Zaretskii
2012-04-27 13:15 ` Siva Chandra
2012-04-27 15:38 ` Eli Zaretskii
2012-04-27 16:59 ` Doug Evans
2012-04-27 17:33 ` Eli Zaretskii
2012-04-27 17:46 ` Doug Evans
2012-04-27 19:42 ` Siva Chandra
2012-04-28 7:15 ` Eli Zaretskii
2012-04-30 19:20 ` Siva Chandra
2012-05-02 17:32 ` Siva Chandra
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=CAGyQ6gyV9+jn1f6Vcqt+8PtzqZG2CZi8bZ_tW21+_21M+26DUQ@mail.gmail.com \
--to=sivachandra@google.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