Debugging with GDB Manual The GNU Source-Level Debugger (769148-001, March 2014)

^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"
The -exec-abort command
Synopsis
-exec-abort
Kill the inferior running program.
GDB command
The corresponding GDB command is 'kill'.
Example
N.A.
The -exec-arguments command
Synopsis
-exec-arguments args
Set the inferior program arguments, to be used in the next '-exec-run'.
GDB command
The corresponding GDB command is 'set args'.
Example
Do not have one around.
The -exec-continue command
Synopsis
-exec-continue
Asynchronous command. Resumes the execution of the inferior program until a breakpoint is
encountered, or until the inferior exits.
GDB command
The corresponding GDB is 'continue'.
Example
-exec-continue
^running
(gdb)
@Hello world
*stopped,reason="breakpoint-hit",bkptno="2",thread-id="1",frame=addr="0x000029d8",
func="foo",args=[],file="hello.c",line="16"file="hello.c",line="13"}
(gdb)
252 The GDB/MI Interface