gdb loads symbols for an inferior from various symbol-containing files (see Files). These include the primary executable file, any shared libraries used by the inferior, and any separate debug info files (see Separate Debug Files). gdb calls these symbol-containing files objfiles.
The following objfile-related functions are available in the
When auto-loading a Python script (see Python Auto-loading), gdb sets the “current objfile” to the corresponding objfile. This function returns the current objfile. If there is no current objfile, this function returns
Return a sequence of all the objfiles current known to gdb. See Objfiles In Python.
Look up name, a file name or build ID, in the list of objfiles for the current program space (see Progspaces In Python). If the objfile is not found throw the Python
If name is a relative file name, then it will match any source file name with the same trailing components. For example, if name is ‘gcc/expr.c’, then it will match source file name of /build/trunk/gcc/expr.c, but not /build/trunk/libcpp/expr.c or /build/trunk/gcc/x-expr.c.
If by_build_id is provided and is
Truethen name is the build ID of the objfile. Otherwise, name is a file name. This is supported only on some operating systems, notably those which use the ELF format for binary files and the gnu Binutils. For more details about this feature, see the description of the --build-id command-line option in Command Line Options.
Each objfile is represented by an instance of the
For separate debug info objfiles this is the corresponding
gdb.Objfileobject that debug info is being provided for. Otherwise this is
None. Separate debug info objfiles are added with the
gdb.Objfile.add_separate_debug_filemethod, described below.
The build ID of the objfile as a string. If the objfile does not have a build ID then the value is
This is supported only on some operating systems, notably those which use the ELF format for binary files and the gnu Binutils. For more details about this feature, see the description of the --build-id command-line option in Command Line Options.
The containing program space of the objfile as a
gdb.Progspaceobject. See Progspaces In Python.
pretty_printersattribute is a list of functions. It is used to look up pretty-printers. A
Valueis passed to each function in order; if the function returns
None, then the search continues. Otherwise, the return value should be an object which is used to format the value. See Pretty Printing API, for more information.
type_printersattribute is a list of type printer objects. See Type Printing API, for more information.
frame_filtersattribute is a dictionary of frame filter objects. See Frame Filter API, for more information.
One may add arbitrary attributes to
in the usual Python way.
This is useful if, for example, one needs to do some extra record keeping
associated with the objfile.
In this contrived example we record the time when gdb loaded the objfile.
(gdb) python import datetime def new_objfile_handler(event): # Set the time_loaded attribute of the new objfile. event.new_objfile.time_loaded = datetime.datetime.today() gdb.events.new_objfile.connect(new_objfile_handler) end (gdb) file ./hello Reading symbols from ./hello...done. (gdb) python print gdb.objfiles().time_loaded 2014-10-09 11:41:36.770345
gdb.Objfile object has the following methods:
gdb.Objfileobject is valid,
Falseif not. A
gdb.Objfileobject can become invalid if the object file it refers to is not loaded in gdb any longer. All other
gdb.Objfilemethods will throw an exception if it is invalid at the time the method is called.
Add file to the list of files that gdb will search for debug information for the objfile. This is useful when the debug info has been removed from the program and stored in a separate file. gdb has built-in support for finding separate debug info files (see Separate Debug Files), but if the file doesn't live in one of the standard places that gdb searches then this function can be used to add a debug info file from a different place.