OpenE2K/binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

gdb/fortran: Add test for module variables in 'info variables' output

Browse Source 
Recent work from Tom Tromey to better handle variables with associated
copy relocations has fixed a Fortran issue where module variables
wouldn't show up in the output of 'info variables'.

This commit adds a test for this functionality to ensure it doesn't
get broken in the future.

gdb/testsuite/ChangeLog:

	* gdb.fortran/module.exp: Extend with 'info variables' test.

Change-Id: I7306b1d0a9a72947fd48ad7a03f49df774d6573b
This commit is contained in:
Andrew Burgess 2019-07-24 14:00:07 +01:00
parent 7ff5fae704
commit 0b54364d92
2 changed files with 28 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,7 @@
2019-10-16 Andrew Burgess <andrew.burgess@embecosm.com>
* gdb.fortran/module.exp: Extend with 'info variables' test.
2019-10-16 Andrew Burgess <andrew.burgess@embecosm.com>
* boards/cc-with-tweaks.exp: Setup F90_FOR_TARGET and

24
gdb/testsuite/gdb.fortran/module.exp
View File

@ -13,6 +13,8 @@
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
load_lib "fortran.exp"
standard_testfile .f90
if { [prepare_for_testing "failed to prepare" $testfile $srcfile {debug f90}] } {
@ -32,6 +34,28 @@ if ![runto MAIN__] then {
continue
}
set int_type [fortran_int4]
# Test 'info variables' can find module variables.
gdb_test "info variables -n" \
[multi_line \
"All defined variables:" \
"" \
"File .*$srcfile:" \
"18:\[ \t\]+${int_type} mod1::var_const;" \
"17:\[ \t\]+${int_type} mod1::var_i;" \
"23:\[ \t\]+${int_type} mod2::var_i;" \
"28:\[ \t\]+${int_type} mod3::mod1;" \
"27:\[ \t\]+${int_type} mod3::mod2;" \
"29:\[ \t\]+${int_type} mod3::var_i;" \
"33:\[ \t\]+${int_type} modmany::var_a;" \
"33:\[ \t\]+${int_type} modmany::var_b;" \
"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;" ]
# Do not use simple single-letter names as GDB would pick up for expectedly
# nonexisting symbols some static variables from system libraries debuginfos.