Probe effect

Probe effect is unintended alteration in system behavior caused by measuring that system. In code profiling and performance measurements, the delays introduced by insertion or removal of code instrumentation may result in a non-functioning application, or unpredictable behavior.

Examples

In electronics, by attaching a multimeter, oscilloscope, or other testing device via a test probe, small amounts of capacitance, resistance, or inductance may be introduced. Though good scopes have very slight effects, in sensitive circuitry these can lead to unexpected failures, or conversely, unexpected fixes to failures.

In debugging of parallel computer programs, sometimes failures (such as deadlocks) are not present when debugger's code (which was meant to help finding a reason for deadlocks by visualising points of interest in the program code) is attached to the program. This is because additional code changed timing of the execution of parallel processes, and because of that deadlocks were avoided.[1] This type of bug is known colloquially as a Heisenbug, by analogy with the observer effect in quantum mechanics.

Sources
  1. Event manipulation for Nondeterministic Shared-Memory Programs / High-Performance Computing and Networking. 9th International Conference, HPCN Europe 2001, Amsterdam, The Netherlands, June 25–27, 2001,
gollark: String literals are specified as byte arrays!
gollark: Oh dear, a comment. I need to stop it somehow. Hmm.
gollark: 1. No dedicated syntax2. Any string making up a whole statement on its own is stdouted3. ???
gollark: You can get rid of them, mostly.
gollark: Also, add no syntax for comments.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.