aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.python
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2023-06-16 13:32:43 +0200
committerTom de Vries <tdevries@suse.de>2023-06-16 13:32:43 +0200
commite2adba909e74b9c60c1e776d5d0e7079f502363c (patch)
tree12fe1e4ede0b1780d97fc994123b6da43cd03573 /gdb/testsuite/gdb.python
parent9fb38608660d25f368b458a17e5f013271da7d4a (diff)
downloadbinutils-e2adba909e74b9c60c1e776d5d0e7079f502363c.zip
binutils-e2adba909e74b9c60c1e776d5d0e7079f502363c.tar.gz
binutils-e2adba909e74b9c60c1e776d5d0e7079f502363c.tar.bz2
[gdb/testsuite] Clean up before compilation in gdb.ada/call-no-debug.exp
Running test-case gdb.ada/call-no-debug.exp with target board unix/-m64 works fine, but if we run it again with target board unix-m32, we run into: ... gnatlink prog.ali -m32 -g -o prog^M ld: i386:x86-64 architecture of input file `b~prog.o' is incompatible with \ i386 output^M ... This is due to compiling with no-force. The test-case: - first compiles pck.adb into pck.o (without debug info), and - then compiles prog.adb and pck.o into prog (with debug info). Using no-force in the second compilation make sure that pck.adb is not compiled again, with debug info. But it also means it will pick up intermediate files related to prog.adb from a previous compilation. Fix this by removing prog.o and prog.ali before compilation. Tested on x86_64-linux.
Diffstat (limited to 'gdb/testsuite/gdb.python')
0 files changed, 0 insertions, 0 deletions