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] Fix gdb.fortran/module.exp for debug info from other files Date: Tue, 22 Oct 2019 20:52:00 -0000 [thread overview] Message-ID: <062f1fc13a075a34890988f3a396b5e58fc86396@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 062f1fc13a075a34890988f3a396b5e58fc86396 *** commit 062f1fc13a075a34890988f3a396b5e58fc86396 Author: Tom de Vries <tdevries@suse.de> AuthorDate: Thu Oct 17 10:07:05 2019 +0200 Commit: Tom de Vries <tdevries@suse.de> CommitDate: Thu Oct 17 10:07:05 2019 +0200 [gdb/testsuite] Fix gdb.fortran/module.exp for debug info from other files On openSUSE Leap 15.1, I get: ... FAIL: gdb.fortran/module.exp: info variables -n ... because the info variables command prints info also for init.c: ... File init.c:^M 24: const int _IO_stdin_used;^M ... while the regexps in the test-case only expect info for module.f90. Fix this by extending the regexps. Tested on x86_64-linux. gdb/testsuite/ChangeLog: 2019-10-17 Tom de Vries <tdevries@suse.de> * gdb.fortran/module.exp: Allow info variables to print info for files other than module.f90. Change-Id: I401d8018b121fc7343f6bc8b671900349462457f diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 395a3ccacf..1075a1d614 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2019-10-17 Tom de Vries <tdevries@suse.de> + + * gdb.fortran/module.exp: Allow info variables to print info for files + other than module.f90. + 2019-10-16 Andrew Burgess <andrew.burgess@embecosm.com> * gdb.fortran/module.exp: Extend with 'info variables' test. diff --git a/gdb/testsuite/gdb.fortran/module.exp b/gdb/testsuite/gdb.fortran/module.exp index 276f7dc3c2..a2aff3cb7c 100644 --- a/gdb/testsuite/gdb.fortran/module.exp +++ b/gdb/testsuite/gdb.fortran/module.exp @@ -53,7 +53,10 @@ gdb_test "info variables -n" \ "33:\[ \t\]+${int_type} modmany::var_c;" \ "33:\[ \t\]+${int_type} modmany::var_i;" \ "37:\[ \t\]+${int_type} moduse::var_x;" \ - "37:\[ \t\]+${int_type} moduse::var_y;" ] + "37:\[ \t\]+${int_type} moduse::var_y;(" \ + "" \ + "File .*:(" \ + "$decimal:.*)+)*"] # Do not use simple single-letter names as GDB would pick up for expectedly
next reply other threads:[~2019-10-22 20:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-22 20:52 gdb-buildbot [this message] 2019-10-22 20:52 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot 2019-10-22 21:31 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot 2019-11-03 1:32 ` Failures on Fedora-i686, " gdb-buildbot 2019-11-03 2:22 ` Failures on Fedora-x86_64-m32, " gdb-buildbot 2019-11-03 2:31 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2019-11-03 3:17 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2019-11-03 4:03 ` 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=062f1fc13a075a34890988f3a396b5e58fc86396@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: linkBe 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).