I got some user feedback about some terminology they didn't quite
understand and this patch tries to address the issues by:
- Simplifying the name of the reverse debugging options.
- Simplifying the preference page.
The patch aslo removes un-used strings in plugin.properties.
Change-Id: I1e4487eeda23f81d391ef11ddbe7dd6feba401ec
The patch implements the event handler which
queries the trace method and triggers the necessary
update in the command handler.
Change-Id: I9c1827deb56dce099b7f455e942d1b6735a80643
Signed-off-by: raddepal <ravitheja.addepally@intel.com>
Signed-off-by: ravitheja.addepally <ravitheja.addepally@intel.com>
- Extend query for already connected process to all sessions for local
session types
Change-Id: I36591ff96d28977b4670700a2a2eb92c34945c7a
Signed-off-by: Teodor Madan <teodor.madan@nxp.com>
This is a follow-up to the work done to show errors when attaching to
processes. We were also not showing errors when trying to start a new
process using the "Debug new executable..." context menu option of the
debug view.
Change-Id: I9f68410b6d41a28df6f76f63b091a049a38b14e9
This patch adds the "Switch Off Tracing" option to
the select reverse debugging method pull down menu.
Change-Id: Ib184c1f4c1d1db781bea4468bc8c939bd27db27d
Signed-off-by: raddepal <ravitheja.addepally@intel.com>
There was a race condition between commandTimedOutDuringSession
finishing and the next test starting that checked for unterminated
launches (in BaseTestCase removeTeminatedLaunchesBeforeTest).
While commandTimedOutDuringSession did wait for the shutdown to be
received (ICommandControlShutdownDMEvent), that can happen a few ms
before the launch is fully terminated (fLaunch.isTerminated() == true)
Change-Id: Ib4e6655938f6b0e3ab3ce89fd06528f1b72ee04d
Signed-off-by: Jonah Graham <jonah@kichwacoders.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
Every time we report a problem in a declaration/expression that occupies more
than one line, the codan marks the entire line as a problem - including
everything before the node. This patch solves this inconvenient behavior.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=486610 for a complete
explanation.
Change-Id: I742cbaac8a1392676695d574355597b0cfc87385
Signed-off-by: Alisson Linhares de Carvalho <arescarv@gmail.com>
