This is the mail archive of the gdb-patches@sourceware.org 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: [PATCH] Target stderr not displayed thru MI

From: Jim Blandy <jimb at red-bean dot com>
To: Nick Roberts <nickrob at snap dot net dot nz>
Cc: Daniel Jacobowitz <drow at false dot org>, Denis PILAT <denis dot pilat at st dot com>, gdb-patches at sources dot redhat dot com
Date: Thu, 1 Dec 2005 17:23:28 -0800
Subject: Re: [PATCH] Target stderr not displayed thru MI
References: <17293.36697.854192.691800@kahikatea.snap.net.nz> <438DA1DE.2020406@st.com> <17294.2894.345752.773239@kahikatea.snap.net.nz> <438F011F.7050403@st.com> <20051201140436.GA31759@white> <20051201143218.GB13069@nevyn.them.org> <17295.22919.290876.649298@kahikatea.snap.net.nz>

Adding a new MI output stream with its own magic character will break
existing MI clients.  I don't think that's worthwhile, especially
given that, when a program is talking to a TTY, you can't distinguish
the two either.

If, at some point in the future, the MI protocol does get extended to
distinguish the two streams, the code will be ready for it, since we
already distinguish gdb_stdtarg and gdb_stdtargerr internally.  This
change doesn't make future improvements difficult.

References:
- Re: [PATCH] Target stderr not displayed thru MI
  - From: Denis PILAT
- Re: [PATCH] Target stderr not displayed thru MI
  - From: Bob Rossi
- Re: [PATCH] Target stderr not displayed thru MI
  - From: Daniel Jacobowitz
- Re: [PATCH] Target stderr not displayed thru MI
  - From: Nick Roberts

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