From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/testsuite] Clean up before compilation in gdb.ada/call-no-debug.exp
Date: Fri, 16 Jun 2023 13:33:05 +0200 [thread overview]
Message-ID: <20230616113305.27867-1-tdevries@suse.de> (raw)
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
next reply other threads:[~2023-06-16 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 11:33 Tom de Vries [this message]
2023-06-16 18:38 ` Tom Tromey
2023-06-17 10:50 ` Tom de Vries
2023-06-17 20:14 ` Tom Tromey
2023-06-19 14:25 ` Luis Machado
2023-06-19 14:26 ` Luis Machado
2023-06-19 17:12 ` Tom de Vries
2023-06-19 17:22 ` Tom Tromey
2023-06-21 5:31 ` Tom de Vries
2023-06-21 7:40 ` Luis Machado
2023-06-22 16:01 ` Tom Tromey
2023-06-19 17:19 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230616113305.27867-1-tdevries@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).