4 ms·
the evil scheduler would be useful for catching deadlock bugs early
by gfody 5y ago
the evil scheduler would be useful for catching deadlock bugs early
- reubenbond 5y agoCoyote is a great tool/library from Microsoft for testing large numbers of schedules in .NET programs: https://microsoft.github.io/coyote/ https://microsoft.github.io/coyote/
- neerajsi 5y agoThere's also https://www.microsoft.com/en-us/research/project/cuzz-concurrency-fuzzing/ https://www.microsoft.com/en-us/research/project/cuzz-concur.... This is part of the Windows App Verifier, so it should be usable for any Windows app.
- Nzen 5y agoI don't doubt someone has built something like that for testing, though perhaps not as a library. I'm reminded of a networking service that does the same at a higher level, given its easy to remember name : https://github.com/tylertreat/comcast https://github.com/tylertreat/comcast
- nyanpasu64 5y agohttps://github.com/tokio-rs/loom https://github.com/tokio-rs/loom perhaps? It also models weak memory reordering, but takes some work to integrate into existing apps. For triggering race conditions in compiled binaries, you could try https://robert.ocallahan.org/2016/02/introducing-rr-chaos-mode.html https://robert.ocallahan.org/2016/02/introducing-rr-chaos-mo....