180
Chapter 20. Configuration-Specific Information
time
Execution time in 60ths of a second.
You can refer to these values in gdb expressions with the usual conventions; for example,
b fputc
if $cycles
L
5000
sets a conditional breakpoint that suspends only after at least 5000 simulated
clock ticks.
20.4. Architectures
This section describes characteristics of architectures that affect all uses of gdb with the architecture,
both native and cross.
20.4.1. A29K
set rstack_high_address
address
On AMD 29000 family processors, registers are saved in a separate
register stack
. There is no
way for gdb to determine the extent of this stack. Normally, gdb just assumes that the stack
is "large enough". This may result in gdb referencing memory locations that do not exist. If
necessary, you can get around this problem by specifying the ending address of the register stack
with the
set rstack_high_address
command. The argument should be an address, which
you probably want to precede with
0x
to specify in hexadecimal.
show rstack_high_address
Display the current limit of the register stack, on AMD 29000 family processors.
20.4.2. Alpha
See the following section.
20.4.3. MIPS
Alpha- and MIPS-based computers use an unusual stack frame, which sometimes requires gdb to
search backward in the object code to find the beginning of a function.
To improve response time (especially for embedded applications, where gdb may be restricted to a
slow serial line for this search) you may want to limit the size of this search, using one of these
commands:
set heuristic-fence-post
limit
Restrict gdb to examining at most
limit
bytes in its search for the beginning of a function. A
value of
0
(the default) means there is no limit. However, except for
0
, the larger the limit the
more bytes
heuristic-fence-post
must search and therefore the longer it takes to run.
show heuristic-fence-post
Display the current limit.
These commands are available
only
when gdb is configured for debugging programs on Alpha or
MIPS processors.
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: ......