aboutsummaryrefslogtreecommitdiff
path: root/gdb/python
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2025-01-08 16:24:11 +0100
committerTom de Vries <tdevries@suse.de>2025-01-08 16:24:11 +0100
commit1da36057976ea565045f319e3d65be7412ca0588 (patch)
treed1e4b6b465192abf368c8d0b8c23833dfe2def75 /gdb/python
parent3573490bf0e5d2c550cebed5f4e1a8be0fab2c71 (diff)
downloadbinutils-1da36057976ea565045f319e3d65be7412ca0588.zip
binutils-1da36057976ea565045f319e3d65be7412ca0588.tar.gz
binutils-1da36057976ea565045f319e3d65be7412ca0588.tar.bz2
[gdb/testsuite] Check gnatmake version in gdb.ada/scalar_storage.exp
On a system with gcc 14.2.0 and gnatmake 13.3.0 I run into: ... (gdb) PASS: gdb.ada/scalar_storage.exp: print V_LE get_compiler_info: gcc-14-2-0 print V_BE^M $2 = (value => 126, another_value => 12, color => red)^M (gdb) FAIL: gdb.ada/scalar_storage.exp: print V_BE ... The test-case contains a corresponding kfail: ... # This requires a compiler fix that is in GCC 14. if {[gcc_major_version] < 14} { setup_kfail "DW_AT_endianity on enum types" *-*-* } ... which doesn't trigger because it checks the gcc version rather than the gnatmake version. Fix this by checking the gnatmake version instead. Tested on aarch64-linux and x86_64-linux.
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions