In gdb, symbols are stored in blocks. A block corresponds
roughly to a scope in the source code. Blocks are organized
hierarchically, and are represented individually in Python as a
gdb.Block
. Blocks rely on debugging information being
available.
A frame has a block. Please see Frames In Python, for a more in-depth discussion of frames.
The outermost block is known as the global block. The global block typically holds public global variables and functions.
The block nested just inside the global block is the static block. The static block typically holds file-scoped variables and functions.
gdb 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 (see Symbol Tables In Python).
Here is a short example that should help explain blocks:
/* This is in the global block. */ int global; /* This is in the static block. */ static int file_scope; /* 'function' is in the global block, and 'argument' is in a block nested inside of 'function'. */ int function (int argument) { /* 'local' is in a block inside 'function'. It may or may not be in the same block as 'argument'. */ int local; { /* 'inner' is in a block whose superblock is the one holding 'local'. */ int inner; /* If this call is expanded by the compiler, you may see a nested block here whose function is 'inline_function' and whose superblock is the one holding 'inner'. */ inline_function (); } }
A gdb.Block
is iterable. The iterator returns the symbols
(see Symbols In Python) local to the block. Python programs
should not assume that a specific block object will always contain a
given symbol, since changes in gdb features and
infrastructure may cause symbols move across blocks in a symbol
table.
The following block-related functions are available in the gdb
module:
Return the innermost
gdb.Block
containing the given pc value. If the block cannot be found for the pc value specified, the function will returnNone
. This is identical togdb.current_progspace().block_for_pc(pc)
and is included for historical compatibility.
A gdb.Block
object has the following methods:
Returns
True
if thegdb.Block
object is valid,False
if not. A block object can become invalid if the block it refers to doesn't exist anymore in the inferior. All othergdb.Block
methods will throw an exception if it is invalid at the time the method is called. The block's validity is also checked during iteration over symbols of the block.
A gdb.Block
object has the following attributes:
One past the last address that appears in the block. This attribute is not writable.
The name of the block represented as a
gdb.Symbol
. If the block is not named, then this attribute holdsNone
. This attribute is not writable.For ordinary function blocks, the superblock is the static block. However, you should note that it is possible for a function block to have a superblock that is not the static block – for instance this happens for an inlined function.
The block containing this block. If this parent block does not exist, this attribute holds
None
. This attribute is not writable.
The global block associated with this block. This attribute is not writable.
The static block associated with this block. This attribute is not writable.