Use breakpoints

A breakpoint causes the execution of a thread to suspend at the location where the breakpoint is set. A list of all breakpoints (for all debug sessions) appears in the Breakpoints view, unless you use the filter by debug target action. To filter out breakpoints that are not related to the current debug session, click the Breakpoints view Show Breakpoints Supported by Selected Target push button. To link the Breakpoints view with the Debug view click the Link with Debug view toggle - when this is selected, only those breakpoints that are associated with the selected debug target in the Debug view will appear in the Breakpoints view.

Note: Filtering by debug target does not filter out breakpoints for debug targets that are similar to that of the current debug session.

Breakpoints can be enabled and disabled via pop-up menus or check box in the Breakpoints view. When a breakpoint is enabled, it will cause a thread to suspend whenever it is hit. When a breakpoint is disabled, it will not cause threads to suspend. For further information about enabling and disabling breakpoints, see the related topic below.

There are two indicators to the left of a set breakpoint. To the far left is a check box which indicates if the breakpoint is enabled (when enabled, the check box contains a check mark). To the near left, a filled indicator with a check mark overlay indicates a breakpoint that has been successfully installed by the debug engine. Breakpoints must be installed before they will suspend execution. It is possible to add a breakpoint that is not valid for the current debug session. This breakpoint will not be installed until it is part of a debug session which includes a debug engine that will recognize the breakpoint.

While in the Breakpoints view, the source editor will open to the location of a breakpoint if you do one of the following:

 

Related concepts

Breakpoints

 

Related tasks

Enabling and disabling breakpoints
Removing breakpoints