Re: [PATCH] Target stderr not displayed thru MI

Daniel Jacobowitz
2005-12-01T14:32:29Z

On Thu, Dec 01, 2005 at 09:04:36AM -0500, Bob Rossi wrote:
> > I attach a new patch in that sense. It does not include the documentation
> > patch about MI new stream but it's just to give you an idea.
> > Any comment ?
>
> > + /* MI 1 and 2 target error stream use the same steam prefix "@" in oder
> > + to ensure backward compatibility with old frondtend, MI 3 uses
> > + a new prefix "#" */
> > + if (mi_version (uiout) > 2)
> > + mi->targerr = mi_console_file_new (raw_stdout, "#", '"');
> > + else
> > + mi->targerr = mi_console_file_new (raw_stdout, "@", '"');
> > +
> > mi->event_channel = mi_console_file_new (raw_stdout, "=", 0);
>
> We have a lot of people that are confused about the target-stream-output
> and it was recently brought up that maybe this wasn't used and should be
> removed.
>
> http://sources.redhat.com/ml/gdb/2005-11/msg00391.html
>
> However, you seem to be using it, and want to add another stream-output,
> probably called something like target-stream-stderr-output.
>
> 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.

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.

--
Daniel Jacobowitz
CodeSourcery, LLC