Debugging with GDB (September 2007)

Chapter 20: GDB Annotations 263
20.9 Invalidation notices
The following annotations say that certain pieces of state may have changed:
^Z^Zframes-invalid
The frames (for example, output from the backtrace command) may have
changed.
^Z^Zbreakpoints-invalid
The breakpoints may have changed. For example, the user just added or deleted
a breakpoint.
20.10 Running the program
When the program starts executing due to a GDB command such as step or continue,
^Z^Zstarting
is output. When the program stops,
^Z^Zstopped
is output. Before the stopped annotation, a variety of annotations describe how the
program stopped.
^Z^Zexited exit-status
The program exited, and exit-status is the exit status (zero for successful exit,
otherwise nonzero).
^Z^Zsignalled
The program exited w ith a signal. After the ^Z^Zsignalled, the annotation
continues:
intro-text
^Z^Zsignal-name
name
^Z^Zsignal-name-end
middle-text
^Z^Zsignal-string
string
^Z^Zsignal-string-end
end-text
where name is the name of the signal, such as SIGILL or SIGSEGV, and string is
the explanation of the signal, such as Illegal Instruction or Segmentation
fault. intro-text, middle-text, and end-text are for the user’s benefit and have
no particular format.
^Z^Zsignal
The syntax of this annotation is just like signalled, but GDB is just saying
that the program received the signal, not that it was te rminated with it.
^Z^Zbreakpoint number
The program hit breakpoint number number.
^Z^Zwatchpoint number
The program hit watchp oint number number.