This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Flawed Run-Time Error Check Causes Build Failure

Other Parts Discussed in Thread: MSP430F5438A

I've seen this problem recurring with CCS v5.1M7 & CGT v3.3.3 when building for MSP430F5438A.

The run-time error check flags valid code as a syntax error and the subsequent build fails--but only if the source file is open in the editor (thus triggering the run-time check).

The code in question is part of Georges Menie's printf-stdarg.c code which is included in the MSP430X distribution of FreeRTOS:

 

            if( *format == 's' ) {
                register char *s = va_arg( args, char* );
                pc += prints (out, s?s:"(null)", width, pad);
                continue;
            }

And the error given is:  "Symbol 's' could not be resolved".

If I close and re-open the project, then rebuild without opening printf-stdarg.c, the project builds without error.  Once the file has been opened, however, the project will not build successfully until closed and re-opened again.

How can I turn off the run time error checking?

Thanks & Regards,

--Mike

 

 

  • I believe the behavior you are seeing is related this thread. Please check the last post there for an explanation and workaround.

  • Aarti,

     

    Thanks, that did it--now I can go home a good 20 minutes earlier each day!

    If anyone should find their way here, open Windows/Preferences, then select C/C++/Code Analysis and uncheck the following:

         Symbol is not resolved (under Syntax and Semantic Errors)

    I also unchecked these annoying warnings:

         Unused variable declaration in file scope

         Unused function declaration

         Unused static function.

     

    Thanks & Regards,

    --Mike