Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 359726

Summary: Saving a file after removing lines prevents build console jumping to error lines
Product: [Tools] CDT Reporter: Phil Mason <pmason>
Component: cdt-buildAssignee: cdt-build-inbox <cdt-build-inbox>
Status: NEW --- QA Contact: Jonah Graham <jonah>
Severity: normal    
Priority: P3 CC: cdtdoug, yevshif
Version: 8.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Phil Mason CLA 2011-10-03 11:45:32 EDT 
Build Identifier: I20110613-1736

If a file has more that one error and correcting the first adds (or removes) lines then saving the file stops the double click jumping to error from the build console. 

Note that it does work as the user expected if the file is modified but not saved (it jumps to the line with the error even though it might be a different line number to that shown in the build console).

Reproducible: Always

Steps to Reproduce:
1 - Create code with at least two problems.
2 - Build code
3 - Double click on first warning in build console
4 - Resolve the warning in a way that adds or removes lines of code.
5 - Save the file
6 - Click on the next warning in the list (nothing happens)
Comment 1 Andrew Gvozdev CLA 2011-10-03 12:02:07 EDT 
Removing the line removes the marker from the list (see Problems View) so it is problematic.
But adding lines should not prevent jumping. Note also that all error/warning lines after removed/added line get invalidated.
You can get back the jumping ability though if you restore line numbers matching (i.e. remove added lines).