Not sure why this stuff was on master anyway. It was supposed to be
on the oeremote branch. At any rate, I've started to contribute the
new API to o.e.remote properly so this is no longer needed.
Change-Id: I83409423ee5d5ad1295efadabb9d686b4d0fce4f
- one case where debugger fails to return stack depth, but returns
correct stack frames
- second case where debugger fails to return stack frames when asked
without limit, but can return a specific frame
Both of these are workaround for GDB bugs where it fails to return data
consistently
Change-Id: I4fb0d4e850fbce6adc655849ec3f73c85adb1bdc
Signed-off-by: Alena Laskavaia <elaskavaia.cdt@gmail.com>
java.lang.NullPointerException
at
org.eclipse.cdt.internal.ui.workingsets.IWorkingSetProjectConfigurationFactory$Registry$1.compare(IWorkingSetProjectConfigurationFactory.java:180)
at
org.eclipse.cdt.internal.ui.workingsets.IWorkingSetProjectConfigurationFactory$Registry$1.compare(IWorkingSetProjectConfigurationFactory.java:1)
at java.util.TimSort.countRunAndMakeAscending(TimSort.java:352)
at java.util.TimSort.sort(TimSort.java:216)
at java.util.Arrays.sort(Arrays.java:1438)
Change-Id: Ibe91a679c876ed5f70f4f787188e13e52203466c
Signed-off-by: Alena Laskavaia <elaskavaia.cdt@gmail.com>
Factor out the code for testSettingVariableWithSet and
testSettingVariableWithPrint.
testSettingVariableWithSetWithMemory is not exactly the same, so I
didn't factor it out.
Change-Id: Ib4e79eda4851ec2291fcf32054694b76e40c65ca
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Added a popup menu in expressions menu to add locals group
and registers group - for discoverability of this feature.
The menus are added to generic dsf but the command handlers
added to the gdb plugin, just in case somebody wants to implement
this for another dsf based debugger
Change-Id: Iab64e2a9f3a0c81f8bac939a2a5e94c67ef1daba
This patch adds a setup file for Oomph. To test it:
1. Start the Oomph installer (https://wiki.eclipse.org/Eclipse_Oomph_Installer)
2. At the package selection, click the Advanced Mode button in the top-right
corner
3. Select Eclipse IDE for Eclipse Committers. Click next.
4. Select Eclipse.org
5. Click on the '+' button in the top-right corner, browse file system for
CDT.setup.
6. Double-click on CDT in the tree. Click next.
7. Enter installation folder name, workspace name. Click Next, Finish.
This should install and start a new Eclipse installation with the CDT code
ready to be worked on. Once this patch is merged, the setup will be added to
Eclipse catalog so that the user doesn't have to browse for the file.
Change-Id: Ia84383e9cc64fd3eec0e738e5266dcd8ba6dad0a
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
updateBuildConfigCombo originally accepted null as arument, restored
this behavior (it is not called with null from cdt code, but may be
called from overriding classes)
Change-Id: I7d0f271b2bd414d380a1804b838ce38fbdc7c0af
Signed-off-by: Alena Laskavaia <elaskavaia.cdt@gmail.com>
With this change the build will now contain the
packed jars for each plugin. They can be seen under
releng/org.eclipse.cdt.repo/target/repository/plugins/*pack.gz.
Those packed jars are removed from the zip file as they just duplicate
the existing jars.
Change-Id: Ida5804e6939f1dd99a5cc169518738bb394198a6
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
- fixed issues when list is not drawn properly
- fixed that Esc does not work to close pop up sometimes
- fixed filtering for list with edit button
- fixed layout issues when only one item in the list and filter becomes
visible (filter is disabled in this case)
Change-Id: I562f12df8326b4efecf75150b57b699c53d398da
- switched default ui from actions to commands
- for DSF implemented this in DSF GDB
- for CDI implemented command wrappers
- created new API to support loading symbols in IModules service
(IModules2)
Change-Id: Id44f42fa9f0f3d7f22ff7dda07c0830262667d9c
Catching the exception and asserting false just hides the real reason,
making failures harder to debug.
Change-Id: I1a73fb5893da2762d0b9a9a496749643471f75b4
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Reviewed-on: https://git.eclipse.org/r/39787
Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com>
Tested-by: Marc Khouzam <marc.khouzam@ericsson.com>
runToLine uses gdb's -exec-until, which has a very strange and
unpredictable behaviour. It is safer to use runToLocation, which uses a
temporary breakpoint + continue.
Change-Id: If7bbbdd12570b50f38eb92f1748d10dff96f1f45
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Reviewed-on: https://git.eclipse.org/r/39769
Tested-by: Hudson CI
Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com>
Tested-by: Marc Khouzam <marc.khouzam@ericsson.com>
