From: Andrew Cagney <cagney@gnu.org>
To: Johannes Overmann <Johannes.Overmann@arm.com>
Cc: gdb@sources.redhat.com
Subject: Re: Not seeing target output in GDB/MI
Date: Sun, 12 Dec 2004 15:25:00 -0000 [thread overview]
Message-ID: <41BC627C.2070702@gnu.org> (raw)
In-Reply-To: <41B97648.5040107@arm.com>
> - Is there a way to see the target output (stdout) unbuffered or line
> buffered
> and still using pipes to comminucate with gdb?
>
> - Why is the target output not visible in the target-stream-output
> described in the
> MI documentation (e.g. prefixed by @)? I see it just as any other output
> coming from gdb without any indication that it comes from the target.
MI was first developed on a remote target where implementing this was
relatively easy. That isn't the case for native and the code was never
written. Instead, as you note for DDD, native MI clients use 'gdb
--tty=...'.
Perhaphs the thing to do here is deprecate the MI mechanism and
recommend -tty for both native and remote cases (this of course will
mean that the remotes need to be changed).
Andrew
prev parent reply other threads:[~2004-12-12 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 10:12 Johannes Overmann
2004-12-10 13:38 ` Daniel Jacobowitz
2004-12-12 15:25 ` Andrew Cagney [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=41BC627C.2070702@gnu.org \
--to=cagney@gnu.org \
--cc=Johannes.Overmann@arm.com \
--cc=gdb@sources.redhat.com \
/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