In addition to showing the parameter list (with the current parameter
bolded), the hint now shows the function's name, return type, and
whether or not it is virtual.
Change-Id: I24be893ee8968fca8d9893230266ec98e2b9ae5a
Commit 6fc6c3c671 mistakenly removed the
two strings that were being used for the Run launch delegate. We
haven't noticed because we only have one Run launch delegate and
therefore its name does not end up being shown in most cases.
However, by going to Preferences->Run/Debug->Perspectives and then
expanding the C/C++ Application launch configuration type, the Run
delegate is shown with a missing string.
Change-Id: I2435097b0a13efd21ef3da01e2d4969d231a6f97
This commit removes explicit source features and has tycho create them
automatically, along with all other source features that were not
previously defined. The logic to auto-generate is in the root pom.xml
For all pre-existing source feature, the name presented to the user has
been changed to use the default name used by Tycho, which is "Developer
Resources". This will provide a more standard user-experience with
respect to other source features built by Tycho.
Existing SDK features are kept for backwards compatibility.
All the names of the auto-generated source features that replace an
existing source feature have stayed the same except for the
'testsrunner' feature; for that one name change, a p2.inf file is added
to allow upgrading from the old named feature to the new named feature.
Change-Id: Ie632e798c93898fd828f88df4983fc43e2749d22
With GDB 7.12, it is possible to receive queries on the dedicated MI
channel. This channel is not accessible or shown to the user so if we
don't answer, GDB will wait forever.
This patch blindly answers 'y' to any query on the MI channel unless it
has already been answered automatically (which happens when we don't use
the full console).
Change-Id: I0e208fc3495ce6ba57b3e477661f47e50680fd88
Proposals where the extension is not a known C/C++ header file extension
are ranked below proposals where the extension is one.
Proposals where the extension is a known C/C++ *source* file extension,
and proposals where the filename begins with a '.', are still not considered.
Change-Id: I80784f8f15a01b05977a288affbe3958f1400bdf
The value returned by IBreakpointAction#getTypeName() must match the
value provided in the plugin.xml file for that same action. The two
names are compared in ActionDialog.createDialogArea() to know if the
proper action has been found. This is a fragile technique, that should
eventually be improved. For now, we just fix the current problem.
Change-Id: I70fd8b90fc680d3a5d55a95bdd5193d382b6c6f2
This apply to the Floating Point and Traditional Renderings,
When calling these preferences from the drop down inside the memory
view, the associated preferences dialog comes up with the left side
empty, this left side shall reflect the preference page three path.
The call to the preference dialog has been replaced to use
PreferenceUtil.createPreferenceDialogOn which takes care of this.
Change-Id: I89d6b1289a7eac5ffcca54a1ca6d8b3c3ed831df
Cleaned up some error messages. Especially when a system has no
serial ports. Also added a delay when ports are closed since some
serial port drivers (FDTI in particular) take a bit longer to
properly close. Especially important in pause situations where we
want to use the serial port for some other purpose right away.
Change-Id: Ifc9b7171682962e0aed8e9ed9ebf5472fc9e8206
(cherry picked from commit db3d5974e6)
The set was moved to EvalUtil.getVariableValue() in bug 508254, but this
left some paths unprotected. This restores the set to
CPPVariable.getInitialValue() (while keeping the EvalUtil one too).
Change-Id: I4a579720f4bc23d41e50c484649a73c29698373d
This commit also enables a richer set of enablement checks when
contributing ConsolePageParticipants to the Debugger Console view.
Change-Id: I34aa010fd9cfa91f24781e2bef5ba41b9525eab0
This patch officially limits the ConsolePageParticipant to handling
consoles from the platform's console view, and not any consoles from the
new Debugger Console view. The code currently behaves like this, but
this patch cleans it up and no longer even checks for GDB consoles.
The ConsolePageParticipant used to provide two things for the GDB
console, when it was part of the platform's Console view:
1- it would select the GDB console when the GDB process was selected
2- it would provide a 'save' button for the GDB console
For #1, when the GDB process is selected in the debug view, this patch
selects the same inferior console as when the launch is selected which
is the last inferior console. As for the synchronization of the Debugger
Console views, it is already handled by each console itself.
For #2 the save button must be handled differently based on the
different type of debugger console (basic vs full). This should be done
in another commit. Besides, the code, before this patch, was not adding
the save button to the debugger consoles since those consoles are not an
instanceof org.eclipse.debug.ui.console.IConsole as first checked in
ConsolePagePartipant#isConsoleGdbCli()
Change-Id: I0813ad2261633ce8630ab5842f06a047868856e8
To perform actions on the GdbFullCliConsole, it is important to provide
access to the terminal widget. This patch adds the new method
GdbFullCliConsolePage#getTerminalViewControl() to give access to the
ITerminalViewControl.
Also, to be consistent with the platform's ConsoleView, this patch also
adds the same groups in the toolbar. Namely
IConsoleConstants.LAUNCH_GROUP and IConsoleConstants.OUTPUT_GROUP.
Extenders can use these groups to add their buttons to the Debugger
Console view.
Change-Id: I217ce54ada63796de776c6b4cb6b925c3feb7eea
This commit borrows code from ConsoleView and ConsoleManager to allow
adding page participants to GdbFullCliConsole.
Change-Id: I4b99600bc4fba3bfecb9a4822f94e2be7d3aa601
Signed-off-by: Stephen Flynn <stephen.flynn@dell.com>
freezes
Optimized IndexFileSet.containsDeclaration method for performance and to
reduce its memory footprint.
Change-Id: I0e867b96c6d6ab102561bc999127980d1be26a7b
The Properties dialog displayed for a Dynamic printf breakpoint
display a "printf (" field, however the end parenthesis is not added
and not expected as part of the parameter list as the ending parenthesis
is added internally.
If the user adds it to complete the opening parenthesis the printf does
not work.
This update adds a validation to this field so if the user adds a final
parenthesis, the dialog will display an error message and the OK button
will be disabled.
Change-Id: Ib25c5a11176c6f92c7367246483be0f703e145bd
Adding a GDBJtagDSFFinalLaunchSequence_7_12 class to be used when
interfacing with GDB 7.12 or higher.
A new step is added to the sequence in order to enable async mode,
which will allow us to use the new GDBFullCLIConsole
Change-Id: I08c382550c6dd8a8567a66169495a9e490c35397
For example, opening the CMake property page, there was a missing
message for the cmake-ui button.
Change-Id: I126fe1cb6e290edc289a2dade44500dd35ed1207
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
