Hubbry Logo
search
search button
Sign in
Historyarrow-down
starMorearrow-down
Hubbry Logo
search
search button
Sign in
Probe effect
Community hub for the Wikipedia article
logoWikipedian hub
Welcome to the community hub built on top of the Probe effect Wikipedia article. Here, you can discuss, collect, and organize anything related to Probe effect. The purpose of the hub is to connect people, foster deeper knowledge, and help improve the root Wikipedia article.
Add your contribution
Inside this hub
Probe effect

Probe effect is an 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

[edit]

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 the debugger's code (which was meant to help to find a reason for deadlocks by visualising points of interest in the program code) is attached to the program. This is because additional code changed the 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.

See also

[edit]

Sources

[edit]
  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,
Add your contribution
Related Hubs