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>
The protected method GdbLaunchDelegate.cleanupLaunch() has been removed.
It has been replaced with GdbLaunchDelegate.cleanupLaunch(ILaunch).
The complexity about not using a class field in GdbLaunchDelegate is that
throughout the process of launching a session, we must be ready to cleanup
the GdbLaunch object. The problem is that the platform does not provide
that launch object in the methods preLaunchCheck() and finalLaunchCheck(),
so we needed to store the launch object in a field.
This patch delays the call to GdbLaunch.initialize() so that we don't need
to cleanup the launch object if preLaunchCheck() and finalLaunchCheck()
abort the launch. One hurdle was that we still needed to create the DsfSession
when constructing GdbLaunch, so still needed to clean it up. This patch adds
a check in GdbLaunch itself, when the launch is removed, to cleanup any
lingering DsfSession automatically.
I've tested every path that aborts the launch in GdbLaunchDelegate and
confirmed that things are properly disposed of in every case.
Change-Id: Ie2981a843917b464f1785a477871073227e027c3
This patch cleans up the debugger tab and puts the new ReverseMode
dropdown box on the same line as the reverse checkbox.
The patch also decouples the gdb and gdbinit boxes (which require three
columns) from the other options (which require one or two columns). This
will make modifying options simpler and more versatile.
Change-Id: I11909ed72237128f354dbf05ab3ba1de062aad2f
This adds support for the more general case, where the expansion pattern
is not just a template parameter pack itself.
Change-Id: Ia6e4626d184d17fee57f1986cf92056ab38b8f17
The original toggle button for reverse debugging
has been modified to a pulldown menu for selecting
between hardware and software methods along with all necessary support.
Change-Id: I2e4d97c46950253986d427cb87cda66b820744c9
Signed-off-by: raddepal <ravitheja.addepally@intel.com>
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Before calling setEnabled on the ToolItem check if it is disposed. If
thats the case, do nothing, else enable the ToolItem.
Bug: 487920
Change-Id: I1f7b9e0da7f07b2b49e3176e162b9ffb7968439b
Signed-off-by: Martin Schreiber <m.schreiber@bachmann.info>
GDBBackend.getGDBCommandLine() and GDBBackend.launchGDBProcess(String)
have been removed.
GDBBackend.getGDBCommandLineArray() and
GDBBackend.launchGDBProcess(String[]) should be used instead.
Change-Id: I50b118a0dfeef5c427c61ba5a9b38662cbe9748f
pack
This change solves the example in the bug but I'm not sure if it works
properly in other similar cases.
Change-Id: I6fb6b0c2501ef1fcd25bb31fae019ec5ec0379f9
