Next: , Previous: Basic Python, Up: Python API Exception Handling

When executing the python command, Python exceptions uncaught within the Python code are translated to calls to gdb error-reporting mechanism. If the command that called python does not handle the error, gdb will terminate it and print an error message containing the Python exception name, the associated value, and the Python call stack backtrace at the point where the exception was raised. Example:

     (gdb) python print foo
     Traceback (most recent call last):
     NameError: name 'foo' is not defined

gdb errors that happen in gdb commands invoked by Python code are converted to Python exceptions. The type of the Python exception depends on the error.

This is the base class for most exceptions generated by gdb. It is derived from RuntimeError, for compatibility with earlier versions of gdb.

If an error occurring in gdb does not fit into some more specific category, then the generated exception will have this type.


In all cases, your exception handler will see the gdb error message as its value and the Python call stack backtrace at the Python statement closest to where the gdb error occured as the traceback.

When implementing gdb commands in Python via gdb.Command, it is useful to be able to throw an exception that doesn't cause a traceback to be printed. For example, the user may have invoked the command incorrectly. Use the gdb.GdbError exception to handle this case. Example:

     (gdb) python
     >class HelloWorld (gdb.Command):
     >  """Greet the whole world."""
     >  def __init__ (self):
     >  def invoke (self, args, from_tty):
     >    argv = gdb.string_to_argv (args)
     >    if len (argv) != 0:
     >    print "Hello, World!"
     >HelloWorld ()
     (gdb) hello-world 42
     hello-world takes no arguments