| Summary: | Code analysis problems trigger a confirmation dialog when launching a program | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Sergey Prigogin <eclipse.sprigogin> |
| Component: | cdt-codan | Assignee: | Project Inbox <cdt-core-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | Elena Laskavaia <elaskavaia.cdt> |
| Severity: | normal | ||
| Priority: | P3 | CC: | cdtdoug |
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Sergey Prigogin
If it is a problem marker of type error that will trigger the dialog. You can change them to be a Warning instead in preferences, but they won't be red. Are they false positives? (In reply to comment #1) > If it is a problem marker of type error that will trigger the dialog. > You can change them to be a Warning instead in preferences, > but they won't be red. Are they false positives? My code base utilizes a lot of generated include files. When these include files are out of date, it causes name resolution problems. Unfortunately, these name resolution problems often persist even after the include files are updated due to the scenario described in bug 319328. If problems with includes are fixed you can "Select All" markers in Problems view and delete them as workaround. Nothing I can do here unfortunately. If codan markers defined as Error this is platform behavior. I will try to implement solution for bug 319328. |