Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346301

Summary:	add/edit/remove/restore register group for registers view should be overridable for non CDI debuggers
Product:	[Tools] CDT	Reporter:	Winnie Lai <wlai>
Component:	cdt-debug	Assignee:	cdt-debug-inbox <cdt-debug-inbox>
Status:	REOPENED ---	QA Contact:	Jonah Graham <jonah>
Severity:	normal
Priority:	P3	CC:	cdtdoug, marc.khouzam, pawel.1.piech, steffen-schmidt
Version:	8.0	Flags:	alvaro.sanchez-leon: juno-
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:
Bug Depends on:
Bug Blocks:	235747

Description Winnie Lai

2011-05-18 12:54:22 EDT

Build Identifier: 3.7 M7

Current actions for add/remove/edit/restore register group in registers view
assume the 'debug target' is IDebugElement and ICDebugTarget. These assumptions do not fit into dsf gdb, thus there is a need to let other cdt gdb (non-cdi) debugger based registers view to override these actions.


Reproducible: Always

Comment 1 Marc Khouzam

2012-06-29 15:01:27 EDT

Winnie, do you have some implementation of register groups for DSF?

Comment 2 Winnie Lai

2012-06-29 17:03:35 EDT

(In reply to comment #1)
> Winnie, do you have some implementation of register groups for DSF?

I have the concept of nested register groups. No magic - I simply allow a register group dm context can have (0..*) register group dm context on service side; and a similar concept on view model side - a group node can have a group node and a regiser node.

The hierarchy is determined by both the hardware model and the software side. The sw side is more or less making a simple grouping, say any group having >100 registers will be grouped -- nothing elegant.
After the nested group is implemented, it won't be hard to allow user driven grouping - just an extension of sw grouping logic.

Comment 3 Alvaro Sanchez-Leon

2013-06-17 11:24:01 EDT

Accidentally marked as fixed, 
so it's now re-opened