This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Target stderr not displayed thru MI
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: Denis PILAT <denis dot pilat at st dot com>, gdb-patches at sources dot redhat dot com
- Date: Fri, 2 Dec 2005 09:13:59 +1300
- 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>
> Nick, what's your reasoning for separating this from the stdout data?
> When we put the inferior onto its own TTY, we don't get stdout and
> stderr separated, either.
I was just trying to interpret what Denis said:
DP> The main problem with MI is that we can not distinguish target stdout
DP> from target stderr.
I don't see any harm as, in the remote case, it presumably just prepends parts
of a single stream with a different character. This would be easy to merge
back if it wasn't needed.
More recently, he has said that one stream is enough for his purposes:
DP> I'm not sticked to have one more MI stream today since nobody
DP> will use it efficiently, I just need to have at least target error
DP> reported to a stream, even if it's the only mi stream available (mi->targ).
Since no-one else appears to need another MI stream, or possibly even use MI
for remote debugging, if we accept that adding a stream later may present
compatibility problems, his original patch seems appropriate.
Nick