From: Manoj Iyer <manjo@austin.ibm.com>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: testcase help
Date: Thu, 05 Aug 2004 15:35:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0408051004010.29091@lazy> (raw)
In-Reply-To: <411166D3.nailDGY11SVF9@mindspring.com>
Michael,
I tried ur suggestion but it still did not work, so I used send_gdb and
gdb_expect{} and got it to work. Thanks for the help.
Thanks
----- ----
Manoj Iyer
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cognito ergo sum +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
On Wed, 4 Aug 2004, Michael Chastain wrote:
> I don't even use gdb_continue ... how about just plain:
>
> gdb_test_multiple "continue" "continue to foo ..." {
> ...
> }
>
> Or maybe I'm not getting the problem.
>
> Michael C
>
next prev parent reply other threads:[~2004-08-05 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 20:45 Manoj Iyer
2004-08-04 22:44 ` Michael Chastain
2004-08-05 15:35 ` Manoj Iyer [this message]
2004-08-05 23:26 ` thread testcase compile issue (question) Manoj Iyer
2004-08-06 6:09 ` Michael 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=Pine.LNX.4.58.0408051004010.29091@lazy \
--to=manjo@austin.ibm.com \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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).