RE: Output stream for monitor commands

[Marc Khouzam <marc.khouzam@ericsson.com>]

> -----Original Message-----
> From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
> Behalf Of Luis Machado
> Sent: Thursday, July 03, 2014 6:47 AM
> To: Adrian Sendroiu; gdb@sourceware.org
> Subject: Re: Output stream for monitor commands
> 
> On 07/03/2014 11:22 AM, Adrian Sendroiu wrote:
> > Hello,
> >
> > When running gdb inside the Eclipse environment, I noticed that the
> output of the monitor commands goes to the "gdb traces" window, as
> opposed to all others that go to the "gdb" window. This happens because the
> qRcmd packet's response uses the gdb_stdtarg stream while the others use
> gdb_stdout.

[...]
 
> There seems to be an ongoing discussion at
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=208950.

Yes, we are struggling with how to handle the target-stream (prefixed with @).
Currently, from what we understand, GDB does not differentiate between
output from the target (like the result to a monitor command) and output
from the inferior.  This was directing us to print all target-stream output
to the eclipse gdb console, just like when you run gdb from the command-line.

However, this is apparently quite confusing when you have to also handle
input from the inferior and from gdb.  (This may be a non-stop issue only
and I'm waiting on an answer to that).

The solution that is currently being proposed is to have an inferior 
console in eclipse in which we would print target-stream output and handle
input to the inferior, and pay special attention to results of monitor commands
which would be sent to the gdb console instead.  I'm not a fan of this solution
which specifically focuses on the monitor command as an exception.

If anyone has some information on how the target-stream (@) is meant to
be used by a front-end, it may clarify our discussion.

Thanks

Marc