From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Ensure index cache entry written in test
Date: Tue, 7 Mar 2023 12:21:28 -0500 [thread overview]
Message-ID: <2fd34bd5-fe16-e2d4-7585-f693fdc5d8dd@simark.ca> (raw)
In-Reply-To: <87sfegsj5f.fsf@tromey.com>
On 3/7/23 09:58, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
>
>>> + gdb_test_no_output "maintenance wait-for-index-cache"
>
> Simon> I would perhaps put this command in the run_test_with_flags proc, so
> Simon> that it applies to other tests as well. It shouldn't be necessary for
> Simon> those tests, but if there's a bug somewhere, it would make it reproduce
> Simon> more reliably.
>
> I made this change. It required the appended hunk as well, to avoid a
> duplicate test name.
>
> I'm going to check it in now.
Heh, we get that now:
(gdb) maintenance selftest help
Running selftest help_doc_invariants.
help doc broken invariant: command 'maintenance wait-for-index-cache' help doc first line is not terminated with a '.' character
Self test failed: self-test failed at /home/simark/src/binutils-gdb/gdb/unittests/command-def-selftests.c:99
Ran 1 unit tests, 1 failed
I guess swap the lines? That's how other commands do it:
Print value of expression EXP.
Usage: print [[OPTION]... --] [/FMT] [EXP]
Print backtrace of all stack frames, or innermost COUNT frames.
Usage: backtrace [OPTION]... [QUALIFIER]... [COUNT | -COUNT]
Simon
next prev parent reply other threads:[~2023-03-07 17:21 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 [this message]
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
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=2fd34bd5-fe16-e2d4-7585-f693fdc5d8dd@simark.ca \
--to=simark@simark.ca \
--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).