From: Tom Tromey <tom@tromey.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch, testsuite] skip tab-completion tests if no readline
Date: Wed, 19 Sep 2018 12:57:00 -0000 [thread overview]
Message-ID: <87o9ctr6gq.fsf@tromey.com> (raw)
In-Reply-To: <ae3d90cf-0096-18fc-a004-68c6888c50b7@codesourcery.com> (Sandra Loosemore's message of "Tue, 18 Sep 2018 22:23:49 -0600")
>>>>> "Sandra" == Sandra Loosemore <sandra@codesourcery.com> writes:
Sandra> I found a bunch of borked tab-completion tests when running tests on a
Sandra> remote Windows host, where the input stream is not a tty and has no
Sandra> readline support. I've copied the test for readline support verbatim
Sandra> from the older gdb.base/completion.exp testcase into these newer
Sandra> testcases. OK to commit?
Actually, I had a couple thoughts just as I hit send...
Sandra> # This file is part of the gdb testsuite.
Sandra> +# Tests below are about tab-completion, which doesn't work if readline
Sandra> +# library isn't used. Check it first.
Sandra> +
Sandra> +if { ![readline_is_used] } {
Sandra> + return -1
Sandra> +}
Perhaps the early returns should call "untested". I'm on the fence
about this, sometimes it is done, sometimes not. I don't know if it
matters to anybody -- I never really look at these lines.
https://sourceware.org/gdb/wiki/GDBTestcaseCookbook#A.22untested.22_calls
Second, this particular check runs early. I wonder if readline_is_used
actually works at this spot, because I would imagine gdb isn't running yet.
What does "runtest cpls-ops.exp" do?
Tom
next prev parent reply other threads:[~2018-09-19 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 4:23 Sandra Loosemore
2018-09-19 12:52 ` Tom Tromey
2018-09-19 12:57 ` Tom Tromey [this message]
2018-09-20 2:18 ` Sandra Loosemore
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=87o9ctr6gq.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=sandra@codesourcery.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