gdb/testsuite: Fix race condition compiling fortran test
authorAndrew Burgess <andrew.burgess@embecosm.com>
Wed, 27 Nov 2019 21:18:38 +0000 (21:18 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Wed, 27 Nov 2019 21:18:38 +0000 (21:18 +0000)
commit640ab94712483457b99bd1039b52821c510b28a7
tree70e59ecbf1754fcf3d25af3c74e3ad827d73c878
parentd22670f0780f4d296325d35049f0d57791ef6d73
gdb/testsuite: Fix race condition compiling fortran test

The Fortran test gdb.fortran/info-modules compiles the files
info-types.f90 and info-types-2.f90 in that order.  Unfortunately
info-types.f90 makes use of a module defined in info-types-2.f90.

This currently doesn't cause a problem if you run all of the Fortran
tests as the info-types.exp test already compiles info-types-2.f90 and
so the module description file 'mod2.mod' will be created, and can
then be found by info-modules.exp during its compile.

If however you try to run just info-modules.exp in a clean build
directory, the test will fail to compile.

Fix this by compiling the source files in the reverse order so that
the module is compiled first, then the test program that uses the
module.

gdb/testsuite/ChangeLog:

* gdb.fortran/info-modules.exp: Compile source files in correct
order.

Change-Id: Ic3a1eded0486f6264ebe3066cf1beafbd2534a91
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.fortran/info-modules.exp
This page took 0.025583 seconds and 4 git commands to generate.