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

Table Of Contents
(gdb)
*stopped,reason="end-stepping-range",
frame={addr="0x000100f4",func="foo",args=[],file="try.c",line="10"}
(gdb)
The -exec-until command
Synopsis
-exec-until [ location ]
Asynchronous command. Executes the inferior until the location specified in the
argument is reached. If there is no argument, the inferior executes until a source line
greater than the current one is reached. The reason for stopping in this case will be
'location-reached'.
GDB command
The corresponding GDB command is 'until'.
Example
(gdb)
-exec-until recursive2.c:6
^running
(gdb)
x = 55
*stopped,reason="location-reached",thread-id="1",frame=addr="0x00002a24",func="main",args=[],
file="recursive2.c",line="6"
(gdb)
The -file-exec-and-symbols command
Synopsis
-file-exec-and-symbols file
Specify the executable file to be debugged. This file is the one from which the symbol
table is also read. If no file is specified, the command clears the executable and symbol
information. If breakpoints are set when using this command with no arguments, GDB
will produce error messages. Otherwise, no output is produced, except a completion
notification.
GDB command
The corresponding GDB command is 'file'.
Example
(gdb)
-file-exec-and-symbols /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
^done
(gdb)
336 The GDB/MI Interface