Clean up cases when Qt installs aren't registered for a given
config. Fix bug on first scanner info request in build config.
Clean up the Qt Run launch delegate in extension.
Also added a method to GDBLaunch to allow subclasses to override
what the default gdb path is.
Change-Id: Icf158633e1c1327cc87ce59c1605bb26258f8708
- Extend OSView to provide a structured selection of
IResourcesInformation
- Add Connect process handler in view toolbar.
- Add Connect process handler in selection pop-up menu
Change-Id: I9e2ca4bafc72d035f78cbbe87ee6ff0f56f6ae22
Signed-off-by: Teodor Madan <teodor.madan@nxp.com>
We reuse GDBLaunch but need to override some settings that are
normally in the launch configuration. These things are calculated
at launch time.
Note there is also an added dependency to the launch bar core
to make GDBLaunch a targeted launch so we can set the target properly.
At some point we'll move this launch target stuff lower down, maybe
to the debug platform.
Change-Id: Ibbf6b794a9ecf25b79d46093cc624ea69dc04641
GdbLaunchDelegate.newServiceFactory(String) has been deprecated for 4
years and has now been removed. It has been replaced with
GdbLaunchDelegate.newServiceFactory(ILaunchConfiguration, String)
Change-Id: Ida8e164da48fcd9d26baf1c77efef7b207ef7565
The methods
MIDataListRegisterValues.MIDataListRegisterValues(IMIExecutionDMContext,
int) and
MIDataListRegisterValues.MIDataListRegisterValues(IMIExecutionDMContext,
int, int[]) have been deprecated for over two years and have been
removed. Callers should instead the methods of the same name but
passing in an IFrameDMContext instead of an IMIExecutionDMContext.
Following that change, the methods
CommandFactory.MIDataListRegisterValues(IMIExecutionDMContext, int) and
CommandFactory.MIDataListRegisterValues(IMIExecutionDMContext, int,
int[]) have also been removed, and their corresponding methods using
IFrameDMContext should be used instead.
Change-Id: Ifa518b9a113dadb9d3dc44d803d8c3819afe810c
The method
GDBRunControl_7_0_NS.eventDispatched(ITraceRecordSelectedChangedDMEvent)
was removed;
GDBRunControl_7_2_NS.eventDispatched(ITraceRecordSelectedChangedDMEvent)
should be used instead.
Change-Id: Ic30186e29b4601f1054a5988a6330ec095079253
The following macos packages were removed:
org.eclipse.cdt.dsf.gdb.service.macos,
org.eclipse.cdt.dsf.mi.service.command.commands.macos,
org.eclipse.cdt.dsf.mi.service.command.output.macos
org.eclipse.cdt.debug.gdbjtag.core.dsf.gdb.service.macos
The following classes, contained in the above packages are now removed:
MacOSCommandFactory.java
MacOSGDBProcesses.java
MacOSGDBRunControl.java
MacOSGdbDebugServicesFactory.java
MacOSMIEnvironmentCD.java
MacOSMIVarUpdate.java
MacOSMIVarUpdateInfo.java
MacOSGdbJtagDebugServicesFactory.java
The constant LaunchUtils.MACOS_GDB_MARKER was removed.
Change-Id: Iea54886a02015dd0b11678a0cd5d911bed129485
Due to improvements in target platform in 12843ef it is now possible to
use mockito instead of easymock. This commit does that switch.
Note because of Bug 334540 we need to explicitly require the org.hamcrest
bundle so that it resolves. From the bug, Matthias Sohn says in Comment 1:
"I would just use Require-Bundle to get around this."
Change-Id: Ib49a767c826aa04f4daf1de0bf1b25a4f8ae07ba
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
Includes:
- CSourceLookupParticipant only did one useful thing (For DSF). When the
object being looked up is a String, as is the case when disassembly
view/editor is doing a lookup, the CSourceLookupParticipant would be the
one to do the resolution. Updated
DsfSourceLookupParticipant.getSourceName to be able to handle a String
- Changed super of DsfSourceLookupParticipant to
AbstractSourceLookupParticipant, saves duplicate code, and adds comment
about what is different about findSourceElements
- a previously missing test for an unusual case (no containers)
- Some of these methods that are only part of CDI have been
marked as such for eventual removal in Bug 484900
Change-Id: I9954b4469e9db9cb46eb117f3beba9e01634689b
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
Add some more tests for source path mappings to ensure that the upcoming
change of using gdb's set substitute-path does not regress any issues.
Change-Id: I9067c8859293c3332439679cb1f663e36a4cc34e
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
A new command, ShowVersionHandler, has been added to the plug-in to
demonstrate all the pieces that need to be put in place to connect
a command to a DSF session.
Change-Id: Iefde0ba144c12ce2e580da7717b390258c0d3675
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
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>
