This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: mi/1654: Textual output from target not contained in target outputstream
- From: Salvador Eduardo Tropea <salvador at inti dot gov dot ar>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 25 Aug 2004 21:08:00 -0000
- Subject: Re: mi/1654: Textual output from target not contained in target outputstream
- Reply-to: Salvador Eduardo Tropea <salvador at inti dot gov dot ar>
The following reply was made to PR mi/1654; it has been noted by GNATS.
From: Salvador Eduardo Tropea <salvador@inti.gov.ar>
To: gdb-gnats@sources.redhat.com, nick@optonline.net
Cc:
Subject: Re: mi/1654: Textual output from target not contained in target output
stream
Date: Wed, 25 Aug 2004 17:58:35 -0300
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=3Dview audit-trail
The change isn=B4t that easy, go and take a look at the gdb code. At leas=
t=20
the gdb versions I analyzed doesn=B4t process the output of the target at=
=20
all. You get it directly from the target program.
And this behavior doesn=B4t "voids the purpose of MI2".
My frontend uses a separated terminal for the target, that=B4s all you=20
need to avoid the mix of messages.
Take a look at libmigdb project at Source Forge.
SET