Visual Studio > Debugger > Breakpoints
Visual Studio Icon

Breakpoints in Visual Studio

Breakpoints are fundamental tools for debugging applications. They allow you to pause the execution of your program at a specific point, inspect the state of your variables, and step through your code line by line. This guide covers how to set, manage, and use various types of breakpoints in Visual Studio.

Key Takeaway: Breakpoints are essential for understanding and fixing issues in your code by enabling precise control over program execution.

Types of Breakpoints

Visual Studio supports several types of breakpoints, each suited for different debugging scenarios:

1. Simple Breakpoints (Unconditional)

This is the most common type of breakpoint. When the execution reaches a simple breakpoint, the debugger always pauses.

Setting a Simple Breakpoint

To set a simple breakpoint:

  1. Open your code file in Visual Studio.
  2. Click in the gutter (the area to the left of the line numbers) next to the line of code where you want to pause. A red circle will appear.
  3. Alternatively, place the cursor on the line and press F9.

When you run your application in debug mode, execution will stop at this line, and the line will be highlighted.

2. Conditional Breakpoints

Conditional breakpoints pause execution only when a specified condition is met. This is incredibly useful for debugging loops or when you want to stop only under specific circumstances.

Setting a Conditional Breakpoint

  1. Right-click on an existing breakpoint (red circle) in the gutter.
  2. Select Conditions... from the context menu.
  3. In the Breakpoint Settings dialog, enter your condition in the Conditions text box. For example, to stop when a variable count is greater than 10, you would enter: 
    count > 10
  4. You can also specify Hit Count conditions (e.g., break every 5 times) or Filter conditions (e.g., break only on a specific thread or process).
  5. Click Close. The breakpoint icon will change to indicate it's conditional.

3. Hit Count Breakpoints

These breakpoints pause execution after a specific number of times a breakpoint has been hit.

Setting a Hit Count Breakpoint

  1. Right-click on a breakpoint in the gutter.
  2. Select Conditions....
  3. Choose the Hit Count radio button.
  4. Specify the desired hit count (e.g., Break when hit count is equal to: 5, or Break when hit count is a multiple of: 3).
  5. Click Close.

4. Tracepoints (Trace Output)

Tracepoints are like breakpoints but instead of pausing execution, they log a message to the Output window. This is excellent for tracking variable values or program flow without interrupting execution.

Setting a Tracepoint

  1. Right-click on a breakpoint in the gutter.
  2. Select Conditions....
  3. Check the Actions radio button.
  4. In the When hit text box, enter the message you want to log. You can use curly braces {} to embed variable values. For example: 
    Processing item {itemName} with ID {itemId}.
  5. Ensure Continue execution is checked if you don't want the debugger to pause.
  6. Click Close. The breakpoint icon will change to a diamond shape.

5. Data Breakpoints

Data breakpoints (available in some editions) pause execution when the value of a specific variable changes. This is invaluable for tracking down memory corruption or unexpected value modifications.

Setting a Data Breakpoint (for C++, C#, JavaScript)

  1. Ensure you are debugging.
  2. Open the Watch window (Debug > Windows > Watch > Watch 1).
  3. Right-click on the variable you want to monitor.
  4. Select Break when value changes.

Alternatively, you can set data breakpoints via the Breakpoints window (Debug > Windows > Breakpoints), by clicking New > Data Breakpoint....

Managing Breakpoints

The Breakpoints window is your central hub for managing all breakpoints in your project.

Using the Breakpoints Window

  • Open the Breakpoints window by going to Debug > Windows > Breakpoints.
  • In this window, you can:
    • Enable/Disable: Check/uncheck breakpoints to temporarily ignore them.
    • Delete: Remove breakpoints.
    • Filter: Show breakpoints for specific files, modules, or threads.
    • Move: Change the order of breakpoints.
    • Import/Export: Save and load breakpoint configurations.

Debugging with Breakpoints

Once execution pauses at a breakpoint, you can use the debugger's stepping commands:

Tip: Hovering your mouse over variables while paused will show their current values (data tips).

Mastering breakpoints is crucial for efficient debugging. Experiment with the different types and settings to find the most effective ways to diagnose and resolve issues in your code.