Debugging with GDB Manual HP WDB v6.3 (5900-2180, August 2012)

query When GDB wants the user to confirm a potentially dangerous
operation.
prompt-for-continue When GDB is asking the user to press return to continue. Note:
Don't expect this to work well; instead use set height 0 to
disable prompting. This is because the counting of lines is buggy
in the presence of annotations.
20.7 Errors
^Z^Zquit
This annotation occurs right before GDB responds to an interrupt.
^Z^Zerror
This annotation occurs right before GDB responds to an error.
Quit and error annotations indicate that any annotations which GDB was in the middle of may
end abruptly. For example, if a value-history-begin annotation is followed by a error, one
cannot expect to receive the matching value-history-end. One cannot expect not to receive
it either; however, an error annotation does not necessarily mean that GDB is immediately returning
all the way to the top level.
A quit or error annotation may be preceded by:
^Z^Zerror-begin
Any output between that and the quit or error annotation is the error message.
Warning messages are not yet annotated.
20.8 Information on breakpoints
The output from the info breakpoints command is annotated as follows:
^Z^Zbreakpoints-headers
header-entry
^Z^Zbreakpoints-table
where header-entry has the same syntax as an entry (see below) but instead of containing
data, it contains strings which are intended to convey the meaning of each field to the user. This
is followed by any number of entries. If a field does not apply for this entry, it is omitted. Fields
may contain trailing whitespace. Each entry consists of:
^Z^Zrecord
^Z^Zfield 0
number
^Z^Zfield 1
type
^Z^Zfield 2
disposition
^Z^Zfield 3
enable
^Z^Zfield 4
address
^Z^Zfield 5
what
^Z^Zfield 6
frame
^Z^Zfield 7
condition
^Z^Zfield 8
ignore-count
^Z^Zfield 9
commands
Note that address is intended for user consumption|the syntax varies depending on the language.
20.7 Errors 239