explicit → indirect ("TIMEOUT" string absent from log) |
Config-Coverage-1: Using default analysis anchor removed (absent from log) |
Plain-Unknown-1: Using default analysis anchor removed (absent from log)
Annotation protocol — column rules
Boundary rule — observed: filled from log text alone, no "because". interpreted: requires at least one "because X → Y" step.
| ID / Pattern | observed (log-literal) | interpreted (inference) | |||||
|---|---|---|---|---|---|---|---|
| Surface | Evidence | Raw-log anchors | Terminal cause | Diagnostic cause | Confidence | Run validity | |
| TIMEOUT-1 P-RESOURCE |
TIMEOUT / ERROR (SIGNAL 15) |
indirect |
PORTFOLIO :: {'program': 'Program', 'spec': 'Specification'}
Verifier :: esbmc-kind
Verifier :: utaipan
Verifier :: two_ls
Verifier :: symbiotic
{'verdict': 'ERROR(SIGNAL 15)', 'witness': }
|
Resource |
unobservable
SIGTERM in log; which verifier was running and at what state is not exposed. |
plausible | incomplete |
|
TIMEOUT-2 P-RESOURCE v4.2 updated |
TIMEOUT | indirect |
Partial Incremental Mode
153 variables, 66 clauses
SAT checker: instance is SATISFIABLE
SAT checker inconsistent: instance is UNSATISFIABLE
75723 variables, 15605 clauses
75724 variables, 12 clauses
⚠ "TIMEOUT" string is not present in the log. External kill is inferred from the log truncating after repeated SAT iterations. Evidence corrected from explicit → indirect. |
Resource |
search-space
Variable counts are in log (153→75723). "search-space" is one inference step from those counts. |
plausible | incomplete |
|
TIMEOUT-3 P-RESOURCE v4.1 updated |
TIMEOUT | indirect |
INFO: Starting verification
klee -dump-states-on-halt=0 ... -max-time=0
KLEE: output directory is "…/klee-out-0"
KLEE: Using Z3 solver backend
[log ends here — no further output]
⚠ v3 anchors |
Resource |
unobservable
|
plausible | incomplete |
|
Config-Coverage-1 P-CONFIG v4.2 updated |
UNKNOWN / ERROR | explicit |
Ultimate.py --spec …/termination.prp
No suitable file found in config dir
using search string *Termination.xml
No suitable toolchain file found using *Termination.xml
⚠ |
Config-Missing |
config-absent
Search string and failure both in log. No inference step required. |
safe | unsupported |
| Config-Coverage-2 P-CHAIN |
UNKNOWN | explicit |
TerminationAnalysisResult: Unable to decide termination
Overapproximations
C: (x-1)&y [17] (Reason bitwiseAnd)
RESULT: unable to determine termination
Using bit-precise analysis
No suitable settings file found using Termination*64bit*_Bitvector
ERROR: UNSUPPORTED PROPERTY
Result: UNKNOWN
|
Incomplete → Config-Missing Two distinct terminal events chained. |
precision-loss
fallback-failed
Log transition (chain) ①
Unable to decide + Reason bitwiseAnd → precision-loss↓ fallback triggered
②
Using bit-precise analysis → attempt noted in log↓ config lookup
③
No suitable settings file …Bitvector → fallback-failedEach anchor individually explicit; connecting ①→②→③ requires knowing the fallback mechanism. |
plausible | incomplete |
| Config-Coverage-3 P-UNSUP |
UNKNOWN / ERROR | explicit |
Bubaak version 0.9.2
- program terminates
does not support termination
Caught exception, killing tasks...
NotImplementedError("BSELF does not support termination")
|
Unsupported |
property-unsupported
Exception text is in log verbatim. No inference required. |
safe | unsupported |
|
Plain-Unknown-1 P-CONFIG v4.2 updated |
UNKNOWN / ERROR | explicit |
Ultimate.py --spec …/termination.prp
and-03-false.c
No suitable file found in config dir
using search string *Termination.xml
No suitable toolchain file found using *Termination.xml
⚠ |
Config-Missing |
config-absent
Same pattern as CC-1. Search and failure both in log. |
safe | unsupported |
| Plain-Unknown-2 P-INCOMPLETE |
UNKNOWN / INCOMPLETE |
explicit |
Counterexample to termination found, but deemed imprecise
Termination algorithm did not find a non-terminating loop.
Analysis 2 terminated, but result is unsound.
No further configuration available.
Verification result: UNKNOWN, incomplete analysis.
|
Incomplete |
precision-loss
"Imprecise" and "unsound" are in log. What caused the imprecision is not stated — identifying the primary factor is the risky step. |
risky | questionable |
| Plain-Unknown-3 P-INCOMPLETE |
UNKNOWN | indirect |
Specification: Termination → enabling termination analyses
unrolling loop at …and-04-false.c:15 with factor 12
SV-COMP specification: CHECK( init(main()), LTL(F end) )
[Warning][Integer > Overflow][CWE-191] Signed integer underflow
[Warning][Termination] The program might not terminate!
[Warning][Deadcode][CWE-571] condition 'x < 8' always true
SV-COMP result: unknown
|
Incomplete |
precision-loss
Warning cluster is in log. Causal link to UNKNOWN is inferred. |
risky | valid |