Gets the short identifier of the detector, used in analyzer warnings.
The unique identifier of the detector.
Gets the kind of the detector.
Defines the behavior of warnings generated by this detector when working with multiple projects within a single Tact configuration.
Here are the available options:
"union"
Leave this value if you don't care about warnings generated in other projects."intersect"
If the warning is generated for some source location of the imported file,
it should be generated by each of the projects. Example: Constants from an
imported file should not be reported iff they are unused in all the projects,
so you need "intersect".Checks whether this detector needs the Soufflé binary to be executed.
Executes the detector's logic to check for issues within the provided compilation unit.
The compilation unit to be analyzed.
List of warnings has highlighted by this detector.
Protected
makeA wrapper method that creates Misti warnings with additional context about the detector generated it.
Protected
skip
A detector that identifies cell overflow and underflow problems.
Why is it bad?
Cell overflow and underflow are issues specific to the TON blockchain. TON stores data in cells, which are low-level data structures used for serialization and deserialization.
The overflow issue occurs when the user attempts to store more data in a cell than it supports. The current limitation is 1023 bits and 4 references to other cells. When these limits are exceeded, the contract throws an error with the exit code
8
during the compute phase.The underflow issue occurs when the user attempts to get more data from a structure than it supports. cells. When it happens, the contract throws an error with the exit code
9
during the compute phase.Example
Use instead:
Resources