A wrapper debugger to control command line debuggers from vim.

Supported debuggers:

• mdbg: .Net
• cdb: Windows C++
• gdb: GNU Debugger
• jdb: Java debugger
• fdb: Flex debugger

not support pdb now

!!cdb is a command-line debugger for windows.

!!mdbg is a command-line debugger for .Net Framework.

1. dbg.vim is requires vimproc and each debuggers.

2. Through the path to each debugger or define the vimrc as follows.

   let g:dbg#command_shell = 'cmd.exe' let g:dbg#shell_prompt = '> '

   let g:dbg#command_cdb = 'cdb.exe' let g:dbg#command_mdbg= 'C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\NETFX 4.0 Tools\mdbg.exe' let g:dbg#command_jdb = 'jdb' let g:dbg#command_gdb = 'gdb' let g:dbg#command_fdb = 'fdb' !! let g:dbg#command_python = 'python' !! now not support pdb.

1. start shell as follow.

   :DbgShell or :Dbg shell

1. start debugger as follow.

   :Dbg cdb exe-file-path

2. set first breakpoint.

   bp main or

   bp WinMain or

   bp wWinMain or

3. run the program.

   g or Press in command mode.

1. start debugger as follow.

   :Dbg mdbg exe-file-path

2. run the program.

   run

1. start debugger as follow

   :Dbg gdb out-file-path

2. set first breakpoint.

   break sorce:line or Press on the break line in command mode.

3. run the program.

   run or Press in command mode.

1. start debugger as follow

   :Dbg jdb Main-Class-Name And input source-code-base-directory.

2. set first breakpoint.

   stop in Class.main or Press on the break line in command mode.

3. run the program.

   run or Press in command mode.

1. start debugger as follow

   :Dbg fdb swf-file-path And input source-code-base-directory.

2. set first breakpoint.

   break method or break file:line or Press on the break line in command mode.

3. continue the program.

   continue or Press in command mode.

gdb mode is a input method like a gdb.

1. start debugger.

2. input gdb command with atmark.

   @run

   @next

   @step

   @continue

   @finish

   @print xxx

   @info bt

   @info locals

   @info threads

   @info where

   @info backtrace

   @info quit

It is also possible shorthand.

> @n

> @p

... etc

• <F2> Print variable under the cursor.
• <F5> Continue the program.
• <F6> Show locals variable.
• <F7> Show threads variable.
• <F8> Show callstack.
• <F9> Set breakpoints under the cursor.
• <F10> Next
• <F11> Step
• <S-F11> stepout

xxx

• support shell-mode (win -> cmd.exe, other -> bash)
• fix read-stdout

• support mdbg (.Net Framework console debugger)

• first release