public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Braxton Thomason <brax@ieeecs.ece.utexas.edu>
To: James Ingham <jingham@cygnus.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: GDB Console Q
Date: Thu, 02 Mar 2000 11:00:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.96.1000302125923.22408A-100000@ieeecs.ece.utexas.edu> (raw)
In-Reply-To: <14526.44844.697200.155056@leda.cygnus.com>

Thanks guys!  The command "tk gdb_restore_fputs" did correct the problem,
however, I cannot seem to reproduce the error with the debug window
open... I will continue running the deubg window, and see what happens...

thanks,
brax.


On Thu, 2 Mar 2000, James Ingham wrote:

> Bad boy, read ALL mail before responding...
> 
> Anyway, Keith's explanation may be the ticket.  The way to test this
> is to try running my little sanity proc, just do:
> 
> (gdb) tk gdb_restore_fputs
> 
> and if you get output again, then Keith is right, there was some error 
> down in the guts of gdb.  The "tk" command just routes its arguments
> to the Tcl interpreter hiding in Insight...
> 
> I have noticed a few of these in the variable subsystem, I stamped out
> a few, but would not be suprised if more remain.  One thing you can
> try is to set the environment variable
> 
> setenv GDBTK_DEBUG 2
> 
> Then when you next start up gdb, you will get a debug window that
> spews out lots of output as gdb does its thing.  In here you may see
> some suspicious output shortly before you lose output.  Cut & paste
> that here, and it will give us a hand in figuring out what is going
> on.
> 
> Jim
> 
> 
>  > Braxton,
>  > 
>  > The GDB Console in Insight is not a exactly equivalent to the console
>  > in command line gdb.  In particular, it does not intercept stdout &
>  > stdin.  That is because we didn't want to have to write a full
>  > terminal emulator in the Tk text widget.  Instead, program I/O still
>  > goes to the console from which you launched gdb, which already knows
>  > how to handle raw mode I/O, etc...  The Insight console is just used
>  > for interactions with gdb.
>  > 
>  > Jim
>  > 
>  >  > 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...
>  >  > 
>  >  > thanks,
>  >  > brax.
>  >  > 
>  >  > 
>  >  > 
>  > 
>  > -- 
>  > ++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++
>  > Jim Ingham                                              jingham@cygnus.com
>  > Cygnus Solutions, a Red Hat Company                      
>  > 
> 
> -- 
> ++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++
> Jim Ingham                                              jingham@cygnus.com
> Cygnus Solutions, a Red Hat Company                      
> 

      reply	other threads:[~2000-03-02 11:00 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
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 [this message]

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=Pine.LNX.3.96.1000302125923.22408A-100000@ieeecs.ece.utexas.edu \
    --to=brax@ieeecs.ece.utexas.edu \
    --cc=insight@sourceware.cygnus.com \
    --cc=jingham@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).