Also added the command shell console to the cdt 4.5 target so we can
test the Arduino command shell.
Change-Id: I185f9b39d23a6718204112e1fd4388c2458f7e5e
This patch creates a product so that the stand-alone can be downloaded
without
the rest of the C/C++ EPP. It also makes it easier to use because the
user only
has to launch the executable, just like a regular Eclipse instead of
finding
the script.
To try the RCP:
mvn clean package -Pbuild-standalone-debugger-rcp
The result (tar.gz) is available under
debug/org.eclipse.cdt.debug.application.product/target/products
Once extracted, it can be started just like the normal script:
./cdtdebug -e myexecutable
Change-Id: Ifb849af8a8f2ec03abcae57cf43d57cde2333759
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
- use the new docker tooling plug-ins to launch and debug
CDT C/C++ applications in docker containers
Change-Id: I30689255a3443ce6d49f937f5e2506d86452915b
Looks like platform 4.5 now depends on
org.eclipse.e4.core.di.annotations
Change-Id: Ic7ecde8e52c825a563956ffeb1b56407f6d98325
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
- Add a note about turning pre-processor off so edits made as part of
the tutorial are not overwritten
- Add missing ConfinedToDsfExecutor for Exercise 4
- Fix typo
Change-Id: I790fc2e3f640510a665a9a29a04f20502af7c710
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
When creating BP with dialog, make sure it starts out as
not-relocated.
Change-Id: Ia5b703315ce4a6ea55bac584097b255f08b19b17
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
The cause of the different output is a change in o.e.core.resources
where the order of visiting a project has changed to become
alphabetical. See
http://eclip.se/461838
Therefore, our benchmark files must also have the output of
subdirectories in alphabetical order.
Change-Id: I3331649cf516adbe3b453b11f1ed6733a007ce4d
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>
This could happen if a project was selected before creating the launch
and the project was missing a project description. For example, if the
.cproject was missing.
Change-Id: I3ecea6c4ee3cd3939c07ade361b2180fd86e6949
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
