This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC - Python scripting] New methods Symtab.global_block and Symtab.static_block (docs included)


Doug> It would not be unexpected to me if a symbol disappeared from either
Doug> list, moved from one list to another, or a new symbol appeared.

Even in the API currently public, Block.superblock can take a user to
global or static block and make him/her vulnerable to the above
problem.  But, can we view this from a different angle:  Let us first
take the case of a global block.  As I understand, this should very
definitely contain the global functions and global variables defined
in a source file.  If these two kinds of symbols do not change from
release to release, then we document saying that the user should rely
only on this information being constant.  Similarly, if my
understanding is correct, static functions and static variables
defined in a source file should always be present in a static block.
Hence, we again document saying that the user rely only on this
information being constant.  Does this sound reasonable?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]