* Added an adjustment to the calculation of the addressable char width
so it does not go beyond the containing cell size when using radixes
where the number of characters does not grow linearly with the number
of octets being represented.
This adjustment is only necessary when the cell can contain the same
number of octets as the addressable size
Change-Id: Ic9643c98094bc28621e6807eeed0c283dbe6672a
information
This facility is dependent of the issues below.
Bug 489512 - Show local variables in the traditional memory render
Bug 489513 - Show registers in the traditional memory render
Allow the user to choose visibility of the available cross reference
information e.g. Variables, Registers
In addition to the preferences at a instance level, a global preference
is introduced to disable the resolution of additional information
altogether.
Change-Id: I9f8b9b612ff288b369ba6fca3402c0c911aa5f48
There are many opportunities for replacing `StringBuffer` with
`StringBuilder` provided that the type isn't visible from the
public API and is used only in internal methods. Replace these
where appropriate.
Change-Id: Ic2f50c5b6f3c3a4eae301bb3b40fb6faed235f79
Signed-off-by: Alex Blewitt <alex.blewitt@gmail.com>
When using DSF-GDB, the handleSuspend event is received only when a
breakpoint is hit (i.e. not when it's actually suspended),
However memory changed events are received when applicable during
stepping, however the base code does not call the "archiveDeltas()" for
this event.
This change adds a call to archiveDeltas if the update mode is set to
UPDATE_ALWAYS upon reception of memory change events.
TO REPRODUCE this problem:
The issue is that only one snap shot of history is applied with the first
address / expression search, and this is used for all other comparissions,
So you can search for a variable with bigger address value as a first
memory search, and then step the code and see that variables close by
with smaller address values will be updated but not colored.
e.g.
&Test -> address 0x110
&X -> address 0x100
if &Test is used as the first memory search, and then the code changes
value of &X while stepping the code, the cell holding &X will not be
colored as expected.
Change-Id: Ibdc1fae6ed73ec2819fe9539d56f9ea9b6302535
spaces with 64-bit address
- Fix scroll adjustments according to current viewport addresses
- Add CTRL-Home/CTRL-END to go to start/end of memory space
- Add Home/END to go to start/end of the row
- Add eclipse debug tracing support
Change-Id: Ifba9f1e6c67e1cc6ccb8f6f8787a55520d8bf9be
Signed-off-by: Teodor Madan <teodor.madan@freescale.com>
Change-Id: I0e72b6a4d685197191427c93b67b9a96d80da682
Signed-off-by: Ling Wang <ling.wang@silabs.com>
Reviewed-on: https://git.eclipse.org/r/15214
Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com>
IP-Clean: Marc Khouzam <marc.khouzam@ericsson.com>
Tested-by: Marc Khouzam <marc.khouzam@ericsson.com>
This is an initial solution which is made up of 2 parts
1.) Changed the lower-level renderer to filter based on memory block as well as debug target.
2.) Changed the parent render to become a listener for model changed events which are translated
in to direct calls to the renderer to update the displayed values.
This is an initial solution which is made up of 2 parts
1.) Changed the lower-level renderer to filter based on memory block as well as debug target.
2.) Changed the parent render to become a listener for model changed events which it translated in
to the older debug events the lower-level renderer is expecting.
Pawel has suggested a more compact implementation which I will persue. But for now this is at least
a current fix.
Improves the scroll bar position when moving within the data pane.
Supplied by Andre St. LAurent ( Wind Rive Systems Inc. )
Randy Rohrbach
781-364-2226
