The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.
From OpenAlex, which stores abstracts as an
index of words and their positions: what is shown is rebuilt from that,
and reads fluently whether or not it is what the author wrote.
Abstract
Practical software verification is dominated by two major classes of techniques. The first is model checking, which provides total precision, but suffers from the state space explosion problem. The second is abstract interpretation, which is usually much less demanding, but often returns a high number of false positives. We present Loopfrog, a static analyzer that combines the best of both worlds: the precision of model checking and the performance of abstract interpretation. In contrast to traditional static analyzers, it also provides `leaping' counterexamples to aid in the diagnosis of errors.
How it got here
How it got here
agent via openalex
Added
2026-10-28 21:48 UTC
Not denied by
a person 2026-10-29 17:12 UTC
Cite it as
@misc{kroening2009loopfrog,
title = {Loopfrog: A Static Analyzer for ANSI-C Programs},
author = {Daniel Kroening and Natasha Sharygina and Stefano Tonetta and Aliaksei Tsitovich and Christoph M. Wintersteiger},
year = {2009},
journal = {IEEE/ACM International Conference on Automated Software Engineering (ASE)},
pages = {668--670},
doi = {10.1109/ase.2009.35},
}