Debugger: Attach with pid input or pick from processes

[wxitcode]

Like this one in VSCode

vadimcn/codelldb#169 (comment)

input

[
  {
      "label": "attach pid",
      "request": "attach",
      "adapter": "CodeLLDB",
      "pid": "${input:pickPid}"
  }
]

"inputs": [
    {
      "id": "pickPid",
      "type": "promptString",
      "description": "Enter process id"
    }
  ]

pick

[
  {
      "label": "attach pid",
      "request": "attach",
      "adapter": "CodeLLDB",
      "pid": "${command:pickMyProcess}"
  }
]

[JaagupAverin]

What IS the current intended approach for picking the PID?
The documentation is a bit vague with it. Surely it is not to modify the debug.json file every time the executable is started?

[wxitcode]

Currently, there is no available support. The debug.json file must be modified each time.

[Anthony-Eid]

We have an attach picker you can use to make the process more streamlined

[Anthony-Eid]

@wxitcode Would you be happy with something that's like this?

"label": "attach pid",
"request": "attach",
"adapter": "CodeLLDB",
"pid": "$PickProcessId"

[wxitcode]

@Anthony-Eid Yes, in addition to popping up a selection for choosing the local process to attach for debugging, it would be helpful to also support manual input of the process ID. There are two use cases: one is entering a local process ID for local debugging, and the other is entering a remote process ID for remote debugging.

[Anthony-Eid]

Sounds good, thankfully we already have an attach process modal that works with both local and remote debugging 😀. So connecting it to the raw configuration shouldn't be too difficult

[Anthony-Eid]

@wxitcode Merging #42913 later today, that should fix your issue.

[wxitcode]

@wxitcode Merging #42913 later today, that should fix your issue.

Thank you. This is really good news. I can't wait to try it.