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 toggle is selected, only those breakpoints that are associated with the selected debug target in the Debug view will be displayed in the Breakpoints view.
Breakpoints can be enabled and disabled with pop-up menus and check boxes in the Breakpoints view. When a breakpoint is enabled, it will cause execution to suspend whenever it is hit. When a breakpoint is disabled, it will not cause execution to suspend. For further information about enabling and disabling breakpoints, see the related topic.
Depending on the editor that you are using, line breakpoint indicators are displayed in the marker bar in the editor area and in a list in the Breakpoints view. The breakpoint entries in the list provide you, in brackets, with a summary of the breakpoints' properties.
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 perform one of the following tasks: