Using -pdv (verbose diagnostic) will reduce problem description to ID

Roger44834 said:

After update to CCS 5.2.1.00018 the descriptions of the errors, warnings and remarks contain only the ID (e.g. "#880-D" ).

If deactivating the verbose diagnostic the description contains the string "#880-D parameter "MyVar" was never referenced".

I'm not sure if I understand correctly. Are you saying that only when you deactivate/remove the --verbose_diagnostics message do you see the full description of the error? If so, that is not the same as what I see with CCS 5.2.1. Could you please attach a screenshot that shows the CCS build console output and Problems view so we can understand it better?

There was one known issue with problems view not clearing automatically when projects are rebuilt via 'Project->Build Automatically'. I believe this was fixed for 5.2.1 though. Could you opening a new clean workspace, import your project into it and see if you still see the behavior with Problems view not getting cleared out?

Thank you for your answer.

This was done with a new workspace in which I imported a existing project.

The console output seems to be ok, the "Problems" window which lists all the erros, warnings and remarks as summery is the one which  is affected.

The output without -pdv (verbose diagnostics is deactivated):

In the console the remark is one line:

All OK.

Now with -pdv

In this case the remarks on the console output take more than one line (this must be the problem for the Problems window):

The additional mentioned 'feature' is:

If a do simply a "Build" (without Clean before), the Problems view is not cleared as it was before 5.2.1. The warnings and remarks of last build are still listed. Here you can see the output of 2 builds (one without -pdv, one with -pdv)

Regards,

Roger

I did update from within CCS.

Thank you for your reply!

AartiG said:

If a do simply a "Build" (without Clean before), the Problems view is not cleared as it was before 5.2.1. The warnings and remarks of last build are still listed.

We have identified one specific cause for this to happen. Please take a look at this related thread: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/203725/724283.aspx#724283

We also suspect there may be other instances where the problems view is not cleared, and if there, we'd like to get those identified and fixed as well. If your case is not related to error parses handling of long lines, could you please attach a simple test project that demonstrates the issue so we can ananlyze if there are other factors contributing to the problems view not getting cleared?

Hello

I changed to code composer 5.4 and the same behaviour occurs. Enabling the verbose mode suppressing the error description.

Greets Reto