Skip to content

Commit ab7a97b

Browse files
committed
edits
1 parent a41628b commit ab7a97b

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/debugger/how-to-use-the-call-stack-window.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ In the **Call Stack** window, select the function, right-click, and then choose
107107

108108
## Set a breakpoint on the exit point of a function call
109109

110-
See [Set a breakpoint at a call stack function](../debugger/using-breakpoints.md#BKMK_Set_a_breakpoint_from_debugger_windows).
110+
See [Set a breakpoint at a call stack function](../debugger/get-started-with-breakpoints.md#BKMK_Set_a_breakpoint_from_debugger_windows).
111111

112112
## Display calls to or from another thread
113113

docs/debugger/using-breakpoints.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The following table shows common debugging scenarios for breakpoints and the rec
3333
|----------|---------------|
3434
| How do I pause running code to inspect a line of code that may contain a bug? | Set a breakpoint. For more information, see [Get started with breakpoints](get-started-with-breakpoints.md). |
3535
| Does my variable have an unexpected value? Or, do I want to inspect my app when it reaches a specific state? | Try a conditional breakpoint to control where and when a breakpoint gets activated by using conditional logic. Right-click on a breakpoint to add conditions. Set the condition to be true when the variable equals the unexpected value. For more information, see [Breakpoint conditions](#breakpoint-conditions). |
36-
| How do I log information to the Output window under configurable conditions without modifying or stopping my code? | Tracepoints allow you to log information to the Output window under configurable conditions without modifying or stopping your code. |
36+
| How do I log information to the Output window under configurable conditions without modifying or stopping my code? | Tracepoints allow you to log information to the Output window under configurable conditions without modifying or stopping your code. For more information, see [Use tracepoints in the Visual Studio debugger](../debugger/using-tracepoints.md).|
3737
| How do I know when the value of my variable changes? | For C++, set a [data breakpoint](#BKMK_set_a_data_breakpoint_native_cplusplus). <br> For apps using .NET Core 3 and later, you can also set a [data breakpoint](#BKMK_set_a_data_breakpoint_managed). <br> Otherwise, for C# and F# only, you can [track an object ID with a conditional breakpoint](#using-object-ids-in-breakpoint-conditions-c-and-f). |
3838
| How do I break execution only if another breakpoint is hit? | Set a Dependent Breakpoint that breaks execution only if another breakpoint is first hit. For more information, see [Dependent Breakpoint](#BKMK_set_a_dependent_breakpoint). |
3939
| Can I hit a breakpoint only once? | Set a temporary breakpoint which lets you break the code only once. For more information, see [Temporary Breakpoint](#BKMK_set_a_temporary_breakpoint). |
@@ -47,7 +47,7 @@ A *tracepoint* is a breakpoint that prints a message to the **Output** window. A
4747

4848
## Breakpoint conditions
4949

50-
You can control when and where a breakpoint executes by setting conditions. The condition can be any valid expression that the debugger recognizes. For more information about valid expressions, see [Expressions in the debugger](../debugger/expressions-in-the-debugger.md).
50+
You can control when and where a breakpoint executes by setting conditions. The condition can be any valid expression that the debugger recognizes. (For more information about valid expressions, see [Expressions in the debugger](../debugger/expressions-in-the-debugger.md).)
5151

5252
**To set a breakpoint condition:**
5353

0 commit comments

Comments
 (0)