Jinx Debugger
This article needs additional citations for verification. (February 2018) |
Jinx was a
Jinx worked by dynamically building a set of potential interleavings (i.e. alternate eventualities, or execution scenarios, that will occur under some future condition) that are most likely to result in concurrency faults, and quickly tested those execution paths to surface concurrency problems such as deadlocks, race conditions and atomicity violations that are found in multiprocessing applications.
Unlike model checkers, Jinx did not require the specification of a model. Unlike
Jinx was implemented as a hypervisor, giving it the ability to observe the effects of all elements of the software environment on thread interleaving. Jinx operated independently of any programming language or threading libraries or tools.
Jinx was developed by a (now defunct) company named Corensic in Seattle, Washington based on research performed at the University of Washington[2] and initially presented at the ASPLOS conference of 2009.
References
- ^ Bartosz Milewski [@BartoszMilewski] (September 23, 2014). "@double_thunk Corensic was bought by F5 and Jinx got cancelled. Sorry!" (Tweet) – via Twitter.
- ^ "Sampa: Research Projects". sampa.cs.washington.edu. Retrieved June 11, 2023.