From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH][gdb/testsuite] Set language in gdb.ada/minsym.exp
Date: Wed, 11 Mar 2020 16:31:47 +0100 [thread overview]
Message-ID: <20200311153145.GA13018@delia> (raw)
Hi,
When building gdb using configure flag
--with-separate-debug-dir=/usr/lib/debug, and running test-case
gdb.ada/minsyms.exp, I run into:
...
(gdb) PASS: gdb.ada/minsyms.exp: print some_minsym
print integer(some_minsym)^M
A syntax error in expression, near `some_minsym)'.^M
(gdb) FAIL: gdb.ada/minsyms.exp: print integer(some_minsym)
...
and 2 other FAILs.
This is due to the fact that the language after arriving at the ada main
function turns out to be auto/c. [ This has been filed as PR25655 -
"Language is not auto/ada in main ada function for exec without debug info". ]
When building gdb without the configure flag mentioned above, we have instead
auto/ada in the ada main function, and all tests pass.
Fix the FAILs by working around PR25655 in the test-case, and manually setting
the language to ada.
Tested on x86_64-linux.
OK for trunk?
Thanks,
- Tom
[gdb/testsuite] Set language in gdb.ada/minsym.exp
gdb/testsuite/ChangeLog:
2020-03-11 Tom de Vries <tdevries@suse.de>
* gdb.ada/minsyms.exp: Set language to ada.
---
gdb/testsuite/gdb.ada/minsyms.exp | 2 ++
1 file changed, 2 insertions(+)
diff --git a/gdb/testsuite/gdb.ada/minsyms.exp b/gdb/testsuite/gdb.ada/minsyms.exp
index 1730eb3bd7..1bed2e40da 100644
--- a/gdb/testsuite/gdb.ada/minsyms.exp
+++ b/gdb/testsuite/gdb.ada/minsyms.exp
@@ -28,6 +28,8 @@ if ![runto "_ada_foo_qb07_057" ] then {
return
}
+gdb_test_no_output "set language ada"
+
gdb_test "print some_minsym" \
"'some_minsym' has unknown type; cast it to its declared type"
next reply other threads:[~2020-03-11 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 15:31 Tom de Vries [this message]
2020-03-11 18:17 ` 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=20200311153145.GA13018@delia \
--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