[pushed] [gdb/testsuite] Clean up before compilation in gdb.ada/call-no-debug.exp

Tom de Vries via Gdb-patches
2023-06-16T11:33:01Z

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.
---
gdb/testsuite/gdb.ada/call-no-debug.exp | 5 +++++
1 file changed, 5 insertions(+)

diff --git a/gdb/testsuite/gdb.ada/call-no-debug.exp b/gdb/testsuite/gdb.ada/call-no-debug.exp
index 422b83761d9..df81c87ade2 100644
--- a/gdb/testsuite/gdb.ada/call-no-debug.exp
+++ b/gdb/testsuite/gdb.ada/call-no-debug.exp
@@ -21,6 +21,11 @@ require allow_ada_tests

standard_ada_testfile prog

+# Since we use no-force to compile prog, make sure we don't pick up files
+# from a previous compilation.
+remote_file host delete [standard_output_file prog.o]
+remote_file host delete [standard_output_file prog.ali]
+
# Compile pck without debuginfo but prog with it.
if {[gdb_compile_ada $srcdir/$subdir/$testdir/pck.adb \
[standard_output_file pck.o] object {}] != ""} {

base-commit: 9fb38608660d25f368b458a17e5f013271da7d4a
--
2.35.3