Merge pull request MicrosoftDocs#5087 from MicrosoftDocs/main

10/27/2023 AM Publish

Author: PhilKang0704

docs/_breadcrumb/toc.yml

@@ -1,129 +1,3 @@
-items: 
-- name: Docs
-  tocHref: /
-  topicHref: /
-  items:
-  - name: Microsoft C++, C, and Assembler
-    tocHref: /cpp/
-    topicHref: /cpp/index
-    items:
-    - name: Compiler intrinsics and assembly language
-      tocHref: /cpp/intrinsics/
-      topicHref: /cpp/intrinsics/index
-      items:
-      - name: Compiler intrinsics
-        tocHref: /cpp/intrinsics/
-        topicHref: /cpp/intrinsics/compiler-intrinsics
-      - name: ARM and ARM64 assembler
-        tocHref: /cpp/assembler/arm/
-        topicHref: /cpp/assembler/arm/arm-assembler-reference
-      - name: C/C++ x86 inline assembler
-        tocHref: /cpp/assembler/inline/
-        topicHref: /cpp/assembler/inline/inline-assembler
-      - name: x86 and x64 assembler
-        tocHref: /cpp/assembler/masm/
-        topicHref: /cpp/assembler/masm/microsoft-macro-assembler-reference
-    - name: ATL
-      tocHref: /cpp/atl/
-      topicHref: /cpp/atl/atl-com-desktop-components
-    - name: ATL/MFC shared classes
-      tocHref: /cpp/atl-mfc-shared/
-      topicHref: /cpp/atl-mfc-shared/atl-mfc-shared-classes
-      items:
-      - name: ATL/MFC reference
-        tocHref: /cpp/atl-mfc-shared/reference/
-        topicHref: /cpp/atl-mfc-shared/reference/classes-shared-by-mfc-and-atl
-    - name: Build C/C++ projects
-      tocHref: /cpp/build/
-      topicHref: /cpp/build/building-c-cpp-programs
-      items:
-      - name: Build reference
-        tocHref: /cpp/build/reference/
-        topicHref: /cpp/build/reference/c-cpp-building-reference
-    - name: Build insights
-      tocHref: /cpp/build-insights/
-      topicHref: /cpp/build-insights/index
-    - name: C language
-      tocHref: /cpp/c-language/
-      topicHref: /cpp/c-language/index
-    - name: C runtime library
-      tocHref: /cpp/c-runtime-library/
-      topicHref: /cpp/c-runtime-library/c-run-time-library-reference
-      items:
-      - name: UCRT reference
-        tocHref: /cpp/c-runtime-library/reference/
-        topicHref: /cpp/c-runtime-library/reference/crt-alphabetical-function-reference
-    - name: Cloud and web
-      tocHref: /cpp/cloud/
-      topicHref: /cpp/cloud/cloud-and-web-programming-in-visual-cpp
-    - name: Code analysis
-      tocHref: /cpp/code-quality/
-      topicHref: /cpp/code-quality/index
-    - name: Code sanitizers
-      tocHref: /cpp/sanitizers/
-      topicHref: /cpp/sanitizers/index
-    - name: C++ language
-      tocHref: /cpp/cpp/
-      topicHref: /cpp/cpp/index
-    - name: C++/CX
-      tocHref: /cpp/cppcx/
-      topicHref: /cpp/cppcx/visual-c-language-reference-c-cx
-    - name: Cross-platform mobile development
-      tocHref: /cpp/cross-platform/
-      topicHref: /cpp/cross-platform/index
-    - name: Data access
-      tocHref: /cpp/data/
-      topicHref: /cpp/data/data-access-in-cpp
-      items:
-      - name: OLEDB
-        tocHref: /cpp/data/oledb/
-        topicHref: /cpp/data/oledb/ole-db-programming
-      - name: ODBC
-        tocHref: /cpp/data/odbc/
-        topicHref: /cpp/data/odbc/open-database-connectivity-odbc
-    - name: C++/CLI for .NET
-      tocHref: /cpp/dotnet/
-      topicHref: /cpp/dotnet/dotnet-programming-with-cpp-cli-visual-cpp
-    - name: Errors and warnings
-      tocHref: /cpp/error-messages/
-      topicHref: /cpp/error-messages/compiler-errors-1/c-cpp-build-errors
-    - name: Edit, navigate, and refactor code
-      tocHref: /cpp/ide/
-      topicHref: /cpp/ide/read-and-understand-code-cpp
-    - name: Linux
-      tocHref: /cpp/linux/
-      topicHref: /cpp/linux/index
-    - name: Linux
-      tocHref: /cpp/build/configure-cmake-debugging-sessions
-      topicHref: /cpp/linux/index
-    - name: MFC
-      tocHref: /cpp/mfc/
-      topicHref: /cpp/mfc/mfc-desktop-applications
-      items:
-      - name: MFC reference
-        tocHref: /cpp/mfc/reference/
-        topicHref: /cpp/mfc/reference/mfc-classes
-    - name: Microsoft C/C++
-      tocHref: /cpp/overview/
-      topicHref: /cpp/overview/visual-cpp-in-visual-studio
-    - name: Parallel programming
-      tocHref: /cpp/parallel/
-      topicHref: /cpp/parallel/parallel-programming-in-visual-cpp
-    - name: Porting and upgrading
-      tocHref: /cpp/porting/
-      topicHref: /cpp/porting/visual-cpp-porting-and-upgrading-guide
-    - name: C/C++ preprocessor
-      tocHref: /cpp/preprocessor/
-      topicHref: /cpp/preprocessor/c-cpp-preprocessor-reference
-    - name: Security
-      tocHref: /cpp/security/
-      topicHref: /cpp/security/security-best-practices-for-cpp
-    - name: C++ standard library
-      tocHref: /cpp/standard-library/
-      topicHref: /cpp/standard-library/cpp-standard-library-reference 
-    - name: Text and strings
-      tocHref: /cpp/text/
-      topicHref: /cpp/text/text-and-strings-in-visual-cpp
-    - name: Windows
-      tocHref: /cpp/windows/
-      topicHref: /cpp/windows/overview-of-windows-programming-in-cpp
+- name: C++, C, and Assembler
+  tocHref: /cpp/
+  topicHref: /cpp/index

