Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/puremourning/vimspector
vimspector - A multi-language debugging system for Vim
https://github.com/puremourning/vimspector
cpp debug-adapter-protocol debugger debugging java python tcl vim
Last synced: about 2 months ago
JSON representation
vimspector - A multi-language debugging system for Vim
- Host: GitHub
- URL: https://github.com/puremourning/vimspector
- Owner: puremourning
- License: apache-2.0
- Created: 2018-05-20T14:19:41.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2024-07-24T19:56:09.000Z (about 2 months ago)
- Last Synced: 2024-07-24T22:45:05.920Z (about 2 months ago)
- Topics: cpp, debug-adapter-protocol, debugger, debugging, java, python, tcl, vim
- Language: Vim Script
- Homepage: http://puremourning.github.io/vimspector-web
- Size: 5.31 MB
- Stars: 4,051
- Watchers: 38
- Forks: 169
- Open Issues: 31
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- Code of conduct: CODE_OF_CONDUCT.md
- Support: support/bin/testecho
Awesome Lists containing this project
README
# vimspector - A multi language graphical debugger for Vim
For a tutorial and usage overview, take a look at the
[Vimspector website][website].
For detailed explanation of the `.vimspector.json` format, see the
[reference guide][vimspector-ref].
[](https://github.com/puremourning/vimspector/actions/workflows/build.yaml) [](https://matrix.to/#/#vimspector_Lobby:gitter.im) [](https://gitter.im/vimspector/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
* [Features and Usage](#features-and-usage)
* [Supported debugging features](#supported-debugging-features)
* [Supported languages](#supported-languages)
* [Other languages](#other-languages)
* [Installation](#installation)
* [Quick Start](#quick-start)
* [Method 1: Using a repo clone, Vim packages and select gadgets to be installed](#method-2-using-a-repo-clone-vim-packages-and-select-gadgets-to-be-installed)
* [Method 2: Using a plugin manager](#method-3-using-a-plugin-manager)
* [Dependencies](#dependencies)
* [Neovim limitations](#neovim-limitations)
* [Windows differences](#windows-differences)
* [Trying it out](#trying-it-out)
* [Cloning the plugin](#cloning-the-plugin)
* [Install some gadgets](#install-some-gadgets)
* [VimspectorInstall and VimspectorUpdate commands](#vimspectorinstall-and-vimspectorupdate-commands)
* [install_gadget.py](#install_gadgetpy)
* [Manual gadget installation](#manual-gadget-installation)
* [The gadget directory](#the-gadget-directory)
* [Upgrade](#upgrade)
* [About](#about)
* [Background](#background)
* [What Vimspector is not](#what-vimspector-is-not)
* [Status](#status)
* [Experimental](#experimental)
* [Motivation](#motivation)
* [License](#license)
* [Sponsorship](#sponsorship)
* [Mappings](#mappings)
* [Visual Studio / VSCode](#visual-studio--vscode)
* [Human Mode](#human-mode)
* [Usage and API](#usage-and-api)
* [Launch and attach by PID:](#launch-and-attach-by-pid)
* [Picking a PID](#picking-a-pid)
* [Launch with options](#launch-with-options)
* [Debug configuration selection](#debug-configuration-selection)
* [Get configurations](#get-configurations)
* [Breakpoints](#breakpoints)
* [Breakpoints Window](#breakpoints-window)
* [Line breakpoints](#line-breakpoints)
* [Conditional breakpoints and logpoints](#conditional-breakpoints-and-logpoints)
* [Exception breakpoints](#exception-breakpoints)
* [API Summary](#api-summary)
* [Instruction breakpoints](#instruction-breakpoints)
* [Clear breakpoints](#clear-breakpoints)
* [Run to Cursor](#run-to-cursor)
* [Go to current line](#go-to-current-line)
* [Save and restore](#save-and-restore)
* [Stepping](#stepping)
* [Variables and scopes](#variables-and-scopes)
* [Variable or selection hover evaluation](#variable-or-selection-hover-evaluation)
* [Watches](#watches)
* [Watch autocompletion](#watch-autocompletion)
* [Disassembly](#disassembly)
* [Dump memory](#dump-memory)
* [Stack Traces](#stack-traces)
* [Child sessions](#child-sessions)
* [Program Output](#program-output)
* [Console](#console)
* [Console autocompletion](#console-autocompletion)
* [Log View](#log-view)
* [Closing debugger](#closing-debugger)
* [Terminate debuggee](#terminate-debuggee)
* [Multiple debugging sessions](#multiple-debugging-sessions)
* [Debug profile configuration](#debug-profile-configuration)
* [C, C , Rust, etc.](#c-c-rust-etc)
* [Data visualization / pretty printing](#data-visualization--pretty-printing)
* [C Remote debugging](#c-remote-debugging)
* [C Remote launch and attach](#c-remote-launch-and-attach)
* [Rust](#rust)
* [Jai](#jai)
* [Python](#python)
* [Python Remote Debugging](#python-remote-debugging)
* [Python Remote launch and attach](#python-remote-launch-and-attach)
* [Python 2](#python-2)
* [TCL](#tcl)
* [C♯](#c)
* [Go](#go)
* [PHP](#php)
* [Debug web application](#debug-web-application)
* [Debug cli application](#debug-cli-application)
* [JavaScript and TypeScript](#javascript-and-typescript)
* [Java](#java)
* [Hot code replace](#hot-code-replace)
* [Usage with YouCompleteMe](#usage-with-youcompleteme)
* [Other LSP clients](#other-lsp-clients)
* [Lua](#lua)
* [Other servers](#other-servers)
* [Customisation](#customisation)
* [Changing the default signs](#changing-the-default-signs)
* [Sign priority](#sign-priority)
* [Presentation Hints](#presentation-hints)
* [Changing the default window sizes](#changing-the-default-window-sizes)
* [Changing the terminal size](#changing-the-terminal-size)
* [Custom mappings while debugging](#custom-mappings-while-debugging)
* [Pre-launch building strategies](#pre-launch-building-strategies)
* [Disabling the WinBar](#disabling-the-winbar)
* [Advanced UI customisation](#advanced-ui-customisation)
* [Customising the WinBar](#customising-the-winbar)
* [Example](#example)
* [FAQ](#faq)
# Features and Usage
The plugin is a capable Vim graphical debugger for multiple languages.
It's mostly tested for C++, Python and TCL, but in theory supports any
language that Visual Studio Code supports (but see caveats).
The [Vimspector website][website] has an overview of the UI, along with basic
instructions for configuration and setup.
But for now, here's a (rather old) screenshot of Vimspector debugging Vim:
And a couple of brief demos:
[](https://asciinema.org/a/VmptWmFHTNLPfK3DVsrR2bv8S)
[](https://asciinema.org/a/1wZJSoCgs3AvjkhKwetJOJhDh)
## Supported debugging features
- flexible configuration syntax that can be checked in to source control
- breakpoints (function, line and exception breakpoints)
- conditional breakpoints (function, line)
- step in/out/over/up, stop, restart
- run to cursor
- go to line (reset program counter to line)
- launch and attach, including PID picker
- remote launch, remote attach
- locals and globals display
- watch expressions with autocompletion
- variable inspection tooltip on hover
- disassembly view and step-by-instruction
- set variable value in locals, watch and hover windows
- call stack display and navigation
- hierarchical variable value display popup (see `VimspectorBalloonEval`)
- interactive debug console with autocompletion
- launch debuggee within Vim's embedded terminal
- logging/stdout display
- simple stable API for custom tooling (e.g. integrate with language server)
- view hex dump of process memory
- multiple independent debugging sessions (debug different apps in tabs)
- multi-process (multi-session) debugging
## Supported languages
The following table lists the languages that are "built-in" (along with their
runtime dependencies). They are categorised by their level of support:
* `Tested` : Fully supported, Vimspector regression tests cover them
* `Supported` : Fully supported, frequently used and manually tested
* `Experimental`: Working, but not frequently used and rarely tested
* `Legacy`: No longer supported, please migrate your config
* `Retired`: No longer included or supported.
| Language(s) | Status | Switch (for `install_gadget.py`) | Adapter (for `:VimspectorInstall`) | Dependencies |
| -------------------- | ----------- | ---------------------------------- | ------------------------------------ | -------------------------------------------- |
| C, C++, Rust, Jai, etc. | Tested | `--all` or `--enable-c` (or cpp) | vscode-cpptools | mono-core |
| C, C++, Rust, Jai, etc. | Tested | `--enable-rust`, `--enable-c`, etc. | CodeLLDB | none |
| Python | Tested | `--all` or `--enable-python` | debugpy | Python 3 |
| Go | Tested | `--enable-go` | delve | Go 1.16+ |
| TCL | Supported | `--all` or `--enable-tcl` | tclpro | TCL 8.5 |
| Bourne Shell | Supported | `--all` or `--enable-bash` | vscode-bash-debug | Bash v?? |
| Lua | Tested | `--all` or `--enable-lua` | local-lua-debugger-vscode | Node >=12.13.0, Npm, Lua interpreter |
| Node.js | Supported | `--force-enable-node` | vscode-js-debug | Node >= 18 |
| Node.js (legacy) | Supported | `--force-enable-node_legacy` | vscode-node-debug2 | 6 < Node < 12, Npm |
| Javascript | Supported | `--force-enable-chrome` | debugger-for-chrome | Chrome |
| Javascript | Supported | `--force-enable-firefox` | vscode-firefox-debug | Firefox |
| Java | Supported | `--force-enable-java ` | vscode-java-debug | Compatible LSP plugin (see [later](#java)) |
| PHP | Experimental | `--force-enable-php` | vscode-php-debug | Node, PHP, XDEBUG |
| C# (dotnet core) | Tested | `--force-enable-csharp` | netcoredbg | DotNet core |
| F#, VB, etc. | Supported | `--force-enable-[fsharp,vbnet]` | netcoredbg | DotNet core |
| Go (legacy) | Legacy | `--enable-go` | vscode-go | Node, Go, [Delve][] |
| Python 2 | Legacy | `--force-enable-python2` | debugpy-python2 | Python 2.7 |
## Other languages
Vimspector should work for any debug adapter that works in Visual Studio Code.
To use Vimspector with a language that's not "built-in", see this
[wiki page](https://github.com/puremourning/vimspector/wiki/Additional-Language-Support).
# Installation
## Quick Start
There are 2 installation methods:
* Using a repo clone and Vim packages
* Using a plugin manager
### Method 1: Using a repo clone, Vim packages and select gadgets to be installed
1. [Check the dependencies](#dependencies)
1. Install the plugin as a Vim package. See `:help packages`.
2. Add `packadd! vimspector` to your `.vimrc`
2. Install some 'gadgets' (debug adapters) - see [here for installation commands](#install-some-gadgets) and [select gadgets to install](#supported-languages)
3. Configure your project's debug profiles (create `.vimspector.json`, or set
`g:vimspector_configurations`) - see the [reference guide][vimspector-ref]
### Method 2: Using a plugin manager
1. [Check the dependencies](#dependencies)
1. See the plugin manager's docs and install the plugin
For Vundle, use:
```vim
Plugin 'puremourning/vimspector'
```
2. Install some 'gadgets' (debug adapters) - see [here for installation commands](#install-some-gadgets) and [select gadgets to install](#supported-languages)
3. Configure your project's debug profiles (create `.vimspector.json`, or set
`g:vimspector_configurations`) - see the [reference guide][vimspector-ref]
The following sections expand on the above brief overview.
## Dependencies
Vimspector requires:
* One of:
* Vim 8.2.4797 or later "huge" build compiled with Python 3.10 or later
* Neovim 0.8 with Python 3.10 or later
* One of the following operating systems:
* Linux
* macOS Mojave or later
* Windows (experimental)
Which Linux versions? I only test on Ubuntu 20.04 and later and RHEL 7.
### Neovim limitations
neovim doesn't implement mouse hover balloons. Instead there is the
`VimspectorBalloonEval` mapping. There is no default mapping for this, so
I recommend something like this to get variable display in a popup:
```viml
" mnemonic 'di' = 'debug inspect' (pick your own, if you prefer!)
" for normal mode - the word under the cursor
nmap di VimspectorBalloonEval
" for visual mode, the visually selected text
xmap di VimspectorBalloonEval
```
### Windows differences
The following features are not implemented for Windows:
* Tailing the vimspector log in the Output Window.
## Trying it out
If you just want to try out vimspector without changing your vim config, there
are example projects for a number of languages in `support/test`, including:
* Python ([support/test/python/simple_python](support/test/python/simple_python))
* Go ([support/test/go/hello_world](support/test/go/hello_world) and [support/test/go/name-starts-with-vowel](support/test/go/name-starts-with-vowel))
* Nodejs ([support/test/node/simple](support/test/node/simple))
* Chrome/Firefox ([support/test/web](support/test/web))
* etc.
To test one of these out, cd to the directory and run:
```
vim -Nu /path/to/vimspector/tests/vimrc --cmd "let g:vimspector_enable_mappings='HUMAN'"
```
Then press ``.
There's also a C++ project in `tests/testdata/cpp/simple/` with a `Makefile`
which can be used to check everything is working. This is used by the regression
tests in CI so should always work, and is a good way to check if the problem is
your configuration rather than a bug.
## Installing the plugin
1. Clone the plugin
There are many Vim plugin managers, and I'm not going to state a particular
preference, so if you choose to use one, follow the plugin manager's
documentation. For example, for Vundle, use:
```viml
Plugin 'puremourning/vimspector'
```
If you don't use a plugin manager already, install vimspector as a Vim package
by cloning this repository into your package path, like this:
```
$ git clone https://github.com/puremourning/vimspector ~/.vim/pack/vimspector/opt/vimspector
```
2. Configure vimspector in your `.vimrc`, for example to enable the standard
mappings:
```viml
let g:vimspector_enable_mappings = 'HUMAN'
```
3. Load vimspector at runtime. This can also be added to your `.vimrc` after
configuring vimspector:
```
packadd! vimspector
```
See `support/doc/example_vimrc.vim` for a minimal example.
## Install some gadgets
Vimspector is a generic client for Debug Adapters. Debug Adapters (referred to
as 'gadgets' or 'adapters') are what actually do the work of talking to the real
debuggers.
In order for Vimspector to be useful, you need to have some adapters installed.
There are a few ways to do this:
* Using `:VimspectorInstall ` (use TAB `wildmenu` to see the
options, also accepts any `install_gadget.py` option)
* Using `python3 install_gadget.py ` (use `--help` to see all options)
* Attempting to launch a debug configuration; if the configured adapter
can't be found, vimspector will suggest installing one.
* Using `:VimspectorUpdate` to install the latest supported versions of the
gadgets.
Here's a demo of doing some installs and an upgrade:
[](https://asciinema.org/a/Hfu4ZvuyTZun8THNen9FQbTay)
Both `install_gadget.py` and `:VimspectorInstall` do the same set of things,
though the default behaviours are slightly different. For supported languages,
they will:
* Download the relevant debug adapter at a version that's been tested from the
internet, either as a 'vsix' (Visusal Studio plugin), or clone from GitHub. If
you're in a corporate environment and this is a problem, you may need to
install the gadgets manually.
* Perform any necessary post-installation actions, such as:
* Building any binary components
* Ensuring scripts are executable, because the VSIX packages are usually
broken in this regard.
* Set up the `gadgetDir` symlinks for the platform.
For example, to install the tested debug adapter for a language, run:
| To install | Script | Command |
| --- | --- | --- |
| `` | | `:VimspectorInstall ` |
| ``, ``, ... | | `:VimspectorInstall ...` |
| `` | `./install_gadget.py --enable- ...` | `:VimspectorInstall --enable- ...` |
| Supported adapters | `./install_gadget.py --all` | `:VimspectorInstall --all` |
| Supported adapters, but not TCL | `./install_gadget.py --all --disable-tcl` | `:VimspectorInstall --all --disable-tcl` |
| Supported and experimental adapters | `./install_gadget.py --all --force-all` | `:VimspectorInstall --all` |
| Adapter for specific debug config | | Suggested by Vimspector when starting debugging |
### VimspectorInstall and VimspectorUpdate commands
`:VimspectorInstall` runs `install_gadget.py` in the background with some of
the options defaulted.
`:VimspectorUpdate` runs `install_gadget.py` to re-install (i.e. update) any
gadgets already installed in your `.gadgets.json`.
The output is minimal, to see the full output add `--verbose` to the command, as
in `:VimspectorInstall --verbose ...` or `:VimspectorUpdate --verbose ...`.
If the installation is successful, the output window is closed (and the output
lost forever). Use a `!` to keep it open (e.g. `:VimspectorInstall! --verbose
--all` or `:VimspectorUpdate!` (etc.).
If you know in advance which gadgets you want to install, for example so that
you can reproduce your config from source control, you can set
`g:vimspector_install_gadgets` to a list of gadgets. This will be used when:
* Running `:VimspectorInstall` with no arguments, or
* Running `:VimspectorUpdate`
For example:
```viml
let g:vimspector_install_gadgets = [ 'debugpy', 'vscode-cpptools', 'CodeLLDB' ]
```
### install\_gadget.py
By default `install_gadget.py` will overwrite your `.gadgets.json` with the set
of adapters just installed, whereas `:VimspectorInstall` will _update_ it,
overwriting only newly changed or installed adapters.
If you want to just add a new adapter using the script without destroying the
existing ones, add `--update-gadget-config`, as in:
```bash
$ ./install_gadget.py --enable-tcl
$ ./install_gadget.py --enable-rust --update-gadget-config
$ ./install_gadget.py --enable-java --update-gadget-config
```
If you want to maintain `configurations` outside of the vimspector repository
(this can be useful if you have custom gadgets or global configurations),
you can tell the installer to use a different basedir, then set
`g:vimspector_base_dir` to point to that directory, for example:
```bash
$ ./install_gadget.py --basedir $HOME/.vim/vimspector-config --all --force-all
```
Then add this to your `.vimrc`:
```viml
let g:vimspector_base_dir=expand( '$HOME/.vim/vimspector-config' )
```
When using `:VimspectorInstall`, the `g:vimspector_base_dir` setting is
respected unless `--basedir` is manually added (not recommended).
See `--help` for more info on the various options.
## Manual gadget installation
If the language you want to debug is not in the supported list above, you can
probably still make it work, but it's more effort.
You essentially need to get a working installation of the debug adapter, find
out how to start it, and configure that in an `adapters` entry in either your
`.vimspector.json` or in `.gadgets.json` or in `g:vimspector_adapters`.
The simplest way in practice is to install or start Visual Studio Code and use
its extension manager to install the relevant extension. You can then configure
the adapter manually in the `adapters` section of your `.vimspector.json` or in
a `gadgets.json` or in `g:vimspector_adapters`.
PRs are always welcome to add supported languages (which roughly translates to
updating `python/vimspector/gadgets.py` and testing it).
### The gadget directory
Vimspector uses the following directory by default to look for a file named
`.gadgets.json`: `/gadgets/`.
This path is exposed as the vimspector _variable_ `${gadgetDir}`. This is useful
for configuring gadget command lines.
Where os is one of:
* `macos`
* `linux`
* `windows` (though note: Windows is not supported)
The format is the same as `.vimspector.json`, but only the `adapters` key is
used:
Example:
```json
{
"adapters": {
"lldb-vscode": {
"variables": {
"LLVM": {
"shell": "brew --prefix llvm"
}
},
"attach": {
"pidProperty": "pid",
"pidSelect": "ask"
},
"command": [
"${LLVM}/bin/lldb-vscode"
],
"env": {
"LLDB_LAUNCH_FLAG_LAUNCH_IN_TTY": "YES"
},
"name": "lldb"
},
"vscode-cpptools": {
"attach": {
"pidProperty": "processId",
"pidSelect": "ask"
},
"command": [
"${gadgetDir}/vscode-cpptools/debugAdapters/bin/OpenDebugAD7"
],
"name": "cppdbg"
}
}
}
```
The gadget file is automatically written by `install_gadget.py` (or
`:VimspectorInstall`).
Vimspector will also load any files matching:
`/gadgets//.gadgets.d/*.json`. These have the same
format as `.gadgets.json` but are not overwritten when running
`install_gadget.py`.
## Upgrade
After updating the Vimspector code (either via `git pull` or whatever package
manager), run `:VimspectorUpdate` to update any already-installed gadgets.
# About
## Background
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. So
vimspector has first-class support for executing programs remotely and attaching
to them. This support is unique to vimspector and on top of (complementary to)
any such support in actual debug adapters.
# What Vimspector is not
Vimspector is a vim UI on top of the Debug Adapter Protocol. It's intended to be high level and convenient for day-to-day debugging tasks.
Vimspector is not:
* a debugger! It's just the UI and some glue.
* fast. It's abstractions all the way down. If you want a fast, native debugger,
there are other options.
* comprehensive. It's limited by DAP, and limited by my time. I implement the
features I think most users will need, not every feature possible.
* for everyone. Vimspector intentionally provides a "one size fits all" UI and
aproach. This means that it can only provide essential/basic debugging
features for a given language. This makes it convenient for everyday usage,
but not ideal for power users or those with very precise or specific
requirements. See [motivation](#motivation) for more info.
## Status
Vimspector is a work in progress, and any feedback/contributions are more
than welcome.
The backlog can be [viewed on Trello](https://trello.com/b/yvAKK0rD/vimspector).
### Experimental
The plugin is currently _experimental_. That means that any part of it
can (and probably will) change, including things like:
- breaking changes to the configuration
- keys, layout, functionality of the UI
However, I commit to only doing this in the most extreme cases and to announce
such changes on Gitter well in advance. There's nothing more annoying than stuff
just breaking on you. I get that.
## Motivation
A message from the author about the motivation for this plugin:
> Many development environments have a built-in debugger. I spend an inordinate
> amount of my time in Vim. I do all my development in Vim and I have even
> customised my workflows for building code, running tests etc.
>
> For many years I have observed myself, friends and colleagues have been
> writing `printf`, `puts`, `print`, etc. debugging statements in all sorts of
> files simply because there is no _easy_ way to run a debugger for _whatever_
> language we happen to be developing in.
>
> I truly believe that interactive, graphical debugging environments are the
> best way to understand and reason about both unfamiliar and familiar code, and
> that the lack of ready, simple access to a debugger is a huge hidden
> productivity hole for many.
>
> Don't get me wrong, I know there are literally millions of developers out
> there that are more than competent at developing without a graphical debugger,
> but I maintain that if they had the ability to _just press a key_ and jump
> into the debugger, it would be faster and more enjoyable that just cerebral
> code comprehension.
>
> I created Vimspector because I find changing tools frustrating. `gdb` for c++,
> `pdb` for python, etc. Each has its own syntax. Each its own lexicon. Each its
> own foibles.
>
> I designed the configuration system in such a way that the configuration can
> be committed to source control so that it _just works_ for any of your
> colleagues, friends, collaborators or complete strangers.
>
> I made remote debugging a first-class feature because that's a primary use
> case for me in my job.
>
> With Vimspector I can _just hit ``_ in all of the languages I develop in
> and debug locally or remotely using the exact same workflow, mappings and UI.
> I have integrated this with my Vim in such a way that I can hit a button and
> _run the test under the cursor in Vimspector_. This kind of integration has
> massively improved my workflow and productivity. It's even made the process
> of learning a new codebase... fun.
>
> \- Ben Jackson, Creator.
## License
[Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0)
Copyright © 2018 Ben Jackson
## Sponsorship
If you like Vimspector so much that you're wiling to part with your hard-earned
cash, please consider donating to one of the following charities, which are
meaningful to the author of Vimspector (in order of preference):
* [Hector's Greyhound Rescue](http://hectorsgreyhoundrescue.org)
* [Cancer Research UK](https://www.cancerresearchuk.org)
* [ICCF Holland](https://iccf.nl)
* Any charity of your choosing.
# Mappings
By default, vimspector does not change any of your mappings. Mappings are very
personal and so you should work out what you like and use vim's powerful mapping
features to set your own mappings. To that end, Vimspector defines the following
`` mappings:
| Mapping | Function | API |
| --- | --- | --- |
| `VimspectorContinue` | When debugging, continue. Otherwise start debugging. | `vimspector#Continue()` |
| `VimspectorStop` | Stop debugging. | `vimspector#Stop()` |
| `VimpectorRestart` | Restart debugging with the same configuration. | `vimspector#Restart()` |
| `VimspectorPause` | Pause debuggee. | `vimspector#Pause()` |
| `VimspectorBreakpoints` | Show/hide the breakpoints window | `vimspector#ListBreakpoints()` |
| `VimspectorToggleBreakpoint` | Toggle line breakpoint on the current line. | `vimspector#ToggleBreakpoint()` |
| `VimspectorToggleConditionalBreakpoint` | Toggle conditional line breakpoint or logpoint on the current line. | `vimspector#ToggleBreakpoint( { trigger expr, hit count expr } )` |
| `VimspectorAddFunctionBreakpoint` | Add a function breakpoint for the expression under cursor | `vimspector#AddFunctionBreakpoint( '' )` |
| `VimspectorGoToCurrentLine` | Reset the current program counter to the current line | `vimspector#GoToCurrentLine()` |
| `VimspectorRunToCursor` | Run to Cursor | `vimspector#RunToCursor()` |
| `VimspectorStepOver` | Step Over | `vimspector#StepOver()` |
| `VimspectorStepInto` | Step Into | `vimspector#StepInto()` |
| `VimspectorStepOut` | Step out of current function scope | `vimspector#StepOut()` |
| `VimspectorDisassemble` | Show disassembly. Enable instruction stepping | `vimspector#ShowDisassembly()` |
| `VimspectorUpFrame` | Move up a frame in the current call stack | `vimspector#UpFrame()` |
| `VimspectorDownFrame` | Move down a frame in the current call stack | `vimspector#DownFrame()` |
| `VimspectorJumpToNextBreakpoint` | Move Cursor to the next breakpoint in current file | `vimspector#JumpToNextBreakpoint()` |
| `VimspectorJumpToPreviousBreakpoint` | Move Cursor to the previous breakpoint in current file | `vimspector#JumpToPreviousBreakpoint()` |
| `VimspectorJumpToProgramCounter` | Move Cursor to the program counter in the current frame | `vimspector#JumpToProgramCounter()` |
| `VimspectorBalloonEval` | Evaluate expression under cursor (or visual) in popup | *internal* |
These map roughly 1-1 with the API functions below.
For example, if you want `` to start/continue debugging, add this to some
appropriate place, such as your `vimrc` (hint: run `:e $MYVIMRC`).
```viml
nmap VimspectorContinue
```
In addition, many users probably want to only enable certain Vimspector mappings
while debugging is active. This is also possible, though it requires writing
[some vimscipt](#custom-mappings-while-debugging).
That said, many people are familiar with particular debuggers, so the following
mappings can be enabled by setting `g:vimspector_enable_mappings` to the
specified value.
## Visual Studio / VSCode
To use Visual Studio-like mappings, add the following to your `vimrc` **before
loading vimspector**:
```viml
let g:vimspector_enable_mappings = 'VISUAL_STUDIO'
```
| Key | Mapping | Function
| --- | --- | ---
| `F5` | `VimspectorContinue` | When debugging, continue. Otherwise start debugging.
| `Shift F5` | `VimspectorStop` | Stop debugging.
| `Ctrl Shift F5` | `VimspectorRestart` | Restart debugging with the same configuration.
| `F6` | `VimspectorPause` | Pause debuggee.
| `F8` | `VimspectorJumpToNextBreakpoint` | Jump to next breakpoint in the current file.
| `Shift F8` | `VimspectorJumpToPreviousBreakpoint` | Jump to previous breakpoint in the current file.
| `F9` | `VimspectorToggleBreakpoint` | Toggle line breakpoint on the current line.
| `Shift F9` | `VimspectorAddFunctionBreakpoint` | Add a function breakpoint for the expression under cursor
| `F10` | `VimspectorStepOver` | Step Over
| `Ctrl F10` | `VimspectorRunToCursor` | Run to cursor*
| `F11` | `VimspectorStepInto` | Step Into
| `Shift F11` | `VimspectorStepOut` | Step out of current function scope
| `Alt 8` | `VimspectorDisassemble` | Show disassembly
***NOTE: Some mappings, such as ctrl and F-keys may not work depending on your
terminal, keyboard, windowing system and all sorts of other things.
See `:help modifyOtherKeys` and other sources. If you are unable to make this
work, just use the "human mode" mappings.***
## Human Mode
If, like me, you only have 2 hands and 10 fingers, you probably don't like
Ctrl-Shift-F keys. Also, if you're running in a terminal, there's a real
possibility of terminfo being wrong for shifted-F-keys, particularly if your
`TERM` is `screen-256color`. If these issues (number of hands, `TERM` variables)
are unfixable, try the following mappings, by adding the following **before
loading vimspector**:
```viml
let g:vimspector_enable_mappings = 'HUMAN'
```
| Key | Mapping | Function
| --- | --- | ---
| `F5` | `VimspectorContinue` | When debugging, continue. Otherwise start debugging.
| `F3` | `VimspectorStop` | Stop debugging.
| `F4` | `VimspectorRestart` | Restart debugging with the same configuration.
| `F6` | `VimspectorPause` | Pause debuggee.
| `F9` | `VimspectorToggleBreakpoint` | Toggle line breakpoint on the current line.
| `F9` | `VimspectorToggleConditionalBreakpoint` | Toggle conditional line breakpoint or logpoint on the current line.
| `F8` | `VimspectorAddFunctionBreakpoint` | Add a function breakpoint for the expression under cursor
| `F8` | `VimspectorRunToCursor` | Run to Cursor
| `F10` | `VimspectorStepOver` | Step Over
| `F11` | `VimspectorStepInto` | Step Into
| `F12` | `VimspectorStepOut` | Step out of current function scope
In addition, I recommend adding a mapping to `VimspectorBalloonEval`, in
normal and visual modes, for example:
```viml
" mnemonic 'di' = 'debug inspect' (pick your own, if you prefer!)
" for normal mode - the word under the cursor
nmap di VimspectorBalloonEval
" for visual mode, the visually selected text
xmap di VimspectorBalloonEval
```
You may also wish to add mappings for navigating up/down the stack, toggling
the breakpoints window, and showing disassembly, for example:
```viml
nmap VimspectorUpFrame
nmap VimspectorDownFrame
nmap B VimspectorBreakpoints
nmap D VimspectorDisassemble
```
# Usage and API
This section defines detailed usage instructions, organised by feature. For most
users, the [mappings](#mappings) section contains the most common commands and
default usage. This section can be used as a reference to create your own
mappings or custom behaviours.
All the below instructions assume a single debugging session. For deatils on how
to debug multiple independent apps at the same time, see
[multiple debugging sessions][#multiple-debugging-sessions].
## Launch and attach by PID:
* Create `.vimspector.json`. See [below](#supported-languages).
* `:call vimspector#Launch()` and select a configuration.
Launching a new session makes it the active
[debugging session][#multiple-debugging-sessions].
### Picking a PID
If the debug adapter configuration uses `pidProperty`, and you make an `attach`
request, then you will be asked to enter a PID (process ID) to attach to.
To make this easier, Vimspector supplies a little utility for listing PIDs. It's
like a very very simple clone of `ps` but works on all the supported platforms.
See [its README](support/vimspector_process_list/README.md) for instructions on
setting it up.
Run `go build` in the `support/vimspector_process_list` directory to set it
up.
If Vimspector is able to find this app, it will try to list all processes owned
by the current user by default.
Alternatively (preferably), you can use a special form of variable expansion
called `${PickProcess(\"binaryName\")}`. The version of this call will list all
processes for the current user that match this binary name.
For example:
```jsonc
"Attach": {
"adapter": "CodeLLDB",
"configuration": {
"request": "attach",
"program": "${workspaceRoot}/Jails",
"pid": "${PickProcess(\"jails\")}"
}
}
```
This will list each matching processes, its parent process, start time and
working directory. It's looks something like this:
```
PID PPID CWD START
52218 52217 (Python) /Users/ben/.vim/bundle/lsp-examples/jai/Jails 2023-05-22 16:02:24
Enter Process ID:
```
You then enter the PID and hit ``.
You can even replace the process picker with your own function. If you define
some function and set `g:vimspector_custom_process_picker_func` to the name of
that function. It will be passed any arguments passed to the `PickProcess`
expansion function. It will also be used whenever a `pidProperty` is specified,
so it must also handle no arguments (use `...` as the formal arguments
for the function, see `:help ...`).
For example, to use `fzf` along with the supplied `vimspector_process_list`:
```viml
function! CustomPickProcess( ... ) abort
let ps = $HOME .. '/.vim/bundle/vimspector/support/vimspector_process_list/vimspector_process_list'
" a:0 is number of args
" a:1 is the optional binary name
if a:0 > 0
let ps .= ' ^' . a:1 . '$'
endif
let line_selected = fzf#run( {
\ 'source': ps,
\ 'options': '--header-lines=1 '
\ . '--prompt="Select Process: " '
\ ,
\
\ } )[ 0 ]
if empty( line_selected)
return 0
endif
let pid = split( line_selected )[ 0 ]
return str2nr( pid )
endfunction
let g:vimspector_custom_process_picker_func = 'CustomPickProcess'
```
Or to use `fzf` with the output of `ps`:
```viml
function! CustomPickProcess( ... ) abort
let ps = 'ps aux'
let line_selected = fzf#run( {
\ 'source': ps,
\ 'options': '--header-lines=1 '
\ . '--prompt="Select Process: " '
\ ,
\
\ } )[ 0 ]
if empty( line_selected)
return 0
endif
let pid = split( line_selected )[ 0 ]
return str2nr( pid )
endfunction
let g:vimspector_custom_process_picker_func = 'CustomPickProcess'
```
### Launch with options
To launch a specific debug configuration, or specify [replacement
variables][vimspector-ref-var] for the launch, you can use:
* `:call vimspector#LaunchWithSettings( dict )`
The argument is a `dict` with the following keys:
* `configuration`: (optional) Name of the debug configuration to launch
* ``: (optional) Name of a variable to set
This allows for some integration and automation. For example, if you have a
configuration named `Run Test` that contains a [replacement
variable][vimspector-ref-var] named `${Test}` you could write a mapping which
ultimately executes:
```viml
vimspector#LaunchWithSettings( #{ configuration: 'Run Test'
\ Test: 'Name of the test' } )
```
This would start the `Run Test` configuration with `${Test}` set to `'Name of
the test'` and Vimspector would _not_ prompt the user to enter or confirm these
things.
See [our YouCompleteMe integration guide](#usage-with-youcompleteme) for
another example where it can be used to specify the port to connect the [java
debugger](#java---partially-supported)
To launch with an ad-hoc config you can use:
* `call vimspector#LaunchWithConfigurations( dict )`
The argument is a `dict` which is the `configurations` section of a .vimspector
file. Pass one configuration in and that will be selected as the one to run.
For example:
```viml
let pid =
call vimspector#LaunchWithConfigurations({
\ "attach": {
\ "adapter": "netcoredbg",
\ "configuration": {
\ "request": "attach",
\ "processId": pid
\ }
\ }
\})
```
This would launch the debugger and attach to the specified process without the need
to have a local .vimspector file on disk.
The `${workspaceRoot}` variable will point to the parent folder of the file that is
currently open in vim.
### Debug configuration selection
Vimspector uses the following logic to choose a configuration to launch:
1. If a configuration was specified in the launch options (as above), use that.
2. Otherwise if there's only one configuration and it doesn't have `autoselect`
set to `false`, use that.
3. Otherwise if there's exactly one configuration with `default` set to `true`
and without `autoselect` set to `false`, use that.
4. Otherwise, prompt the user to select a configuration.
See [the reference guide][vimspector-ref-config-selection] for details.
### Get configurations
* Use `vimspector#GetConfigurations()` to get a list of configurations for the
filetype of the current buffer
For example, to get an array of configurations and fuzzy matching on the result
```viml
:call matchfuzzy(vimspector#GetConfigurations(), "test::case_1")
```
## Breakpoints
See the [mappings](#mappings) section for the default mappings for working with
breakpoints. This section describes the full API in vimscript functions.
Breakpoints are associated with the current
[debugging session][#multiple-debugging-sessions]. When switching between
sessions, the breakpont signs for the previous session are removed and the
breakpoints for the newly activated session are displayed. While it might be
useful to see breakpoints for all sessions, this can be very confusing.
### Breakpoints Window
Use `:VimspectorBreakpoints` or map something to `VimspectorBreakpoints`
to open the breakpoints view. From here you can list, jump to delete, add and
toggle breakpoints.
I recommend a mapping like this to toggle the breakpoints window:
```viml
nmap db VimspectorBreakpoints
```
The following mappings apply by default in the breakpoints window:
* `t`, `` - toggle, i.e. enable/disable breakpoint
* `T` - toggle, i.e. enable/disable ALL breakpoints
* `dd`, `` - delete the current breakpoint
* `cc`, `C` - edit the current breakpoint options
* `i`, `a`, `o` - add a new line breakpoint
* `I`, `A`, `O` - add a new function breakpoint
* `` or double-click - jump to the line breakpoint
A WinBar is provided (where supported) too. This adds functions like
saving/restoring sessions, clearing all breakpoints, and resetting the exception
breakpoints options.
### Line breakpoints
The simplest and most common form of breakpoint is a line breakpoint. Execution
is paused when the specified line is executed.
For most debugging scenarios, users will just hit `` to create a line
breakpoint on the current line and `` to launch the application.
### Conditional breakpoints and logpoints
Some debug adapters support conditional breakpoints. Note that vimspector does
not tell you if the debugger doesn't support conditional breakpoints (yet). A
conditional breakpoint is a breakpoint which only triggers if some expression
evaluates to true, or has some other constraints met.
Some of these functions above take a single optional argument which is a
dictionary of options. The dictionary can have the following keys:
* `condition`: An optional expression evaluated to determine if the breakpoint
should fire. Not supported by all debug adapters. For example, to break when
`abc` is `10`, enter something like `abc == 10`, depending on the language.
* `hitCondition`: An optional expression evaluated to determine a number of
times the breakpoint should be ignored. Should (probably?) not be used in
combination with `condition`. Not supported by all debug adapters. For
example, to break on the 3rd time hitting this line, enter `3`.
* `logMessage`: An optional string to make this breakpoint a "logpoint" instead.
When triggered, this message is printed to the console rather than
interrupting execution. You can embed expressions in braces `{like this}`, for
example `#{ logMessage: "Iteration {i} or {num_entries / 2}" }`
In each case expressions are evaluated by the debugger, so should be in
whatever dialect the debugger understands when evaluating expressions.
When using the `` mapping, the user is prompted to enter these
expressions in a command line (with history).
### Exception breakpoints
Exception breakpoints typically fire when an exception is throw or other error
condition occurs. Depending on the debugger, when starting debugging, you may be
asked a few questions about how to handle exceptions. These are "exception
breakpoints" and vimspector remembers your choices while Vim is still running.
Typically you can accept the defaults (just keep pressing ``!) as most debug
adapter defaults are sane, but if you want to break on, say `uncaught exception`
then answer `Y` to that (for example).
You can configure your choices in the `.vimspector.json`. See
[the configuration guide][vimspector-ref-exception] for details on that.
### API Summary
***NOTE:*** Previously, ToggleBreakpoint would cycle between 3 states:
enabled, disabled, deleted. Many users found the 'disabled' state was rarely
useful, so the behaviour has been changed. ToggleBreakpoint always creates or
deletes a breakpoint. If you wish to 'disable' breakpoints, use the
[breakpoints window](#breakpoints-window) and 'toggle' (`t`) from there.
* Use `vimspector#ToggleBreakpoint( { options dict } )` to set/delete
a line breakpoint. The argument is optional (see below).
* Use `vimspector#AddFunctionBreakpoint( '', { options dict} )`
to add a function breakpoint. The second argument is optional (see below).
* Use `vimspector#SetLineBreakpoint( file_name, line_num, { options dict } )` to
set a breakpoint at a specific file/line. The last argument is optional
(see below)
* Use `vimspector#ClearLineBreakpoint( file_name, line_num )` to
remove a breakpoint at a specific file/line
* Use `vimspector#ClearBreakpoints()` to clear all breakpoints
* Use `vimspector#ResetExceptionBreakpoints()` to clear the exception breakpoints
configuration and re-anser the various questions like "Break on C++ Throw"
* Use `:VimspectorMkSession` and `:VimspectorLoadSession` to save and restore
breakpoints
* `call vimspector#ListBreakpoints()` - toggle breakpoints window
* `call vimspector#BreakpointsAsQuickFix()` - return the current set of
breakpoints in vim quickfix format
Examples:
* `call vimspector#ToggleBreakpoint()` - toggle breakpoint on current line
* `call vimspector#SetLineBreakpoint( 'some_file.py', 10 )` - set a breakpoint
on `some_filepy:10`
* `call vimspector#AddFunctionBreakpoint( 'main' )` - add a function breakpoint
on the `main` function
* `call vimspector#ToggleBreakpoint( { 'condition': 'i > 5' } )` - add a
breakpoint on the current line that triggers only when `i > 5` is `true`
* `call vimspector#SetLineBreakpoint( 'some_file.py', 10, { 'condition': 'i > 5' } )` - add a
breakpoint at `some_file.py:10` that triggers only when `i > 5` is `true`
* `call vimspector#ClearLineBreakpoint( 'some_file.py', 10 )` - delete the
breakpoint at `some_file.py:10`
* `call vimspector#ClearBreakpoints()` - clear all breakpoints
* `VimspectorMkSession` - create `.vimspector.session`
* `VimspectorLoadSession` - read `.vimspector.session`
* `VimspectorMkSession my_session_file` - create `my_session_file`
* `VimspectorLoadSession my_session_file` - read `my_session_file`
### Instruction breakpoints
**NOTE**: Experimental feature, which may change significantly in future based
on user feedback.
Instruction breakpoints can be added from the [disassembly window](#disassembly)
in the same way that you add [line breakpoints](#line-breakpoints) in the code
window. The same mappings and functions work for adding and toggling them. Where
supported by the debug adapter, you can even create logpoints and conditional
breakpoints this way.
Currently, instruction breakpoints are internally modelled as line breakpoints
against the buffer containing the disassembly, but that may change in future, so
please don't rely on this.
Instruction breakpoints are also visible from and can be deleted/disabled from
the [breakpoints window](#breakpoints-window).
Currently, instruction breakpoints are automatically cleared when the debug
session ends. The reason for this is that the addresses can't be guaranteed to
be valid for any other debug session. However, this may also change in future.
### Clear breakpoints
Use `vimspector#ClearBreakpoints()`
to clear all breakpoints including the memory of exception breakpoint choices.
### Run to Cursor
Use `vimspector#RunToCursor` or ``: this creates a temporary
breakpoint on the current line, then continues execution, clearing the
breakpoint when it is hit.
### Go to current line
Use `vimspector#GoToCurrentLine()` or some mapping to
`VimspectorGoToCurrentLine` to jump the current execution to the line your
cursor is currently on.
Where supported this can be useful to re-run sections of code or skip over
them entirely.
If there are multiple possible "targets" on the current line, you're prompted to
pick one.
### Save and restore
Vimspector can save and restore breakpoints (and some other stuff) to a session
file. The following commands exist for that:
* `VimspectorMkSession [file/dir name]` - save the current set of line breakpoints,
logpoints, conditional breakpoints, function breakpoints and exception
breakpoint filters to the supplied session file or the default file in the
supplied directory.
* `VimspectorLoadSession [file/dir name]` - read breakpoints from the session
file supplied or the default file in the supplied directory and replace any
currently set breakpoints. Prior to loading, all current breakpoints are
cleared (as if `vimspector#ClearLineBreakpoints()` was called).
In both cases, the file/dir name argument is optional. By default, the file is
named `.vimspector.session`, but this can be changed globally by setting
`g:vimspector_session_file_name` to something else, or by manually specifying a
path when calling the command. If you supply a directory, the default or
configured session file name is read fron or written to that directory.
Othewise, the file is read based on the currently open buffer or written to the
current working directory.
Advanced users may wish to automate the process of loading and saving, for
example by adding `VimEnter` and `VimLeave` autocommands. It's recommended in
that case to use `silent!` to avoid annoying errors if the file can't be read or
written.
The simplest form of automation is to load the vimspector session whenever you
start vim with a session file. This is as simple as doing this:
```
$ echo silent VimspectorLoadSession > Sessionx.vim
```
See `:help mksession` for details of the `*x.vim` file. You can also do
something like this using `SessionLoadPost`:
```viml
autocmd SessionLoadPost * silent! VimspectorLoadSession
```
## Stepping
* Step in/out, finish, continue, pause etc. using the WinBar, or mappings.
* Stepping is contextual. By default, stepping is statement granularity. But
if your cursor is in the [disassembly window](#disassembly), then stepping
defaults to instruction granularity.
* If you really want to, the API is `vimspector#StepInto()` etc.. There are also
`vimspector#StepSOver()` and `vimspector#StepIOver()` etc. variants for
statement and instruction granularity respectively.
## Variables and scopes
* Current scope shows values of locals.
* Use ``, or double-click with left mouse to expand/collapse (+, -).
* Set the value of the variable with `` (control + ``) or
`` (if `modifyOtherKeys` doesn't work for you)
* View the type of the variable via mouse hover.
* When changing the stack frame the locals window updates.
* While paused, hover to see values.
Scopes and variables are represented by the buffer `vimspector.Variables`.
If you prefer a more verbose display for variables and watches, then you can
`let g:vimspector_variables_display_mode = 'full'`. By default only the name and
value are displayed, with other data available from hovering the mouse or
triggering `VimspectorBalloonEval` on the line containing the value in the
variables (or watches) window.
## Variable or selection hover evaluation
All rules for `Variables and scopes` apply plus the following:
* With mouse enabled, hover over a variable and get the value it evaluates to.
This applies to the variables and watches windows too, and allows you to view
the type of the value.
* Use your mouse to perform a visual selection of an expression (e.g. `a + b`)
and get its result.
* Make a normal mode (`nmap`) and visual mode (`xmap`) mapping to
`VimspectorBalloonEval` to manually trigger the popup.
* Set the value of the variable with `` (control + ``) or
`` (if `modifyOtherKeys` doesn't work for you)
* Use regular navigation keys (`j`, `k`) to choose the current selection; ``
(or leave the tooltip window) to close the tooltip.
You can disable automatic hovering popup by settings
`g:vimspector_enable_auto_hover=0` before starting the debug session. You can
then map something to `VimspectorBalloonEval` and trigger it manually.
## Watches
The watch window is used to inspect variables and expressions. Expressions are
evaluated in the selected stack frame which is "focussed"
The watches window is a prompt buffer, where that's available. Enter insert mode
to add a new watch expression.
* Add watches to the variables window by entering insert mode and
typing the expression. Commit with ``.
* Alternatively, use `:VimspectorWatch `. Tab-completion for
expression is available in some debug adapters.
* View the type of the variable via mouse hover.
* Expand result with ``, or double-click with left mouse.
* Set the value of the variable with `` (control + ``) or
`` (if `modifyOtherKeys` doesn't work for you)
* Delete with ``.
The watches are represented by the buffer `vimspector.Watches`.
If you prefer a more verbose display for variables and watches, then you can
`let g:vimspector_variables_display_mode = 'full'`. By default only the name and
value are displayed, with other data available from hovering the mouse or
triggering `VimspectorBalloonEval` on the line containing the value in the
variables (or watches) window.
You can disable automatic hovering popup by settings
`g:vimspector_enable_auto_hover=0` before starting the debug session. You can
then map something to `VimspectorBalloonEval` and trigger it manually.
### Watch autocompletion
The watch prompt buffer has its `omnifunc` set to a function that will
calculate completion for the current expression. This is trivially used with
`` (see `:help ins-completion`), or integrated with your
favourite completion system. The filetype in the buffer is set to
`VimspectorPrompt`.
For YouCompleteMe, the following config works well:
```viml
let g:ycm_semantic_triggers = {
\ 'VimspectorPrompt': [ '.', '->', ':', '<' ]
}
```
## Disassembly
* Dispplay disassembly around current PC
* Step over/into/out by instruction (contextually, or using the WinBar)
* `:VimspectorDisassemble`, `vimspector#ShowDisassembly()` or
`VimspectorDisassemble`
[](https://asciinema.org/a/esEncAxP45CJmo8Em1sQtxRYe)
Some debug adapters (few!) support disassembly. The way this works in DAP is a
little wierd, but in practice vimspector will ask to disassemble a number of
instructions around the current stack frame's PC. This is then shown in a window
with a WinBar similar to the Code window, but with instruction stepping
granularity. There's a sign for the current instruction and the syntax
highighting defaults to "asm" which mostly works ok for x86 and ARM.
As mentioned above, when your current window is the disassembly windows and you
use the default "step" commands (e.g. ``), the stepping is automatically
chnged to per-instruction rather than per statement.
Each time the process stops, vimspector requests about 2 windows full of
instructions around the current PC. To see more, you can scroll the window.
Vimspector will page in an extra screenful of instructions when the window
scrolls to the top or near the bottom. This isn't perfect. Sometimes you have to
scroll a bit more to make it page in (e.g. ctrl-e ctrl-y at the top).
This is not ideal, and may be improved in future.
You can control the intial height of the disassembly window with
`let g:vimspector_disassembly_height = 10` (or whatver number of lines).
The filetype (and syntax) of the buffers in the disassembly window is
`vimspector-disassembly`. You can use `FileType` autocommands to customise
things like the syntax highlighting.
***NOTE***: This feature is experimental and may change in any way based on user
feedback.
## Dump memory
Some debug adapters provide a way to dump process memory associated with
variables. This can be done from the Variables and Watches windows with:
* The WinBar option "Dump"
* `m` mapping (by default, can be customised)
* `vimspector#ReadMemory()` function
On doing this, you're asked to enter a number of bytes to read (from the
location associated with the current cursor line) and an offset from that
location. A new buffer is displayed in the Code Window containing a memory dump
in hex and ascii, similar to the output of `xxd`.
***NOTE***: This feature is experimental and may change in any way based on user
feedback.
## Stack Traces
The stack trace window shows the state of each program thread. Threads which
are stopped can be expanded to show the stack trace of that thread.
Often, but not always, all threads are stopped when a breakpoint is hit. The
status of a thread is show in parentheses after the thread's name. Where
supported by the underlying debugger, threads can be paused and continued
individually from within the Stack Trace window.
A particular thread, highlighted with the `CursorLine` highlight group is the
"focussed" thread. This is the thread that receives commands like "Step In",
"Step Out", "Continue" and "Pause" in the code window. The focussed thread can
be changed manually to "switch to" that thread.
* Use ``, or double-click with left mouse to expand/collapse a thread stack
trace, or use the WinBar button.
* Use ``, or double-click with left mouse on a stack frame to jump to it.
* Use the WinBar or `vimspector#PauseContinueThread()` to individually pause or
continue the selected thread.
* Use the "Focus" WinBar button, `` or `vimspector#SetCurrentThread()`
to set the "focussed" thread to the currently selected one. If the selected
line is a stack frame, set the focussed thread to the thread of that frame and
jump to that frame in the code window.
* The current frame when a breakpoint is hit or if manual jumping is also
highlighted.
The stack trace is represented by the buffer `vimspector.StackTrace`.
### Child sessions
If there are child debug sessions, such as where the debugee
launches child processes and the debug adapter supports multi-session
debugging, then each session's threads are shown separately. The currently
active session is the one that is highlighted as the currently active
thread/stack frame. To switch control to a different session, focus a thread
within that session.
Note: This refers to sessions created as children of an existing session, and is
not to be confused with
[multiple (parent) debugging sessions][#multiple-debugging-sessions].
## Program Output
* In the outputs window, use the WinBar to select the output channel.
* Alternatively, use `:VimspectorShowOutput `. Use command-line
completion to see the categories.
* The debuggee prints to the stdout channel.
* Other channels may be useful for debugging.
If the output window is closed, a new one can be opened with
`:VimspectorShowOutput ` (use tab-completion - `wildmenu` to see the
options).
### Console
The console window is a prompt buffer, where that's available, and can be used
as an interactive CLI for the debug adapter. Support for this varies amongst
adapters.
* Enter insert mode to enter a command to evaluate.
* Alternatively, `:VimspectorEval `. Completion is available with
some debug adapters.
* Commit the request with ``
* The request and subsequent result are printed.
NOTE: See also [Watches](#watches) above.
If the output window is closed, a new one can be opened with
`:VimspectorShowOutput Console`.
### Console autocompletion
The console prompt buffer has its `omnifunc` set to a function that will
calculate completion for the current command/expression. This is trivially used
with `` (see `:help ins-completion`), or integrated with your
favourite completion system. The filetype in the buffer is set to
`VimspectorPrompt`.
For YouCompleteMe, the following config works well:
```viml
let g:ycm_semantic_triggers = {
\ 'VimspectorPrompt': [ '.', '->', ':', '<' ]
}
```
### Log View
The Vimspector log file contains a full trace of the communication between
Vimspector and the debug adapter. This is the primary source of diagnostic
information when something goes wrong that's not a Vim traceback.
If you just want to see the Vimspector log file, use `:VimspectorToggleLog`,
which will tail it in a little window (doesn't work on Windows).
You can see some debugging info with `:VimspectorDebugInfo`
## Closing debugger
To close the debugger, use:
* `Reset` WinBar button
* `:VimspectorReset` when the WinBar is not available.
* `call vimspector#Reset()`
## Terminate debuggee
If the debuggee is still running when stopping or resetting, then some debug
adapters allow you to specify what should happen to it when finishing debugging.
Typically, the default behaviour is sensible, and this is what happens most of
the time. These are the defaults according to DAP:
* If the request was 'launch': terminate the debuggee
* If the request was 'attach': don't terminate the debuggee
Some debug adapters allow you to choose what to do when disconnecting. If you
wish to control this behaviour, use `:VimspectorReset` or call
`vimspector#Reset( { 'interactive': v:true } )`. If the debug adapter offers a
choice as to whether or not to terminate the debuggee, you will be prompted to
choose. The same applies for `vimspector#Stop()` which can take an argument:
`vimspector#Stop( { 'interactive': v:true } )`.
# Multiple debugging sessions
**NOTE**: This feature is _experimental_ and any part of it may change in
response to user feedback.
Vimspector supports starting an arbitrary number of debug sessions. Each session
is associated with an individual UI tab. Typically, you only debug a single app
and so don't need to think about this, but this advanced feature can be useful
if you need to simultaneously debug multiple, independent applications, or
multiple independent instances of your application.
At any time there is a single "active" root session. Breakpoints are associated
with the current session, and all UI and API commands are applied to the
currently active session.
When switching between root sessions, the breakpont signs for the previous
session are removed and the breakpoints for the newly activated session are
displayed. While it might be useful to see breakpoints for all sessions, this
can be very confusing.
A typical workflow might be:
1. Start debugging a server app (e.g. `:edit server.cc` then ``). This
starts a debug session named after the configuration selected. You could
rename it `:VimspectorRenameSession server`.
2. Open the client code in a new tab (e.g. `:tabedit client.cc`)
3. Instantiate and make active a new debugging session and name it `client`:
`:VimspectorNewSession client` (`client` is now the active session).
4. Add a breakpoint in the `client` session and start debugging with ``.
You now have 2 vimspector tabs. Intuitively, wwitching to a particular tab will
make its session active. You can also manually switch the active session with
`:VimspectorSwitchToSession `.
So, in summary you have the following facilities:
* `VimspectorNewSession `
This creates a new session and makes it active. Optional name is used
in place of the generated one when starting a launch.
* Switching to a specific debug tab makes that session active. This is
intuitive and probably the most common way to work with this.
* Switching manually using `VimspectorSwitchToSession `.
* Name/Rename session with `VimspectorRenameSession `
* Root-level sessions are never 'destroyed' but you can manually destroy
them (if you're brave) using `VimspectorDestroySession `. You
can't destroy a running/active session.
* `vimspector#GetSessionName()` useful for putting in a statusline. There's also
`vimspector#GetSessionID()` for techies.
Here's an example of how you can display the current session name in the
`statusline` (see `:help statusline`, or the documentation for your fancy status
line plugin).
```viml
function! StlVimspectorSession()
" Only include in buffers containing actual files
if !empty( &buftype )
return ''
endif
" Abort if vimspector not loaded
if !exists( '*vimspector#GetSessionName' ) ||
\ !exists( '*vimspector#GetSessionID' )
return ''
endif
return vimspector#GetSessionName()
\ .. ' ('
\ .. vimspector#GetSessionID()
\ .. ')'
endfunction
" ... existing statusline stuff
" set statusline=...
" Show the vimspector active session name (max 20 chars) if there is onw.
set statusline+=%(\ %.20{StlVimspectorSession()}\ %)
```
# Debug profile configuration
For an introduction to the configuration of `.vimspector.json`, take a look at
the Getting Started section of the [Vimspector website][website].
For a full explanation, including how to use variables, substitutions and how to
specify exception breakpoints, see [the docs][vimspector-ref].
The JSON configuration file allows C-style comments:
* `// comment to end of line ...`
* `/* inline comment ... */`
Currently tested with the following debug adapters.
## C, C++, Rust, etc.
* [vscode-cpptools](https://github.com/Microsoft/vscode-cpptools)
* On macOS, I *strongly* recommend using [CodeLLDB](#rust) instead for C and C++
projects. It's really excellent, has fewer dependencies and doesn't open console
apps in another Terminal window.
Example `.vimspector.json` (works with both `vscode-cpptools` and `lldb-vscode`.
For `lldb-vscode` replace the name of the adapter with `lldb-vscode`:
* vscode-cpptools Linux/MacOS:
```json
{
"configurations": {
"Launch": {
"adapter": "vscode-cpptools",
"filetypes": [ "cpp", "c", "objc", "rust" ], // optional
"configuration": {
"request": "launch",
"program": "",
"args": [ ... ],
"cwd": "",
"environment": [ ... ],
"externalConsole": true,
"MIMode": ""
}
},
"Attach": {
"adapter": "vscode-cpptools",
"filetypes": [ "cpp", "c", "objc", "rust" ], // optional
"configuration": {
"request": "attach",
"program": "",
"MIMode": ""
}
}
// ...
}
}
```
* vscode-cpptools Windows
***NOTE FOR WINDOWS USERS:*** You need to install `gdb.exe`. I recommend using
`scoop install gdb`. Vimspector cannot use the visual studio debugger due to
licensing.
```json
{
"configurations": {
"Launch": {
"adapter": "vscode-cpptools",
"filetypes": [ "cpp", "c", "objc", "rust" ], // optional
"configuration": {
"request": "launch",
"program": "",
"stopAtEntry": true
}
}
}
}
```
### Data visualization / pretty printing
Depending on the backend you need to enable pretty printing of complex types
manually.
* LLDB: Pretty printing is enabled by default
* GDB: To enable gdb pretty printers, consider the snippet below.
It is not enough to have `set print pretty on` in your .gdbinit!
```json
{
"configurations": {
"Launch": {
"adapter": "vscode-cpptools",
"filetypes": [ "cpp", "c", "objc", "rust" ], // optional
"configuration": {
"request": "launch",
"program": "",
// ...
"MIMode": "gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
}
}
}
}
```
### C++ Remote debugging
The cpptools documentation describes how to attach cpptools to gdbserver using
`miDebuggerAddress`. Note that when doing this you should use the
`"request": "attach"`.
### C++ Remote launch and attach
If you're feeling fancy, check out the [reference guide][remote-debugging] for
an example of getting Vimspector to remotely launch and attach.
* CodeLLDB (MacOS)
CodeLLDB is superior to vscode-cpptools in a number of ways on macOS at least.
See [Rust](#rust).
* lldb-vscode (MacOS)
An alternative is to to use `lldb-vscode`, which comes with llvm. Here's how:
* Install llvm (e.g. with HomeBrew: `brew install llvm`)
* Create a file named
`/path/to/vimspector/gadgets/macos/.gadgets.d/lldb-vscode.json`:
```json
{
"adapters": {
"lldb-vscode": {
"variables": {
"LLVM": {
"shell": "brew --prefix llvm"
}
},
"attach": {
"pidProperty": "pid",
"pidSelect": "ask"
},
"command": [
"${LLVM}/bin/lldb-vscode"
],
"env": {
"LLDB_LAUNCH_FLAG_LAUNCH_IN_TTY": "YES"
},
"name": "lldb"
}
}
}
```
## Rust
Rust is supported with any gdb/lldb-based debugger. So it works fine with
`vscode-cpptools` and `lldb-vscode` above. However, support for rust is best in
[`CodeLLDB`](https://github.com/vadimcn/vscode-lldb#features).
* `./install_gadget.py --enable-rust` or `:VimspectorInstall CodeLLDB`
* Example: `support/test/rust/vimspector_test`
```json
{
"configurations": {
"launch": {
"adapter": "CodeLLDB",
"filetypes": [ "rust" ],
"configuration": {
"request": "launch",
"program": "${workspaceRoot}/target/debug/vimspector_test"
}
},
"attach": {
"adapter": "CodeLLDB",
"filetypes": [ "rust", "c", "cpp", "jai" ],
"configuration": {
"request": "attach",
"program": "${workspaceRoot}/${fileBasenameNoExtension}",
"PID": "${PID}"
}
}
}
}
```
* Docs: https://github.com/vadimcn/vscode-lldb/blob/master/MANUAL.md
* ***NOTE***: The CodeLLDB manual assumes you are using VSCode (sigh) and therefore says things which don't work in vimspector, as there is a whole load of javascript nonesense behind every VSCode plugin. I can't possibly document all the wierdnesses, but the following are known
1. To use the ["custom" launch](https://github.com/vadimcn/vscode-lldb/blob/master/MANUAL.md#custom-launch), you can't use `"request": "custom"` - this is invalid. Instead use `"request": "launch", "custom": true`. Because [reasons](https://github.com/vadimcn/vscode-lldb/blob/master/extension/main.ts#L397-L401)
2. All the integration with `cargo` is done in the vscode javascript madness, so is not supported.
3. The stuff about [remote agents](https://github.com/vadimcn/vscode-lldb/blob/master/MANUAL.md#connecting-to-a-gdbserver-style-agent) uses `"request": custom`; see the point about "custom" launch above
4. Source Mapping (i.e., enabling `step-into` for standard library functions) can be done by adding `"sourceMap": { "from_path" : "to_path" }`. `"from_path"` can be found in disassembly window by going up in the stack trace; `"to_path"` is just your locally installed standard library path for current toolchain.
## Jai
Jai debugging works fine with any of the other native debuggers. I recommend [CodeLLDB](#rust), but cpptools also works.
Example:
```jsonc
{
"$schema": "https://puremourning.github.io/vimspector/schema/vimspector.schema.json",
"adapters": {
"gdb-with-build": {
"extends": "vscode-cpptools",
"variables": {
"buildme": {
"shell": "jai ${workspaceRoot}/build.jai"
}
}
},
"codelldb-with-build": {
"extends": "CodeLLDB",
"variables": {
"buildme": {
"shell": "jai ${workspaceRoot}/build.jai"
}
}
}
},
"configurations": {
"Run - gdb": {
"adapter": "gdb-with-build",
"filetypes": [ "jai" ],
"configuration": {
"request": "launch",
"program": "${workspaceRoot}/${binaryName}",
"args": [ "*${args}" ],
"stopAtEntry": true,
"stopOnEntry": true
}
},
"Run - lldb": {
"extends": "Run - gdb",
"filetypes": [ "jai" ],
"adapter": "codelldb-with-build"
},
"Attach - gdb": {
"adapter": "vscode-cpptools",
"filetypes": [ "jai" ],
"configuration": {
"request": "attach",
"program": "${workspaceRoot}/${binaryName}",
"processId": "${PID}"
}
},
"Attach - lldb": {
"extends": "Attach - gdb",
"filetypes": [ "jai" ],
"adapter": "CodeLLDB",
"configuration": {
"pid": "${PID}"
}
}
}
}
```
## Python
* Python: [debugpy][]
* Install with `install_gadget.py --enable-python` or `:VimspectorInstall
debugpy`, ideally requires a working compiler and the python development
headers/libs to build a C python extension for performance.
* ***NOTE***: Debugpy no longer supports python 2. In order to continue to debug
python 2 applications, use the `debugpy-python2` adapter after installing the
`debugpy-python2` gadget.
* Full options: https://github.com/microsoft/debugpy/wiki/Debug-configuration-settings
```json
{
"configurations": {
": Launch": {
"adapter": "debugpy",
"filetypes": [ "python" ],
"configuration": {
"name": ": Launch",
"type": "python",
"request": "launch",
"cwd": "",
"python": "/path/to/python/interpreter/to/use",
"stopOnEntry": true,
"console": "externalTerminal",
"debugOptions": [],
"program": ""
}
}
...
}
}
```
### Python Remote Debugging
In order to use remote debugging with debugpy, you have to connect Vimspector
directly to the application that is being debugged. This is easy, but it's a
little different from how we normally configure things. Specifically, you need
to:
* Start your application with debugpy, specifying the `--listen` argument. See
[the debugpy
documentation](https://github.com/microsoft/debugpy#debugpy-cli-usage) for
details.
* Use the built-in "multi-session" adapter. This just asks for the host/port to
connect to. For example:
```json
{
"configurations": {
"Python Attach": {
"adapter": "multi-session",
"filetypes": [ "python" ], // optional
"configuration": {
"request": "attach",
"pathMappings": [
// mappings here (optional)
]
}
}
}
}
```
See [details of the launch
configuration](https://github.com/microsoft/debugpy/wiki/Debug-configuration-settings)
for explanation of things like `pathMappings`.
Additional documentation, including how to do this when the remote machine can
only be contacted via SSH [are provided by
debugpy](https://github.com/microsoft/debugpy/wiki/Debugging-over-SSH).
### Python Remote launch and attach
If you're feeling fancy, checkout the [reference guide][remote-debugging] for
an example of getting Vimspector to remotely launch and attach.
### Python 2
In order to continue to debug python 2 applications, ensure that you install the
`debugpy-python2` gadget (e.g. `--force-enable-python2` or
`:VimspectorInstall debugpy-python2`), and then change your configuration to
use:
```json
{
"configurations": {
"Python Attach": {
"adapter": "debugpy-python2",
// ...
}
}
}
```
for examk
## TCL
* TCL (TclProDebug)
See [my fork of TclProDebug](https://github.com/puremourning/TclProDebug) for instructions.
## C♯
* C# - dotnet core
Install with `install_gadget.py --force-enable-csharp` or `:VimspectorInstall
netcoredbg`
```json
{
"configurations": {
"launch - netcoredbg": {
"adapter": "netcoredbg",
"filetypes": [ "cs", "fsharp", "vbnet" ], // optional
"configuration": {
"request": "launch",
"program": "${workspaceRoot}/bin/Debug/netcoreapp2.2/csharp.dll",
"args": [],
"stopAtEntry": true,
"cwd": "${workspaceRoot}",
"env": {}
}
}
}
}
```
## Go
* Go (delve dap)
Requires:
* `install_gadget.py --enable-go` or `:VimspectorInstall delve`
* `go 1.16` or later (YMMV on earlier versions)
This uses the DAP support built in to the delve debugger
```json
{
"configurations": {
"run": {
"adapter": "delve",
"filetypes": [ "go" ], // optional
"variables": {
// example, to disable delve's go version check
// "dlvFlags": "--check-go-version=false"
},
"configuration": {
"request": "launch",
"program": "${fileDirname}",
"mode": "debug"
}
}
}
}
```
Use Variables to configure the following:
* `dlvFlags`: (string) additional command line arguments to pass to delve
The debugger (delve) is launched in a terminal window so that you can see its
output and pass input to the debuggee.
See [vscode-go docs](https://github.com/golang/vscode-go/blob/master/docs/debugging.md#launchjson-attributes) for full launch options.
Yes, it seems that's the only place they are documented (apparently, they are
not documented by delve itself).
The vscode-go docs also have useful
[troubleshooting information](https://github.com/golang/vscode-go/blob/master/docs/debugging.md#troubleshooting)
* Go (legacy vscode-go)
Requires:
* `install_gadget.py --enable-go` or `:VimspectorInstall vscode-go`
* [Delve][delve-install] installed, e.g. `go get -u github.com/go-delve/delve/cmd/dlv`
* Delve to be in your PATH, or specify the `dlvToolPath` launch option
NOTE: Vimspector uses the ["legacy" vscode-go debug adapter](https://github.com/golang/vscode-go/blob/master/docs/debugging-legacy.md) rather than the "built-in" DAP support in Delve. You can track https://github.com/puremourning/vimspector/issues/186 for that.
```json
{
"configurations": {
"run": {
"adapter": "vscode-go",
"filetypes": [ "go" ], // optional
"configuration": {
"request": "launch",
"program": "${fileDirname}",
"mode": "debug",
"dlvToolPath": "$HOME/go/bin/dlv"
// example, to disable delve's go version check
// "dlvFlags": [ "--check-go-version=false" ]
}
}
}
}
```
See the vscode-go docs for
[troubleshooting information](https://github.com/golang/vscode-go/blob/master/docs/debugging-legacy.md#troubleshooting)
## PHP
This uses the php-debug, see
https://marketplace.visualstudio.com/items?itemName=felixfbecker.php-debug
Requires:
* (optional) Xdebug helper for chrome https://chrome.google.com/webstore/detail/xdebug-helper/eadndfjplgieldjbigjakmdgkmoaaaoc
* `install_gadget.py --force-enable-php` or `:VimspectorInstall
vscode-php-debug`
* configured php xdebug extension
* nodejs for vscode-php-debug
```ini
zend_extension=xdebug.so
xdebug.remote_enable=on
xdebug.remote_handler=dbgp
xdebug.remote_host=localhost
xdebug.remote_port=9000
```
replace `localhost` with the ip of your workstation.
lazy alternative
```ini
zend_extension=xdebug.so
xdebug.remote_enable=on
xdebug.remote_handler=dbgp
xdebug.remote_connect_back=true
xdebug.remote_port=9000
```
* .vimspector.json
```json
{
"configurations": {
"Listen for XDebug": {
"adapter": "vscode-php-debug",
"filetypes": [ "php" ], // optional
"configuration": {
"name": "Listen for XDebug",
"type": "php",
"request": "launch",
"port": 9000,
"stopOnEntry": false,
"pathMappings": {
"/var/www/html": "${workspaceRoot}"
}
}
},
"Launch currently open script": {
"adapter": "vscode-php-debug",
"filetypes": [ "php" ], // optional
"configuration": {
"name": "Launch currently open script",
"type": "php",
"request": "launch",
"program": "${file}",
"cwd": "${fileDirname}",
"port": 9000
}
}
}
}
```
### Debug web application
append `XDEBUG_SESSION_START=xdebug` to your query string
```
curl "http://localhost?XDEBUG_SESSION_START=xdebug"
```
or use the previously mentioned Xdebug Helper extension (which sets a `XDEBUG_SESSION` cookie)
### Debug cli application
```sh
export XDEBUG_CONFIG="idekey=xdebug"
php
```
## JavaScript and TypeScript
* Node.js
This uses [vscode-js-debug](https://github.com/microsoft/vscode-js-debug), the
debugger that is used in vscode as well. For additional configurations, check
the documentation [here](https://github.com/microsoft/vscode-js-debug/blob/main/OPTIONS.md).
To install vscode-js-debug, run `VimspectorInstall vscode-js-debug` from vim or
run the install script `install_gadget.py --force-enable-node`. There are
multiple examples which you can check out. Find them under
`support/test/node/simple`, `support/test/node/multiprocess` and
`support/test/node/typescript`. A typical configuration for debugging typescript
looks like this:
```json
{
"configurations": {
"run - js-debug": {
"adapter": "js-debug",
"filetypes": [ "javascript", "typescript" ],
"configuration": {
"request": "launch",
"program": "${workspaceRoot}/src/index.ts",
"cwd": "${workspaceRoot}",
"stopOnEntry": false,
"type": "pwa-node"
},
// 'breakpoints' is an optional part. This is a way to configure exception
// breakpoints. You can leave this out or set as you prefer.
"breakpoints": {
"exception": {
"all": "N",
"uncaught": "N"
}
}
}
}
}
```
`vscode-js-debug` supports a number of different "types" and can do some stuff
that may or may not work. The `type` field is sadly not documented, but the
valid values are [defined here in the DebugType enum](https://github.com/microsoft/vscode-js-debug/blob/main/src/common/contributionUtils.ts#L61).
Vimspector has only been tested with `pwa-node` type.
Note also that for some reason this debug adapter always forces us to start
multiple debug sessions. For a user, that shouldn't change anything (other than
perhaps a slightly confusing stack trace). But it does make things more
complicated and so there may be subtle bugs.
* Node.js (legacy)
**NOTE**: This configuration uses the *deprecated* legacy debug adapter and will
be removed in future. Please update your configurations to use the `js-debug`
adapter. You _may_ be able to just change the adapter name.
Requires:
* `install_gadget.py --force-enable-node`
* For installation, a Node.js environment that is < node 12. I believe this is an
incompatibility with gulp. Advice, use [nvm](https://github.com/nvm-sh/nvm) with `nvm install --lts 10; nvm
use --lts 10; ./install_gadget.py --force-enable-node ...`
* Options described here:
https://code.visualstudio.com/docs/nodejs/nodejs-debugging
* Example: `support/test/node/simple`
```json
{
"configurations": {
"run": {
"adapter": "vscode-node",
"filetypes": [ "javascript", "typescript" ], // optional
"configuration": {
"request": "launch",
"protocol": "auto",
"stopOnEntry": true,
"console": "integratedTerminal",
"program": "${workspaceRoot}/simple.js",
"cwd": "${workspaceRoot}"
}
}
}
}
```
* Chrome/Firefox
This uses the chrome/firefox debugger (they are very similar), see
https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome and
https://marketplace.visualstudio.com/items?itemName=firefox-devtools.vscode-firefox-debug, respectively.
It allows you to debug scripts running inside chrome from within Vim.
* `./install_gadget.py --force-enable-chrome` or `:VimspectorInstall
debugger-for-chrome`
* `./install_gadget.py --force-enable-firefox` or `:VimspectorInstall
debugger-for-firefox`
* Example: `support/test/web`
```json
{
"configurations": {
"chrome": {
"adapter": "chrome",
"configuration": {
"request": "launch",
"url": "http://localhost:1234/",
"webRoot": "${workspaceRoot}/www"
}
},
"firefox": {
"adapter": "firefox",
"configuration": {
"request": "launch",
"url": "http://localhost:1234/",
"webRoot": "${workspaceRoot}/www",
"reAttach": true
}
}
}
}
```
## Java
Vimspector works well with the [java debug server][java-debug-server], which
runs as a jdt.ls (Java Language Server) plugin, rather than a standalone
debug adapter.
Vimspector is not in the business of running language servers, only debug
adapters, so this means that you need a compatible Language Server Protocol
editor plugin to use Java. I recommend [YouCompleteMe][], which has full support
for jdt.ls, and most importantly a trivial way to load the debug adapter and to
use it with Vimspector.
### Hot code replace
When using the [java debug server][java-debug-server], Vimspector supports the
hot code replace custom feature. By default, when the underlying class files
change, vimspector asks the user if they wish to reload these classes at
runtime.
This behaviour can be customised:
* `let g:vimspector_java_hotcodereplace_mode = 'ask'` - the default, ask the
user for each reload.
* `let g:vimspector_java_hotcodereplace_mode = 'always'` - don't ask, always
reload
* `let g:vimspector_java_hotcodereplace_mode = 'never'` - don't ask, never
reload
### Usage with YouCompleteMe
* Set up [YCM for java][YcmJava].
* Get Vimspector to download the java debug plugin:
`install_gadget.py --force-enable-java ` or
`:VimspectorInstall java-debug-adapter`
* Configure Vimspector for your project using the `vscode-java` adapter, e.g.:
```json
{
"configurations": {
"Java Attach": {
"adapter": "vscode-java",
"filetypes": [ "java" ],
"configuration": {
"request": "attach",
"hostName": "${host}",
"port": "${port}",
"sourcePaths": [
"${workspaceRoot}/src/main/java",
"${workspaceRoot}/src/test/java"
]
}
}
}
}
```
* Tell YCM to load the debugger plugin. This should be the `gadgets/`
directory, not any specific adapter. e.g. in `.vimrc`
```viml
" Tell YCM where to find the plugin. Add to any existing values.
let g:ycm_java_jdtls_extension_path = [
\ ''
\ ]
```
* Create a mapping, such as `` to start the debug server and launch
vimspector, e.g. in `~/.vim/ftplugin/java.vim`:
```viml
let s:jdt_ls_debugger_port = 0
function! s:StartDebugging()
if s:jdt_ls_debugger_port <= 0
" Get the DAP port
let s:jdt_ls_debugger_port = youcompleteme#GetCommandResponse(
\ 'ExecuteCommand',
\ 'vscode.java.startDebugSession' )
if s:jdt_ls_debugger_port == ''
echom "Unable to get DAP port - is JDT.LS initialized?"
let s:jdt_ls_debugger_port = 0
return
endif
endif
" Start debugging with the DAP port
call vimspector#LaunchWithSettings( { 'DAPPort': s:jdt_ls_debugger_port } )
endfunction
nnoremap :call StartDebugging()
```
You can then use `` to start debugging rather than just ``.
If you see "Unable to get DAP port - is JDT.LS initialized?", try running
`:YcmCompleter ExecuteCommand vscode.java.startDebugSession` and note the
output. If you see an error like `ResponseFailedException: Request failed:
-32601: No delegateCommandHandler for vscode.java.startDebugSession`, make sure
that:
* Your YCM jdt.ls is actually working, see the
[YCM docs](https://github.com/ycm-core/YouCompleteMe#troubleshooting) for
troubleshooting
* The YCM jdt.ls has had time to initialize before you start the debugger
* That `g:ycm_java_jdtls_extension_path` is set in `.vimrc` or prior to YCM
starting
For the launch arguments, see the
[vscode document](https://code.visualstudio.com/docs/java/java-debugging).
### Other LSP clients
See [this issue](https://github.com/puremourning/vimspector/issues/3) for more
background.
## Lua
Lua is supported through
[local-lua-debugger-vscode](https://github.com/tomblind/local-lua-debugger-vscode).
This debugger uses stdio to communicate with the running process, so calls to
`io.read` will cause problems.
* `./install_gadget.py --enable-lua` or `:VimspectorInstall local-lua-debugger-vscode`
* Examples: `support/test/lua/simple` and `support/test/lua/love`
```json
{
"$schema": "https://puremourning.github.io/vimspector/schema/vimspector.schema.json#",
"configurations": {
"lua": {
"adapter": "lua-local",
"filetypes": [ "lua" ],
"configuration": {
"request": "launch",
"type": "lua-local",
"cwd": "${workspaceFolder}",
"program": {
"lua": "lua",
"file": "${file}"
}
}
},
"luajit": {
"adapter": "lua-local",
"filetypes": [ "lua" ],
"configuration": {
"request": "launch",
"type": "lua-local",
"cwd": "${workspaceFolder}",
"program": {
"lua": "luajit",
"file": "${file}"
}
}
},
"love": {
"adapter": "lua-local",
"filetypes": [ "love" ],
"configuration": {
"request": "launch",
"type": "lua-local",
"cwd": "${workspaceFolder}",
"program": {
"command": "love"
},
"args": ["${workspaceFolder}"]
}
}
}
}
```
## Other servers
* Java - vscode-javac. This works, but is not as functional as Java Debug
Server. Take a look at [this
comment](https://github.com/puremourning/vimspector/issues/3#issuecomment-576916076)
for instructions.
- See also [the wiki](https://github.com/puremourning/vimspector/wiki/Additional-Language-Support)
which has community-contributed plugin files for some languages.
# Customisation
There is very limited support for customisation of the UI.
## Changing the default signs
Vimsector uses the following signs internally. If they are defined before
Vimsector uses them, they will not be replaced. So to customise the signs,
define them in your `vimrc`.
| Sign | Description | Priority |
|---------------------------|-----------------------------------------|----------|
| `vimspectorBP` | Line breakpoint | 9 |
| `vimspectorBPCond` | Conditional line breakpoint | 9 |
| `vimspectorBPLog` | Logpoint | 9 |
| `vimspectorBPDisabled` | Disabled breakpoint | 9 |
| `vimspectorPC` | Program counter (i.e. current line) | 200 |
| `vimspectorPCBP` | Program counter and breakpoint | 200 |
| `vimspectorNonActivePC` | Program counter for non-focused thread | 9 |
| `vimspectorCurrentThread` | Focussed thread in stack trace view | 200 |
| `vimspectorCurrentFrame` | Current stack frame in stack trace view | 200 |
The default symbols are the equivalent of something like the following:
```viml
sign define vimspectorBP text=\ ● texthl=WarningMsg
sign define vimspectorBPCond text=\ ◆ texthl=WarningMsg
sign define vimspectorBPLog text=\ ◆ texthl=SpellRare
sign define vimspectorBPDisabled text=\ ● texthl=LineNr
sign define vimspectorPC text=\ ▶ texthl=MatchParen linehl=CursorLine
sign define vimspectorPCBP text=●▶ texthl=MatchParen linehl=CursorLine
sign define vimspectorNonActivePC linehl=DiffAdd
sign define vimspectorCurrentThread text=▶ texthl=MatchParen linehl=CursorLine
sign define vimspectorCurrentFrame text=▶ texthl=Special linehl=CursorLine
```
If the signs don't display properly, your font probably doesn't contain these
glyphs. You can easily change them by defining the sign in your vimrc. For
example, you could put this in your `vimrc` to use some simple ASCII symbols:
```viml
sign define vimspectorBP text=o texthl=WarningMsg
sign define vimspectorBPCond text=o? texthl=WarningMsg
sign define vimspectorBPLog text=!! texthl=SpellRare
sign define vimspectorBPDisabled text=o! texthl=LineNr
sign define vimspectorPC text=\ > texthl=MatchParen
sign define vimspectorPCBP text=o> texthl=MatchParen
sign define vimspectorCurrentThread text=> texthl=MatchParen
sign define vimspectorCurrentFrame text=> texthl=Special
```
## Sign priority
Many different plugins provide signs for various purposes. Examples include
diagnostic signs for code errors, etc. Vim provides only a single priority to
determine which sign should be displayed when multiple signs are placed at a
single line. If you are finding that other signs are interfering with
vimspector's (or vice-versa), you can customise the priority used by vimspector
by setting the following dictionary:
```viml
let g:vimspector_sign_priority = {
\ '': ,
\ }
```
For example:
```viml
let g:vimspector_sign_priority = {
\ 'vimspectorBP': 3,
\ 'vimspectorBPCond': 3,
\ 'vimspectorBPLog': 3,
\ 'vimspectorBPDisabled': 3,
\ 'vimspectorNonActivePC': 3,
\ 'vimspectorPC': 999,
\ 'vimspectorPCBP': 999,
\ }
```
All keys are optional. If a sign is not customised, the default priority it used
(as shown above).
See `:help sign-priority`. The default priority is 10, larger numbers override
smaller ones.
***NOTE***: The default `vimspectorNonActivePC` sign does not add any text to
the sign column, it simply adds a line highlight so that you can see the lines
where other threads or processes are currently stopped. As a result this sign
normally should _merge_ with any sign that adds a symbol (such as a breakpoint
sign). Vim will only merge the properties of signs with the same priority, so
if changing the default priorities, it's recommended that:
1. All the breakpoint signs (`vimspectorBP`, `vimspectorBPCond`, etc.) have the
same priority.
2. You also set the `vimspectorNonActivePC` sign that same priority
3. Active PC ( `vimspectorPC`, `vimspectorPCBP`, etc.) have a higher priority.
## Presentation Hints
***NOTE:*** This customisation point is currently ***unsable*** and may change
at any time.
Sometimes the Debug Adapter provides hints as to how the UI should display
certain things. This includes stack frames, variables etc.
Vimspector provides a simple way to customise how these are displayed, by
setting values in the dictionary `g:vimsepctor_presentation_hint_hl`.
The following keys are supported with the mentioned default highlight group.
| Group | Key | Usage | Default |
| ------------ | ------------ | ------------------------------------- | ------------ |
| *all* | `normal` | anything not covered below | `Normal` |
| Stack trace | `emphasize` | emphasize sources in stack trace | `Title` |
| Stack trace | `deemphasize` | deemphasize sources in stack trace | `Conceal` |
| Stack trace | `label` | stack frames which are "labels", not representing actual frames | `NonText` |
| Stack trace | `subtle` | stack frames which are internal or not interesting | `Conceal` |
| Scopes | `arguments` | Function arguments scope | `Title` |
| Scopes | `locals` | Local variables scope | `Title` |
| Scopes | `registers` | Registers scope | `Title` |
| Variables | `property` | Function arguments scope | `Identifier` |
| Variables | `method` | Local variables scope | `Function` |
| Variables | `class` | Registers scope | `Type` |
| Variables | `data` | Registers scope | `String` |
In addition, any value supplied in the DAP `VariablePresentationHint` can be set
which will be used if supplied by the debug adapter.
A silly example; the defaults should probably be OK for most colour scehemes:
```viml
let g:vimspector_presentation_hint_hl = {
\ 'normal': 'Identifier',
\ 'label': 'Title',
\ }
```
## Changing the default window sizes
> ***Please Note***: This customisation API is ***unstable***, meaning that it may
change at any time. I will endeavour to reduce the impact of this and announce
changes in Gitter.
The following options control the default sizes of the UI windows (all of them
are numbers)
- `g:vimspector_sidebar_width` (default: 50 columns):
The width in columns of the left utility windows (variables, watches, stack
trace)
- `g:vimspector_bottombar_height` (default 10 lines):
The height in rows of the output window below the code window.
Example:
```viml
let g:vimspector_sidebar_width = 75
let g:vimspector_bottombar_height = 15
```
## Changing the terminal size
The terminal is typically created as a vertical split to the right of the code
window, and that window is re-used for subsequent terminal buffers.
The following control the sizing of the terminal window used
for debuggee input/output when using Vim's built-in terminal.
- `g:vimspector_code_minwidth` (default: 82 columns):
Minimum number of columns to try and maintain for the code window when
splitting to create the terminal window.
- `g:vimspector_terminal_maxwidth` (default: 80 columns):
Maximum number of columns to use for the terminal.
- `g:vimspector_terminal_minwidth` (default: 10 columns):
Minimum number of columns to use when it is not possible to fit
`g:vimspector_terminal_maxwidth` columns for the terminal.
That's a lot of options, but essentially we try to make sure that there are at
least `g:vimspector_code_minwidth` columns for the main code window and that the
terminal is no wider than `g:vimspector_terminal_maxwidth` columns.
`g:vimspector_terminal_minwidth` is there to ensure that there's a reasonable
number of columns for the terminal even when there isn't enough horizontal space
to satisfy the other constraints.
Example:
```viml
let g:vimspector_code_minwidth = 90
let g:vimspector_terminal_maxwidth = 75
let g:vimspector_terminal_minwidth = 20
```
## Custom mappings while debugging
It's useful to be able to define mappings only while debugging and remove those
mappings when debugging is complete. For this purpose, Vimspector provides 2
`User` autocommands:
* `VimspectorJumpedToFrame` - triggered whenever a 'break' event happens, or
when selecting a stack from to jump to. This can be used to create (for
example) buffer-local mappings for any files opened in the code window.
* `VimspectorDebugEnded` - triggered when the debug session is terminated
(actually when Vimspector is fully reset)
An example way to use this is included in `support/custom_ui_vimrc`. In there,
these autocommands are used to create buffer-local mappings for any files
visited while debugging and to clear them when completing debugging. This is
particularly useful for commands like `VimspectorBalloonEval` which only
make sense while debugging (and only in the code window). Check the commented
section `Custom mappings while debugging`.
NOTE: This is a fairly advanced feature requiring some nontrivial vimscript.
It's possible that this feature will be incorporated into Vimspector in future
as it is a common requirement.
## Pre-launch building strategies
In many cases you will want to rebuild your project before starting a new debugging
session. Vimspector is not a task manager and implementing this functionality
is out of the scope of this project. However, there are some strategies described in the
[community wiki](https://github.com/puremourning/vimspector/wiki/Pre-launch-building-strategies)
to achieve similar functionality.
## Disabling the WinBar
You can tell vimspector not to draw the WinBar (the toolbars in the code,
variables, output, etc. windows) by setting:
```viml
let g:vimspector_enable_winbar=0
```
The WinBar is in any case not displayed if the mouse is not enabled.
## Advanced UI customisation
> ***Please Note***: This customisation API is ***unstable***, meaning that it may
change at any time. I will endeavour to reduce the impact of this and announce
changes in Gitter.
The above customisation of window sizes is limited intentionally to keep things
simple. Vimspector also provides a way for you to customise the UI without
restrictions, by running a `User` autocommand just after creating the UI or
opening the terminal. This requires you to write some vimscript, but allows you
to do things like:
* Hide a particular window or windows
* Move a particular window or windows
* Resize windows
* Have multiple windows for a particular buffer (say, you want 2 watch windows)
* etc.
You can essentially do anything you could do manually by writing a little
vimscript code.
The `User` autocommand is raised with `pattern` set with the following values:
* `VimspectorUICreated`: Just after setting up the UI for a debug session
* `VimspectorTerminalOpened`: Just after opening the terminal window for program
input/output.
The following global variable is set up for you to get access to the UI
elements: `g:vimspector_session_windows`. This is a `dict` with the following
keys:
* `g:vimspector_session_windows.tabpage`: The tab page for the session
* `g:vimspector_session_windows.variables`: Window ID of the variables window,
containing the `vimspector.Variables` buffer.
* `g:vimspector_session_windows.watches`: Window ID of the watches window,
containing the `vimspector.Watches` buffer.
* `g:vimspector_session_windows.stack_trace`: Window ID of the stack trade
window containing the `vimspector.StackTrace` buffer.
* `g:vimspector_session_windows.code`: Window ID of the code window.
* `g:vimspector_session_windows.output`: Window ID of the output window.
In addition, the following key is added when triggering the
`VimspectorTerminalOpened` event:
* `g:vimspector_session_windows.terminal`: Window ID of the terminal window
## Customising the WinBar
You can even customise the WinBar buttons by simply running the usual `menu`
(and `unmenu`) commands.
By default, Vimspector uses something a bit like this:
```viml
nnoremenu WinBar.■\ Stop :call vimspector#Stop( { 'interactive': v:false } )
nnoremenu WinBar.▶\ Cont :call vimspector#Continue()
nnoremenu WinBar.▷\ Pause :call vimspector#Pause()
nnoremenu WinBar.↷\ Next :call vimspector#StepOver()
nnoremenu WinBar.→\ Step :call vimspector#StepInto()
nnoremenu WinBar.←\ Out :call vimspector#StepOut()
nnoremenu WinBar.⟲: :call vimspector#Restart()
nnoremenu WinBar.✕ :call vimspector#Reset( { 'interactive': v:false } )
```
If you prefer a different layout or if the unicode symbols don't render
correctly in your font, you can customise this in the `VimspectorUICreated`
autocommand, for example:
```viml
func! CustomiseUI()
call win_gotoid( g:vimspector_session_windows.code )
" Clear the existing WinBar created by Vimspector
nunmenu WinBar
" Create our own WinBar
nnoremenu WinBar.Kill :call vimspector#Stop( { 'interactive': v:true } )
nnoremenu WinBar.Continue :call vimspector#Continue()
nnoremenu WinBar.Pause :call vimspector#Pause()
nnoremenu WinBar.Step\ Over :call vimspector#StepOver()
nnoremenu WinBar.Step\ In :call vimspector#StepInto()
nnoremenu WinBar.Step\ Out :call vimspector#StepOut()
nnoremenu WinBar.Restart :call vimspector#Restart()
nnoremenu WinBar.Exit :call vimspector#Reset()
endfunction
augroup MyVimspectorUICustomistaion
autocmd!
autocmd User VimspectorUICreated call s:CustomiseUI()
augroup END
```
## Example
There is some example code in `support/custom_ui_vimrc` showing how you can use
the window IDs to modify various aspects of the UI using some basic vim
commands, primarily `win_gotoid` function and the `wincmd` ex command.
To try this out `vim -Nu support/custom_ui_vimrc `.
Here's a rather smaller example. A simple way to use this is to drop it into a
file named `my_vimspector_ui.vim` in `~/.vim/plugin` (or paste into your
`vimrc`):
```viml
" Set the basic sizes
let g:vimspector_sidebar_width = 80
let g:vimspector_code_minwidth = 85
let g:vimspector_terminal_minwidth = 75
function! s:CustomiseUI()
" Customise the basic UI...
" Close the output window
call win_gotoid( g:vimspector_session_windows.output )
q
endfunction
function s:SetUpTerminal()
" Customise the terminal window size/position
" For some reasons terminal buffers in Neovim have line numbers
call win_gotoid( g:vimspector_session_windows.terminal )
set norelativenumber nonumber
endfunction
augroup MyVimspectorUICustomistaion
autocmd!
autocmd User VimspectorUICreated call s:CustomiseUI()
autocmd User VimspectorTerminalOpened call s:SetUpTerminal()
augroup END
```
# FAQ
1. Q: Does it work with _this_ language? 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. See [the wiki](https://github.com/puremourning/vimspector/wiki/Additional-Language-Support) for details on additional language support
3. How do I stop it starting a new Terminal.app on macOS? See [this
comment](https://github.com/puremourning/vimspector/issues/90#issuecomment-577857322)
4. Can I specify answers to the annoying questions about exception breakpoints
in my `.vimspector.json` ? Yes, see [here][vimspector-ref-exception].
5. Do I have to specify the file to execute in `.vimspector.json`, or could it be the current vim file?
You don't need to. You can specify $file for the current active file. See [here][vimspector-ref-var] for complete list of replacements in the configuration file.
6. You allow comments in `.vimspector.json`, but Vim highlights these as errors,
do you know how to make this not-an-error? Yes, put this in
`~/.vim/after/syntax/json.vim`:
```viml
syn region jsonComment start="/\*" end="\*/"
hi link jsonCommentError Comment
hi link jsonComment Comment
```
7. What is the difference between a `gadget` and an `adapter`? A gadget is
something you install with `:VimspectorInstall` or `install_gadget.py`, an
`adapter` is something that Vimspector talks to (actually it's the Vimspector
config describing that thing). These are _usually_ one-to-one,
but in theory a single gadget can supply multiple `adapter` configs.
Typically this happens when a `gadget` supplies different `adapter` config
for, say remote debugging, or debugging in a container, etc.
8. The signs and winbar display funny symbols. How do I fix them? See
[this](#changing-the-default-signs) and [this](#customising-the-winbar)
9. What's this telemetry stuff all about? Are you sending my data to evil companies?
Debug adapters (for some reason) send telemetry data to clients. Vimspector simply
displays this information in the output window. It *does not* and *will not ever*
collect, use, forward or otherwise share any data with any third parties.
10. Do I _have_ to put a `.vimspector.json` in the root of every project? No, you
can use `g:vimspector_adapters` and `g:vimspector_configurations` or put all
of your adapter and debug configs in a [single directory](https://puremourning.github.io/vimspector/configuration.html#debug-configurations)
if you want to, but note the caveat that `${workspaceRoot}` won't be
calculated correctly in that case. The vimsepctor author uses this [a lot](https://github.com/puremourning/.vim-mac/tree/master/vimspector-conf)
11. I'm confused about remote debugging configuration, can you explain it?
eh... kind of. Reference:
https://puremourning.github.io/vimspector/configuration.html#remote-debugging-support.
Some explanations here too:
https://github.com/puremourning/vimspector/issues/478#issuecomment-943515093
12. I'm trying to debug a Django (django?) project and it's not working. Can you
help? sure, check [this link which has a working example](https://www.reddit.com/r/neovim/comments/mz4ari/how_to_set_up_vimspector_for_django_debugging/).
Or google it.
13. Can vimspector build my code before debugging it? Can I deploy it to a remote host before debugging it?
No, not really. Vimspector is just a debugger, not a task system or build automation system - there are other tools for that. There is however a hack you can use - you can use a 'shell' variable to execute a command and just discard the output. Other options are discussed in [this issue](https://github.com/puremourning/vimspector/issues/227)
14. It's annoying to manually type in the PID when attaching. Do you have a PID picker? There's no PID picker in vimspector at the moment, but you could write something and wrap `vimspector#LaunchWithSettings( { 'ThePID': the_pid_i_picked } )`. Alternatively, you could use a `shell` variable to guess the PID, like this (which runs `pgrep vim | sort | tail -1` to get the 'highest' PID of the command to be debugged (NOTE: this is for debugging Vim. replace with something appropriate to your actual use case. If this doesn't make sense to you, you might be better off just typing in the PID).
```json
"Attach: max PID": {
"adapter": "CodeLLDB",
"variables": {
"pid": {
"shell": [
"/bin/bash",
"-c",
"pgrep vim | sort | tail -1"
]
}
},
"configuration": {
"request": "attach",
"program": "${workspaceRoot}/src/vim",
"expressions": "native",
"stopOnEntry#json": "${StopOnEntry:true}",
"pid": "${pid}"
}
},
```
Example `g:vimspector_adapters` and `g:vimspector_configurations`:
```viml
let g:vimspector_adapters = #{
\ test_debugpy: #{ extends: 'debugpy' }
\ }
let g:vimspector_configurations = {
\ "test_debugpy_config": {
\ "adapter": "test_debugpy",
\ "filetypes": [ "python" ],
\ "configuration": {
\ "request": "launch",
\ "type": "python",
\ "cwd": "${fileDirname}",
\ "args": [],
\ "program": "${file}",
\ "stopOnEntry": v:false,
\ "console": "integratedTerminal",
\ "integer": 123,
\ },
\ "breakpoints": {
\ "exception": {
\ "raised": "N",
\ "uncaught": "",
\ "userUnhandled": ""
\ }
\ }
\ } }
```
[ycmd]: https://github.com/Valloric/ycmd
[gitter]: https://gitter.im/vimspector/Lobby?utm_source=share-link&utm_medium=link&utm_campaign=share-link
[java-debug-server]: https://github.com/Microsoft/java-debug
[website]: https://puremourning.github.io/vimspector-web/
[delve]: https://github.com/go-delve/delve
[delve-install]: https://github.com/go-delve/delve/tree/master/Documentation/installation
[vimspector-ref]: https://puremourning.github.io/vimspector/configuration.html
[vimspector-ref-var]: https://puremourning.github.io/vimspector/configuration.html#replacements-and-variables
[vimspector-ref-exception]: https://puremourning.github.io/vimspector/configuration.html#exception-breakpoints
[vimspector-ref-config-selection]: https://puremourning.github.io/vimspector/configuration.html#configuration-selection
[debugpy]: https://github.com/microsoft/debugpy
[YouCompleteMe]: https://github.com/ycm-core/YouCompleteMe#java-semantic-completion
[remote-debugging]: https://puremourning.github.io/vimspector/configuration.html#remote-debugging-support
[YcmJava]: https://github.com/ycm-core/YouCompleteMe#java-semantic-completion