Project

General

Profile

Actions

Feature #9931

closed

Introduce specific comments and error trace actions to distinguish important environment models

Added by Evgeny Novikov about 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Environment models
Target version:
Start date:
11/18/2019
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

Some environment models can result in faults. Typical examples are the following:

  1. Assertions can fail within ldv_check_final_state().
  2. CPAchecker SMG can reveal, say, memory leaks, when an environment model frees memory for object for which another environment model allocated memory and that was passed to a driver callback that allocated but did not free another memory.

In both cases corresponding actions are not callback actions by definition (although the first one is called so by mistake), so, they are not included in error trace patterns of unsafe marks. This is wrong, since these patterns miss error trace parts important from the point of view of checking.

Actions

Also available in: Atom PDF