From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <ac131313@cygnus.com>
To: tromey@cygnus.com
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: console
Date: Wed, 19 Apr 2000 17:00:00 -0000
Message-id: <38FE4861.4853C1EA@cygnus.com>
References: <87aeiqyp2z.fsf@cygnus.com>
X-SW-Source: 2000-q2/msg00115.html

Tom Tromey wrote:
> 
> A few weeks ago I sent Jim some code to let Insight use xterm as the
> console window.  But while debugging gcc I've come to realize that
> this is overkill for many applications.
> 
> gcc has some very complex data structures and some functions to print
> these out.  I'd like to use these, as opposed to Insight's display
> features, because the gcc functions are still easier to use.  However,
> having a separate xterm (right now, the xterm from which I started
> gdb) for this is a pain.
> 
> So, in some situations at least, it would be very convenient to have
> the inferior's stdout be shown in the gdb console window.

Ha! Trivial ;-^

I believe the work required goes something like this:

	o	get insight / GDB sharing a common
		event loop (the TK one I guess)

	o	have the program output routed
		to gdb where it can in turn (gdb_stdtarg)
		route it through to the console

it should be possibile to attack the two parts fairly independantly.

	Andrew