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

Bug 341790

Summary: "there are build errors" window might not show, when errors are present
Product: [Tools] CDT Reporter: Tomas Martinec <fyzmat>
Component: cdt-debugAssignee: cdt-debug-inbox <cdt-debug-inbox>
Status: NEW --- QA Contact: Jonah Graham <jonah>
Severity: minor    
Priority: P3 CC: cdtdoug, jamesblackburn+eclipse, pawel.1.piech
Version: 8.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Fix none

Description Tomas Martinec CLA 2011-04-04 10:40:23 EDT 
Build Identifier: I20110127-2034

From reading the code I would guess, that method existsProblems of AbstractCLaunchDelegate2 might not work as expected. Because of it the user would not be warned during launching, that he has some build errors in the project. I did not try to produce that, so I am not absolutely sure about it.

Reproducible: Didn't try
Comment 1 Tomas Martinec CLA 2011-04-04 10:40:48 EDT 
Created attachment 192463 [details]
Fix
Comment 2 James Blackburn CLA 2011-04-04 10:48:08 EDT 
A better fix would be:

   return project.findMaxProblemSeverity(ICModelMarker.C_MODEL_PROBLEM_MARKER, true, IResource.DEPTH_INFINITE) >= IMarker.SEVERITY_ERROR;