Polyspace 2018b boolean related 10.3 violation, is it a false positive ?
1 view (last 30 days)
Show older comments
The below code with same configuration settings does not give 10.3 violation in Polyspace 2016b but gives 10.3 in polyspace 2018b:
(Note: The below code is a simplified version of Auto generated code)
typedef unsigned char boolean;
#define True 1U
#define False 0U
void main()
{ boolean a,b;
a = True; /* 10.3 violation only in 2018b */
b = False; /* 10.3 violation only in 2018b */
}
0 Comments
Accepted Answer
Anirban
on 12 Jun 2020
Hi,
This is a bug that has been fixed in R2019b. You can upgrade to the later release or if you continue to use R2018b, justify those specific results coming from 10.3 violations on boolean typedef-s (set the status of those results to No action planned and add a comment explaining the issue). You can select multiple results in the Polyspace UI and add the same status and comment to them.
PS: In future, if you ask questions, can you also set the Product attribute in those questions? I noticed that a previous question of yours was not answered. If you set the Product attribute, there are greater chances of the question being noted.
3 Comments
Anirban
on 14 Jun 2020
Typically, bugs are recorded in External Bug Reports here: https://www.mathworks.com/support/bugreports/ .
But I could not find an External Bug Report about this specific issue. If you contact MathWorks Technical Support, they might be able to help you better.
More Answers (0)
See Also
Categories
Find more on Run Settings in Help Center and File Exchange
Products
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!