Skip to content

Commit d603bdf

Browse files
Merge pull request #11316 from ihor-kitsa/ihor-kitsa-patch-4
Add missing periods
2 parents eba064e + 815e565 commit d603bdf

1 file changed

Lines changed: 10 additions & 10 deletions

File tree

docs/debugger/find-your-debugging-task.yml

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ sections:
3434
3535
- **How do I log information to the Output window under configurable conditions without modifying or stopping my code?**
3636
37-
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)
37+
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).
3838
3939
- **Manage and keep track of my breakpoints**
4040
@@ -103,14 +103,14 @@ sections:
103103
- **How can I attach to the same application repeatedly?**
104104
105105
You can use **Reattach to Process** (**Shift+Alt+P**) to easily allow you to start debugging your application in one click without needing to go through the Attach to Process dialog every time.
106-
See [Reattach to a process](attach-to-running-processes-with-the-visual-studio-debugger.md#BKMK_reattach)
106+
See [Reattach to a process](attach-to-running-processes-with-the-visual-studio-debugger.md#BKMK_reattach).
107107
108108
- question: |
109109
Debug multithreaded applications
110110
answer: |
111111
- **How can I debug a multi-threaded application? Or, is my application in a hung state?**
112112
113-
See [Parallel Stacks window](using-the-parallel-stacks-window.md) further troubleshooting
113+
See [Parallel Stacks window](using-the-parallel-stacks-window.md) further troubleshooting.
114114
115115
- **How can I view the order in which functions are called?**
116116
@@ -145,7 +145,7 @@ sections:
145145
146146
Just My Code is a Visual Studio debugging feature that automatically steps over calls to system, framework, and other non-user code.
147147
In the Call Stack window, Just My Code collapses these calls into [External Code] frames.
148-
See [Debug only user code with Just My Code](just-my-code.md)
148+
See [Debug only user code with Just My Code](just-my-code.md).
149149

150150
- **How can I view or debug the raw assembly instructions that my program is executing?**
151151

@@ -154,17 +154,17 @@ sections:
154154
- **Can I see source code for .NET Libraries?**
155155

156156
Enable Microsoft Symbol Servers from Debug > Options > Symbols in order to download symbols and source for .NET Libraries.
157-
See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md)
157+
See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md).
158158

159159
- **How can I load PDBs from a specific or shared location or server?**
160160

161161
Configure your Symbol Servers from Debug > Options > Symbols.
162-
See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md)
162+
See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md).
163163

164164
- **How can I never load a specific PDB? Or, how can I always load one?**
165165

166166
Configure your Include and Exclude Lists in Debug > Options > Symbols.
167-
See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md)
167+
See [Specify symbol](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md).
168168

169169
- question: |
170170
Configure debugging
@@ -184,12 +184,12 @@ sections:
184184
- **Do I need to save a dump?**
185185
186186
While stopped at an error or breakpoint during debugging, select **Debug > Save Dump As**.
187-
See [Dump files](using-dump-files.md)
187+
See [Dump files](using-dump-files.md).
188188
189189
- **How do I analyze a dump file?**
190190
191191
Open the dump by choosing **File > Open** in Visual Studio. To start debugging, select **Debug with Managed Only**, **Debug with Native Only**, **Debug with Mixed**, or **Debug with Managed Memory**.
192-
See [Dump files](using-dump-files.md)
192+
See [Dump files](using-dump-files.md).
193193
194194
- **Can I edit code during a debugging session?**
195195
@@ -201,7 +201,7 @@ sections:
201201
202202
- **How can I fix performance issues?**
203203
204-
See [First look at the profiling tools](../profiling/profiling-feature-tour.md)
204+
See [First look at the profiling tools](../profiling/profiling-feature-tour.md).
205205
206206
- **How do I fix an exception?**
207207

0 commit comments

Comments
 (0)