C. Maintenance Commands

In addition to commands intended for GDB users, GDB includes a number of commands intended for GDB developers. These commands are provided here for reference.

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.

maint internal-error

maint internal-warning

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.

(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)

Takes an optional parameter that is used as the text of the error or warning message.

maint print registers

maint print raw-registers

maint print cooked-registers

Print GDB's internal register data structures.

The command `maint print raw-registers' includes the contents of the raw register cache; and the command `maint print cooked-registers' includes the (cooked) value of all registers. See section `Registers' in GDB Internals.

Takes an optional file parameter.