Next: Interpreters, Previous: Controlling GDB, Up: Top [Contents][Index]
GDB provides several mechanisms for extension. GDB also provides the ability to automatically load extensions when it reads a file for debugging. This allows the user to automatically customize GDB for the program being debugged.
| • Sequences: | Canned Sequences of GDB Commands | |
| • Python: | Extending GDB using Python | |
| • Guile: | Extending GDB using Guile | |
| • Auto-loading extensions: | Automatically loading extensions | |
| • Multiple Extension Languages: | Working with multiple extension languages | |
| • Aliases: | Creating new spellings of existing commands |
To facilitate the use of extension languages, GDB is capable of evaluating the contents of a file. When doing so, GDB can recognize which extension language is being used by looking at the filename extension. Files with an unrecognized filename extension are always treated as a GDB Command Files. See Command files.
You can control how GDB evaluates these files with the following setting:
set script-extension offAll scripts are always evaluated as GDB Command Files.
set script-extension softThe debugger determines the scripting language based on filename extension. If this scripting language is supported, GDB evaluates the script using that language. Otherwise, it evaluates the file as a GDB Command File.
set script-extension strictThe debugger determines the scripting language based on filename extension, and evaluates the script using that language. If the language is not supported, then the evaluation fails.
show script-extensionDisplay the current value of the script-extension option.
Next: Interpreters, Previous: Controlling GDB, Up: Top [Contents][Index]