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/testsuite/gdb.python/py-error.exp | |
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/testsuite/gdb.python/py-error.exp')
-rw-r--r-- | gdb/testsuite/gdb.python/py-error.exp | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/gdb/testsuite/gdb.python/py-error.exp b/gdb/testsuite/gdb.python/py-error.exp index 58e8549..6eb9cc3 100644 --- a/gdb/testsuite/gdb.python/py-error.exp +++ b/gdb/testsuite/gdb.python/py-error.exp @@ -50,7 +50,12 @@ if {$test2 == ""} { set remote_python_file [gdb_remote_download host \ ${srcdir}/${subdir}/${testfile}.py] -# argc=LookupError: unknown encoding: IBM1047 -gdb_test "source $remote_python_file" "Traceback.*ClassName.*\r\nLookupError: unknown encoding: $charset" $test2 +# With the new way that "source" works, it isn't really possible for +# this to fail "correctly". Converting the filename to a Python +# unicode object will fail -- and, mysteriously, without setting a +# real exception. +gdb_test "source $remote_python_file" \ + "An error occurred in Python.*" \ + $test2 gdb_test "p 1" " = 1" "no delayed error" |