C++ Debugging

C++ Debugging: Finding and Fixing Bugs

As we learned in the previous chapter, Logic Errors and Runtime Errors can cause your program to behave unexpectedly. The process of tracking down and fixing these errors is known as Debugging.

Bugs are a natural part of programming. In this tutorial, we will look at a few strategies you can use to debug your C++ applications effectively.

1. Print Debugging (The Simple Way)

The most common method beginners use to debug code is inserting cout statements throughout their program. By printing the values of your variables at different stages, you can trace exactly what the program is doing and pinpoint where the logic goes wrong.

#include <iostream>
using namespace std;

int main() {
  int total = 0;
  for (int i = 1; i <= 3; i++) {
    // DEBUG: Print the loop counter
    cout << "Current i: " << i << "\n"; 
    total += i;
    // DEBUG: Print the running total
    cout << "Current total: " << total << "\n";
  }
  cout << "Final total is: " << total << "\n";
  return 0;
}

While print debugging is easy, it can make your code messy if you forget to remove the cout statements once the bug is fixed.

2. Using an IDE Debugger

A much more powerful way to find bugs is to use the built-in debugger provided by Integrated Development Environments (IDEs) like Visual Studio, Code::Blocks, or CLion.

A debugger allows you to pause your program while it is running and inspect it in real-time.

Key Debugging Tools:

• Breakpoints: A breakpoint is an intentional stopping or pausing place in a program. You can click next to a line of code in your IDE to set a breakpoint. When the program reaches that line, it pauses.
• Step Over: Once paused, you can execute your code one single line at a time. This lets you watch exactly how your variables change.
• Step Into: If you reach a function call, "stepping into" will take you inside that function so you can debug its internal logic.
• Variable Watch: IDEs have a panel that automatically displays the current values of all variables in memory while the program is paused.

3. Read the Compiler Warnings

While errors stop your program from building, warnings do not. However, warnings are the compiler's way of saying: "This code is legally valid C++, but it looks very suspicious."

Always pay attention to compiler warnings! They often point directly to logic errors, such as using uninitialized variables or forgetting to return a value from a function.