package goblint

You can search for identifiers within the package.

in-package search v0.2.0

Static analysis framework for C

Install

Dune Dependency

goblint.in.tum.de Readme Changelog Edit opam file Versions (8)

Authors

Maintainers

Sources

goblint-2.4.0.tbz

sha256=99b78e6def71534d195eef9084baa26d8334b36084e120aa6afb300c9bf8afa6

sha512=f3162bd95a03c00358a2991f6152fc6169205bfb4c55e2c483e98cc3935673df9656d025b6f1ea0fa5f1bd0aee037d4f483966b0d2907e3fa9bf11a93a3392af

doc/goblint.common/AnalysisState/index.html

Module `AnalysisState`

Global flags for analysis state.

val should_warn : bool Stdlib.ref

If this is true we output messages and collect accesses. This is set to true in control.ml before we verify the result (or already before solving if warn = 'early')

val executing_speculative_computations : bool Stdlib.ref

If this is true, any overflows happening in IntDomains will not lead to warnings being produced or svcomp_may_overflow being set to true. This is useful when, e.g., BaseInvariant.Make.invariant executes computations that are not in the actual program

val svcomp_may_overflow : bool Stdlib.ref

Whether signed overflow or underflow happened

val svcomp_may_not_terminate : bool Stdlib.ref

Whether the termination analysis detects the program as non-terminating

Whether an invalid free happened

val svcomp_may_invalid_free : bool Stdlib.ref

Whether an invalid free happened

val svcomp_may_invalid_deref : bool Stdlib.ref

Whether an invalid pointer dereference happened

val svcomp_may_invalid_memtrack : bool Stdlib.ref

Whether a memory leak occurred and there's no reference to the leaked memory

val svcomp_may_invalid_memcleanup : bool Stdlib.ref

Whether a memory leak occurred

val global_initialization : bool Stdlib.ref

A hack to see if we are currently doing global inits

val postsolving : bool Stdlib.ref

Whether currently in postsolver evaluations (e.g. verify, warn)

val verified : bool option Stdlib.ref