Compiler Errors not reset upon successful build?

I've seen the same problem on CCS 5.2. For me, link errors do not get cleared even though I fixed the error and the build succeeded. I have to do clean and rebuild to clear the error. Not a solution. Curious to see what the TI guys say.

Hi Mike,

do you only see this if you get a "nothing to make"?  I just tried to reproduce this, by introducing an error and then removing it and for me the problems view cleared.

Could you send further details or perhaps a screen capture?

Best Regards,

Lisa

I'll try to track down other areas later, but try editing a .cmd file. Create errors, then repair them.

Hi Mike,

I tried a .cmd file specifically and the problems window cleared for me.  Have you tried clearing the projects .metadata?

Best Regards,
Lisa

I believe it might have something to do with the number of source files. Attached is a test case with 256 source files.
- Clean and build
- Change function name in in func000.c from func000() to funcnnn() to cause a linker error.
- Build. There should be a linker error.
- Change name funcnnn() back to func000().
- Build. Should be successful. Prior linker error still there. Attempt to run the app will cause warning about the "error".

5710.test.zip

Hi Norman,

for me the problems window cleared .....

Cheers,

Lisa

Perhaps the problem I observed got fixed in later versions of CCS. Not at my dev box. I think I am running CCS 5.1. I'll update CCS one day.

Hi Lisa,

Unfortunately, this is still a problem for me, especially the .cmd file errors.

Lisa TI said:

Have you tried clearing the projects .metadata?

How do I do this?

Hi Mike,

in your project files/folders you should notice the .metadata, you may simply delete it.

Best Regards,

Lisa

Lisa,

Lisa TI said:

in your project files/folders you should notice the .metadata, you may simply delete it.

This recommendation should come with a very emphatic warning that all of your previous project will have to be re-imported, and that all of your customized settings will be wiped out. Depending upon your workspace complexity, this could cause quit a bit of re-debugging :(

FYI, the above did NOT fix the problems I am seeing. I have narrowed the non-reset errors to memory allocation errors in the linker .cmd file (text editing errors ARE reset). Please try to create a memory allocation error, then fix it and see whether your errors get set. I created the allocation error below, then fixed it, compiled with no reported errors, but (as the screenshot show) the error indicator was not reset.

Also FYI, even when the compiler gives NO errors, the left-over, non-reset errors will trigger a warning that you are attempting to debug a file with errors when you attempt to debug the non-errored .out file.