| ... | ... | @@ -257,7 +257,7 @@ Here, Lazart produces several results tables: |
|
|
|
- Full attacks results: extended table of attack analysis for redundancy and equivalence analysis (see [tutorial 2](Overview/Tutorial-2:-Symbolic-Inputs,-Equivalence-and-Redundancy)).
|
|
|
|
- Execution: execution metrics of the analysis: traces generated (*Traces*), partial paths (*PP*), ignored ktests (*IgT*), total ktests (*KT*), completed paths (*CP*), explored paths (*EP*) and total executed LLVM instructions (*EI*).
|
|
|
|
- Time metrics: total time (*TT*), total lazart time (*TLz*), total DSE duration (*TDSE*), traces parsing duration (*TTr*) and total analysis duration (*TA*).
|
|
|
|
- Coverage: instruction and basic blocs coverage (*ICov(%)* and *BCov(%)*), incomplete traces (*ITr*), full branches (*FBr*) and partial branches (*PBr*).
|
|
|
|
- Coverage: instruction and basic blocs coverage (*ICov(%)* and *BCov(%)*), incomplete traces (*ITr*, i.e. traces that has not been completely parsed, see [here](https://gricad-gitlab.univ-grenoble-alpes.fr/securitytools/lazart/-/wikis/Core/Traces#trace-parsing-step-and-replay)), full branches (*FBr*) and partial branches (*PBr*), which corresponds to LLVM branches that has been fully or partially explored by the DSE engine.
|
|
|
|
- Hotspots analysis results: providing information about injection points (see the [dedicated section](Analysis/Hotspot-Analysis)).
|
|
|
|
|
|
|
|
All results are stored inside the analysis folder, named `results` (specified in the `path` field in `read_or_make`).
|
| ... | ... | |
