From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite] Fix expected output for "help set follow-fork-mode"
Date: Sun, 04 Apr 2004 21:12:00 -0000 [thread overview]
Message-ID: <20040404211241.GA4932@nevyn.them.org> (raw)
In-Reply-To: <20040404203539.GG871@gnat.com>
On Sun, Apr 04, 2004 at 01:35:39PM -0700, Joel Brobecker wrote:
> There has been a recent change to infrun (made on 2004-01-13) that
> removed the choice "ask" to the possible values for "follow-fork-mode".
> The help text for that variable was then modified, but the test
> verifying that the help for this command exists has not been modified.
>
> This patch updates the expected output to match the new help text.
>
> 2004-04-04 Joel Brobecker <brobecker@gnat.com>
>
> * gdb.base/foll-fork.exp: Update the expected output for
> "help set follow-fork-mode", to match a change that was made
> to the help of this variable on 2004-01-13.
>
> Checked in as obvious.
Thanks. I keep meaning to fix up this test to run, when possible, on
GNU/Linux; but there's some trickiness involved and I've failed to do
it adequately a few times now.
>
> I don't really know the purpose of this test. If, as the comment
> suggests:
>
> # Verify that help is available for "set follow-fork-mode".
>
> Then I would recommend that we don't need to check for the entire
> help text word for word. I would simply check for the first line,
> or even maybe just check that we receive something, anything, before
> we get the prompt back.
I agree, personally.
> (BTW, Is it really necessary to use send_gdb + gdb_expect? Could gdb_test
> work just as well?)
Yes, feel free.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-04-04 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 20:35 Joel Brobecker
2004-04-04 21:12 ` Daniel Jacobowitz [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=20040404211241.GA4932@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.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