News for hackers. Stuff that matters.
Re:Why debugging is all about understanding by AnimalMuppet on Thursday August 06, 2015 @11:25AM (#10017093)
> If you have a race condition in a multi threaded program, a simple printf is enough to screw the timings and make the bug disappear, it's not at all better than breakpoints and stepping in a debugger.

If you have a race condition in a multi threaded program, a simple printf may be enough to change the timings and make the bug disappear. But a breakpoint and stepping in a debugger is guaranteed to completely change the timings (unless your timings are on the order of minutes).

Re:Why debugging is all about understanding by mannykannot on Sunday August 09, 2015 @01:56PM (#10030849)
In concurrent software development, the third way (analysis) is the only way. You need to know (or find out) which resources can be accessed concurrently, and develop a theory of how this could lead to the observed error.