CCSv5.2.1: Problem view not updated

Hi Christian,

I am looking into this to see if I can reproduce it and will get back to you with feedback asap. 

Best Regards,

Lisa

Hi Christian,

I just tried in a fresh workspace and could not reproduce this.  Could you please send more details?  What steps you take?  Do you see this with all projects and workspaces?  Have you been reusing workspaces?

Best Regards,
Lisa

Hi,

I got the same problem, in my case what I did was:

1 - I uninstalled CCS 5.1 and installed 5.2.1

2 - Imported the CCS projects to the new installation

Then I checked if the projects were OK (I also updated compiler, MCSDK..) in just one of the projects I got this problem.

It happened when I added a .oe66 lib file and got some error messages, when I removed the .oe66 lib I still got the error messages associated with the lib file, so I cleaned the project and rebuilt, this way I didn't get the old error messages.

I got this problem just one time.

Regards

I have also seen this problem under similar circumstances.  I have one workspace with multiple projects imported in it.  I uninstalled CCS 5.1, installed 5.2, and pointed 5.2 to the existing workspace.  If I introduce a syntax error, the error parser picks it up and shows it in the problems window.  I can then take out the syntax error, do a build, and it will build cleanly without clearing the problem window first.  If I do a clean, the problems window is cleared.

I also tried creating a new workspace under 5.2 and importing my existing projects into it, but I got the same results.

Since you can cycle through the errors via the up/down buttons in the console window, my workaround right now is to shrink the problems window so I can't see it (limiting the temptation and frustration) and just use the console window.

Hi all,

Following steps i did so far to get that behaviour:

1. Installed a fresh CCS v5.1, set up a new workspace_5_1 and created multiple new projects.
2. Uninstalled CCS v5.1 and installed CCS v5.2.0, set up a new workspace_5_2 and imported the projects. From what I remember, there was the problem there already. I probably didn't noticed it because I have not worked very long with that version.
3. Uninstalled CCS v5.2.0, installed CCS v5.2.1 and reused workspace_5_2 with the existing projects.

I have narrowed down the problem to changing one thing.  I usually have about 20 include paths defined in a project which are defined under the Include Options.  So I tried creating a new workspace and empty project where the error markers behave just fine.  Then I copy/pasted the line in the project file that specifies the tool includes, so there were a total of 20 of the same line (see the line below).  Then I introduced a syntax error in main.c, compiled, and saw the error marker (in the problem window).  If I removed the syntax error, the error marker persisted.  To get it back to the desired behavior, I deleted the 19 copies of the line from the project file, closed/opened the project, cleaned the build and rebuilt.  Then, introducing the syntax error, building, removing the syntax error and re-building causes the error markers and problem window to behave correctly.

<listOptionValue builtIn="false" value="&quot;${CG_TOOL_ROOT}/include&quot;"/>

I tried a similar thing by duplicating pre-defined symbols....same sort of thing.  Since the error markers are based on the console output, I'm guessing this has something to do with the error parser choking on the long lines generated by having so many includes or pre-defined symbols on the command line.

Good deal.  Thanks for the response, Lisa.

And FYI, another workaround I've found is to change the console verbosity level  (Preferences -> CCS -> Build) to Super Quiet.

Hi Andy,

no problem, thanks for the further information and tip.

All the best with development.

Best Regards,

Lisa

Hi Lisa/Andy,

thank you for all the support and tips regarding this problem. I'll try the workarounds given by Andy as long as these bugs are not closed.

Best regards,

Christian