When comparing Chris Wenham's: How to fix bugs, step by step vs Paul Carter's: Common C Errors, the Slant community recommends Paul Carter's: Common C Errors for most people. In the question“What are the best resources to learn to debug C/C++?” Paul Carter's: Common C Errors is ranked 3rd while Chris Wenham's: How to fix bugs, step by step is ranked 4th. The most important reason people chose Paul Carter's: Common C Errors is:
This guide provides plenty of examples of errors that can be found in C programs like string-related errors and I/O errors.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Gives a list of the common types of bugs that can be found
This guide provides a detailed list of common types of bugs that can be found on a C program and some brief explanations on how to fix them.
Pro Gives a highly detailed and procedural list on how to fix bugs
The whole general process of fixing a bug, from finding it to solving is explained in a detailed and procedural manner, step by step.
Pro Provides a list of good practices to follow
Pro Provides examples of some common errors in C programs
This guide provides plenty of examples of errors that can be found in C programs like string-related errors and I/O errors.
Cons
Con Not very detailed
This is a rather short tutorial on how to fix bugs. It has plenty of information, but it's not very detailed. For example, each type of bug is explained in one or two lines.
Con Doesn't really explain how to find bugs
This guide doesn't actually explain how to track down bugs. It's just a collection of common C errors with explanations on how to solve them.