Feature #9305

Provide a list of undefined and modelled functions for a fragment under verification

Added by Ilja Zakharov 2 months ago. Updated 8 days ago.

Environment model
Target version:
Start date:
Due date:
% Done:


Estimated time:
Published in build:


As we claim that our static verification is sound we need to provide some information about preconditions of verification. As a first step in this direction we propose to collect which functions are undefined and for which of them models exist. This should help to understand how many specifications to model functions a user should prepare.


#1 Updated by Vadim Mutilin 10 days ago

The user would like to know how many specifications of the active part of an environment she need to prepare. Is it part of this task?

#2 Updated by Ilja Zakharov 10 days ago

If you mean entry points then it is not a part of this task. Entry points can be easily found from the coverage report. This issue is related to external functions that can be completely undefined or be modelled. Currently, we do not have any report concerning this part of a program fragment under verification.

#3 Updated by Vadim Mutilin 10 days ago

Yes, I'm talking about entry_points and I do not see how they can be found from the coverage report "easily"

#4 Updated by Evgeny Novikov 8 days ago

Let's open another issue that will aim at showing some information on unspecified project specific API. For instance, for Linux loadable kernel modules this API includes uncovered exported functions and all global variables having structure types and which fields are initialized with function pointers.

Also available in: Atom PDF