A probe effect in concurrent programs¶
Gait. (1986). A probe effect in concurrent programs. Software: Practice and Experience.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Heisenbug
- It executes a system call and an implicit memory barrier, adding tens of microseconds and reordering constraints that just happen to serialize the two threads so the tiny race window never opens during the test.
This sourceNames and demonstrates the probe effect - that inserting instrumentation into a concurrent program perturbs its timing enough to mask the synchronization fault being hunted; the syscall, memory-barrier and microsecond details are illustration, not findings of this paper.
- It executes a system call and an implicit memory barrier, adding tens of microseconds and reordering constraints that just happen to serialize the two threads so the tiny race window never opens during the test.
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:16704711e23d · see in the full table