diff options
| author | Tom Tromey <tromey@adacore.com> | 2024-02-15 13:14:43 -0700 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2024-02-27 09:46:31 -0700 |
| commit | a207f6b3a384897be1dab081a0a9a206593029de (patch) | |
| tree | efd01c313bd5d3e926450662d0e799708a808198 /gdb/doc | |
| parent | 8ee6f71b1a09f4077e22c840a16833518c56089a (diff) | |
| download | gdb-a207f6b3a384897be1dab081a0a9a206593029de.zip gdb-a207f6b3a384897be1dab081a0a9a206593029de.tar.gz gdb-a207f6b3a384897be1dab081a0a9a206593029de.tar.bz2 | |
Rewrite "python" command exception handling
The "python" command (and the Python implementation of the gdb
"source" command) does not handle Python exceptions in the same way as
other gdb-facing Python code. In particular, exceptions are turned
into a generic error rather than being routed through
gdbpy_handle_exception, which takes care of converting to 'quit' as
appropriate.
I think this was done this way because PyRun_SimpleFile and friends do
not propagate the Python exception -- they simply indicate that one
occurred.
This patch reimplements these functions to respect the general gdb
convention here. As a bonus, some Windows-specific code can be
removed, as can the _execute_file function.
The bulk of this change is tweaking the test suite to match the new
way that exceptions are displayed. These changes are largely
uninteresting. However, it's worth pointing out the py-error.exp
change. Here, the failure changes because the test changes the host
charset to something that isn't supported by Python. This then
results in a weird error in the new setup.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31354
Acked-By: Tom de Vries <tdevries@suse.de>
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Diffstat (limited to 'gdb/doc')
| -rw-r--r-- | gdb/doc/python.texi | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi index 6b99a74..4ae7271 100644 --- a/gdb/doc/python.texi +++ b/gdb/doc/python.texi @@ -721,9 +721,9 @@ When executing the @code{python} command, Python exceptions uncaught within the Python code are translated to calls to @value{GDBN} error-reporting mechanism. If the command that called @code{python} does not handle the error, @value{GDBN} 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: +terminate it and print an error message. Exactly what will be printed +depends on @code{set python print-stack} (@pxref{Python Commands}). +Example: @smallexample (@value{GDBP}) python print foo |