public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <kseitz@firetalk.com>
To: Braxton Thomason <brax@ieeecs.ece.utexas.edu>
Cc: insight@sourceware.cygnus.com
Subject: Re: GDB Console Q
Date: Thu, 02 Mar 2000 09:05:00 -0000	[thread overview]
Message-ID: <38BE9F62.900E0494@firetalk.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1000301210939.21345A-100000@ieeecs.ece.utexas.edu>

Braxton Thomason wrote:
> 
> Has anyone had problems with the GDB console in Insight not displaying
> anything after pressing the "Run" button in the GUI?  I am runing on AIX
> 4.3.2..
> 
> Wondering if I should follow it up, or forget it...

Ugh. This is a sad state of affairs... All console I/O for native
targets goes to the controlling xterminal where insight was launched. It
does NOT go to the console window. I had some code from Tom Tromey
(tromey@cygnus.com) that demonstrated how gdbtk/Insight could open a new
xterm for the child process, but I never got around to implementing it.
I kinda like the current behavior. (Whether that's because I really do
like it or because I am just used to it doing that is a mystery to me.
:-)

So, rest assured: what you are observing is "normal". (Now, if you don't
see your programs output in the xterm, that's another problem
altogether.)

Keith
-- 
Why chat when you can Firetalk?
Firetalk ID: Keith (10320)
www.firetalk.com

  reply	other threads:[~2000-03-02  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-01 19:11 Braxton Thomason
2000-03-02  9:05 ` Keith Seitz [this message]
2000-03-02  9:15   ` Braxton Thomason
2000-03-02  9:34     ` Keith Seitz
2000-03-02  9:53 ` James Ingham
2000-03-02 10:10   ` James Ingham
2000-03-02 11:00     ` Braxton Thomason

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=38BE9F62.900E0494@firetalk.com \
    --to=kseitz@firetalk.com \
    --cc=brax@ieeecs.ece.utexas.edu \
    --cc=insight@sourceware.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).