From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: Output from target in MI mode
Date: Fri, 18 Nov 2005 15:31:00 -0000 [thread overview]
Message-ID: <20051118153104.GD9100@nevyn.them.org> (raw)
In-Reply-To: <20051118144715.GB2255@white>
On Fri, Nov 18, 2005 at 09:47:15AM -0500, Bob Rossi wrote:
> On Fri, Nov 18, 2005 at 05:43:46PM +0300, Vladimir Prus wrote:
> > Sure, that's what happening now. But that pty handling is a bit messy, since
> > gdb already knows what output comes from inferior, it could just prepend it
> > with some character.
>
> Actually, I don't think it does. GDB allows the inferior to run, and the
> inferior's output get's directed directly to the terminal (I believe).
That is correct. If GDB easily knew which was which, it would already
be using the MI-formatted output.
> > > The 'target' in teh above sentence I believe is refering to when GDB is
> > > using a remote protocol to a specific piece of hardware. It's not
> > > refering to the host.
> >
> > Ok, then it's not clear to me either. There's specific packet in remote
> > protocol ("OXXXX") which allows to pass arbitrary text from remote side to
> > gdb. Is this what's printed with "@". Or there some other messages from
> > remote that are also printed with "@" prefix?
>
> I'm not sure. I've never seen output with the "@" before it. If you are
> on the host, you will not get the "@" before the I/O from the inferior
> process. Someone else might be able to give you more details on when
> target I/O is done, if at all.
Bob was right again; it's used for the remote console output packets
and was never implemented for anything else.
At this point I suspect it should be removed from the MI.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-11-18 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 12:34 Vladimir Prus
2005-11-18 13:48 ` Bob Rossi
2005-11-18 14:43 ` Vladimir Prus
2005-11-18 14:47 ` Bob Rossi
2005-11-18 15:31 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051118153104.GD9100@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox