From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: how to call gdb_test "" ... ?
Date: Mon, 18 Feb 2002 15:16:00 -0000 [thread overview]
Message-ID: <20020218181623.A28849@nevyn.them.org> (raw)
In-Reply-To: <200202182237.g1IMbH122114@duracef.shout.net>
On Mon, Feb 18, 2002 at 04:37:17PM -0600, Michael Elizabeth Chastain wrote:
> I am reworking gdb.base/list.exp and in the process I'm converting a lot
> of send_gdb calls to gdb_test. (If you want to know why I'm reworking it,
> I'm getting rid of the "testcnt" mechanism, which list.exp uses instead
> of just issuing a PASS when a test succeeds).
>
> In one place I want to do this:
>
> gdb_test "list list0.c:10" "..."
> gdb_test "" "..."
> gdb_test "" "..."
> gdb_test "" "..."
>
> That is to say, I want to send a "list" command, and then send some
> empty commands and look at the results as usual.
>
> gdb_test does not work with an argument of "".
>
> Is there an easy way to do this, or should I just stick with send_gdb "\n"?
> The test script already calls send_gdb "\n" and I don't mind keeping it
> that way. I'm just wondering if someone knows a better idiom.
Does gdb_test work with "\n"? I think it will. In fact, it appears to
in casual testing.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-18 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 14:37 Michael Elizabeth Chastain
2002-02-18 15:16 ` Daniel Jacobowitz [this message]
2002-02-18 15:32 ` Keith Seitz
2002-02-18 15:33 Michael Elizabeth Chastain
2002-02-18 16:19 ` Daniel Jacobowitz
2002-02-18 15:46 Michael Elizabeth Chastain
2002-02-18 16:28 Michael Elizabeth Chastain
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=20020218181623.A28849@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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