Debugging 2013- Peter Makholm
1 like92 views
This document provides tips for using printf() for debugging code. It recommends using version control and understanding the code and problem before debugging. It discusses whether to use printf(), where to print output like stderr vs stdout, what information to include like timestamps and IDs, and potential pitfalls like changing buffering. Finally, it suggests writing tests, adding assertions and logging, and taking breaks as part of the debugging process.
Debugging 2013- Peter Makholm
- 7. Four Basic Rules! ● Use a version control system! ● Understand your code ● Understand your problem ● Think before typing!
- 8. To printf or not to printf ● Build time restrictions ● Environment restrictions ● Use your language ● Use your editor
- 10. What to print ● Timestamp ● Location in code ● Process or request ID ● What you are dumping
- 11. Pitfalls ● changes errno ● changes buffering ● can block ● additional file descriptors
- 12. Post Mortem ● Write tests ● Add assertions ● Add logging ● Go to the pub