binutils-gdb/gdb/testsuite/gdb.python/py-template.exp
Tom Tromey a207f6b3a3 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>
2024-02-27 09:46:31 -07:00

64 lines
2.4 KiB
Text

# Copyright (C) 2008-2024 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
# This file is part of the GDB testsuite. It tests the mechanism
# exposing values to Python.
require allow_cplus_tests allow_python_tests
standard_testfile .cc
if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable \
{debug c++}] != "" } {
untested "failed to compile"
return -1
}
clean_restart
proc test_template_arg {exefile type} {
global testfile srcdir subdir srcfile
if { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${exefile}" \
executable \
[list debug c++ additional_flags="-DTYPE=$type"]] != "" } {
untested $type
return -1
}
gdb_load ${exefile}
if {![runto_main]} {
return
}
# There is no executable code in main(), so we are where we want to be
gdb_test "print (foo)" ".*" \
"print (foo) in template test of $type"
gdb_test_no_output "python foo = gdb.history(0)" \
"fetch foo from gdb.history(0) in template test of $type"
# Replace '*' with '\*' in regex.
regsub -all {\*} $type {\*} t
gdb_test "python print (foo.type.template_argument(0))" $t $type
gdb_test "python print(foo.type.template_argument(-1))" \
"Template argument number must be non-negative\r\nError occurred in Python.*" \
"negative template argument number in template test of $type"
}
test_template_arg "${binfile}-ci" "const int"
test_template_arg "${binfile}-vi" "volatile int"
test_template_arg "${binfile}-cir" "const int &"
test_template_arg "${binfile}-vir" "volatile int &"
test_template_arg "${binfile}-vipc" "volatile int * const"
test_template_arg "${binfile}-vipcp" "volatile int * const *"
test_template_arg "${binfile}-cipv" "const int * volatile"
test_template_arg "${binfile}-cipvpcpvp" "const int * volatile * const * volatile *"