Unable to start debugging after Run Without Debugging

[OlafvdSpek]

Issue Type: Bug

Trying to run a toy example on Debian using clang++.

"miDebuggerPath": "/usr/bin/lldb-mi"

/usr/bin/lldb-mi indeed doesn't exist (what pkg do I need to install?), but a debugger shouldn't be necessary to just run something.

VS Code version: Code 1.64.2 (f80445acd5a3dadef24aa209168452a3d97cc326, 2022-02-09T22:02:28.252Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
Remote OS version: Linux x64 5.16.0-1-amd64

System Info

Item	Value
CPUs	Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz (4 x 2946)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	7.99GB (1.50GB free)
Process Argv	--crash-reporter-id 4bd850b3-a2f9-42c9-8c89-3a102309506b
Screen Reader	no
VM	0%

Item	Value
Remote	SSH: debian
OS	Linux x64 5.16.0-1-amd64
CPUs	Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz (2 x 2945)
Memory (System)	1.89GB (0.11GB free)
VM	100%

Extensions (16)

Extension	Author (truncated)	Version
better-cpp-syntax	jef	1.15.13
jupyter-keymap	ms-	1.0.0
remote-containers	ms-	0.217.4
remote-ssh	ms-	0.70.0
remote-ssh-edit	ms-	0.70.0
remote-wsl	ms-	0.64.2
doxdocgen	csc	1.3.2
EditorConfig	Edi	0.16.4
better-cpp-syntax	jef	1.15.13
python	ms-	2022.0.1814523869
vscode-pylance	ms-	2022.2.1
jupyter	ms-	2022.1.1201831736
cmake-tools	ms-	1.9.2
cpptools	ms-	1.8.4
cpptools-extension-pack	ms-	1.1.0
cmake	twx	0.0.17

(2 theme extensions excluded)

A/B Experiments

vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30425749
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30436985
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30433059
pythonvs932:30410667
wslgetstarted:30433507
vsclayoutctrc:30437038
vsrem710cf:30416617
vsbas813:30436447
vscscmwlcmc:30436992
cppdebug:30437093

{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    
    {
      "name": "clang++ - Build and debug active file",
      "type": "cppdbg",
      "request": "launch",
      "program": "${fileDirname}/${fileBasenameNoExtension}",
      "args": [],
      "stopAtEntry": false,
      "cwd": "${fileDirname}",
      "environment": [],
      "externalConsole": false,
      "MIMode": "lldb",
      "setupCommands": [
        {
          "description": "Enable pretty-printing for gdb",
          "text": "-enable-pretty-printing",
          "ignoreFailures": true
        }
      ],
      "preLaunchTask": "C/C++: clang++ build active file",
      "miDebuggerPath": "/usr/bin/lldb-mi"
    }
  ]
}

Originally reported @ microsoft/vscode#142961

[bobbrow]

@WardenGnaw the getting started doc for macOS doesn't set the miDebuggerPath. Does the debugger code take care of lldb-mi for this case, or do they need to install something?

[bobbrow]

And a note from the VS Code debugger folks:

@bobbrow the noDebug argument of the launch request tells the debug adapter whether debugging is actually desired or whether this is a "run without debugging" case. See https://microsoft.github.io/debug-adapter-protocol/specification#Requests_Launch

[WardenGnaw]

@WardenGnaw the getting started doc for macOS doesn't set the miDebuggerPath. Does the debugger code take care of lldb-mi for this case, or do they need to install something?

Only for macOS. On Linux, they will need to build lldb-mi themselves.

And a note from the VS Code debugger folks:

@bobbrow the noDebug argument of the launch request tells the debug adapter whether debugging is actually desired or whether this is a "run without debugging" case. See https://microsoft.github.io/debug-adapter-protocol/specification#Requests_Launch

At the moment, cppdbg does not support noDebug. As MIEngine supports launching processes remotely and connecting to gdbserver, there is work to be done to launch a process without debug and being able to stop it.

Related: #5680