public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Ensure index cache entry written in test
Date: Mon, 06 Mar 2023 20:24:51 +0200	[thread overview]
Message-ID: <83pm9l7n64.fsf@gnu.org> (raw)
In-Reply-To: <20230306164553.1449009-1-tromey@adacore.com> (message from Tom Tromey via Gdb-patches on Mon, 6 Mar 2023 09:45:53 -0700)

> Cc: Tom Tromey <tromey@adacore.com>
> Date: Mon,  6 Mar 2023 09:45:53 -0700
> From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
> 
> 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.
> ---
>  gdb/NEWS                               |  3 +++
>  gdb/doc/gdb.texinfo                    |  6 ++++++
>  gdb/dwarf2/cooked-index.c              | 15 +++++++++++++++
>  gdb/testsuite/gdb.base/index-cache.exp |  2 ++
>  4 files changed, 26 insertions(+)

OK for the documentation parts.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

      parent reply	other threads:[~2023-03-06 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 16:45 Tom Tromey
2023-03-06 17:59 ` Simon Marchi
2023-03-07 14:58   ` Tom Tromey
2023-03-07 17:21     ` Simon Marchi
2023-03-07 18:25       ` Tom Tromey
2023-03-09  1:58         ` Simon Marchi
2023-03-24 22:25           ` Tom Tromey
2023-03-06 18:24 ` Eli Zaretskii [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pm9l7n64.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).