http://cowboyprogramming.com/2008/03/23/debugging-heisenbugs/ Game Development and General Hacking by the Old West Tue, 20 Jul 2010 15:03:31 +0000 http://wordpress.org/?v=2.9.1 hourly 1 http://cowboyprogramming.com/2008/03/23/debugging-heisenbugs/comment-page-1/#comment-137154 lehti Wed, 11 Nov 2009 19:28:57 +0000 http://cowboyprogramming.com/2008/03/23/debugging-heisenbugs/#comment-137154 Uh how I hate debugging. Can't even think this kind of situation when your bug is chanching when trying to catch it. Uh how I hate debugging. Can’t even think this kind of situation when your bug is chanching when trying to catch it.

]]> http://cowboyprogramming.com/2008/03/23/debugging-heisenbugs/comment-page-1/#comment-14631 smallcode » Blog Archive » Debugging buffer overflows Mon, 14 Apr 2008 12:58:34 +0000 http://cowboyprogramming.com/2008/03/23/debugging-heisenbugs/#comment-14631 [...] Once I debugged a program that read 1-2 characters past the end of buffer when some specific input was provided. The bytes after the buffer were usually readable, but if they were not, the program crashed. It was hard to catch the bug, because it occurred rarely (being similar to what Mick West calls Heisenbugs). [...] [...] Once I debugged a program that read 1-2 characters past the end of buffer when some specific input was provided. The bytes after the buffer were usually readable, but if they were not, the program crashed. It was hard to catch the bug, because it occurred rarely (being similar to what Mick West calls Heisenbugs). [...]

]]> http://cowboyprogramming.com/2008/03/23/debugging-heisenbugs/comment-page-1/#comment-13988 Washu Sat, 29 Mar 2008 20:15:09 +0000 http://cowboyprogramming.com/2008/03/23/debugging-heisenbugs/#comment-13988 Another couple of good things you can do: Plug in static analysis tools, often times many such bugs can be caught at compile time, although not always. However, you can also plug in data-flow analysis tools if you have the budget for them, those can almost always catch those suspect areas, either before they happen or even during the act. Another couple of good things you can do:
Plug in static analysis tools, often times many such bugs can be caught at compile time, although not always. However, you can also plug in data-flow analysis tools if you have the budget for them, those can almost always catch those suspect areas, either before they happen or even during the act.

]]> http://cowboyprogramming.com/2008/03/23/debugging-heisenbugs/comment-page-1/#comment-13742 b100dian Mon, 24 Mar 2008 14:27:54 +0000 http://cowboyprogramming.com/2008/03/23/debugging-heisenbugs/#comment-13742 You forgot one important cause of heisenbugs: assert()s that _do_ something. You forgot one important cause of heisenbugs: assert()s that _do_ something.

]]>