The plugin is a capable, if basic, debugger for c++ and python on the author's computer. I think the concept is well and truly proven and it is worth completing.
If you are insanely curious and wish to try it out, it's probably best to find me in #vim or the YCM gitter channel. It's probably too early.
In order to use it you have to currently:
- Write an undocumented configuration file that contains essentially undocumented parameters.
- Use an undocumented API via things like
:call vimsepctor#Launch(). - etc.
The motivation is that debugging in Vim is a pretty horrible experience, particularly if you use multiple languages. With pyclewn no more and the built-in termdebug plugin limited to gdb, I wanted to explore options.
While Language Server Protocol is well known, the Debug Adapter Protocol is less well known, but achieves a similar goal: language agnostic API abstracting debuggers from clients.
The aim of this project is to provide a simple but effective debugging experience in Vim for multiple languages, by leveraging the debug adapters that are being built for Visual Studio Code.
The ability to do remote debugging is a must. This is key to my workflow, so baking it in to the debugging experience is a top bill goal for the project.
Please note the entire UI is placeholder. These are just proofs-of-concept.
- Create
vimspector.json. See below. :call vimsepctor#Launch()and select a configuration.
- Use
vimspector#ToggleBreakpoint()to set/disable/delete a line breakpoint. - Use
vimspector#AddFunctionBreakpoint( '<name>' )to add a function breakpoint.
- Step in/out, finish, continue, pause etc. using the WinBar.
- If you really want to, the API is
vimspector#StepInto()etc.
- Current scope shows values of locals.
- Use
<CR>to expand/collapse (+, -). - When changing the stack frame the locals window updates.
- While paused, hover to see values
- Add watches to the variables window with
:call vimspector#AddWatch( '<expr>' ) - Expand result with
<CR>. - Delete with
<DEL>.
- In the threads window, use
<CR>to expand/collapse. - Use
<CR>on a stack frame to jump to it.
- In the outputs window use the WinBar to select the output channel.
- The debugee prints to the stdout channel.
- Other channels may be useful for debugging.
Current tested with the following debug adapters.
Note, there is no support for installing the extension. Use VSCode to do that by
installing it in the UI. The default extension directory is something like
$HOME/.vscode/extensions.
Note, the launch configurations below are reverse-engineered from the
extensions. Typically they are documented in the extension's package.json, but
not always (or not completely).
- C++: vscode-cpptools
{
"adapters": {
"cppdbg": {
"name": "cppdbg",
"command": [ "<path to extension>/debugAdapters/OpenDebugAD7" ],
"attach": {
"pidProperty": "processId",
"pidSelect": "ask"
}
},
....
},
"configurations": {
"<name>: Launch": {
"adapter": "cppdbg",
"configuration": {
"name": "<name>",
"type": "cppdbg",
"request": "launch",
"program": "<path to binary>",
"args": [ ... ],
"cwd": "<working directory>",
"environment": [ ... ],
"externalConsole": true,
"MIMode": "lldb"
}
},
"<name>: Attach": {
"adapter": "cppdbg",
"configuration": {
"name": "<name>: Attach",
"type": "cppdbg",
"request": "attach",
"program": "<path to binary>",
"MIMode": "lldb"
}
}
...
}
}
- C++: code=debug
{
"adapters": {
"lldb-mi": {
"name": "lldb-mi",
"command": [
"node",
"<path to extension>/out/src/lldb.js"
],
"attach": {
"pidProperty": "target",
"pidSelect": "ask"
}
}
...
},
"configurations": {
"<name>: Launch": {
"adapter": "lldb-mi",
"configuration": {
"request": "attach",
"cwd": "<working directory>",
"program": "<path to binary>",
"args": [ ... ],
"environment": [ ... ],
"lldbmipath": "<path to a working lldb-mi>"
}
},
"<name>: Attach": {
"adapter": "lldb-mi",
"configuration": {
"request": "attach",
"cwd": "<working directory>",
"executable": "<path to binary>",
"lldbmipath": "<path to a working lldb-mi>"
}
}
...
}
}
- C, C++, Rust, etc.: CodeLLDB
{
"adapters": {
"lldb": {
"name": "lldb",
"command": [
"lldb",
"-b",
"-O",
"command script import '<extension path>/adapter'",
"-O",
"script adapter.main.run_stdio_session()"
]
}
...
},
"configurations": {
"<name>: Launch": {
"adapter": "lldb",
"configuration": {
"type": "lldb",
"request": "launch",
"name": "<name>: Launch",
"program": "<path to binary>",
"args": [ .. ],
"cwd": "<working directory>"
}
}
}
}
- Python: vscode-python
{
"adapters": {
"python": {
"name": "python",
"command": [
"node",
"<path to extension>/out/client/debugger/Main.js"
]
}
...
},
"configurations": {
"<name>: Launch": {
"adapter": "python",
"configuration": {
"name": "<name>: Launch",
"type": "python",
"request": "launch",
"cwd": "<working directory>",
"stopOnEntry": true,
"console": "externalTerminal",
"debugOptions": [],
"program": "<path to main python file>"
}
}
...
}
}
Also the mock debugger, but that isn't actually useful.
Known not to work:
- Java Debug Server. This doesn't work (yet) because it runs as a jdt.ls plugin. Support for this may be added in conjunction with ycmd, but this architecture is incredibly complex and vastly different from any other.
- C-sharp. The license appears to require that it is only used with Visual Studio Code.
Currently on the author's environment which is macOS.
The plugin might work on other UNIX-like environments but it hasn't been tested. It will almost certainly not work on Windows.
Requires:
- Vim 8.1 compiled with python 3 support.
- Q: Does it work? A: Yeah, sort of. It's incredibly buggy and unpolished.
- Q: Does it work with ? A: Probably, but it won't
necessarily be easy to work out what to put in the
.vimspector.json. As you can see above, some of the servers aren't really editor agnostic, and require very-specific unique handling.
Copyright © 2018 Ben Jackson