A probe effect in concurrent programs¶
Gait, J. (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.
Supported in partVerified against the source
- 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¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:16704711e23d · see in the full table