docs/build/configure-cmake-debugging-sessions.md

@@ -1,7 +1,7 @@
 ---
 title: "Configure CMake debugging sessions in Visual Studio"
 description: "Describes how to use Visual Studio to configure CMake debugger settings."
-ms.date: 12/16/2020
+ms.date: 10/26/2023
 helpviewer_keywords: ["CMake debugging"]
 ---
 # Configure CMake debugging sessions
@@ -16,26 +16,26 @@ Native CMake support is available in Visual Studio 2017 and later. To see the do
 
 All executable CMake targets are shown in the **Startup Item** dropdown in the toolbar. Select one to start a debugging session and launch the debugger.
 
-:::image type="complex" source="media/new-dropdowns.png" alt-text="Screenshot of the CMake startup items.":::
-There is a play button dropdown to select the current debug target. It shows your debug targets. In this example, the HelloWorld.exe debug target is available.
+:::image type="complex" source="media/new-dropdowns.png" alt-text="Screenshot of the CMake startup items dropdown.":::
+The dropdown provides a list of debug targets to choose from. The selected item appears as a play button followed by the name of the selected debug target to run. In this example, the selected debug target is Hello World .exe.
 :::image-end:::
 
 You can also start a debug session from Solution Explorer. First, switch to **CMake Targets View** in the **Solution Explorer** window.
 
-:::image type="complex" source="media/switch-to-targets-view.png" alt-text="Screenshot of the CMake Targets View menu":::
-The solution explorer is shown. A right-click on an item in the Folder View has opened a menu. On that menu, the Switch to Targets View item is highlighted.
+:::image type="complex" source="media/switch-to-targets-view.png" alt-text="Screenshot of the CMake Targets View menu.":::
+The solution explorer is shown. A right-click on an item in the Folder View has opened a menu that shows options such as Open, Open with, Compare with, and so on. The Switch to Targets View menu item is highlighted.
 :::image-end:::
 
 Then, right-click on an executable and select **Debug**. This command automatically starts debugging the selected target based on your active configuration.
 
 :::image type="complex" source="media/debug-targets-view.png" alt-text="Screenshot of the CMake Targets View debug option menu.":::
-When you right-click on a target in the CMake Targets view, there is an option to debug a chosen target. The Debug option is highlighted.
+A right-click on a target in the CMake Targets view has opened a menu with options such as Set as Startup item, Build, Clean All, and so on. The Debug menu option is highlighted.
 :::image-end:::
 
 Starting in Visual Studio 2022 Version 17.6, you can also start a debugging session on your CMakeLists.txt file. To do so, just set a breakpoint in your CMakeLists.txt file and run **Configure Project with CMake Debugger** from the **Project** dropdown.
 
 :::image type="complex" source="media/cmake-debugger-entry.png" alt-text="Screenshot of the CMake Debugger dropdown.":::
-The Project dropdown is shown. The option to Configure Project with CMake debugger is highlighted.
+The Project dropdown is shown. The menu option to Configure Project with CMake debugger is highlighted.
 :::image-end:::
 
 ## Customize debugger settings

