+1 for assigning a low priority to
this. It’s nice to have, but not necessary.
In fact, I just tried this on CDI-GDB and
it’s not working very well. The newly added register groups don’t
show up until I launch a subsequent debug session!
This feature also doesn’t support
drag-and-drop, which I think it should. In any case, I don’t think
it was used very often so assigning it a low priority makes sense.
- Navid
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of ken.ryall@xxxxxxxxx
Sent: Friday, April 16, 2010 11:02
AM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] editing
register groups
I noticed that too, I agree
it’s nice to keep track of but not required for now.
- Ken
From: ext John
Cortell <rat042@xxxxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Fri, 16 Apr 2010 14:39:07
+0200
To: "cdt-dev@xxxxxxxxxxx" <cdt-dev@xxxxxxxxxxx>
Subject: [cdt-dev] editing
register groups
235747 was opened as a DSF-GDB parity issue and it is currently in the
high-priority bucket. The description states:This
is not necessarily very practical but for feature equivalence, DSF-GDB should
implement it.
I suspect that is correct--that editing register groups is a rarely
used feature of the CDT debugger (CDI-GDB). If that's true, then this issue
should be lowered in priority, as per the discussions we've had on this topic
recently. If you know people are using it, or are very confident they are,
please speak up.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=235747
