From: Keith Seitz <keiths@cygnus.com>
To: Nick Duffek <nsd@redhat.com>
Cc: fnasser@redhat.com, gdb@sources.redhat.com, insight@sources.redhat.com
Subject: Re: Register group proposal
Date: Wed, 21 Feb 2001 07:58:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010221074809.22540B-100000@ryobi.cygnus.com> (raw)
In-Reply-To: <200102211518.f1LFIm501695@rtl.cygnus.com>
On Wed, 21 Feb 2001, Nick Duffek wrote:
> On 21-Feb-2001, Fernando Nasser wrote:
>
> >The idea is to have a combobox in the register window where the user can
> >select which group of registers to show (or to show all).
>
> I wonder whether it'd be useful to allow multiple register windows, each
> displaying a different group.
Nick, I think this is all a great idea! I was worried for a while that I
would have to extend Insight's stupid "target database" even more than we
already have. It's amazing how much more information a GUI needs compared
to the command line.
I am always happy to see things get pushed back into gdb proper,
especially when there is command line access to the same functionality
(so that means that dejagnu can test the underlying infrastructure).
I hope the people on the other side of the fence realize the utility in
such an interface.
And, yes, having multiple register windows would be useful. I am going to
push back to the philosophy that it would be useful to have multiples of
any window -- some tracking the current execution status of the target,
some 'frozen'. Heck, if we ever get to multi-arch Insight, we'll need the
ability to track, say, different CPUs (and possibly register sets) in the
same session.
Keith
next prev parent reply other threads:[~2001-02-21 7:58 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 20:56 Nick Duffek
2001-02-21 6:44 ` Fernando Nasser
2001-02-21 7:10 ` Nick Duffek
2001-02-21 7:36 ` Fernando Nasser
2001-02-21 7:58 ` Keith Seitz [this message]
2001-02-21 8:50 ` Andrew Cagney
2001-02-21 11:43 ` Andrew Cagney
2001-02-25 15:36 ` Nick Duffek
2001-02-21 11:43 ` Andrew Cagney
2001-02-21 12:28 ` Andrew Cagney
2001-02-21 12:18 ` Andrew Cagney
2001-02-22 0:59 ` Eli Zaretskii
2001-02-22 4:29 ` Nick Duffek
2001-02-22 8:46 ` Andrew Cagney
2001-02-22 8:56 ` Keith Seitz
2001-02-22 9:20 ` Andrew Cagney
2001-02-22 5:17 ` Nick Duffek
2001-02-22 6:36 ` Fernando Nasser
2001-02-22 8:23 ` Andrew Cagney
2001-02-22 7:58 ` Andrew Cagney
2001-02-22 8:37 ` Nick Duffek
2001-02-22 9:12 ` Andrew Cagney
2001-02-22 10:15 ` Nick Duffek
2001-02-22 10:25 ` Andrew Cagney
2001-02-22 11:40 ` Eli Zaretskii
2001-02-22 11:02 ` Kevin Buettner
2001-02-22 12:08 ` Andrew Cagney
2001-02-22 8:16 ` Andrew Cagney
2001-02-21 3:00 Stephane Carrez
2001-02-21 7:00 ` Nick Duffek
2001-02-21 9:34 ` Andrew Cagney
2001-02-22 9:19 Michael Elizabeth Chastain
2001-02-23 2:52 Bernard Dautrevaux
2001-02-24 15:43 ` Nick Duffek
2001-02-26 18:21 ` Andrew Cagney
2001-02-27 10:30 ` Jim Kleck
2001-02-27 11:24 ` Per Bothner
2001-02-27 13:44 ` Jim Kleck
2001-02-27 15:17 ` Andrew Cagney
2001-02-26 5:29 Bernard Dautrevaux
2001-02-26 9:28 ` Christopher Faylor
2001-02-26 10:56 ` Andrew Cagney
2001-02-26 11:28 ` Christopher Faylor
2001-02-26 17:02 ` Andrew Cagney
2001-02-27 8:53 ` Christopher Faylor
2001-02-27 9:57 ` Andrew Cagney
2001-02-28 1:59 Bernard Dautrevaux
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.SOL.3.91.1010221074809.22540B-100000@ryobi.cygnus.com \
--to=keiths@cygnus.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=insight@sources.redhat.com \
--cc=nsd@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).