Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: "Martin M. Hunt" <hunt@redhat.com>,
	gdb@sources.redhat.com, insight@sources.redhat.com
Subject: Re: [RFA] New ui_file streams for Insight
Date: Sun, 01 Apr 2001 15:37:00 -0000	[thread overview]
Message-ID: <15047.44412.868498.822806@kwikemart.cygnus.com> (raw)
In-Reply-To: <3AC78B21.8F35C566@cygnus.com>

Andrew Cagney writes:
 > "Martin M. Hunt" wrote:
 > > 
 > > Here are my first set of changes to add support for multiple streams to
 > > Insight. Instead of using the tui code and copying gdb_stdlog and
 > > gdb_stdtarg to gdb_stdout, it creates unique ui_files for each.  Currently
 > > Insight will simple write stderr, stdlog, and stdtarg to the console
 > > window (if it is open).  stderr messages appear in red, stdlog in green,
 > > and stdtarg in blue.
 > 
 > Yes! Thanks.
 > 
 > > In main.c, I moved the creation of the gdbtk ui_files until after the
 > > arguments are parsed.  I don't see that this would cause problems,
 > > although I don't see why any of the ui_files are created before the
 > > command line is processed.
 > 
 > I suspect it isn't yet wired up quite right.  Can this be done by
 > hooking init_ui_hook and/or pre_init_ui_hook and thus eliminate the need
 > for the #ifdefs and externs (1).
 > 

Oops, I missed that. Yes. Thanks

Elena


 > 	Andrew
 > 
 > (1) Don't forget that GDB is trying to reduce the total number of .c
 > extern's and #ifdefs :-)
 > 


  reply	other threads:[~2001-04-01 15:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-31  0:23 Martin M. Hunt
2001-03-31  7:15 ` Fernando Nasser
2001-04-01 12:52 ` Elena Zannoni
2001-04-01 13:10 ` Andrew Cagney
2001-04-01 15:37   ` Elena Zannoni [this message]
2001-04-01 20:02   ` Martin M. Hunt
2001-04-04 16:46     ` Andrew Cagney

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=15047.44412.868498.822806@kwikemart.cygnus.com \
    --to=ezannoni@cygnus.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=hunt@redhat.com \
    --cc=insight@sources.redhat.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