docs/build/reference/debug-generate-debug-info.md

@@ -1,7 +1,7 @@
 ---
 description: "Learn more about: /DEBUG (Generate debug info)"
 title: "/DEBUG (Generate Debug Info)"
-ms.date: 12/05/2022
+ms.date: 10/26/2023
 f1_keywords: ["VC.Project.VCLinkerTool.GenerateDebugInformation", "/debug"]
 helpviewer_keywords: ["DEBUG linker option", "/DEBUG linker option", "-DEBUG linker option", "PDB files", "debugging [C++], debug information files", "generate debug info linker option", "pdb files, generating debug info", ".pdb files, generating debug info", "debugging [C++], linker option", "program databases [C++]"]
 ms.assetid: 1af389ae-3f8b-4d76-a087-1cdf861e9103
@@ -20,15 +20,15 @@ The **`/DEBUG`** option puts the debugging information from linked object and li
 
 An executable (an EXE or DLL file) created for debugging contains the name and path of the corresponding PDB. The debugger reads the embedded name and uses the PDB when you debug the program. The linker uses the base name of the program and the extension *`.pdb`* to name the program database, and embeds the path where it was created. To override this default, set the [`/PDB`](pdb-use-program-database.md) option and specify a different file name.
 
-The **`/DEBUG:FASTLINK`** option is available in Visual Studio 2017 and later. This option generates a limited PDB that indexes into the debug information in the object files and libraries used to build the executable instead of making a full copy. You can only use this limited PDB to debug from the computer where the binary and its libraries were built. If you deploy the binary elsewhere, you may debug it remotely from the build computer, but not directly on the test computer. In Visual Studio 2017, this option can sometimes greatly improve link times compared with **`/DEBUG:FULL`**. In Visual Studio 2019 and later, **`/DEBUG:FULL`** is faster than in earlier versions. Now, **`/DEBUG:FASTLINK`** isn't always faster than **`/DEBUG:FULL`**, and it's rarely more than twice as fast.
+The **`/DEBUG:FASTLINK`** option is available in Visual Studio 2017 and later. This option generates a limited PDB that indexes into the debug information in the object files and libraries used to build the executable instead of making a full copy. You can only use this limited PDB to debug from the computer where the binary and its libraries were built. If you deploy the binary elsewhere, you may debug it remotely from the build computer, but not directly on the test computer. Despite its name, **`/DEBUG:FASTLINK`** is generally slower than **`/DEBUG:FULL`**, so this option is not recommended.
 
 A **`/DEBUG:FASTLINK`** PDB can be converted to a full PDB that you can deploy to a test machine for local debugging. In Visual Studio, use the **Property Pages** dialog as described below to create a full PDB for the project or solution. In a developer command prompt, you can use the `mspdbcmf.exe` tool to create a full PDB.
 
 The **`/DEBUG:FULL`** option moves all private symbol information from individual compilation products (object files and libraries) into a single PDB, and can be the most time-consuming part of the link. However, the full PDB can be used to debug the executable when no other build products are available, such as when the executable is deployed.
 
 The **`/DEBUG:NONE`** option doesn't generate a PDB.
 
-In Visual Studio 2015 and earlier versions, when you specify **`/DEBUG`** with no extra arguments, the linker defaults to **`/DEBUG:FULL`** for command line and makefile builds, for release builds in the Visual Studio IDE, and for both debug and release builds. Beginning in Visual Studio 2017, the build system in the IDE defaults to **`/DEBUG:FASTLINK`** when you specify the **`/DEBUG`** option for debug builds. Other defaults are unchanged to maintain backward compatibility.
+Specifying **`/DEBUG`** with no extra arguments is equivalent to specifying **`/DEBUG:FULL`**.
 
 The compiler's [`/Z7`](z7-zi-zi-debug-information-format.md) (C7 Compatible) option causes the compiler to leave the debugging information in the object (OBJ) files. You can also use the [`/Zi`](z7-zi-zi-debug-information-format.md) (Program Database) compiler option to store the debugging information in a PDB for the OBJ file. The linker looks for the object's PDB first in the absolute path written in the OBJ file, and then in the directory that contains the OBJ file. You can't specify an object's PDB file name or location to the linker.
 

docs/docfx.json

@@ -38,7 +38,6 @@
     "externalReference": [],
     "globalMetadata": {
       "breadcrumb_path": "~/_breadcrumb/toc.yml",
-      "extendBreadcrumb": "true",
       "uhfHeaderId": "MSDocsHeader-CPP",
       "ROBOTS": "INDEX,FOLLOW",
       "manager": "markl",