From f0c3dcc1ca714cb17602f4c12c00b3604f36b035 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Fri, 3 Mar 2023 09:41:35 -0700 Subject: Ensure index cache entry written in test Now that index cache files are written in the background, one test in index-cache.exp is racy -- it assumes that the cache file will have been written during startup. This patch fixes the problem by introducing a new maintenance command to wait for all pending writes to the index cache. Approved-By: Simon Marchi Reviewed-By: Eli Zaretskii --- gdb/doc/gdb.texinfo | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'gdb/doc') diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index bfda7ed..954f148 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -41374,6 +41374,12 @@ give an error. For platforms that do support creating the backtrace this feature is @code{on} by default. +@kindex maint wait-for-index-cache +@item maint wait-for-index-cache +Wait until all pending writes to the index cache have completed. This +is used by the test suite to avoid races when the index cache is being +updated by a worker thread. + @kindex maint with @item maint with @var{setting} [@var{value}] [-- @var{command}] Like the @code{with} command, but works with @code{maintenance set} -- cgit v1.1