Refresh Debugging content (#8058)

ntrogh · web-flow · commit 8c6217ebf136 · 2025-02-21T12:42:27.000+01:00
* Refresh Debugging article and split off debug configuration

* Edit pass
diff --git a/build/sitemap.xml b/build/sitemap.xml
@@ -235,6 +235,11 @@
         <changefreq>weekly</changefreq>
         <priority>0.8</priority>
     </url>
+    <url>
+        <loc>https://code.visualstudio.com/docs/editor/debugging-configuration</loc>
+        <changefreq>weekly</changefreq>
+        <priority>0.8</priority>
+    </url>
     <url>
         <loc>https://code.visualstudio.com/docs/editor/testing</loc>
         <changefreq>weekly</changefreq>
diff --git a/docs/containers/debug-common.md b/docs/containers/debug-common.md
@@ -127,7 +127,7 @@ Example `launch.json` configuration for debugging a .NET application using `Dock
 
 ### node object properties
 
-> These properties are the same as those described in the [VS Code documentation](/docs/nodejs/nodejs-debugging.md#launch-configuration-attributes) for attaching a debugger to Node.js applications. All properties passed in the `node` object will be passed on to the Node.js debug adaptor, even if not specifically listed below.
+> These properties are the same as those described in the [VS Code documentation](/docs/nodejs/nodejs-debugging-configuration.md#launch-configuration-attributes) for attaching a debugger to Node.js applications. All properties passed in the `node` object will be passed on to the Node.js debug adaptor, even if not specifically listed below.
 
 | Property | Description | Default |
 | --- | --- | --- |
diff --git a/docs/containers/docker-compose.md b/docs/containers/docker-compose.md
@@ -53,7 +53,7 @@ First, refer to the debugging documentation for your target platform, to underst
 
 If you want to debug in Docker Compose, run the command **Docker Compose Up** using one of the two Docker Compose files as described in the previous section, and then attach using the appropriate **Attach** launch configuration. Launching directly using the normal launch configuration does not use Docker Compose.
 
-Create an **Attach** [launch configuration](/docs/editor/debugging.md#launch-configurations). This is a section in `launch.json`. The process is mostly manual, but in some cases, the Docker extension can help by adding a pre-configured launch configuration that you can use as a template and customize. The process for each platform (Node.js, Python, and .NET) is described in the following sections.
+Create an **Attach** [launch configuration](/docs/editor/debugging-configuration.md#launch-configurations). This is a section in `launch.json`. The process is mostly manual, but in some cases, the Docker extension can help by adding a pre-configured launch configuration that you can use as a template and customize. The process for each platform (Node.js, Python, and .NET) is described in the following sections.
 
 ### Node.js
 
diff --git a/docs/editor/debugging-configuration.md b/docs/editor/debugging-configuration.md
diff --git a/docs/editor/debugging.md b/docs/editor/debugging.md
diff --git a/docs/editor/images/debugging/debug-start.png b/docs/editor/images/debugging/debug-start.png
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:401e40fca1a123bd8fc244116c0f50b7b0d2065ab27028f10b5f54e80e2c8f06
-size 21783
+oid sha256:4031d4829a1f74312cf414724a24c9409cf88467027b03f2833b2653d30dd184
+size 19469
diff --git a/docs/editor/images/debugging/launch-configuration-dropdown.png b/docs/editor/images/debugging/launch-configuration-dropdown.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:503a45295482a89cbb95e96f983ccc9f861589cdcfdc62ed24a666df9286ec1e
+size 160060
diff --git a/docs/editor/images/debugging/launch-json-intellisense.png b/docs/editor/images/debugging/launch-json-intellisense.png
diff --git a/docs/java/java-debugging.md b/docs/java/java-debugging.md
@@ -52,7 +52,7 @@ If you would like to customize and persist your launch configuration, you can se
 
 The `launch.json` file is located in a `.vscode` folder in your workspace (project root folder).
 
-For more details on how to create the `launch.json`, read [Launch configurations](/docs/editor/debugging.md#launch-configurations); for more details on configuration options for Java, you can read [Configuration options](/docs/java/java-debugging.md#configuration-options).
+For more details on how to create the `launch.json`, read [Launch configurations](/docs/editor/debugging-configuration.md#launch-configurations); for more details on configuration options for Java, you can read [Configuration options](/docs/java/java-debugging.md#configuration-options).
 
 ## Run and Debug
 
diff --git a/docs/java/java-spring-apps.md b/docs/java/java-spring-apps.md
@@ -59,7 +59,7 @@ Once you have the Extension Pack for Java installed, it will automatically build
 
 ![debug configuration in the Status bar](images/java-webapp/debugging-status-bar.png)
 
-You can learn more about how VS Code launches your application in Debugging [Launch Configurations](/docs/editor/debugging.md#launch-configurations). Press `kb(workbench.action.debug.start)` again to launch the debugger.
+You can learn more about how VS Code launches your application in Debugging [Launch Configurations](/docs/editor/debugging-configuration.md#launch-configurations). Press `kb(workbench.action.debug.start)` again to launch the debugger.
 
 ![Run Spring Boot](images/java-webapp/run-spring-boot.gif)
 
diff --git a/docs/languages/ruby.md b/docs/languages/ruby.md
@@ -156,7 +156,7 @@ in a new terminal or launch the debugger. For these uses, no configuration is re
 
 ### Debugging through launch tasks
 
-To use the debugger through launch tasks, you will need to create [debugging configurations](/docs/editor/debugging.md#launch-configurations)
+To use the debugger through launch tasks, you will need to create [debugging configurations](/docs/editor/debugging-configuration.md#launch-configurations)
 in a `launch.json` file. The configuration lets you configure the program to be executed.
 
 To create a `launch.json` for a Ruby program:
diff --git a/docs/nodejs/browser-debugging.md b/docs/nodejs/browser-debugging.md
@@ -100,7 +100,7 @@ Now, you can press `kb(workbench.action.debug.start)` or the **Start** button in
 
 ### Launch configuration attributes
 
-Debugging configurations are stored in a `launch.json` file located in your workspace's `.vscode` folder. An introduction into the creation and use of debugging configuration files is in the general [Debugging](/docs/editor/debugging.md#launch-configurations) article. You can either "launch" a browser with your application, or "attach" to an existing browser that you [started in debug mode](#attaching-to-browsers).
+Debugging configurations are stored in a `launch.json` file located in your workspace's `.vscode` folder. An introduction into the creation and use of debugging configuration files is in the general [Debugging](/docs/editor/debugging-configuration.md#launch-configurations) article. You can either "launch" a browser with your application, or "attach" to an existing browser that you [started in debug mode](#attaching-to-browsers).
 
 Below is a reference of common `launch.json` attributes specific to browser debugging. You can view the complete set of options in the [vscode-js-debug options](https://github.com/microsoft/vscode-js-debug/blob/main/OPTIONS.md) documentation.
 
diff --git a/docs/nodejs/nodejs-debugging.md b/docs/nodejs/nodejs-debugging.md
@@ -102,7 +102,7 @@ If you'd like to watch an introductory video, see [Getting started with debuggin
 
 ## Launch configuration attributes
 
-Debugging configurations are stored in a `launch.json` file located in your workspace's `.vscode` folder. An introduction into the creation and use of debugging configuration files is in the general [Debugging](/docs/editor/debugging.md#launch-configurations) article.
+Debugging configurations are stored in a `launch.json` file located in your workspace's `.vscode` folder. An introduction into the creation and use of debugging configuration files is in the general [Debugging](/docs/editor/debugging-configuration.md#launch-configurations) article.
 
 Below is a reference of common `launch.json` attributes specific to the Node.js debugger. You can view the complete set of options in the [vscode-js-debug options](https://github.com/microsoft/vscode-js-debug/blob/main/OPTIONS.md) documentation.
 
@@ -123,7 +123,7 @@ These attributes are only available for launch configurations of request type `l
 * `program` - an absolute path to the Node.js program to debug.
 * `args` - arguments passed to the program to debug. This attribute is of type array and expects individual arguments as array elements.
 * `cwd` - launch the program to debug in this directory.
-* `runtimeExecutable` - absolute path to the runtime executable to be used. Default is `node`. See section [Launch configuration support for 'npm' and other tools](/docs/nodejs/nodejs-debugging.md#launch-configuration-support-for-npm-and-other-tools).
+* `runtimeExecutable` - absolute path to the runtime executable to be used. Default is `node`. See section [Launch configuration support for 'npm' and other tools](/docs/nodejs/nodejs-debugging-configuration.md#launch-configuration-support-for-npm-and-other-tools).
 * `runtimeArgs` - optional arguments passed to the runtime executable.
 * `runtimeVersion` - if "[nvm](https://github.com/creationix/nvm)" (or "[nvm-windows](https://github.com/coreybutler/nvm-windows)") or "[nvs](https://github.com/jasongin/nvs)" is used for managing Node.js versions, this attribute can be used to select a specific version of Node.js. See section [Multi version support](/docs/nodejs/nodejs-debugging.md#multi-version-support) below.
 * `env` - optional environment variables. This attribute expects environment variables as a list of string typed key/value pairs.
diff --git a/docs/python/debugging.md b/docs/python/debugging.md
@@ -450,7 +450,7 @@ Allows for the automatic reload of the debugger when changes are made to code af
 
 ### `subProcess`
 
-Specifies whether to enable subprocess debugging. Defaults to `false`, set to `true` to enable. For more information, see [multi-target debugging](/docs/editor/debugging.md#multitarget-debugging).
+Specifies whether to enable subprocess debugging. Defaults to `false`, set to `true` to enable. For more information, see [multi-target debugging](/docs/editor/debugging.md#multi-target-debugging).
 
 ### `cwd`
 
diff --git a/docs/toc.json b/docs/toc.json
@@ -38,6 +38,7 @@
         ["Code Navigation", "/docs/editor/editingevolved"],
         ["Refactoring", "/docs/editor/refactoring"],
         ["Debugging", "/docs/editor/debugging"],
+        ["Debug Configuration", "/docs/editor/debugging-configuration"],
         ["Testing", "/docs/editor/testing"],
         ["VS Code for the Web", "/docs/editor/vscode-web"],
         ["Keyboard Shortcuts", "/docs/editor/keybindings"],
