VDB is a Vim plug-in that provides an all-in-one debug tool for every language by offering text-based debuggers.
VDB is a convenient Vim plugin that provides an integrated debugger for any language that has a text-based debugger. Currently, VDB works only with gdb, however, the plugin's developer intends to make it more extensible in the future. Eventually, the plan is to offer a generic interface to any text-based, line-oriented debugger by using "interface configuration files" that specify the debugger's recommended commands for various actions. It is worth noting that the use of XML for this purpose is being considered, but this may be an overkill solution.
Although VDB has some limitations end-users should be aware of. As it only works on operating systems that support pty's, so it is not compatible with Windows. However, it has a range of powerful features that developers will find useful. For instance, users are able to step over or into a specific line of code, execute code until the current cursor line is reached, set watches on expressions, view the output of their programs within a Vim buffer, and enter data interactively into the same buffer if and when required. Additionally, the debug console offers developers direct access to the back-end debugger process, which enables users to execute more complex actions. Commands typed in the debug console are reflected both in text and status displays within the Vim interface.
To use VDB, you will require a Vim version of 7.0 or higher. However, it may still work on lower versions, though this has not been tested. For an in-depth overview of the plugin, users should check the README file that comes bundled with the package.
To install VDB, users can follow either of two steps. For an installation without privileged access, the VDB.vim file should be placed in the home directory of the user. Next, add the following command to their ~/.vimrc source ~/vdb.vim The user may place the file wherever they deem appropriate, so long as the source command points to it correctly. Users should also confirm that VDB.vim is readable by them.
For a system-wide installation, VDB.vim should be placed in the /usr/share/vim/vimfiles/ftplugin directory. Once VDB.vim is placed in this directory, each user can activate it as desired by adding source /usr/share/vim/vimfiles/vdb.vim to their respective ~/.vimrc files.
Although VDB has some limitations end-users should be aware of. As it only works on operating systems that support pty's, so it is not compatible with Windows. However, it has a range of powerful features that developers will find useful. For instance, users are able to step over or into a specific line of code, execute code until the current cursor line is reached, set watches on expressions, view the output of their programs within a Vim buffer, and enter data interactively into the same buffer if and when required. Additionally, the debug console offers developers direct access to the back-end debugger process, which enables users to execute more complex actions. Commands typed in the debug console are reflected both in text and status displays within the Vim interface.
To use VDB, you will require a Vim version of 7.0 or higher. However, it may still work on lower versions, though this has not been tested. For an in-depth overview of the plugin, users should check the README file that comes bundled with the package.
To install VDB, users can follow either of two steps. For an installation without privileged access, the VDB.vim file should be placed in the home directory of the user. Next, add the following command to their ~/.vimrc source ~/vdb.vim The user may place the file wherever they deem appropriate, so long as the source command points to it correctly. Users should also confirm that VDB.vim is readable by them.
For a system-wide installation, VDB.vim should be placed in the /usr/share/vim/vimfiles/ftplugin directory. Once VDB.vim is placed in this directory, each user can activate it as desired by adding source /usr/share/vim/vimfiles/vdb.vim to their respective ~/.vimrc files.
What's New
Version 0.4.1: N/A