Added Mdbg to the vimdoc and the readme

README.md

@@ -18,6 +18,7 @@ interactive shell debugger, and comes with implementations for:
 
  * GDB - doesn't need introdcution...
  * JDB - a Java debugger
+ * Mdbg - a .NET debugger(Windows only)
  * PDB - a Python module for debugging Python scripts
  * RDebug - a Ruby command line option for debugging Ruby scripts
 

doc/vebugger.txt

@@ -4,7 +4,7 @@
 Author:  Idan Arye <https://github.com/someboddy/>
 License: Same terms as Vim itself (see |license|)
 
-Version: 1.0.0
+Version: 1.1.0
 
 INTRODUCTION                                                       *vebugger*
 
@@ -21,6 +21,7 @@ Vebugger is built as a generic framework for building frontends for
 interactive shell debugger, and comes with implementations for:
 * GDB - doesn't need introdcution...
 * JDB - a Java debugger
+* Mdbg - a .NET debugger(Windows only)
 * PDB - a Python module for debugging Python scripts
 * RDebug - a Ruby command line option for debugging Ruby scripts
 Other implementations can be added with ease, and I will accept pull requests
@@ -155,6 +156,38 @@ PDB can also be launched with the *VBGstartPDB* command:
     VBGstartPDB script.py hello world
 <
 
+LAUNCHING MDBG                                                *vebugger-mdbg*
+
+Mdbg is launched with *vebugger#mdbg#start*
+>
+    call vebugger#mdbg#start('App.exe',{
+        \'srcpath':'src',
+        \'args':['hello','world']})
+<
+
+The supported extra arguments are:
+* "srcpath": Where to look for source files
+* "noConsole": If non-zero, do not open a console for the debugged program
+* "args": Command line arguments for the debugged program
+* "pid": Process id to attach to
+If you specify "pid", you can't specify "args" and/or "noConsole".
+
+If you don't supply "srcpath", Vebugger will assume you are
+using the current directory for source files.
+
+Mdbg does not have a command for starting it, since you usually want to supply
+"srcpath".
+
+You can also search for a process with *vebugger#mdbg#searchAndAttach*
+>
+    call vebugger#mdbg#searchAndAttach('App.exe','src')
+<
+Here the first argument is the executable and the second is the source files
+directory. This will display a list of available processes to attach to.
+Notice that unlike GDB, you need "src" here since Mdbg doesn't display full
+source file paths.
+
+
 USING THE DEBUGGERS                        *vebugger-usage* *vebugger-commands*
 
 Once you have launched a debugger, you can use the following commands to