Child Breakpoints
This topic applies to:
Edition |
Visual Basic |
C# |
F# |
C++ |
Web Developer |
|---|---|---|---|---|---|
Express |
.gif "Topic does not apply") |
|
|
.gif "Topic applies") |
|
Standard |
|
|
|
|
|
Pro, Premium, and Ultimate |
|
|
|
|
|
Table legend:
|
Applies |
|
Does not apply |
.gif "Topic applies but command hidden by default") |
Command or commands hidden by default. |
The Breakpoints window enables you to view child breakpoints, which are additional breakpoints the debugger creates when you set a breakpoint in a location such as an overloaded function. The parent-child relationship is represented by a tree control that appears next to the breakpoint name. You can expand the tree control to see a breakpoint's children.
Child breakpoints are also created when you attach to more than one instance of the same program. In that case, you can look at the Program column to see which instance each child breakpoint belongs to. For more information, see Attaching to Running Processes.
Disabling and Deleting Child Breakpoints
You can disable individual child breakpoints, but you cannot remove a child breakpoint except by removing the parent. Trying to delete a child breakpoint disables the child breakpoint rather than removing it. The debugger remembers child breakpoints, and their enabled/disabled states, between debugging sessions.
See Also
Tasks
How to: Use the Breakpoints Window