D-10
Motorola DSP56000 Family Optimizing C Compiler User’s Manual
For More Information On This Product,
Go to: www.freescale.com
Motorola
Specifying GDB’s Files
Also, GDB may at times produce more information about its own workings than is of
interest to the user. Some of these informational messages can be turned on and off with
the ‘set verbose’ command:
set verbose off
Disables GDB’s output of certain informational messages.
set verbose on
Re-enables GDB’s output of certain informational messages.
Currently, the messages controlled by ‘set verbose’ are those which announce that the
symbol table for a source file is being read (see section File Commands, in the description
of the command ‘symbol-file’).
D.3 Specifying GDB’s Files
GDB needs to know the file name of the program to be debugged, both in order to read its
symbol table and in order to start the program. To debug a core dump of a previous run,
GDB must be told the file name of the core dump.
D.3.1 Specifying Files with Arguments
The usual way to specify the executable and core dump file names is with two command
arguments given when you start GDB. The first argument is used as the file for execution
and symbols, and the second argument (if any) is used as the core dump file name. Thus,
gdb progm core
specifies ‘progm’ as the executable program and ‘core’ as a core dump file to examine.
(You do not need to have a core dump file if what you plan to do is debug the program
interactively.)
See section Options, for full information on options and arguments for invoking GDB.
D.3.2 Specifying Files with Commands
Usually you specify the files for GDB to work with by giving arguments when you invoke
GDB. But occasionally it is necessary to change to a different file during a GDB session.
Or you may run GDB and forget to specify the files you want to use. In these situations the
GDB commands to specify new files are useful.
F
Freescale Semiconductor, Inc.
n
.