Changes between Version 2 and Version 3 of DebuggingSansDebugger
- Timestamp:
- 05/04/10 08:25:01 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DebuggingSansDebugger
v2 v3 3 3 The fundamental requirement is to correct your understanding of how your program is behaving in the context of the inputs and environment in which the bug occurs. Of course, a debugger helps you gain that understanding, but there are also non-debugger-based techniques to do so: 4 4 5 * Use `cobra -d` option to get debugging symbols so that uncaught exceptions will include source line numbers for the stack frames. 5 6 * Add more contracts in order to reveal the bug closer to its source. 6 7 * Add more unit tests to isolate and verify various behaviors expected of your methods and classes.