diff options
author | Tom de Vries <tdevries@suse.de> | 2024-09-10 10:25:07 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2024-09-10 10:25:07 +0200 |
commit | 258c81da3c13971dc7667f30baf506ececd2cc0e (patch) | |
tree | 4c1280da8f8f5fce2e2ea629983456e07291af74 /ld/testsuite/ld-elf/pr30907-1.d | |
parent | bc13da1980ceec05cff958d72a774b4373c9e00d (diff) | |
download | gdb-master.zip gdb-master.tar.gz gdb-master.tar.bz2 |
When running test-case gdb.xml/tdesc-regs.exp on riscv64-linux, I get:
...
(gdb) set tdesc file single-reg.xml^M
warning: Architecture rejected target-supplied description^M
(gdb) FAIL: gdb.xml/tdesc-regs.exp: set tdesc file single-reg.xml
UNSUPPORTED: gdb.xml/tdesc-regs.exp: register tests
...
The FAIL and UNSUPPORTED are produced here:
...
# If no core registers were specified, assume this target does not
# support target-defined registers. Verify that we get a warning if
# we try to use them. This not only tests the warning, but also
# reminds maintainers to add test support when they add the feature.
if {[string equal ${core-regs} ""]} {
gdb_test "set tdesc file $single_reg_xml" \
"warning: Target-supplied registers are not supported.*" \
"set tdesc file single-reg.xml"
unsupported "register tests"
return 0
}
...
The test-case contains target-specific setting of the core-regs variable, and
adding this for riscv64 bypasses this code and makes the test-case pass.
However, without that change, the test-case shouldn't produce a FAIL since
gdb isn't doing anything wrong.
Fix this by producing instead:
...
PASS: $exp: set tdesc file single-reg.xml
UNSUPPORTED: $exp: register tests (missing architecture-specific core-regs setting)
...
Tested on riscv64-linux.
Diffstat (limited to 'ld/testsuite/ld-elf/pr30907-1.d')
0 files changed, 0 insertions, 0 deletions