diff --git a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_jumperror.htm b/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_jumperror.htm index 3bf77fa8d8a..437c4e7348e 100644 --- a/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_jumperror.htm +++ b/doc/org.eclipse.cdt.doc.user/tasks/cdt_t_jumperror.htm @@ -15,34 +15,42 @@
The CDT will parse the output from the make and compiler/linker. If the CDT can -determine the location of an error, it is added to the Console view.
- -To jump to the source of an error:
+determine an error or a warning, the line is highlighted in the Console view and added +to the Problems view as a Problem Marker adorned with +errorTo jump to the source of an error do one of the following:
In the Console view, double-click the Error iconor
- the Warning icon
.
The file opens in the C/C++ editor and the cursor moves to the line with the error.
-In the Console view, double-click the highlighted line.
In the Problems view, double-click the row of the specific error in the table.
If in the Problems view the error is identified as External Location in Location column, + use mouse right-click on it, then click on Open external location item in the context menu.
If CDT can determine file and error line and the file exists - the file opens in the C/C++ editor and the cursor moves to the line with the error.
To jump to errors sequentially:
-
-
-Defining Project Build settings
-Filtering the Problems view
+
Tracking down compilation errors
+