The constructor MIThreadGroupExitedEvent(IProcessDMContext, int, String)
has been removed. MIThreadGroupExitedEvent(IProcessDMContext ctx, int,
MIResult[]) instead.
Change-Id: I1314f63e98b654daab81e30602c14b3e44c7a128
The constructor MITargetAttach(ICommandControlDMContext, String) has be
removed. MITargetAttach(IMIContainerDMContext, String) or
MITargetAttach(IMIContainerDMContext, String, boolean) should be used
instead.
Correspondingly, the method
CommandFactory.createMITargetAttach(ICommandControlDMContext, String)
was removed. CommandFactory.createMITargetAttach(IMIContainerDMContext,
String) or CommandFactory.createMITargetAttach(IMIContainerDMContext,
String, boolean) should be used instead.
Change-Id: I2c35f0a7817d135511a851c400d3ad71781afd0c
The constructors MIFileExecAndSymbols(ICommandControlDMContext) and
MIFileExecAndSymbols(ICommandControlDMContext, String) where removed.
MIFileExecAndSymbols(IMIContainerDMContext) and
MIFileExecAndSymbols(IMIContainerDMContext, String) should be used
instead.
Change-Id: I1c54599f930430c9640833420256691d01184e76
In GDBControl_7_0, the classes InitializationShutdownStep,
CommandMonitoringStep, CommandProcessorsStep, RegisterStep have been
removed; their counterparts, defined in GDBControl, should be used
instead.
Also, the class GDBControl_7_0.ListFeaturesStep now extends
GDBControl.InitializationShutdownStep instead of the removed
GDBControl_7_0.InitializationShutdownStep.
Change-Id: I9365e746ac3cee67abcdc9507dd15e45337a1396
MIVariableManager.MIVariableObject.setExpressionData(String,String,int)
which has been deprecated for over 4 years has been removed. The method
MIVariableManager.MIVariableObject.setExpressionData(ExpressionInfo,String,int,boolean)
should be used instead.
Change-Id: I3ac346eddd8dc119e725d475481836aa5fbd7d79
The method AbstractMIControl.getControlDMContext() has been deprecated.
I has been replaced by ICommandControlService.getContext(). It should
have been deprecated at the same time as when
GDBControl.getControlDMContext() was deprecated, but was forgotten.
Change-Id: Ib568fce51b29455281a3d26b5ace914b9f4dece8
This allows specifying the multiplier on the command line and pass
it along to the tests.
Change-Id: I35cb764a6494a0eb98e5e2205a47522935c2b206
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
We can obtain the full path of the executable using
File#getAbsolutePath(). This is much better than the hack that was
actually doing a launch to ask GDB where the binary was.
I cannot explain why I didn't use this in the original implementation.
Change-Id: Ifa0d538919cd0c231547f1f3e9c4b72837df4257
Commit 84a53f8d80 broke this test for an
architecture with fWordSize == 2. The buffer for writing a word went from
length fWordSize to 1, and the expected buffer size of a read as well.
This commit fixes it.
Change-Id: Ie50766031fc7dd8d480f126abc48a6dfd487b9e5
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
- Fix getModelDataForRegisterDataValueInDifferentNumberFormats failure
Nothing seems to set the register we use to do the test to a particular
value. The value happened to be 0. This broke the octal test, because
it assumes that the result starts with a 0, but has characters after
that 0. This is not true when the result is 0. The fix is to set the
register to a know value beforehand (0x1234).
- Fix compareRegisterForMultipleExecutionContexts for slow targets by
adding missing massageTimeout.
Change-Id: I681acdeb08f8e3c2fdaf8dc9cf60801584da4423
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
The action changes were not immediately shown when changes were done
from the while-stepping action dialog
Change-Id: I36c4b366f0fd97d0a5c939b17eda5e6cd696d89d
Tracepoint action changes were not immediately reflected in
the list of attached actions.
Change-Id: I6d0ad788d40c69febf2df5226252a7eeabde39b4
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
With gdbserver 7.5, detaching from a process leaves gdbserver hanging
which prevents the next testcase from running.
We therefore disable the two detach testcases for version 7.5 only.
Note that we cannot simply @ignore the testcases since we want to run
them for the local case, even for version 7.5.
Change-Id: Id4b69420abd1218be5eaf2c54a9f44349283edc2
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Instead of modifying the source files of the documentation, it's cleaner
to replace the invocation to makeinfo to invoke "true". This will skip
building of all the docs.
Change-Id: I33a8ba7e1932433de48ab98d6cda3fda0bb09143
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
As a safety net, fail if a line tag is defined more than once.
Also, allow calling resolveLineTagLocations more than once for a single
test.
Change-Id: I0832d3d28c4d688c38fd33dfc668b0ec6b8c4ffa
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
- Have CBreakpointPropertyPage check if any CBreakpoint already exists
at the specified location
- Have GDBDynamicPrintfPropertyPage check if any CBreakpoint already
exists at the specified location
- Have GDBTracepointPropertyPage check if any CBreakpoint already exists
at the specified location
Change-Id: I67096343a7173a98a144e3577a6b8a05377759e3
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
- Add generics for ServiceRegistration and ServiceReference
(added <?>), See Bug 322007 which added generics to OSGI
- Add generics for getAdapter, See Bug Bug 442021
- Fix calls to MessageFormat.format()
- Cross reference some unused/commented out code for dprintf with
associated @SuppressWarnings("unused")
Change-Id: I4bacb3b37b69c97ab35615413f0f1f3e71aa2092
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
- use the new docker tooling plug-ins to launch and debug
CDT C/C++ applications in docker containers
Change-Id: I30689255a3443ce6d49f937f5e2506d86452915b
Currently, CDT does not ask GDB for the value of the variables it
believes to be of complex types, such as structures. However, as
described in the bug, it assumes that a typedefed pointer is a complex
structure. Because of that, it displays a value of "{...}" for it
instead of the pointer value.
By asking GDB for the value of the variable even if it's of a complex
type, CDT will always display the right thing for the value. This will
cause a few more -var-evaluate-expression calls, but their number is
still limited to what is visible in the variables view. So the impact
should be negligible.
Screenshot of before/after:
http://i.imgur.com/Sx5ZPfO.png
It is still impossible to edit the value, but this would be addressed in
another patch.
Change-Id: I92e6ead6351677e098a56d4af5bdb85fc61df080
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
The try/catch doesn't add anything. If getStackTrace throws, the test
will fail and will show the useful stack trace.
Change-Id: Icf453ff2ca6c10a32f264fece0f0db9af8049612
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
