This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Not seeing target output in GDB/MI
- From: Andrew Cagney <cagney at gnu dot org>
- To: Johannes Overmann <Johannes dot Overmann at arm dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Sun, 12 Dec 2004 10:23:40 -0500
- Subject: Re: Not seeing target output in GDB/MI
- References: <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