The Breakpoints view shows your program's breakpoints in a tree-like structure, beginning with the root or parent breakpoint. This breakpoint, "All Breakpoints", expands into lower-level breakpoints, which may in turn expand into still lower-level breakpoints. For example, a class breakpoint expands to a set of breakpoints, one for each method of the class, and each of these in turn expands to a set of breakpoints, one for each process running under debug control.
The purpose of structuring breakpoints in a tree is that it makes it easier for you to disable, delete, or re-enable entire categories or groups of breakpoints. By applying your action to a single parent breakpoint, you can enable, disable or delete all its child breakpoints.
Each statement, function, or other breakpoint in the Breakpoints view expands into one or more active processes, with a status shown for each process running under debug control. Enabled breakpoints are indicated by a red stop sign (because they will cause execution to stop when encountered). Disabled breakpoints are indicated by a green octagon.
![]()
Enable, Disable, or Delete
Breakpoints from the Breakpoints Pane
