aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPedro Alves <pedro@palves.net>2024-03-22 19:38:39 +0000
committerPedro Alves <pedro@palves.net>2024-03-25 20:05:36 +0000
commit02d02fc7924992ddd98073b95810b957efdc421a (patch)
treecfdc167bfb58d91c262adb6db2419f5261219ae0
parentccf3148e3133f016a8e1484e85e5e4d8c271c4f0 (diff)
downloadbinutils-02d02fc7924992ddd98073b95810b957efdc421a.zip
binutils-02d02fc7924992ddd98073b95810b957efdc421a.tar.gz
binutils-02d02fc7924992ddd98073b95810b957efdc421a.tar.bz2
gdb/testsuite: Fix set_unbuffered_mode.o handling in parallel mode
Cygwin/MinGW testing links in a set_unbuffered_mode.o object to all test programs. When running the testsuite in parallel mode, on Cygwin, I noticed errors like: ERROR: remote_download to host of ..../build/set_unbuffered_mode.o to ..../build/set_unbuffered_mode_saved.o: cp: cannot open '..../build/set_unbuffered_mode.o' for reading: No such file or directory ... ERROR: remote_download to host of ..../build/set_unbuffered_mode.o to ..../build/set_unbuffered_mode_saved.o: cp: cannot stat '..../build/set_unbuffered_mode.o': No such file or directory ... ERROR: remote_download to host of ..../build/set_unbuffered_mode.o to ..../build/set_unbuffered_mode_saved.o: cp: skipping file '..../build/set_unbuffered_mode.o', as it was replaced while being copied (Absolute paths elided above.) The problem is that gdb_compile's unbuffered_mode_obj cache isn't parallel safe. This is fixed in this commit. Reviewed-by: Kevin Buettner <kevinb@redhat.com> Change-Id: I67a289473c14ce0603d4b0beb755b124588f18d2
-rw-r--r--gdb/testsuite/lib/gdb.exp21
1 files changed, 19 insertions, 2 deletions
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 606a393..d48ea37 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -5569,10 +5569,20 @@ proc gdb_compile {source dest type options} {
# which is time consuming, especially if we're remote
# host testing.
#
+ # Note the special care for GDB_PARALLEL. In that
+ # scenario, multiple expect instances will potentially try
+ # to compile the object file at the same time. The result
+ # should be identical for every one of them, so we just
+ # need to make sure that the final objfile is written to
+ # atomically.
+
if { $gdb_saved_set_unbuffered_mode_obj == "" } {
verbose "compiling gdb_saved_set_unbuffered_obj"
set unbuf_src ${srcdir}/lib/set_unbuffered_mode.c
- set unbuf_obj ${objdir}/set_unbuffered_mode.o
+ # This gives us a per-expect-instance unique filename,
+ # which is important for GDB_PARALLEL. See comments
+ # above.
+ set unbuf_obj [standard_temp_file set_unbuffered_mode.o]
set result [gdb_compile "${unbuf_src}" "${unbuf_obj}" object {nowarnings}]
if { $result != "" } {
@@ -5585,7 +5595,14 @@ proc gdb_compile {source dest type options} {
}
# Link a copy of the output object, because the
# original may be automatically deleted.
- remote_download host $unbuf_obj $gdb_saved_set_unbuffered_mode_obj
+ if {[info exists ::GDB_PARALLEL]} {
+ # Make sure to write the .o file atomically.
+ # (Note GDB_PARALLEL mode does not support remote
+ # host testing.)
+ file rename -force -- $unbuf_obj $gdb_saved_set_unbuffered_mode_obj
+ } else {
+ remote_download host $unbuf_obj $gdb_saved_set_unbuffered_mode_obj
+ }
} else {
verbose "gdb_saved_set_unbuffered_obj already compiled"
}