280
Chapter 27. gdb Annotations
Between these annotations is the main body of the frame, which can consist of
•
^Z^Zfunction-call
function-call-string
where
function-call-string
is text designed to convey to the user that this frame is associated
with a function call made by gdb to a function in the program being debugged.
•
^Z^Zsignal-handler-caller
signal-handler-caller-string
where
signal-handler-caller-string
is text designed to convey to the user that this frame
is associated with whatever mechanism is used by this operating system to call a signal handler (it
is the frame which calls the signal handler, not the frame for the signal handler itself).
•
A normal frame.
This can optionally (depending on whether this is thought of as interesting information for the user
to see) begin with
^Z^Zframe-address
address
^Z^Zframe-address-end
separator-string
where
address
is the address executing in the frame (the same address as in the
frame-begin
annotation, but printed in a form which is intended for user consumption--in particular, the syntax
varies depending on the language), and
separator-string
is a string intended to separate this
address from what follows for the user’s benefit.
Then comes
^Z^Zframe-function-name
function-name
^Z^Zframe-args
arguments
where
function-name
is the name of the function executing in the frame, or
??
if not known,
and
arguments
are the arguments to the frame, with parentheses around them (each argument is
annotated individually as well, (refer to Section 27.3
Values
).
If source information is available, a reference to it is then printed:
^Z^Zframe-source-begin
source-intro-string
^Z^Zframe-source-file
filename
^Z^Zframe-source-file-end
:
^Z^Zframe-source-line
line-number
^Z^Zframe-source-end
where
source-intro-string
separates for the user’s benefit the reference from the text which
precedes it,
filename
is the name of the source file, and
line-number
is the line number within
that file (the first line is line 1).
If gdb prints some information about where the frame is from (which library, which load segment,
etc.; currently only done on the RS/6000), it is annotated with
^Z^Zframe-where
information
Summary of Contents for ENTERPRISE LINUX 4 - DEVELOPER TOOLS GUIDE
Page 1: ...Red Hat Enterprise Linux 4 Debugging with gdb ...
Page 12: ...2 Chapter 1 Debugging with gdb ...
Page 28: ...18 Chapter 4 Getting In and Out of gdb ...
Page 34: ...24 Chapter 5 gdb Commands ...
Page 44: ...34 Chapter 6 Running Programs Under gdb ...
Page 68: ...58 Chapter 8 Examining the Stack ...
Page 98: ...88 Chapter 10 Examining Data ...
Page 112: ...102 Chapter 12 Tracepoints ...
Page 118: ...108 Chapter 13 Debugging Programs That Use Overlays ...
Page 138: ...128 Chapter 14 Using gdb with Different Languages ...
Page 144: ...134 Chapter 15 Examining the Symbol Table ...
Page 170: ...160 Chapter 19 Debugging remote programs ...
Page 198: ...188 Chapter 21 Controlling gdb ...
Page 204: ...194 Chapter 22 Canned Sequences of Commands ...
Page 206: ...196 Chapter 23 Command Interpreters ...
Page 216: ...206 Chapter 25 Using gdb under gnu Emacs ...
Page 296: ...286 Chapter 27 gdb Annotations ...
Page 300: ...290 Chapter 28 Reporting Bugs in gdb ...
Page 322: ...312 Chapter 30 Using History Interactively ...
Page 362: ...352 Appendix D gdb Remote Serial Protocol ...
Page 380: ...370 Appendix F GNU GENERAL PUBLIC LICENSE ...
Page 386: ...376 Appendix G GNU Free Documentation License ...
Page 410: ......