Skip to content

Commit b4b2c3d

Browse files
committed
more link fixes
1 parent 9dfbc7c commit b4b2c3d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/debugger/getting-started-with-the-debugger-cpp.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -166,7 +166,7 @@ First, you'll create a C++ console application project. The project type comes w
166166
167167
2. Press **F5** or the **Start Debugging** button ![Start Debugging](../debugger/media/dbg-tour-start-debugging.png "Start Debugging"), the app starts, and the debugger runs to the line of code where you set the breakpoint.
168168
169-
![Set and hit a breakpoint](../debugger/media/get-started-set-breakpoint.png)
169+
![Set and hit a breakpoint](../debugger/media/get-started-set-breakpoint-cpp.png)
170170
171171
The yellow arrow represents the statement on which the debugger paused, which also suspends app execution at the same point (this statement has not yet executed).
172172
@@ -283,7 +283,7 @@ Features that allow you to inspect variables are one of the most useful features
283283
284284
2. Click **F11** a few times until you see the debugger pause in the `SendMessage` method. Look at the **Call Stack** window.
285285
286-
![Examine the call stack](../csharp/media/get-started-call-stack.png "ExamineCallStack")
286+
![Examine the call stack](../debugger/media/get-started-call-stack.png "ExamineCallStack")
287287
288288
The **Call Stack** window shows the order in which methods and functions are getting called. The top line shows the current function (the `SendMessage` method in this app). The second line shows that `SendMessage` was called from the `main` method, and so on.
289289

0 commit comments

Comments
 (0)