Differences between version 4 and predecessor to the previous major change of HeisenBug.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Wednesday, April 6, 2005 5:11:56 am | by DeePatton | Revert |
| Older page: | version 2 | Last edited on Wednesday, March 24, 2004 9:04:22 pm | by StuartYeates | Revert |
@@ -1,4 +1,9 @@
A bug that disappears or changes behaviour when you are trying to track it down.
-An example cause of this is the act of debugging changes the program's execution (for example, uninitialised memory patterns or a RaceCondition) in such a way that the bug is not triggered.
-See JargonFile:heisenbug
, the
"BUGS" section
of assert(3)
+"What do yo mean
, I shouldn't initialize variables in an assert(3)?
"
+
+An example
of this is when the act of debugging changes the program's execution (for example, uninitialised memory patterns or a RaceCondition) in such a way that the bug is not triggered.
+
+See also:
+* __BUGS__ in
assert(3)
+* JargonFile:heisenbug
