Info Catalog gdb: Python API gdb: Python gdb: Python modules

gdb: Python Auto-loading

 
 23.2.3 Python Auto-loading
 --------------------------
 
 When a new object file is read (for example, due to the 'file' command,
 or because the inferior has loaded a shared library), GDB will look for
 Python support scripts in several ways: 'OBJFILE-gdb.py' and
 '.debug_gdb_scripts' section.  Auto-loading extensions.
 
    The auto-loading feature is useful for supplying application-specific
 debugging commands and scripts.
 
    Auto-loading can be enabled or disabled, and the list of auto-loaded
 scripts can be printed.
 
 'set auto-load python-scripts [on|off]'
      Enable or disable the auto-loading of Python scripts.
 
 'show auto-load python-scripts'
      Show whether auto-loading of Python scripts is enabled or disabled.
 
 'info auto-load python-scripts [REGEXP]'
      Print the list of all Python scripts that GDB auto-loaded.
 
      Also printed is the list of Python scripts that were mentioned in
      dotdebug_gdb_scripts section::) or were not auto-loaded due to
      'auto-load safe-path' rejection (Auto-loading).  This is
      useful because their names are not printed when GDB tries to load
      them and fails.  There may be many of them, and printing an error
      message for each one is problematic.
 
      If REGEXP is supplied only Python scripts with matching names are
      printed.
 
      Example:
 
           (gdb) info auto-load python-scripts
           Loaded Script
           Yes    py-section-script.py
                  full name: /tmp/py-section-script.py
           No     my-foo-pretty-printers.py
 
    When reading an auto-loaded file or script, GDB sets the "current
 objfile".  This is available via the 'gdb.current_objfile' function
 (Objfiles In Python).  This can be useful for registering
 objfile-specific pretty-printers and frame-filters.
 

Info Catalog gdb: Python API gdb: Python gdb: Python modules