Skip to content

Conversation

@da-viper
Copy link
Contributor

We have always supported it but it was undocumented. It shows a warning unknown key when added in vscode attach configuration.

We have always supported it but it was undocumented.
It shows a warning unknown key when added in vscode attach
configuration.
@llvmbot
Copy link
Member

llvmbot commented Dec 18, 2025

@llvm/pr-subscribers-lldb

Author: Ebuka Ezike (da-viper)

Changes

We have always supported it but it was undocumented. It shows a warning unknown key when added in vscode attach configuration.


Full diff: https://github.com/llvm/llvm-project/pull/172927.diff

2 Files Affected:

  • (modified) lldb/tools/lldb-dap/README.md (+1)
  • (modified) lldb/tools/lldb-dap/package.json (+5)
diff --git a/lldb/tools/lldb-dap/README.md b/lldb/tools/lldb-dap/README.md
index e83384f89bc1f..7aa59ef1b7252 100644
--- a/lldb/tools/lldb-dap/README.md
+++ b/lldb/tools/lldb-dap/README.md
@@ -276,6 +276,7 @@ the following `lldb-dap` specific key/value pairs:
 | **program**                       | string      |     | Path to the executable to attach to. This value is optional but can help to resolve breakpoints prior the attaching to the program.
 | **pid**                           | number      |     | The process id of the process you wish to attach to. If **pid** is omitted, the debugger will attempt to attach to the program by finding a process whose file name matches the file name from **program**. Setting this value to `${command:pickMyProcess}` will allow interactive process selection in the IDE.
 | **waitFor**                       | boolean     |     | Wait for the process to launch.
+| **stopOnEntry**                   | boolean     |     | Whether to stop program immediately after attaching.
 | **attachCommands**                | [string]    |     | LLDB commands that will be executed after **preRunCommands** which take place of the code that normally does the attach. The commands can create a new target and attach or launch it however desired. This allows custom launch and attach configurations. Core files can use `target create --core /path/to/core` to attach to core files.
 
 ### Configuring `lldb-dap` defaults
diff --git a/lldb/tools/lldb-dap/package.json b/lldb/tools/lldb-dap/package.json
index 75d86f74a95d0..9d058fb4fd957 100644
--- a/lldb/tools/lldb-dap/package.json
+++ b/lldb/tools/lldb-dap/package.json
@@ -727,6 +727,11 @@
                 "description": "If set to true, then wait for the process to launch by looking for a process with a basename that matches `program`. No process ID needs to be specified when using this flag.",
                 "default": true
               },
+              "stopOnEntry": {
+                "type": "boolean",
+                "description": "Automatically stop after attach.",
+                "default": false
+              },
               "sourcePath": {
                 "type": "string",
                 "description": "Specify a source path to remap \"./\" to allow full paths to be used when setting breakpoints in binaries that have relative source paths."

@da-viper da-viper merged commit d07f237 into llvm:main Dec 19, 2025
13 checks passed
mahesh-attarde pushed a commit to mahesh-attarde/llvm-project that referenced this pull request Dec 19, 2025
We have always supported it but it was undocumented. It shows a warning
unknown key when added in vscode attach configuration.
@da-viper da-viper deleted the document-attach-stop-on-entry branch December 22, 2025 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants