| 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: 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.
|
|
|
|
|
|
File: gdb.info, Node: Messages/Warnings, Next: Debugging Output, Prev: Numbers, Up: Controlling GDB
|
File: gdb.info, Node: Messages/Warnings, Next: Debugging Output, Prev: Numbers, Up: Controlling GDB
|
|
|
Optional warnings and messages
|
Optional warnings and messages
|
==============================
|
==============================
|
|
|
| Line 873... |
Line 799... |
ARGUMENTS
|
ARGUMENTS
|
|
|
where FUNCTION-NAME is the name of the function executing in the
|
where FUNCTION-NAME is the name of the function executing in the
|
frame, or `??' if not known, and ARGUMENTS are the arguments to
|
frame, or `??' if not known, and ARGUMENTS are the arguments to
|
the frame, with parentheses around them (each argument is annotated
|
the frame, with parentheses around them (each argument is annotated
|
individually as well, *note Value Annotations::.).
|
individually as well, *note Value Annotations::).
|
|
|
If source information is available, a reference to it is then
|
If source information is available, a reference to it is then
|
printed:
|
printed:
|
|
|
^Z^Zframe-source-begin
|
^Z^Zframe-source-begin
|
| Line 902... |
Line 828... |
^Z^Zframe-where
|
^Z^Zframe-where
|
INFORMATION
|
INFORMATION
|
|
|
Then, if source is to actually be displayed for this frame (for
|
Then, if source is to actually be displayed for this frame (for
|
example, this is not true for output from the `backtrace'
|
example, this is not true for output from the `backtrace'
|
command), then a `source' annotation (*note Source Annotations::.)
|
command), then a `source' annotation (*note Source Annotations::)
|
is displayed. Unlike most annotations, this is output instead of
|
is displayed. Unlike most annotations, this is output instead of
|
the normal text which would be output, not in addition.
|
the normal text which would be output, not in addition.
|
|
|
|
|
File: gdb.info, Node: Displays, Next: Prompting, Prev: Frame Annotations, Up: Annotations
|
File: gdb.info, Node: Displays, Next: Prompting, Prev: Frame Annotations, Up: Annotations
|
| Line 1499... |
Line 1425... |
|
|
* GDB/MI Result Records::
|
* GDB/MI Result Records::
|
* GDB/MI Stream Records::
|
* GDB/MI Stream Records::
|
* GDB/MI Out-of-band Records::
|
* GDB/MI Out-of-band Records::
|
|
|
|
|
|
File: gdb.info, Node: GDB/MI Result Records, Next: GDB/MI Stream Records, Up: GDB/MI Output Records
|
|
|
|
GDB/MI Result Records
|
|
---------------------
|
|
|
|
In addition to a number of out-of-band notifications, the response
|
|
to a GDB/MI command includes one of the following result indications:
|
|
|
|
`"^done" [ "," RESULTS ]'
|
|
The synchronous operation was successful, `RESULTS' is the return
|
|
value.
|
|
|
|
`"^running"'
|
|
The asynchronous operation was successfully started. The target is
|
|
running.
|
|
|
|
`"^error" "," C-STRING'
|
|
The operation failed. The `C-STRING' contains the corresponding
|
|
error message.
|
|
|
|
|
|
File: gdb.info, Node: GDB/MI Stream Records, Next: GDB/MI Out-of-band Records, Prev: GDB/MI Result Records, Up: GDB/MI Output Records
|
|
|
|
GDB/MI Stream Records
|
|
---------------------
|
|
|
|
GDB internally maintains a number of output streams: the console, the
|
|
target, and the log. The output intended for each of these streams is
|
|
funneled through the GDB/MI interface using "stream records".
|
|
|
|
Each stream record begins with a unique "prefix character" which
|
|
identifies its stream (*note GDB/MI Output Syntax: GDB/MI Output
|
|
Syntax.). In addition to the prefix, each stream record contains a
|
|
`STRING-OUTPUT'. This is either raw text (with an implicit new line)
|
|
or a quoted C string (which does not contain an implicit newline).
|
|
|
|
`"~" STRING-OUTPUT'
|
|
The console output stream contains text that should be displayed
|
|
in the CLI console window. It contains the textual responses to
|
|
CLI commands.
|
|
|
|
`"@" STRING-OUTPUT'
|
|
The target output stream contains any textual output from the
|
|
running target.
|
|
|
|
`"&" STRING-OUTPUT'
|
|
The LOG stream contains debugging messages being produced by GDB's
|
|
internals.
|
|
|
|
|
|
File: gdb.info, Node: GDB/MI Out-of-band Records, Prev: GDB/MI Stream Records, Up: GDB/MI Output Records
|
|
|
|
GDB/MI Out-of-band Records
|
|
--------------------------
|
|
|
|
"Out-of-band" records are used to notify the GDB/MI client of
|
|
additional changes that have occurred. Those changes can either be a
|
|
consequence of GDB/MI (e.g., a breakpoint modified) or a result of
|
|
target activity (e.g., target stopped).
|
|
|
|
The following is a preliminary list of possible out-of-band records.
|
|
|
|
`"*" "stop"'
|
