Re: [PATCH] Target stderr not displayed thru MI

[Denis PILAT <denis.pilat@st.com>]

>>
>>I haven't seen MI use the target-stream-output yet. What is your
>>configuration that makes this happen? Is it still useful to you?
>>If so, it would be nice if we could improve the doco a bit, to let users
>>know when this would be useful for them.
>>
>
>It's used for any (most?) remote or simulator targets that can provide
>output.  I'm sorry if I was not adequately clear about that.  The ST
>folks appear to have their own proprietary remote target, which also
>generates these packets.
>
>
>

Daniel, Nick,

You're right, we have remote targets that are accessed thru a GDB that runs
under Eclipse. These targets outputs error that are not displayed anywhere,
my initial patch was about to fix that
(http://sources.redhat.com/ml/gdb-patches/2005-11/msg00497.html).

Adding a new stream to MI (target error stream) with a prefix different
from the others, will offer a possibility for future Eclipse (or any 
front end)
- 1st to get the stderr of the inferior.
- 2nd to distinguish it from target stdout.

I'm not sticked to have one more MI stream today since nobody
will use it efficiently, I just need to have at least target error
reported to a stream, even if it's the only mi stream available (mi->targ).

Hope I'm not adding more confusion.

Denis