--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/GDBMI_exec_run.st	Thu Jun 12 01:21:45 2014 +0100
@@ -0,0 +1,93 @@
+"{ Package: 'jv:libgdbs' }"
+
+GDBMICommand subclass:#GDBMI_exec_run
+	instanceVariableNames:''
+	classVariableNames:''
+	poolDictionaries:''
+	category:'GDB-Core-Commands-MI'
+!
+
+!GDBMI_exec_run class methodsFor:'documentation'!
+
+documentation
+"
+The `-exec-run' Command
+-----------------------
+
+Synopsis
+........
+
+      -exec-run [ --all | --thread-group N ] [ --start ]
+
+   Starts execution of the inferior from the beginning.  The inferior
+executes until either a breakpoint is encountered or the program exits.
+In the latter case the output will include an exit code, if the program
+has exited exceptionally.
+
+   When neither the `--all' nor the `--thread-group' option is
+specified, the current inferior is started.  If the `--thread-group'
+option is specified, it should refer to a thread group of type
+`process', and that thread group will be started.  If the `--all'
+option is specified, then all inferiors will be started.
+
+   Using the `--start' option instructs the debugger to stop the
+execution at the start of the inferior's main subprogram, following the
+same behavior as the `start' command (*note Starting::).
+
+{No value for `GDBN'} Command
+.............................
+
+The corresponding {No value for `GDBN'} command is `run'.
+
+Examples
+........
+
+     (gdb)
+     -break-insert main
+     ^done,bkpt={number='1',addr='0x0001072c',file='recursive2.c',line='4'}
+     (gdb)
+     -exec-run
+     ^running
+     (gdb)
+     *stopped,reason='breakpoint-hit',disp='keep',bkptno='1',
+     frame={func='main',args=[],file='recursive2.c',
+     fullname='/home/foo/bar/recursive2.c',line='4'}
+     (gdb)
+
+Program exited normally:
+
+     (gdb)
+     -exec-run
+     ^running
+     (gdb)
+     x = 55
+     *stopped,reason='exited-normally'
+     (gdb)
+
+Program exited exceptionally:
+
+     (gdb)
+     -exec-run
+     ^running
+     (gdb)
+     x = 55
+     *stopped,reason='exited',exit-code='01'
+     (gdb)
+
+   Another way the program can terminate is if it receives a signal
+such as `SIGINT'.  In this case, GDB/MI displays this:
+
+     (gdb)
+     *stopped,reason='exited-signalled',signal-name='SIGINT',
+     signal-meaning='Interrupt'
+
+
+"
+! !
+
+!GDBMI_exec_run methodsFor:'accessing'!
+
+operation
+	^ 'exec-run'
+! !
+