HomePage |
RecentChanges |
EditorIndex |
TextEditorFamilies |
Preferences
Showing revision 2
Pyclewn allows using vim as a front end to a debugger. Pyclewn currently supports gdb.
Author: Xavier de Gaye
Homepage: http://pyclewn.sourceforge.net/
Family: VIMFamily
Platform: Vim
License: Open source
Screenshot:
http://sourceforge.net/dbimage.php?id=162006
The debugger output is redirected to a vim window, the pyclewn console. The debugger commands are mapped to vim user-defined commands with a common letter prefix, and with completion available on the commands and their first argument.
On unix, the controlling terminal of the program to debug is the terminal used to launch pyclewn, or any other terminal when the debugger allows it, for example after using the attach or tty gdb commands. On Windows, gdb pops up a console attached to the program to debug.
Features
- A debugger command can be mapped in vim to a key sequence using vim key mappings. This allows, for example, to set/clear a breakpoint or print a variable value at the current cursor or mouse position by just hitting a key.
- A sequence of gdb commands can be run from a vim script when the async option is set. This may be useful in a key mapping.
- Breakpoints and the line in the current frame, are highlighted in the source code. Disabled breakpoints are noted with a different highlighting color. Pyclewn automatically finds the source file for the breakpoint if it exists, and tells vim to load and display the file and highlight the line.
- The value of an expression or variable is displayed in a balloon in vim when the mouse pointer is hovering over the selected expression or the variable.
- An expression can be watched in a vim window. The expression value is updated and highlighted whenever it has changed. When the expression is a structure or class instance, it can be expanded (resp. folded) to show (resp. hide) its members and their values.
- The project command saves the current gdb settings to a project file that may be sourced later by the gdb source command. These settings are the working directory, the debuggee program file name, the program arguments and the breakpoints. The sourcing and saving of the project file can be automated to occur on each gdb startup and termination, whith the project command line option.
- Vim command completion on the commands and their first argument.