Line 1... |
Line 1... |
This is ./gdb.info, produced by Makeinfo version 3.12f from gdb.texinfo.
|
This is ./gdb.info, produced by makeinfo version 4.0 from gdb.texinfo.
|
|
|
INFO-DIR-SECTION Programming & development tools.
|
INFO-DIR-SECTION Programming & development tools.
|
START-INFO-DIR-ENTRY
|
START-INFO-DIR-ENTRY
|
* Gdb: (gdb). The GNU debugger.
|
* Gdb: (gdb). The GNU debugger.
|
END-INFO-DIR-ENTRY
|
END-INFO-DIR-ENTRY
|
Line 24... |
Line 24... |
Permission is granted to copy and distribute translations of this
|
Permission is granted to copy and distribute translations of this
|
manual into another language, under the above conditions for modified
|
manual into another language, under the above conditions for modified
|
versions.
|
versions.
|
|
|
|
|
File: gdb.info, Node: Configurations, Next: Controlling GDB, Prev: Targets, Up: Top
|
|
|
|
Configuration-Specific Information
|
|
**********************************
|
|
|
|
While nearly all GDB commands are available for all native and cross
|
|
versions of the debugger, there are some exceptions. This chapter
|
|
describes things that are only available in certain configurations.
|
|
|
|
There are three major categories of configurations: native
|
|
configurations, where the host and target are the same, embedded
|
|
operating system configurations, which are usually the same for several
|
|
different processor architectures, and bare embedded processors, which
|
|
are quite different from each other.
|
|
|
|
* Menu:
|
|
|
|
* Native::
|
|
* Embedded OS::
|
|
* Embedded Processors::
|
|
* Architectures::
|
|
|
|
|
|
File: gdb.info, Node: Native, Next: Embedded OS, Up: Configurations
|
|
|
|
Native
|
|
======
|
|
|
|
This section describes details specific to particular native
|
|
configurations.
|
|
|
|
* Menu:
|
|
|
|
* HP-UX:: HP-UX
|
|
* SVR4 Process Information:: SVR4 process information
|
|
|
|
|
|
File: gdb.info, Node: HP-UX, Next: SVR4 Process Information, Up: Native
|
|
|
|
HP-UX
|
|
-----
|
|
|
|
On HP-UX systems, if you refer to a function or variable name that
|
|
begins with a dollar sign, GDB searches for a user or system name
|
|
first, before it searches for a convenience variable.
|
|
|
|
|
|
File: gdb.info, Node: SVR4 Process Information, Prev: HP-UX, Up: Native
|
|
|
|
SVR4 process information
|
|
------------------------
|
|
|
|
Many versions of SVR4 provide a facility called `/proc' that can be
|
|
used to examine the image of a running process using file-system
|
|
subroutines. If GDB is configured for an operating system with this
|
|
facility, the command `info proc' is available to report on several
|
|
kinds of information about the process running your program. `info
|
|
proc' works only on SVR4 systems that include the `procfs' code. This
|
|
includes OSF/1 (Digital Unix), Solaris, Irix, and Unixware, but not
|
|
HP-UX or Linux, for example.
|
|
|
|
`info proc'
|
|
Summarize available information about the process.
|
|
|
|
`info proc mappings'
|
|
Report on the address ranges accessible in the program, with
|
|
information on whether your program may read, write, or execute
|
|
each range.
|
|
|
|
`info proc times'
|
|
Starting time, user CPU time, and system CPU time for your program
|
|
and its children.
|
|
|
|
`info proc id'
|
|
Report on the process IDs related to your program: its own process
|
|
ID, the ID of its parent, the process group ID, and the session ID.
|
|
|
|
`info proc status'
|
|
General information on the state of the process. If the process is
|
|
stopped, this report includes the reason for stopping, and any
|
|
signal received.
|
|
|
|
`info proc all'
|
|
Show all the above information about the process.
|
|
|
|
|
|
File: gdb.info, Node: Embedded OS, Next: Embedded Processors, Prev: Native, Up: Configurations
|
|
|
|
Embedded Operating Systems
|
|
==========================
|
|
|
|
This section describes configurations involving the debugging of
|
|
embedded operating systems that are available for several different
|
|
architectures.
|
|
|
|
* Menu:
|
|
|
|
* VxWorks:: Using GDB with VxWorks
|
|
|
|
GDB includes the ability to debug programs running on various
|
|
real-time operating systems.
|
|
|
|
|
|
File: gdb.info, Node: VxWorks, Up: Embedded OS
|
File: gdb.info, Node: VxWorks, Up: Embedded OS
|
|
|
Using GDB with VxWorks
|
Using GDB with VxWorks
|
----------------------
|
----------------------
|
|
|
Line 1436... |
Line 1333... |
Print ten commands centered on command number N.
|
Print ten commands centered on command number N.
|
|
|
`show commands +'
|
`show commands +'
|
Print ten commands just after the commands last printed.
|
Print ten commands just after the commands last printed.
|
|
|
|
|
|
File: gdb.info, Node: Screen Size, Next: Numbers, Prev: History, Up: Controlling GDB
|
|
|
|
Screen size
|
|
===========
|
|
|
|
Certain commands to GDB may produce large amounts of information
|
|
output to the screen. To help you read all of it, GDB pauses and asks
|
|
you for input at the end of each page of output. Type when you
|
|
want to continue the output, or `q' to discard the remaining output.
|
|
Also, the screen width setting determines when to wrap lines of output.
|
|
Depending on what is being printed, GDB tries to break the line at a
|
|
readable place, rather than simply letting it overflow onto the
|
|
following line.
|
|
|
|
Normally GDB knows the size of the screen from the terminal driver
|
|
software. For example, on Unix GDB uses the termcap data base together
|
|
with the value of the `TERM' environment variable and the `stty rows'
|
|
and `stty cols' settings. If this is not correct, you can override it
|
|
with the `set height' and `set width' commands:
|
|
|
|
`set height LPP'
|
|
`show height'
|
|
`set width CPL'
|
|
`show width'
|
|
These `set' commands specify a screen height of LPP lines and a
|
|
screen width of CPL characters. The associated `show' commands
|
|
display the current settings.
|
|
|
|
If you specify a height of zero lines, GDB does not pause during
|
|
output no matter how long the output is. This is useful if output
|
|
is to a file or to an editor buffer.
|
|
|
|
Likewise, you can specify `set width 0' to prevent GDB from
|
|
wrapping its output.
|
|
|
|
|
|
File: gdb.info, Node: Numbers, Next: Messages/Warnings, Prev: Screen Size, Up: Controlling GDB
|
|
|
|
Numbers
|
|
=======
|
|
|
|
You can always enter numbers in octal, decimal, or hexadecimal in
|
|
GDB by the usual conventions: octal numbers begin with `0', decimal
|
|
numbers end with `.', and hexadecimal numbers begin with `0x'. Numbers
|
|
that begin with none of these are, by default, entered in base 10;
|
|
likewise, the default display for numbers--when no particular format is
|
|
specified--is base 10. You can change the default base for both input
|
|
and output with the `set radix' command.
|
|
|
|
`set input-radix BASE'
|
|
Set the default base for numeric input. Supported choices for
|
|
BASE are decimal 8, 10, or 16. BASE must itself be specified
|
|
either unambiguously or using the current default radix; for
|
|
example, any of
|
|
|
|
set radix 012
|
|
set radix 10.
|
|
set radix 0xa
|
|
|
|
sets the base to decimal. On the other hand, `set radix 10'
|
|
leaves the radix unchanged no matter what it was.
|
|
|
|
`set output-radix BASE'
|
|
Set the default base for numeric display. Supported choices for
|
|
BASE are decimal 8, 10, or 16. BASE must itself be specified
|
|
either unambiguously or using the current default radix.
|
|
|
|
`show input-radix'
|
|
Display the current default base for numeric input.
|
|
|
|
`show output-radix'
|
|
Display the current default base for numeric display.
|
|
|