From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10226 invoked by alias); 20 Dec 2004 16:27:20 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9957 invoked from network); 20 Dec 2004 16:27:13 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by sourceware.org with SMTP; 20 Dec 2004 16:27:13 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id LAA11959 for ; Mon, 20 Dec 2004 11:52:31 -0500 Received: (from alain@localhost) by smtp.ott.qnx.com (8.8.8/8.6.12) with UUCP id LAA18469 for gdb@sources.redhat.com; Mon, 20 Dec 2004 11:27:09 -0500 Message-Id: <200412201627.LAA18469@smtp.ott.qnx.com> Subject: Re: Registry Group To: cagney@gnu.org (Andrew Cagney) Date: Mon, 20 Dec 2004 16:27:00 -0000 From: "Alain Magloire" Cc: dalexiev@ti.com (Alexiev Dobrin), gdb@sources.redhat.com In-Reply-To: <41C3810A.4070601@gnu.org> from "Andrew Cagney" at Dec 17, 2004 07:59:54 PM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-12/txt/msg00104.txt.bz2 > > Alexiev, Dobrin wrote: > > 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"} > > ] > > Sure! have you looked at the output from: > (gdb) maint print register-groups > as it should make a good starting point. > > I suspect that the output should be more like: > ...{name="r0",groups=["grp1","grp2",...]},... > (the MI syntax police will quickly point out the exact syntax :-). > I think Alexiev is off to see Santa 'til January .. but this is a not from a patch he dropped to the CDT mailing list it should give you a rough idea of his way of thinking. The part about a default "Main" group is probably CDT specific and there for backward compatibility. /** * Custom command for requesting the register groups. * It is not yet in the GDB stream. * * -data-list-register-groups * * The format of the command is: * IN:(gdb)-data-list-register-groups * OUT:^done,register-groups= [{name="r0", group="GRP1"},{name="r8",group="GRP2"}] * * It is similar of the command: "-data-list-register-values". * * The register group names are case sensitive. * * The register groups appear in the Register View in order they are returns from * the command "-data-list-register-groups". * * The registers appear in the groups in the order they are returned from the * command "-data-list-register-names". * The register names are case sensitive. * * If the debugger doesn<92>t support the command "-data-list-register-groups" all * registers are added to the "Main" group. * If there is a register returned by the command "-data-list-register-names" but not * in the command "-data-list-register-groups" it is added to the "Main" group. * The main group itself is added first to the Register view. * If there is a register returned by the command "-data-list-register-groups" but not in * the command "-data-list-register-names" the register is ignored. */ -- au revoir, alain