236053 – ErrorParser console output is handled inconsistent

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

Bug 236053 - ErrorParser console output is handled inconsistent

Summary: ErrorParser console output is handled inconsistent

Status:	RESOLVED DUPLICATE of bug 71511

Alias:	None

Product:	CDT
Classification:	Tools
Component:	cdt-build (show other bugs)
Version:	5.0
Hardware:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	cdt-build-inbox@eclipse.org
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2008-06-06 10:29 EDT by Enrico Ehrich
Modified:	2012-03-22 00:31 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Enrico Ehrich

2008-06-06 10:29:46 EDT

Build ID: I20080530-1730

Steps To Reproduce:
I implemented a simple ManagedMake ToolChain + ErrorParser for a Static Analyse Tool (QA-C) and it worked fine when I "compile" the whole project.
But when I try to compile single c-files (Build selected file(s)) the error parser does not give any output.

After some debugging I found that for building a single c-file only "StdErr" is analysed line by line (IErrorParser.processLine() is called) and when I build the whole project all output StdOut + StdErr .. is analyes line by line.

So why is this behavior different for whole project and single file? My workaround now is to redirect all the QA-C output to StdErr.

IMAO best is to change the ErrorParserManager(?) to analyse the whole console output also for single c-files, to have a chance to catch the compiler warnings.

More information:
CDT 5.0.0 RC3

Comment 1 ZhangYi

2008-08-12 23:55:34 EDT

(In reply to comment #0)
> Build ID: I20080530-1730
> 
> Steps To Reproduce:
> I implemented a simple ManagedMake ToolChain + ErrorParser for a Static Analyse
> Tool (QA-C) and it worked fine when I "compile" the whole project.
> But when I try to compile single c-files (Build selected file(s)) the error
> parser does not give any output.
> 
> After some debugging I found that for building a single c-file only "StdErr" is
> analysed line by line (IErrorParser.processLine() is called) and when I build
> the whole project all output StdOut + StdErr .. is analyes line by line.
> 
> So why is this behavior different for whole project and single file? My
> workaround now is to redirect all the QA-C output to StdErr.
> 
> IMAO best is to change the ErrorParserManager(?) to analyse the whole console
> output also for single c-files, to have a chance to catch the compiler
> warnings.
> 
> More information:
> CDT 5.0.0 RC3
> 
Hi, 

  Could you attach your ToolChain and ErrorParser to Bugzilla? And you'd better give a concrete example step by step. That would be very helpful for me to reproduce it. 

Thank you!

Yi

Comment 2 Andrew Gvozdev

2012-03-22 00:31:48 EDT

This should get solved with bug 71511.

*** This bug has been marked as a duplicate of bug 71511 ***