public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Alexiev, Dobrin" <dalexiev@ti.com>
To: <gdb@sources.redhat.com>
Subject: Registry Group
Date: Thu, 16 Dec 2004 16:44:00 -0000	[thread overview]
Message-ID: <C99FD21253EDE241A6E7FF989CFB493EEA3CE2@dlee2k02.ent.ti.com> (raw)

I am working with the Eclipse C Development Tools community to add a
feature that will group registers in the Register View of Eclipse. 

Since embedded CPUs have lots of peripheral registers (50-100+) it is
getting a burden for the developer to keep scrolling the registry view
to find the right register. A grouping will make the user experience way
better. 

Since the IDE is relying on the GDB for most of the device information I
was wandering if there is a similar MI/GDB command to obtain the name of
the groups and their registers association. 

In our product we added such command "-data-list-register-groups". The
syntax of the command is: 
-data-list-register-groups
^done,register-groups=[{name="r0",group="GRP1"},{name="r8",group="GRP2"}
]
It is created similar to "-data-list-register-names".

I found opened enhancement request for this - "850 - Missing MI
interface to register groups". In case that is not implemented we can
offer to submit patch for GDB that will support this command. 

Any other ideas will be appreciated. 
Thanks

Dobrin Alexiev
Texas Instruments 

             reply	other threads:[~2004-12-16 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 16:44 Alexiev, Dobrin [this message]
2004-12-18  1:03 ` Andrew Cagney
2004-12-20 16:27   ` Alain Magloire
     [not found] <200412201627.LAA00079@smtp.ott.qnx.com>
2005-01-04 20:20 ` 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=C99FD21253EDE241A6E7FF989CFB493EEA3CE2@dlee2k02.ent.ti.com \
    --to=dalexiev@ti.com \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).