This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: MI testsuite to use PTY for inferior


On Mon, Aug 01, 2005 at 09:00:24AM -0400, Daniel Jacobowitz wrote:
> On Mon, Aug 01, 2005 at 07:30:02AM -0400, Bob Rossi wrote:
> > Hi Eli,
> > 
> > I am claiming that a reliable FE can not be written if the inferior writes 
> > data to the same output stream as GDB/MI's output stream. So, on native 
> > windows, if the inferior I/O and GDB/MI I/O can not be separated, it 
> > wouldn't be worth while to write an FE on that platform.
> 
> That's a very strange judgement call:
> 
>  (A) The huge majority of Windows programs don't even write to the
> console.

Yes, well these would work just fine, of course.

>  (B) The huge majority of programs which write to stdout, on Windows
> or otherwise, couldn't possibly be confused with GDB/MI output.

This is the scenario that really stinks for the FE. Currently the way
things stand on UNIX, a FE can be written nicely, and work in all
case's. However, in windows, no longer can a FE have a clean
implementation. It needs to begin guessing what output is from GDB and
what output is from the inferior.

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?

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.

Thanks,
Bob Rossi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]