Finding and Reproducing Heisenbugs in Concurrent Programs¶
Musuvathi, M. (2008). Finding and Reproducing Heisenbugs in Concurrent Programs.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Heisenbug
- Most heisenbugs are rooted in race conditions or uninitialized-memory uses: the extra overhead introduced by a debugger's ptrace syscall, or the memory barriers implicit in a logging call, or the different code layout produced by disabling compiler optimization, alters the interleaving or memory state enough that the race no longer fires during the investigation window.
This sourceEstablishes that heisenbugs are predominantly thread-interference defects whose appearance depends on a particular interleaving, so that changing the schedule changes whether they fire; the uninitialized-memory cause and the specific perturbation sources are not from this paper.
- Most heisenbugs are rooted in race conditions or uninitialized-memory uses: the extra overhead introduced by a debugger's ptrace syscall, or the memory barriers implicit in a logging call, or the different code layout produced by disabling compiler optimization, alters the interleaving or memory state enough that the race no longer fires during the investigation window.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:51ac5749d1d0 · see in the full table