Debugging with GDB Manual (5900-1473; WDB 6.2; January 2011)

The -exec-interrupt command
Synopsis
-exec-interrupt
Asynchronous command. Interrupts the background execution of the target. Note how
the token associated with the stop message is the one for the execution command that
has been interrupted. The token for the interrupt itself only appears in the '^done' output.
If the user is trying to interrupt a non-running program, an error message will be printed.
GDB command
The corresponding GDB command is 'interrupt'.
Example
(gdb)
111-exec-continue
111^running
(gdb)
222-exec-interrupt
222^done
(gdb)
111*stopped,signal-name="SIGINT",signal-meaning="Interrupt",
frame={addr="0x00010140",func="foo",args=[],file="try.c",line="13"}
(gdb)
(gdb)
-exec-interrupt
^error,msg="mi_cmd_exec_interrupt: Inferior not executing."
(gdb)
The -exec-next command
Synopsis
-exec-next
Asynchronous command. Resumes execution of the inferior program, stopping when the
beginning of the next source line is reached.
GDB command
The corresponding GDB command is 'next'.
Example
-exec-next
^running
(gdb)
*stopped,reason="end-stepping-range",thread-id="1",frame=addr="0x00002a10",
func="main",args=[],file="hello.c",line="24"(gdb)
332 The GDB/MI Interface