diff options
| author | Andrew Burgess <andrew.burgess@embecosm.com> | 2019-11-27 21:18:38 +0000 |
|---|---|---|
| committer | Andrew Burgess <andrew.burgess@embecosm.com> | 2019-11-27 21:18:38 +0000 |
| commit | 640ab94712483457b99bd1039b52821c510b28a7 (patch) | |
| tree | 70e59ecbf1754fcf3d25af3c74e3ad827d73c878 /gdb/testsuite/ChangeLog | |
| parent | d22670f0780f4d296325d35049f0d57791ef6d73 (diff) | |
| download | gdb-640ab94712483457b99bd1039b52821c510b28a7.zip gdb-640ab94712483457b99bd1039b52821c510b28a7.tar.gz gdb-640ab94712483457b99bd1039b52821c510b28a7.tar.bz2 | |
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
Diffstat (limited to 'gdb/testsuite/ChangeLog')
| -rw-r--r-- | gdb/testsuite/ChangeLog | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 3a6e925..86f2130 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2019-11-27 Andrew Burgess <andrew.burgess@embecosm.com> + + * gdb.fortran/info-modules.exp: Compile source files in correct + order. + 2019-11-27 Kevin Buettner <kevinb@redhat.com> * gdb.dwarf2/imported-unit.exp: New file. |