From: 'Bob Rossi' <bob@brasko.net>
To: Dave Korn <dave.korn@artimi.com>
Cc: 'GDB' <gdb@sources.redhat.com>
Subject: Re: How do I get regexp from expect at gdb_expect?
Date: Tue, 01 Feb 2005 16:10:00 -0000 [thread overview]
Message-ID: <20050201161012.GD9962@white> (raw)
In-Reply-To: <NUTMEGvFSS9SUhbuAb3000003dd@NUTMEG.CAM.ARTIMI.COM>
On Tue, Feb 01, 2005 at 03:58:40PM -0000, Dave Korn wrote:
> > -----Original Message-----
> > From: gdb-owner On Behalf Of Bob Rossi
> > Sent: 01 February 2005 14:39
>
> > With all of this in mind, does disabling the 'echoing' of the terminal
> > sound reasonable?
>
>
> .... just so long as you create a duplicate of the entire existing testsuite
> that runs without echos, in order to be sure that _both_ modes work .... <g>
Honestly, I could be way off on this, but I don't think that the 'echo'
feature of the MI testsuite is testing anything important. In fact, the
front ends using GDB in this way will never see the 'echo'd' data.
I sort of think it would make complete sense to have Expect not look at
the 'echo'd' data from the terminal. After all, the MI interface wasn't
meant to be run on the terminal ...
Bob Rossi
prev parent reply other threads:[~2005-02-01 16:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 2:57 Bob Rossi
2005-01-29 3:09 ` Paul Hilfinger
2005-01-29 3:11 ` Bob Rossi
2005-01-29 3:16 ` Bob Rossi
2005-01-31 15:07 ` Bob Rossi
2005-01-31 16:28 ` Daniel Jacobowitz
2005-01-31 16:59 ` Bob Rossi
2005-01-31 21:10 ` Bob Rossi
2005-01-31 21:21 ` Daniel Jacobowitz
2005-01-31 22:00 ` Bob Rossi
2005-01-31 22:04 ` Daniel Jacobowitz
2005-01-31 22:12 ` Bob Rossi
2005-02-01 3:52 ` Daniel Jacobowitz
2005-02-01 14:20 ` Bob Rossi
2005-02-01 14:23 ` Daniel Jacobowitz
2005-02-01 14:39 ` Bob Rossi
2005-02-01 15:20 ` Daniel Jacobowitz
2005-02-01 15:38 ` Bob Rossi
2005-02-01 15:58 ` Dave Korn
2005-02-01 16:10 ` 'Bob Rossi' [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=20050201161012.GD9962@white \
--to=bob@brasko.net \
--cc=dave.korn@artimi.com \
--cc=gdb@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