Bugzilla – Full Text Bug Listing
| Summary: | [Build selected File] Compiler Errors are not shown in Problems View | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Harald <Harald.Kaestel-Baumgartner> | ||||||
| Component: | cdt-build-managed | Assignee: | Andrew Gvozdev <angvoz.dev> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Andrew Gvozdev <angvoz.dev> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | cdtdoug, mnazario, yevshif | ||||||
| Version: | 7.0 | ||||||||
| Target Milestone: | 7.0.2 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Could you make a patch in eclipse via project context menu->Team->Create Patch and submit as an attachment? Created attachment 181070 [details]
Screenshot of change shown in compare editor
(In reply to comment #1) > Could you make a patch in eclipse via project context menu->Team->Create Patch > and submit as an attachment? Unfortunatly not. No CVS -> No patch ;) CVS is not working, but that's another story. I usually import the sources directly from the installed plugin. I checked your fix and it works. I need an attachment from you for bureaucratic purpose, so the fact of your contribution is recorded in IP log properly. Any attachment will do, the one from comment 2 is just fine. Committed on HEAD (8.0) and 7.0.2 stream. Thanks for the fix! Created attachment 181102 [details]
The contribution
As requested. Once again.
*** Bug 343186 has been marked as a duplicate of this bug. *** |
Build Identifier: 6.0.0.201004122116 I've seen, that following call in the blue print is wrong (I think): int status = stepBuilder.build( consoleOutStream, epmOutputStream, new SubProgressMonitor( monitor, 1, subProgressMonitor.PREPEND_MAIN_LABEL_TO_SUBTASK)); epmOutputStream is the stream of the ErrorParserManager an consoleOutStream the stream of the console. With our toolchain we've the problem, that for the compile errors no problem markers are generated, when the command "Build selected File(s)" is executed. I think they are not on the err stream and thus are not scanned by the ErrorParserManager. I've patched in my CDT the call to int status = stepBuilder.build( epmOutputStream, epmOutputStream, new SubProgressMonitor(monitor, 1, SubProgressMonitor.PREPEND_MAIN_LABEL_TO_SUBTASK)); and the problem markers are generated. Reproducible: Always Steps to Reproduce: MBS with internal builder 1. Select a c file with errors 2. Run command "Build selected File(s)" 3. Now Problem marker is generated