How can I define a custom exception type for Polyspace Bug Finder?

I am running Polyspace over some code for an embedded system. One thing that I run into is numerous warnings about uninitialized variables. However, this is due to Polyspace not knowing that a certain macro sets registers such that processing will halt, so the values would never get used. All these error handling calls are wrapped in the same macro, so is there a way I can tell Polyspace to stop at these?

There are enough of the errors that manually justifying each would be a massive effort. I'm using Polyspace R2016b

Answer 1

[Alexandre De Barros]

Hello Trenton,

Without further information, it is difficult to find out why Polyspace is not able to know that "a certain macro sets registers such that processing will halt."

I suggest you to contact the Technical support and provide the information on this macro, ideally with a snippet of code.

You can also attach the verification log to your request, as it contains lots of information on the verification.

Best regards,

Alexandre