Skip to content

Update using-breakpoints.md #261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 23, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/debugger/using-breakpoints.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,8 +58,8 @@ translation.priority.mt:
# Use Breakpoints in the Visual Studio Debugger
You can set breakpoints when you want to stop debugger execution, perhaps to see the state of code variables or to look at the call stack. They are one of the most important debugging techniques in a developer's toolbox.

## <a name="BKMK_Overview"></a> Setting a function breakpoint in source code
You set a function breakpoint in source code by clicking in the left margin of a source code file, or by putting your cursor on a line of code and pressing F9. The breakpoint appears as a red dot in the left margin, and the line of code is colored as well:
## <a name="BKMK_Overview"></a> Setting a line breakpoint in source code
You set a line breakpoint in source code by clicking in the left margin of a source code file, or by putting your cursor on a line of code and pressing F9. The breakpoint appears as a red dot in the left margin, and the line of code is colored as well:

![Set a breakpoint](../debugger/media/basicbreakpoint.png "BasicBreakpoint")

Expand Down Expand Up @@ -259,4 +259,4 @@ You can set breakpoints when you want to stop debugger execution, perhaps to see
You cannot set a breakpoint in a source file when the debugger hasn't loaded the debug information for the module where the code is located. Symptoms may include messages such as **the breakpoint will not be set**. The Warning breakpoint glyph appears at the breakpoint location. However, these Warning breakpoints become actual breakpoints when the code is loaded. For more information about loading symbols, see [Specify Symbol (.pdb) and Source Files](../debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md).

## See Also
[Navigating through Code with the Debugger](../debugger/navigating-through-code-with-the-debugger.md)
[Navigating through Code with the Debugger](../debugger/navigating-through-code-with-the-debugger.md)