| Debugging with GDB: Multiple Extension Languages |
|---|
Next: Aliases, Previous: Auto-loading extensions, Up: Extending GDB [Contents][Index]
The Guile and Python extension languages do not share any state, and generally do not interfere with each other. There are some things to be aware of, however.
Python was GDB’s first extension language, and to avoid breaking existing behaviour Python comes first. This is generally solved by the “first one wins” principle. GDB maintains a list of enabled extension languages, and when it makes a call to an extension language, (say to pretty-print a value), it tries each in turn until an extension language indicates it has performed the request (e.g., has returned the pretty-printed form of a value). This extends to errors while performing such requests: If an error happens while, for example, trying to pretty-print an object then the error is reported and any following extension languages are not tried.