public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] [gdb/testsuite] Set language in gdb.ada/minsym.exp
Date: Fri, 20 Mar 2020 13:08:58 -0400	[thread overview]
Message-ID: <5308d1e77167b4bb133302d7a6f66e599abee420@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 5308d1e77167b4bb133302d7a6f66e599abee420 ***

commit 5308d1e77167b4bb133302d7a6f66e599abee420
Author:     Tom de Vries <tdevries@suse.de>
AuthorDate: Wed Mar 11 19:37:01 2020 +0100
Commit:     Tom de Vries <tdevries@suse.de>
CommitDate: Wed Mar 11 19:37:01 2020 +0100

    [gdb/testsuite] Set language in gdb.ada/minsym.exp
    
    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.
    
    gdb/testsuite/ChangeLog:
    
    2020-03-11  Tom de Vries  <tdevries@suse.de>
    
            * gdb.ada/minsyms.exp: Set language to ada.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index f7cdea7da8..f98edafbc6 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2020-03-11  Tom de Vries  <tdevries@suse.de>
+
+	* gdb.ada/minsyms.exp: Set language to ada.
+
 2020-03-11  Tom de Vries  <tdevries@suse.de>
 
 	* gdb.server/sysroot.exp: Allow GLIBC's printf alias __printf.
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"
 


             reply	other threads:[~2020-03-20 17:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 17:08 gdb-buildbot [this message]
2020-03-20 17:08 ` Failures on Fedora-x86_64-cc-with-index, branch master gdb-buildbot
2020-03-20 17:13 ` Failures on Fedora-i686, " gdb-buildbot
2020-03-20 17:39 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2020-03-20 17:53 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-03-20 18:21 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-03-20 18:51 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-03-23  0:28 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2020-03-23 17:12 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot

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=5308d1e77167b4bb133302d7a6f66e599abee420@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-testers@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).