| Debugging with GDB: Symbol Tables In Guile |
|---|
Next: Breakpoints In Guile, Previous: Symbols In Guile, Up: Guile API [Contents][Index]
Access to symbol table data maintained by GDB on the inferior
is exposed to Guile via two objects: <gdb:sal> (symtab-and-line) and
<gdb:symtab>. Symbol table and line data for a frame is returned
from the frame-find-sal <gdb:frame> procedure.
See Frames In Guile.
For more information on GDB’s symbol table management, see Examining the Symbol Table.
The following symtab-related procedures are provided by the
(gdb) module:
Return #t if object is an object of type <gdb:symtab>.
Otherwise return #f.
Return #t if the <gdb:symtab> object is valid,
#f if not. A <gdb:symtab> object becomes invalid when
the symbol table it refers to no longer exists in GDB.
All other <gdb:symtab> procedures will throw an exception
if it is invalid at the time the procedure is called.
Return the symbol table’s backing object file. See Objfiles In Guile.
Return the global block of the underlying symbol table. See Blocks In Guile.
Return the static block of the underlying symbol table. See Blocks In Guile.
The following symtab-and-line-related procedures are provided by the
(gdb) module:
Return #t if object is an object of type <gdb:sal>.
Otherwise return #f.
Return #t if sal is valid, #f if not.
A <gdb:sal> object becomes invalid when the Symbol table object
it refers to no longer exists in GDB. All other
<gdb:sal> procedures will throw an exception if it is
invalid at the time the procedure is called.
Return the <gdb:sal> object corresponding to the pc value.
If an invalid value of pc is passed as an argument, then the
symtab and line attributes of the returned <gdb:sal>
object will be #f and 0 respectively.
Next: Breakpoints In Guile, Previous: Symbols In Guile, Up: Guile API [Contents][Index]