From: Bob Rossi <bob@brasko.net>
To: gdb-patches@sources.redhat.com
Subject: Re: MI testsuite to use PTY for inferior
Date: Mon, 01 Aug 2005 14:07:00 -0000 [thread overview]
Message-ID: <20050801140709.GC26772@white> (raw)
In-Reply-To: <20050801140017.GA6073@nevyn.them.org>
On Mon, Aug 01, 2005 at 10:00:17AM -0400, Daniel Jacobowitz wrote:
> [Sorry for the duplicate; sourceware hiccupped.]
>
> On Mon, Aug 01, 2005 at 09:30:56AM -0400, Bob Rossi wrote:
> > On Mon, Aug 01, 2005 at 09:23:51AM -0400, Daniel Jacobowitz wrote:
> > > On Mon, Aug 01, 2005 at 09:16:27AM -0400, Bob Rossi wrote:
> > > > Is there an easy and clean way to solve this problem? Maybe this problem
> > > > is easier to solve than I think it is. Any suggestions?
> > >
> > > No, but the heuristics are easier than you think they are.
> > >
> > > > Honestly, I don't care if someone writes an FE that does this kind of
> > > > processing, the only reason I really care about this topic is because I
> > > > would prefer to use the TTY option in the testsuite to ensure the I/O is
> > > > separated. Doing this though, leaves target's without TTY's
> > > > semi-untested.
> > >
> > > As already written, expect requires a TTY anyway. No TTY, no
> > > testsuite.
> >
> > I aggree with the above. However, my point is that the testsuite
> > will no longer test interleaved output. It would only test GDB under the
> > assumption that the tty command works.
>
> These are tests of a frontend's ability to handle unexpected output,
> not tests of GDB itself; I don't see GDB needing much in the way of
> tests for them. I pick my things to worry about :-)
OK, So I'm assuming the wise thing to do would be to go ahead with my
patch and drop the discussion of support on native windows.
I'll provide the already given changes needed, and repost.
Thanks,
Bob Rossi
next prev parent reply other threads:[~2005-08-01 14:07 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 5:54 Nick Roberts
2005-07-30 17:39 ` Bob Rossi
2005-07-30 18:08 ` Daniel Jacobowitz
2005-07-30 22:47 ` Nick Roberts
2005-07-31 1:19 ` Daniel Jacobowitz
2005-07-30 22:47 ` Nick Roberts
2005-07-30 23:03 ` Bob Rossi
2005-07-31 1:21 ` Daniel Jacobowitz
2005-07-31 13:16 ` Bob Rossi
2005-07-31 15:31 ` Daniel Jacobowitz
2005-07-31 21:20 ` Bob Rossi
2005-08-01 1:53 ` Daniel Jacobowitz
2005-08-01 2:05 ` Bob Rossi
2005-08-01 2:15 ` Daniel Jacobowitz
2005-08-01 11:32 ` Bob Rossi
2005-08-01 3:56 ` Eli Zaretskii
2005-08-01 11:30 ` Bob Rossi
2005-08-01 13:00 ` Daniel Jacobowitz
2005-08-01 13:16 ` Bob Rossi
2005-08-01 13:23 ` Daniel Jacobowitz
2005-08-01 13:31 ` Bob Rossi
2005-08-01 14:00 ` Daniel Jacobowitz
2005-08-01 14:07 ` Bob Rossi [this message]
2005-08-01 18:45 ` Eli Zaretskii
2005-08-01 19:01 ` Mark Kettenis
2005-08-01 19:25 ` Daniel Jacobowitz
2005-08-01 19:34 ` Mark Kettenis
2005-08-01 19:43 ` Bob Rossi
2005-08-01 20:48 ` Eli Zaretskii
2005-08-01 20:45 ` Eli Zaretskii
2005-08-01 20:52 ` Daniel Jacobowitz
2005-08-02 3:45 ` Eli Zaretskii
2005-08-02 3:50 ` Daniel Jacobowitz
2005-08-02 20:46 ` Eli Zaretskii
2005-08-02 20:48 ` Daniel Jacobowitz
2005-08-13 17:26 ` Bob Rossi
2005-08-13 21:41 ` Daniel Jacobowitz
2005-07-31 21:35 ` Nick Roberts
2005-07-31 21:37 ` Daniel Jacobowitz
2005-07-31 23:32 ` Nick Roberts
2005-08-01 1:51 ` Daniel Jacobowitz
2005-08-03 2:07 ` Bob Rossi
2005-08-03 12:48 ` Bob Rossi
2005-08-03 13:19 ` Daniel Jacobowitz
2005-08-03 18:22 ` Bob Rossi
2005-08-03 18:23 ` Daniel Jacobowitz
2005-08-03 18:24 ` Bob Rossi
2005-08-03 18:32 ` Daniel Jacobowitz
2005-08-03 19:31 ` Bob Rossi
2005-08-04 2:23 ` Bob Rossi
2005-08-04 2:27 ` Bob Rossi
2005-08-04 4:05 ` Daniel Jacobowitz
2005-08-04 13:07 ` Bob Rossi
-- strict thread matches above, loose matches on Subject: below --
2005-07-27 3:18 Bob Rossi
2005-08-13 22:04 ` Mark Kettenis
2005-08-20 9:07 ` Bob Rossi
2005-08-30 2:55 ` Daniel Jacobowitz
2005-09-01 0:52 ` Bob Rossi
2005-09-01 22:12 ` Mark Kettenis
2005-09-01 23:52 ` Bob Rossi
2005-09-05 19:52 ` Bob Rossi
2005-09-10 4:02 ` 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=20050801140709.GC26772@white \
--to=bob@brasko.net \
--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