Merge pull request #9261 from Mikejo5000/mikejo-br16

PRMerger-2 · web-flow · commit 0fe334f1dae9 · 2021-12-22T11:18:03.000-08:00
SEO and edits for article on specifying symbol files in the debugger
diff --git a/docs/debugger/how-to-use-the-modules-window.md b/docs/debugger/how-to-use-the-modules-window.md
@@ -55,7 +55,7 @@ The **Symbol Status** column in the **Modules** window shows which modules have
 
 1. If the symbols don't load, select **Symbol Settings** to open the **Options** dialog, and specify or change symbol loading locations.
 
-   You can download symbols from the public Microsoft Symbol Servers or other servers, or load symbols from a folder on your computer. For details, see [Specify symbol locations and loading behavior](../debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md#BKMK_Specify_symbol_locations_and_loading_behavior).
+   You can download symbols from the public Microsoft Symbol Servers or other servers, or load symbols from a folder on your computer. For details, see [Configure location of symbol files and loading behavior](../debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md#configure-location-of-symbol-files-and-loading-options).
 
 **To change symbol loading behavior settings:**
 
diff --git a/docs/debugger/navigating-through-code-with-the-debugger.md b/docs/debugger/navigating-through-code-with-the-debugger.md
@@ -185,7 +185,7 @@ To look at framework code, third-party library code, or system calls while debug
 
 If you've loaded debugging symbols for Microsoft system code and disabled Just My Code, you can step into a system call just as you can any other call.
 
-To learn about loading Microsoft symbols, see [Configure symbol locations and loading options](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md#configure-symbol-locations-and-loading-options).
+To learn about loading Microsoft symbols, see [Configure location of symbol files and loading options](specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md#configure-location-of-symbol-files-and-loading-options).
 
 **To load symbols for a specific system component**
 
diff --git a/docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md b/docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md
@@ -34,14 +34,16 @@ ms.workload:
 
 Program database (*.pdb*) files, also called symbol files, map identifiers and statements in your project's source code to corresponding identifiers and instructions in compiled apps. These mapping files link the debugger to your source code, which enables debugging.
 
-When you build a project from the Visual Studio IDE with the standard Debug build configuration, the compiler creates the appropriate symbol files. This article describes how to manage symbol files in the IDE, for example, how to [specify the location of symbols in the debugger options](#BKMK_Specify_symbol_locations_and_loading_behavior), how to [check symbol loading status](#work-with-symbols-in-the-modules-window) while debugging, and how to [set symbol options in code](#compiler-symbol-options).
+When you build a project from the Visual Studio IDE with the standard Debug build configuration, the compiler creates the appropriate symbol files. This article describes how to manage symbol files in the IDE, for example:
+
+- [Configure the location of symbol files](#configure-location-of-symbol-files-and-loading-options)
+- [Load symbols while debugging](#load-symbols-while-debugging)
+- [Compiler options for symbols](#compiler-symbol-options).
 
 For a detailed explanation of symbol files, see the following:
 
 - [Understand symbol files and Visual Studio symbol settings](https://devblogs.microsoft.com/devops/understanding-symbol-files-and-visual-studios-symbol-settings/)
 
-- [Why does Visual Studio require debugger symbol files to exactly match the binary files that they were built with?](/archive/blogs/jimgries/why-does-visual-studio-require-debugger-symbol-files-to-exactly-match-the-binary-files-that-they-were-built-with)
-
 ## How symbol files work
 
 The *.pdb* file holds debugging and project state information that allows incremental linking of a Debug configuration of your app. The Visual Studio debugger uses *.pdb* files to determine two key pieces of information while debugging:
@@ -51,27 +53,29 @@ The *.pdb* file holds debugging and project state information that allows increm
 
 Symbol files also show the location of the source files, and optionally, the server to retrieve them from.
 
-The debugger only loads *.pdb* files that exactly match the *.pdb* files created when an app was built (that is, the original *.pdb* files or copies). This [exact duplication](/archive/blogs/jimgries/why-does-visual-studio-require-debugger-symbol-files-to-exactly-match-the-binary-files-that-they-were-built-with) is necessary because the layout of apps can change even if the code itself has not changed.
+The debugger only loads *.pdb* files that exactly match the *.pdb* files created when an app was built (that is, the original *.pdb* files or copies). This exact duplication is necessary because the layout of apps can change even if the code itself has not changed. For more information, see [Why does Visual Studio require debugger symbol files to exactly match the binary files that they were built with?](/archive/blogs/jimgries/why-does-visual-studio-require-debugger-symbol-files-to-exactly-match-the-binary-files-that-they-were-built-with)
 
 > [!TIP]
 > To debug code outside your project source code, such as Windows code or third-party code your project calls, you must specify the location of the external code's *.pdb* files (and optionally, the source files), which must exactly match the builds in your app.
 
-## Symbol file locations and loading behavior
+## Where the debugger looks for symbols
 
-When you debug a project in the Visual Studio IDE, the debugger automatically loads symbol files that are located in the project folder.
+When you debug a project in the Visual Studio IDE, the debugger automatically loads symbol files that it can find by default.
 
 > [!NOTE]
-> When debugging managed code on a remote device, all symbol files must be located either on the local machine, or in a location [specified in the debugger options](#BKMK_Specify_symbol_locations_and_loading_behavior).
+> When debugging managed code on a remote device, all symbol files must be located either on the local machine, or in a location [specified in the debugger options](#configure-location-of-symbol-files-and-loading-options).
+
+The debugger searches for symbol files in the following locations:
 
-The debugger also searches for symbol files in the following locations:
+1. The project folder.
 
 1. The location that is specified inside the DLL or the executable (*.exe*) file.
 
    By default, if you have built a DLL or an *.exe* file on your computer, the linker places the full path and filename of the associated *.pdb* file in the DLL or *.exe* file. The debugger checks to see if the symbol file exists in that location.
 
-2. The same folder as the DLL or *.exe* file.
+1. The same folder as the DLL or *.exe* file.
 
-3. Any locations specified in the debugger options for symbol files. To add and enable symbol locations, see [Configure symbol locations and loading options](#BKMK_Specify_symbol_locations_and_loading_behavior).
+1. Any locations specified in the debugger options for symbol files. To add and enable symbol locations, see [Configure symbol locations and loading options](#configure-location-of-symbol-files-and-loading-options).
 
    - Any local symbol cache folder.
 
@@ -88,14 +92,16 @@ The debugger also searches for symbol files in the following locations:
      > [!WARNING]
      > If you use a symbol server other than the public Microsoft Symbol Servers, make sure that the symbol server and its path are trustworthy. Because symbol files can contain arbitrary executable code, you can be exposed to security threats.
 
-<a name="BKMK_Specify_symbol_locations_and_loading_behavior"></a>
-### Configure symbol locations and loading options
+## Configure location of symbol files and loading options
+
+The debugger checks various locations for symbols by default. See [Where the debugger looks for symbols](#where-the-debugger-looks-for-symbols).
 
 On the **Tools** > **Options** > **Debugging** > **Symbols** page, you can:
 
-- Specify and select search paths and symbol servers for Microsoft, Windows, or third-party components.
+- Specify and select search paths for symbol files.
+- Specify symbol servers for Microsoft, Windows, or third-party components.
 - Specify modules that you do or don't want the debugger to automatically load symbols for.
-- Change these settings while you are actively debugging. See [Manage symbols while debugging](#manage-symbols-while-debugging).
+- Change these settings while you are actively debugging. See [Load symbols while debugging](#load-symbols-while-debugging).
 
 **To specify symbol locations and loading options:**
 
@@ -155,7 +161,7 @@ You can select additional symbol options in **Tools** > **Options** > **Debuggin
   Always shows the disassembly when source or symbol files are not found.
 
   ![Options &#47; Debugging  &#47; General disassembly options](../debugger/media/dbg-options-general-disassembly-checkbox.png "Options &#47; Debugging  &#47; General disassembly options")
-  <a name="BKMK_Use_symbol_servers_to_find_symbol_files_not_on_your_local_machine"></a>
+
 - **Enable source server support**
 
   Uses Source Server to help debug an app when there is no source code on the local machine, or the *.pdb* file does not match the source code. Source Server takes requests for files and returns the actual files from source control. Source Server runs by using a DLL named *srcsrv.dll* to read the app's *.pdb* file. The *.pdb* file contains pointers to the source code repository, as well as commands used to retrieve source code from the repository.
@@ -175,6 +181,8 @@ You can select additional symbol options in **Tools** > **Options** > **Debuggin
 
 When you build a project from the Visual Studio IDE with the standard **Debug** build configuration, the C++ and managed compilers create the appropriate symbol files for your code. You can also set compiler options in code.
 
+To set the compiler options for your build configurations in Visual Studio, see [Set debug and release configurations](../debugger/how-to-set-debug-and-release-configurations.md).
+
 ### .NET options
 
 Build with **/debug** to create a *.pdb* file. You can build applications with **/debug:full** or **/debug:pdbonly**. Building with **/debug:full** generates debuggable code. Building with **/debug:pdbonly** generates *.pdb* files, but does not generate the `DebuggableAttribute` that tells the JIT compiler that debug information is available. Use **/debug:pdbonly** if you want to generate *.pdb* files for a release build that you do not want to be debuggable. For more information, see [/debug (C# compiler options)](/dotnet/csharp/language-reference/compiler-options/debug-compiler-option) or [/debug (Visual Basic)](/dotnet/visual-basic/reference/command-line-compiler/debug).
@@ -207,7 +215,7 @@ Build with **/debug** to create a *.pdb* file. You can build applications with *
 
 Set the *web.config* file of your ASP.NET application to debug mode. Debug mode causes ASP.NET to generate symbols for dynamically generated files and enables the debugger to attach to the ASP.NET application. Visual Studio sets this automatically when you start to debug, if you created your project from the web projects template.
 
-## Manage symbols while debugging
+## Load symbols while debugging
 
 You can use the **Modules**, **Call Stack**, **Locals**, **Autos**, or any **Watch** window to load symbols or change symbol options while debugging. For more information, see [Get more familiar with how the debugger attaches to your app](../debugger/debugger-tips-and-tricks.md#modules_window).
 
