From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: RFC: gdb_test_multiple
Date: Sun, 05 Jan 2003 05:25:00 -0000 [thread overview]
Message-ID: <200301050525.h055PCk10590@duracef.shout.net> (raw)
Sounds great. I am running a Sunday build+test now, which will finish
Sunday evening. Then this will be next on my work list. Among other
things, I will test it with both tcl/expect/dejagnu stacks
(the stock releases that I use / the sourceware dejagnu package,
which has its own version of tcl and expect).
> See the _gdb_message bit? That, _gdb_command, and _gdb_result are set
> in the caller's scope.
Will this work with nested gdb_test_multiple's? People do that occasionally,
although personally I eschew the practice.
> A friend of mine got so fed up with TCL that he rewrote DejaGNU in
> Perl, which he's planning to publish in the next couple of weeks.
> I can see why.
I would be very interested in that but it's a separate line item.
One note about the implementation: could you rename gdb_standard_send
to _gdb_standard_send or gdb_internal_standard_send or something else
that puts more psychological differnce between the exported functions
and the internal functions.
Michael C
next reply other threads:[~2003-01-05 5:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 5:25 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-07 4:33 Michael Elizabeth Chastain
2003-01-05 17:45 Michael Elizabeth Chastain
2003-01-05 16:54 Michael Elizabeth Chastain
2003-01-05 17:38 ` Daniel Jacobowitz
2003-01-05 16:33 Michael Elizabeth Chastain
2003-01-05 16:46 ` Daniel Jacobowitz
2003-01-04 20:16 Daniel Jacobowitz
2003-01-05 15:32 ` Andrew Cagney
2003-01-05 15:42 ` Daniel Jacobowitz
2003-01-06 21:12 ` Andrew Cagney
2003-01-07 3:25 ` Daniel Jacobowitz
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=200301050525.h055PCk10590@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.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