From ce2a50880b576d583f8f3c39db57d677c848d5f7 Mon Sep 17 00:00:00 2001
From: tiruka <33803972+tiruka@users.noreply.github.com>
Date: Mon, 2 Sep 2024 05:37:56 +0900
Subject: [PATCH] fixed the debugger settings doc (#2223)

---
 .../src/getting-started/configuring-your-editor.md  | 13 ++-----------
 1 file changed, 2 insertions(+), 11 deletions(-)

diff --git a/contributor-book/src/getting-started/configuring-your-editor.md b/contributor-book/src/getting-started/configuring-your-editor.md
index d255e1cde..ab3a6eea1 100644
--- a/contributor-book/src/getting-started/configuring-your-editor.md
+++ b/contributor-book/src/getting-started/configuring-your-editor.md
@@ -23,17 +23,8 @@ To use the debugger, follow these steps:
 1. Open `Command Palette` with `Ctrl+Shift+P` or `F1` and type
    `LLDB: Generate Launch Configurations from Cargo.toml` then select it, this will generate a file
    that should be saved as `.vscode/launch.json`.
-2. Select the configuration from the "run and debug" side panel, then select the target from the
-   list.
-   You may also want to enable debugging by creating a `.vscode/settings.json` file:
-    ```
-    {
-      "rust-analyzer.runnables.extraEnv": {
-        "CARGO_PROFILE_DEV_DEBUG": true
-      }
-    }
-    ```
-    since this repo has `debug = 0` in the root `Cargo.toml` to speed up compilation.
+2. Select the configuration from the "run and debug" side panel, then select the target from the list.
+   Since this repo has `debug = 0` in the root `Cargo.toml` to speed up compilation, you need replace it with `debug = true` in the root `Cargo.toml` when using a debugger and breakpoints with `launch.json` settings.
 3. Now you can enable breakpoints on code through IDE then start debugging the library/binary you
    want, like in the following example: