public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <38FE4861.4853C1EA@cygnus.com> (raw)
In-Reply-To: <87aeiqyp2z.fsf@cygnus.com>

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

  parent reply	other threads:[~2000-04-19 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-19 10:29 console Tom Tromey
2000-04-19 12:05 ` console Fernando Nasser
2000-04-19 17:00 ` Andrew Cagney [this message]
2000-04-20  1:11   ` console Kai Ruottu

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=38FE4861.4853C1EA@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=tromey@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).