##### 23.2.2.2 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):
           File "<string>", line 1, in <module>
         NameError: name 'foo' is not defined

gdb errors that happen in gdb commands invoked by Python code are converted to Python `RuntimeError` exceptions. User interrupt (via `C-c` or by typing `q` at a pagination prompt) is translated to a Python `KeyboardInterrupt` exception. If you catch these exceptions in your Python code, your exception handler will see `RuntimeError` or `KeyboardInterrupt` as the exception type, 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.