Red Hat ENTERPRISE LINUX 3 - DEBUGGING WITH GDB Manual page 329

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
itly, 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 resume
Internal breakpoint at the target of a
until
Temporary internal breakpoint used by the gdb
finish
Temporary internal breakpoint used by the gdb
shlib events
Shared library events.
maint internal-error
maint internal-warning
Cause gdb to call the internal function
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.
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.
Maintenance Commands
info breakpoints
longjmp
internal_error
, display both the breakpoints you've set explic-
longjmp
.
command.
until
command.
finish
or
internal_warning
Further
Appendix C.
calls.
and hence