Re: [PATCH] Target stderr not displayed thru MI

Nick Roberts
2005-12-01T20:14:23Z

> 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