diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_create_make_target.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_create_make_target.htm index 8b1445bb94e..641cc21b74b 100644 --- a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_create_make_target.htm +++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_create_make_target.htm @@ -11,20 +11,45 @@
You can define build settings when you create a Make Target.
+Use the Create a Make Target dialog box to define build settings when creating a Make Target.
Option | +Description | +
---|---|
Target Name | +Name of the Make Target. | +
Make Target | +The reference to the make section in your makefile. | +
Use default | +Select this checkbox to use the default make command. Clear the check box to specify a new make command. | +
Build command | +If you clear the Use default checkbox type a new make command in this field. | +
Stop on first build error | +Stops the build when an error occurs. | +
Run all project builders | +Runs additional project builders such as discovery. | +
@@ -36,7 +61,7 @@
Defining Project Build settings
Debug Breadcrumb is a compact presentation of the currently active debug context and its parents.
+Use the Debug Breadcrumb layout to show a compact presentation of the currently active debug context and its parents.
To enable the Debug Breadcrumb, change the Debug View layout to Breadcrumb (Select Layout->Breadcrumb in the Debug View menu). Alternatively, resize the Debug View such that the height of the view is small enough to fit only one line of text. This will cause the view to change over to the Breadcrumb layout automatically.
-The Debug Breadcrumb allows to invoke actions on any element shown in the breadcrumb. Actions can be invoked through the context menu or through key bindings. To select an element in the breadcrumb click on it or activate the Debug view and use the left and right arrow keys. +
To show the Debug Breadcrumb layout, in the Debug view toolbar select View Menu > Layout > Breadcrumb. Alternatively, resize the Debug view such that the height of the view is small enough to fit only one line of text. This causes the view to change over to the Breadcrumb layout automatically.
+The Debug Breadcrumb allows you to invoke actions on any element shown in the breadcrumb. Actions can be invoked through the context menu or through key bindings. To select an element in the breadcrumb click on it or activate the Debug view and use the left and right arrow keys.
You can also change the active debug context using the breadcrumb. Click on one of the arrows or any element top open a drop-down window. The drop-down shows all the siblings of the element for which the drop-down was opened. Click on an element to make it the new active debug context. To open the drop-down with the keyboard, select and element and press the down key.
diff --git a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dsfgdb.htm b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dsfgdb.htm
index ab44169345f..34cf61cc82b 100644
--- a/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dsfgdb.htm
+++ b/doc/org.eclipse.cdt.doc.user/reference/cdt_u_dsfgdb.htm
@@ -6,30 +6,45 @@
This preferences page lets you control how the CDT debugger behaves when debugging with GDB, +
Use the GDB preferences panel to control how the CDT debugger behaves when debugging with GDB, specifically when using a GDB (DSF) launcher. The page is accessible at: Window > Preferences > C/C++ > Debug > GDB.
+Option | +Description | +
---|---|
Enable GDB traces | +When checked, the debug session will produce an additional console which will contain all the gdb/mi activity. Basically, this details the
interaction between the CDT debugger and GDB. This information is often critical when the debugger is not behaving as you expect. Turn this on and submit
- the console output when submitting a bugzilla report against the CDT debugger.
-
- - ![]() |
+
Terminate GDB when last process exits | +When checked, the CDT debugger will terminate the GDB host process's after all the target processes it is debugging have terminated. Otherwise it will leave it running. | +
Use enhanced debug hover | +When checked, hovering over an expression in the editor during a debug session will bring up an enhanced expression evaluation control. Otherwise, a more basic control is used. This, of course, assumes that you have the debugger's hovering capability turned on in C/C++ > Editor > Hovers. If not, this checkbox has no effect. + ![]() |
+