maint agent
expression- Translate the given expression into remote agent bytecodes.
This command is useful for debugging the Agent Expression mechanism
(see Agent Expressions).
maint info breakpoints
- Using the same format as ‘info breakpoints’, display both the
breakpoints you've set explicitly, and those gdb is using for
internal purposes. Internal breakpoints are shown with negative
breakpoint numbers. The type column identifies what kind of breakpoint
is shown:
breakpoint
- Normal, explicitly set breakpoint.
watchpoint
- Normal, explicitly set watchpoint.
longjmp
- Internal breakpoint, used to handle correctly stepping through
longjmp
calls.
longjmp resume
- Internal breakpoint at the target of a
longjmp
.
until
- Temporary internal breakpoint used by the gdb
until
command.
finish
- Temporary internal breakpoint used by the gdb
finish
command.
shlib events
- Shared library events.
set displaced-stepping
show displaced-stepping
- Control whether or not gdb will do displaced stepping
if the target supports it. Displaced stepping is a way to single-step
over breakpoints without removing them from the inferior, by executing
an out-of-line copy of the instruction that was originally at the
breakpoint location. It is also known as out-of-line single-stepping.
set displaced-stepping on
- If the target architecture supports it, gdb will use
displaced stepping to step over breakpoints.
set displaced-stepping off
- gdb will not use displaced stepping to step over breakpoints,
even if such is supported by the target architecture.
set displaced-stepping auto
- This is the default mode. gdb will use displaced stepping
only if non-stop mode is active (see Non-Stop Mode) and the target
architecture supports displaced stepping.
maint check-symtabs
- Check the consistency of psymtabs and symtabs.
maint cplus first_component
name- Print the first C++ class/namespace component of name.
maint cplus namespace
- Print the list of possible C++ namespaces.
maint demangle
name- Demangle a C++ or Objective-C mangled name.
maint deprecate
command [replacement]maint undeprecate
command- Deprecate or undeprecate the named command. Deprecated commands
cause gdb to issue a warning when you use them. The optional
argument replacement says which newer command should be used in
favor of the deprecated one; if it is given, gdb will mention
the replacement as part of the warning.
maint dump-me
- Cause a fatal signal in the debugger and force it to dump its core.
This is supported only on systems which support aborting a program
with the
SIGQUIT
signal.
maint internal-error
[message-text]maint internal-warning
[message-text]- Cause gdb to call the internal function
internal_error
or internal_warning
and hence behave as though an internal error
or internal warning has been detected. In addition to reporting the
internal problem, these functions give the user the opportunity to
either quit gdb or create a core file of the current
gdb session.
These commands take an optional parameter message-text that is
used as the text of the error or warning message.
Here's an example of using internal-error
:
(gdb) maint internal-error testing, 1, 2
.../maint.c:121: internal-error: testing, 1, 2
A problem internal to GDB has been detected. Further
debugging may prove unreliable.
Quit this debugging session? (y or n) n
Create a core file? (y or n) n
(gdb)
maint set internal-error
action [ask|yes|no]
maint show internal-error
actionmaint set internal-warning
action [ask|yes|no]
maint show internal-warning
action- When gdb reports an internal problem (error or warning) it
gives the user the opportunity to both quit gdb and create a
core file of the current gdb session. These commands let you
override the default behaviour for each particular action,
described in the table below.
- ‘quit’
- You can specify that gdb should always (yes) or never (no)
quit. The default is to ask the user what to do.
- ‘corefile’
- You can specify that gdb should always (yes) or never (no)
create a core file. The default is to ask the user what to do.
maint packet
text- If gdb is talking to an inferior via the serial protocol,
then this command sends the string text to the inferior, and
displays the response packet. gdb supplies the initial
‘$’ character, the terminating ‘#’ character, and the
checksum.
maint print architecture
[file]- Print the entire architecture configuration. The optional argument
file names the file where the output goes.
maint print c-tdesc
- Print the current target description (see Target Descriptions) as
a C source file. The created source file can be used in gdb
when an XML parser is not available to parse the description.
maint print dummy-frames
- Prints the contents of gdb's internal dummy-frame stack.
(gdb) b add
...
(gdb) print add(2,3)
Breakpoint 2, add (a=2, b=3) at ...
58 return (a + b);
The program being debugged stopped while in a function called from GDB.
...
(gdb) maint print dummy-frames
0x1a57c80: pc=0x01014068 fp=0x0200bddc sp=0x0200bdd6
top=0x0200bdd4 id={stack=0x200bddc,code=0x101405c}
call_lo=0x01014000 call_hi=0x01014001
(gdb)
Takes an optional file parameter.
maint print registers
[file]maint print raw-registers
[file]maint print cooked-registers
[file]maint print register-groups
[file]- Print gdb's internal register data structures.
The command maint print raw-registers
includes the contents of
the raw register cache; the command maint print cooked-registers
includes the (cooked) value of all registers; and the command
maint print register-groups
includes the groups that each
register is a member of. See Registers.
These commands take an optional parameter, a file name to which to
write the information.
maint print reggroups
[file]- Print gdb's internal register group data structures. The
optional argument file tells to what file to write the
information.
The register groups info looks like this:
(gdb) maint print reggroups
Group Type
general user
float user
all user
vector user
system user
save internal
restore internal
flushregs
- This command forces gdb to flush its internal register cache.
maint print objfiles
- Print a dump of all known object files. For each object file, this
command prints its name, address in memory, and all of its psymtabs
and symtabs.
maint print statistics
- This command prints, for each object file in the program, various data
about that object file followed by the byte cache (bcache)
statistics for the object file. The objfile data includes the number
of minimal, partial, full, and stabs symbols, the number of types
defined by the objfile, the number of as yet unexpanded psym tables,
the number of line tables and string tables, and the amount of memory
used by the various tables. The bcache statistics include the counts,
sizes, and counts of duplicates of all and unique objects, max,
average, and median entry size, total memory used and its overhead and
savings, and various measures of the hash table size and chain
lengths.
maint print target-stack
- A target is an interface between the debugger and a particular
kind of file or process. Targets can be stacked in strata,
so that more than one target can potentially respond to a request.
In particular, memory accesses will walk down the stack of targets
until they find a target that is interested in handling that particular
address.
This command prints a short description of each layer that was pushed on
the target stack, starting from the top layer down to the bottom one.
maint print type
expr- Print the type chain for a type specified by expr. The argument
can be either a type name or a symbol. If it is a symbol, the type of
that symbol is described. The type chain produced by this command is
a recursive definition of the data type as stored in gdb's
data structures, including its flags and contained types.
maint set dwarf2 max-cache-age
maint show dwarf2 max-cache-age
- Control the DWARF 2 compilation unit cache.
In object files with inter-compilation-unit references, such as those
produced by the GCC option ‘-feliminate-dwarf2-dups’, the DWARF 2
reader needs to frequently refer to previously read compilation units.
This setting controls how long a compilation unit will remain in the
cache if it is not referenced. A higher limit means that cached
compilation units will be stored in memory longer, and more total
memory will be used. Setting it to zero disables caching, which will
slow down gdb startup, but reduce memory consumption.
maint set profile
maint show profile
- Control profiling of gdb.
Profiling will be disabled until you use the ‘maint set profile’
command to enable it. When you enable profiling, the system will begin
collecting timing and execution count data; when you disable profiling or
exit gdb, the results will be written to a log file. Remember that
if you use profiling, gdb will overwrite the profiling log file
(often called gmon.out). If you have a record of important profiling
data in a gmon.out file, be sure to move it to a safe location.
Configuring with ‘--enable-profiling’ arranges for gdb to be
compiled with the ‘-pg’ compiler option.
maint set show-debug-regs
maint show show-debug-regs
- Control whether to show variables that mirror the hardware debug
registers. Use
ON
to enable, OFF
to disable. If
enabled, the debug registers values are shown when gdb inserts or
removes a hardware breakpoint or watchpoint, and when the inferior
triggers a hardware-assisted breakpoint or watchpoint.
maint space
- Control whether to display memory usage for each command. If set to a
nonzero value, gdb will display how much memory each command
took, following the command's own output. This can also be requested
by invoking gdb with the --statistics command-line
switch (see Mode Options).
maint time
- Control whether to display the execution time for each command. If
set to a nonzero value, gdb will display how much time it
took to execute each command, following the command's own output.
The time is not printed for the commands that run the target, since
there's no mechanism currently to compute how much time was spend
by gdb and how much time was spend by the program been debugged.
it's not possibly currently
This can also be requested by invoking gdb with the
--statistics command-line switch (see Mode Options).
maint translate-address
[section] addr- Find the symbol stored at the location specified by the address
addr and an optional section name section. If found,
gdb prints the name of the closest symbol and an offset from
the symbol's location to the specified address. This is similar to
the
info address
command (see Symbols), except that this
command also allows to find symbols in other sections.
If section was not specified, the section in which the symbol was found
is also printed. For dynamically linked executables, the name of
executable or shared library containing the symbol is printed as well.