Polyspace Support can help you understand your specific issue. Visit this page. Often, errors like this can indicate some issues in setting up the analysis.
In general, there is one key difference between the code that you see and the code that Polyspace analyzes.
The macros in your code are replaced with their definitions. This is what is called the preprocessed code and emulates what would actually happen at run-time.
Say, you have a file aFile.c that includes a header aFile.h that has this macro definition:
#define FOR_LOOP(n) for(i=0; i<(n); i++);
When analyzing this file, Polyspace includes the content of aFile.h directly in aFile.c, then looks at the macro definitions and replaces all instances of FOR_LOOP() using the above definition. This results in a file aFile.ci, which is the code that Polyspace analyzes.
When you see an error message in a line with a macro, and it seems that the line looks ok, it might mean that replacing the macro with its definition causes the line to be not ok. Looking at the preprocessed code often makes it clear what happened. For instance, the macro definition might itself have a semicolon like in the example above, causing a problem when the replacement is made.
There is a trick to the see the .ci file for each source file. The trick is documented here in context of a different error: https://www.mathworks.com/help/codeprover/ug/conflicting-declarations-in-different-translation-units.html
But since the problem occurs for you in a header file and not in a source file, going down this path might not be a good idea. Often, header files are files that you do not own and even if you find out the exact cause of the error, you might not be able to fix it. The actual fix might be setting an analysis option during setup. For instance, if the header file comes from your compiler, the error might indicate that you have not specified the right compiler version. This is where tech support can help you diagnose your specific issue.
