OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [gnu-stable/] [gdb-7.2/] [gdb/] [doc/] [gdbint.info-1] - Blame information for rev 841

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 342 jeremybenn
This is gdbint.info, produced by makeinfo version 4.13 from
2 330 jeremybenn
./gdbint.texinfo.
3
 
4
INFO-DIR-SECTION Software development
5
START-INFO-DIR-ENTRY
6
* Gdb-Internals: (gdbint).      The GNU debugger's internals.
7
END-INFO-DIR-ENTRY
8
 
9
   Copyright (C) 1990, 1991, 1992, 1993, 1994, 1996, 1998, 1999, 2000,
10
2001, 2002, 2003, 2004, 2005, 2006, 2008, 2009, 2010 Free Software
11
Foundation, Inc.  Contributed by Cygnus Solutions.  Written by John
12
Gilmore.  Second Edition by Stan Shebs.
13
 
14
   Permission is granted to copy, distribute and/or modify this document
15
under the terms of the GNU Free Documentation License, Version 1.3 or
16
any later version published by the Free Software Foundation; with no
17
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
18
Texts.  A copy of the license is included in the section entitled "GNU
19
Free Documentation License".
20
 
21
   This file documents the internals of the GNU debugger GDB.
22
 
23
   Copyright (C) 1990, 1991, 1992, 1993, 1994, 1996, 1998, 1999, 2000,
24
2001, 2002, 2003, 2004, 2005, 2006, 2008, 2009, 2010 Free Software
25
Foundation, Inc.  Contributed by Cygnus Solutions.  Written by John
26
Gilmore.  Second Edition by Stan Shebs.
27
 
28
   Permission is granted to copy, distribute and/or modify this document
29
under the terms of the GNU Free Documentation License, Version 1.3 or
30
any later version published by the Free Software Foundation; with no
31
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
32
Texts.  A copy of the license is included in the section entitled "GNU
33
Free Documentation License".
34
 
35

36
File: gdbint.info,  Node: Top,  Next: Summary,  Up: (dir)
37
 
38
Scope of this Document
39
**********************
40
 
41
This document documents the internals of the GNU debugger, GDB.  It
42
includes description of GDB's key algorithms and operations, as well as
43
the mechanisms that adapt GDB to specific hosts and targets.
44
 
45
* Menu:
46
 
47
* Summary::
48
* Overall Structure::
49
* Algorithms::
50
* User Interface::
51
* libgdb::
52
* Values::
53
* Stack Frames::
54
* Symbol Handling::
55
* Language Support::
56
* Host Definition::
57
* Target Architecture Definition::
58
* Target Descriptions::
59
* Target Vector Definition::
60
* Native Debugging::
61
* Support Libraries::
62
* Coding::
63
* Porting GDB::
64
* Versions and Branches::
65
* Start of New Year Procedure::
66
* Releasing GDB::
67
* Testsuite::
68
* Hints::
69
 
70
* GDB Observers::  GDB Currently available observers
71
* GNU Free Documentation License::  The license for this documentation
72
* Index::
73
 
74

75
File: gdbint.info,  Node: Summary,  Next: Overall Structure,  Prev: Top,  Up: Top
76
 
77
1 Summary
78
*********
79
 
80
* Menu:
81
 
82
* Requirements::
83
* Contributors::
84
 
85

86
File: gdbint.info,  Node: Requirements,  Next: Contributors,  Up: Summary
87
 
88
1.1 Requirements
89
================
90
 
91
Before diving into the internals, you should understand the formal
92
requirements and other expectations for GDB.  Although some of these
93
may seem obvious, there have been proposals for GDB that have run
94
counter to these requirements.
95
 
96
   First of all, GDB is a debugger.  It's not designed to be a front
97
panel for embedded systems.  It's not a text editor.  It's not a shell.
98
It's not a programming environment.
99
 
100
   GDB is an interactive tool.  Although a batch mode is available,
101
GDB's primary role is to interact with a human programmer.
102
 
103
   GDB should be responsive to the user.  A programmer hot on the trail
104
of a nasty bug, and operating under a looming deadline, is going to be
105
very impatient of everything, including the response time to debugger
106
commands.
107
 
108
   GDB should be relatively permissive, such as for expressions.  While
109
the compiler should be picky (or have the option to be made picky),
110
since source code lives for a long time usually, the programmer doing
111
debugging shouldn't be spending time figuring out to mollify the
112
debugger.
113
 
114
   GDB will be called upon to deal with really large programs.
115
Executable sizes of 50 to 100 megabytes occur regularly, and we've
116
heard reports of programs approaching 1 gigabyte in size.
117
 
118
   GDB should be able to run everywhere.  No other debugger is
119
available for even half as many configurations as GDB supports.
120
 
121

122
File: gdbint.info,  Node: Contributors,  Prev: Requirements,  Up: Summary
123
 
124
1.2 Contributors
125
================
126
 
127
The first edition of this document was written by John Gilmore of
128
Cygnus Solutions. The current second edition was written by Stan Shebs
129
of Cygnus Solutions, who continues to update the manual.
130
 
131
   Over the years, many others have made additions and changes to this
132
document. This section attempts to record the significant contributors
133
to that effort. One of the virtues of free software is that everyone is
134
free to contribute to it; with regret, we cannot actually acknowledge
135
everyone here.
136
 
137
     _Plea:_ This section has only been added relatively recently (four
138
     years after publication of the second edition). Additions to this
139
     section are particularly welcome.  If you or your friends (or
140
     enemies, to be evenhanded) have been unfairly omitted from this
141
     list, we would like to add your names!
142
 
143
   A document such as this relies on being kept up to date by numerous
144
small updates by contributing engineers as they make changes to the
145
code base. The file `ChangeLog' in the GDB distribution approximates a
146
blow-by-blow account. The most prolific contributors to this important,
147
but low profile task are Andrew Cagney (responsible for over half the
148
entries), Daniel Jacobowitz, Mark Kettenis, Jim Blandy and Eli
149
Zaretskii.
150
 
151
   Eli Zaretskii and Daniel Jacobowitz wrote the sections documenting
152
watchpoints.
153
 
154
   Jeremy Bennett updated the sections on initializing a new
155
architecture and register representation, and added the section on
156
Frame Interpretation.
157
 
158

159
File: gdbint.info,  Node: Overall Structure,  Next: Algorithms,  Prev: Summary,  Up: Top
160
 
161
2 Overall Structure
162
*******************
163
 
164
GDB consists of three major subsystems: user interface, symbol handling
165
(the "symbol side"), and target system handling (the "target side").
166
 
167
   The user interface consists of several actual interfaces, plus
168
supporting code.
169
 
170
   The symbol side consists of object file readers, debugging info
171
interpreters, symbol table management, source language expression
172
parsing, type and value printing.
173
 
174
   The target side consists of execution control, stack frame analysis,
175
and physical target manipulation.
176
 
177
   The target side/symbol side division is not formal, and there are a
178
number of exceptions.  For instance, core file support involves symbolic
179
elements (the basic core file reader is in BFD) and target elements (it
180
supplies the contents of memory and the values of registers).  Instead,
181
this division is useful for understanding how the minor subsystems
182
should fit together.
183
 
184
2.1 The Symbol Side
185
===================
186
 
187
The symbolic side of GDB can be thought of as "everything you can do in
188
GDB without having a live program running".  For instance, you can look
189
at the types of variables, and evaluate many kinds of expressions.
190
 
191
2.2 The Target Side
192
===================
193
 
194
The target side of GDB is the "bits and bytes manipulator".  Although
195
it may make reference to symbolic info here and there, most of the
196
target side will run with only a stripped executable available--or even
197
no executable at all, in remote debugging cases.
198
 
199
   Operations such as disassembly, stack frame crawls, and register
200
display, are able to work with no symbolic info at all.  In some cases,
201
such as disassembly, GDB will use symbolic info to present addresses
202
relative to symbols rather than as raw numbers, but it will work either
203
way.
204
 
205
2.3 Configurations
206
==================
207
 
208
"Host" refers to attributes of the system where GDB runs.  "Target"
209
refers to the system where the program being debugged executes.  In
210
most cases they are the same machine, in which case a third type of
211
"Native" attributes come into play.
212
 
213
   Defines and include files needed to build on the host are host
214
support.  Examples are tty support, system defined types, host byte
215
order, host float format.  These are all calculated by `autoconf' when
216
the debugger is built.
217
 
218
   Defines and information needed to handle the target format are target
219
dependent.  Examples are the stack frame format, instruction set,
220
breakpoint instruction, registers, and how to set up and tear down the
221
stack to call a function.
222
 
223
   Information that is only needed when the host and target are the
224
same, is native dependent.  One example is Unix child process support;
225
if the host and target are not the same, calling `fork' to start the
226
target process is a bad idea.  The various macros needed for finding the
227
registers in the `upage', running `ptrace', and such are all in the
228
native-dependent files.
229
 
230
   Another example of native-dependent code is support for features that
231
are really part of the target environment, but which require `#include'
232
files that are only available on the host system.  Core file handling
233
and `setjmp' handling are two common cases.
234
 
235
   When you want to make GDB work as the traditional native debugger on
236
a system, you will need to supply both target and native information.
237
 
238
2.4 Source Tree Structure
239
=========================
240
 
241
The GDB source directory has a mostly flat structure--there are only a
242
few subdirectories.  A file's name usually gives a hint as to what it
243
does; for example, `stabsread.c' reads stabs, `dwarf2read.c' reads
244
DWARF 2, etc.
245
 
246
   Files that are related to some common task have names that share
247
common substrings.  For example, `*-thread.c' files deal with debugging
248
threads on various platforms; `*read.c' files deal with reading various
249
kinds of symbol and object files; `inf*.c' files deal with direct
250
control of the "inferior program" (GDB parlance for the program being
251
debugged).
252
 
253
   There are several dozens of files in the `*-tdep.c' family.  `tdep'
254
stands for "target-dependent code"--each of these files implements
255
debug support for a specific target architecture (sparc, mips, etc).
256
Usually, only one of these will be used in a specific GDB configuration
257
(sometimes two, closely related).
258
 
259
   Similarly, there are many `*-nat.c' files, each one for native
260
debugging on a specific system (e.g., `sparc-linux-nat.c' is for native
261
debugging of Sparc machines running the Linux kernel).
262
 
263
   The few subdirectories of the source tree are:
264
 
265
`cli'
266
     Code that implements "CLI", the GDB Command-Line Interpreter.
267
     *Note Command Interpreter: User Interface.
268
 
269
`gdbserver'
270
     Code for the GDB remote server.
271
 
272
`gdbtk'
273
     Code for Insight, the GDB TK-based GUI front-end.
274
 
275
`mi'
276
     The "GDB/MI", the GDB Machine Interface interpreter.
277
 
278
`signals'
279
     Target signal translation code.
280
 
281
`tui'
282
     Code for "TUI", the GDB Text-mode full-screen User Interface.
283
     *Note TUI: User Interface.
284
 
285

286
File: gdbint.info,  Node: Algorithms,  Next: User Interface,  Prev: Overall Structure,  Up: Top
287
 
288
3 Algorithms
289
************
290
 
291
GDB uses a number of debugging-specific algorithms.  They are often not
292
very complicated, but get lost in the thicket of special cases and
293
real-world issues.  This chapter describes the basic algorithms and
294
mentions some of the specific target definitions that they use.
295
 
296
3.1 Prologue Analysis
297
=====================
298
 
299
To produce a backtrace and allow the user to manipulate older frames'
300
variables and arguments, GDB needs to find the base addresses of older
301
frames, and discover where those frames' registers have been saved.
302
Since a frame's "callee-saves" registers get saved by younger frames if
303
and when they're reused, a frame's registers may be scattered
304
unpredictably across younger frames.  This means that changing the
305
value of a register-allocated variable in an older frame may actually
306
entail writing to a save slot in some younger frame.
307
 
308
   Modern versions of GCC emit Dwarf call frame information ("CFI"),
309
which describes how to find frame base addresses and saved registers.
310
But CFI is not always available, so as a fallback GDB uses a technique
311
called "prologue analysis" to find frame sizes and saved registers.  A
312
prologue analyzer disassembles the function's machine code starting
313
from its entry point, and looks for instructions that allocate frame
314
space, save the stack pointer in a frame pointer register, save
315
registers, and so on.  Obviously, this can't be done accurately in
316
general, but it's tractable to do well enough to be very helpful.
317
Prologue analysis predates the GNU toolchain's support for CFI; at one
318
time, prologue analysis was the only mechanism GDB used for stack
319
unwinding at all, when the function calling conventions didn't specify
320
a fixed frame layout.
321
 
322
   In the olden days, function prologues were generated by hand-written,
323
target-specific code in GCC, and treated as opaque and untouchable by
324
optimizers.  Looking at this code, it was usually straightforward to
325
write a prologue analyzer for GDB that would accurately understand all
326
the prologues GCC would generate.  However, over time GCC became more
327
aggressive about instruction scheduling, and began to understand more
328
about the semantics of the prologue instructions themselves; in
329
response, GDB's analyzers became more complex and fragile.  Keeping the
330
prologue analyzers working as GCC (and the instruction sets themselves)
331
evolved became a substantial task.
332
 
333
   To try to address this problem, the code in `prologue-value.h' and
334
`prologue-value.c' provides a general framework for writing prologue
335
analyzers that are simpler and more robust than ad-hoc analyzers.  When
336
we analyze a prologue using the prologue-value framework, we're really
337
doing "abstract interpretation" or "pseudo-evaluation": running the
338
function's code in simulation, but using conservative approximations of
339
the values registers and memory would hold when the code actually runs.
340
For example, if our function starts with the instruction:
341
 
342
     addi r1, 42     # add 42 to r1
343
   we don't know exactly what value will be in `r1' after executing
344
this instruction, but we do know it'll be 42 greater than its original
345
value.
346
 
347
   If we then see an instruction like:
348
 
349
     addi r1, 22     # add 22 to r1
350
   we still don't know what `r1's' value is, but again, we can say it
351
is now 64 greater than its original value.
352
 
353
   If the next instruction were:
354
 
355
     mov r2, r1      # set r2 to r1's value
356
   then we can say that `r2's' value is now the original value of `r1'
357
plus 64.
358
 
359
   It's common for prologues to save registers on the stack, so we'll
360
need to track the values of stack frame slots, as well as the
361
registers.  So after an instruction like this:
362
 
363
     mov (fp+4), r2
364
   then we'd know that the stack slot four bytes above the frame pointer
365
holds the original value of `r1' plus 64.
366
 
367
   And so on.
368
 
369
   Of course, this can only go so far before it gets unreasonable.  If
370
we wanted to be able to say anything about the value of `r1' after the
371
instruction:
372
 
373
     xor r1, r3      # exclusive-or r1 and r3, place result in r1
374
   then things would get pretty complex.  But remember, we're just doing
375
a conservative approximation; if exclusive-or instructions aren't
376
relevant to prologues, we can just say `r1''s value is now "unknown".
377
We can ignore things that are too complex, if that loss of information
378
is acceptable for our application.
379
 
380
   So when we say "conservative approximation" here, what we mean is an
381
approximation that is either accurate, or marked "unknown", but never
382
inaccurate.
383
 
384
   Using this framework, a prologue analyzer is simply an interpreter
385
for machine code, but one that uses conservative approximations for the
386
contents of registers and memory instead of actual values.  Starting
387
from the function's entry point, you simulate instructions up to the
388
current PC, or an instruction that you don't know how to simulate.  Now
389
you can examine the state of the registers and stack slots you've kept
390
track of.
391
 
392
   * To see how large your stack frame is, just check the value of the
393
     stack pointer register; if it's the original value of the SP minus
394
     a constant, then that constant is the stack frame's size.  If the
395
     SP's value has been marked as "unknown", then that means the
396
     prologue has done something too complex for us to track, and we
397
     don't know the frame size.
398
 
399
   * To see where we've saved the previous frame's registers, we just
400
     search the values we've tracked -- stack slots, usually, but
401
     registers, too, if you want -- for something equal to the
402
     register's original value.  If the calling conventions suggest a
403
     standard place to save a given register, then we can check there
404
     first, but really, anything that will get us back the original
405
     value will probably work.
406
 
407
   This does take some work.  But prologue analyzers aren't
408
quick-and-simple pattern patching to recognize a few fixed prologue
409
forms any more; they're big, hairy functions.  Along with inferior
410
function calls, prologue analysis accounts for a substantial portion of
411
the time needed to stabilize a GDB port.  So it's worthwhile to look
412
for an approach that will be easier to understand and maintain.  In the
413
approach described above:
414
 
415
   * It's easier to see that the analyzer is correct: you just see
416
     whether the analyzer properly (albeit conservatively) simulates
417
     the effect of each instruction.
418
 
419
   * It's easier to extend the analyzer: you can add support for new
420
     instructions, and know that you haven't broken anything that
421
     wasn't already broken before.
422
 
423
   * It's orthogonal: to gather new information, you don't need to
424
     complicate the code for each instruction.  As long as your domain
425
     of conservative values is already detailed enough to tell you what
426
     you need, then all the existing instruction simulations are
427
     already gathering the right data for you.
428
 
429
 
430
   The file `prologue-value.h' contains detailed comments explaining
431
the framework and how to use it.
432
 
433
3.2 Breakpoint Handling
434
=======================
435
 
436
In general, a breakpoint is a user-designated location in the program
437
where the user wants to regain control if program execution ever reaches
438
that location.
439
 
440
   There are two main ways to implement breakpoints; either as
441
"hardware" breakpoints or as "software" breakpoints.
442
 
443
   Hardware breakpoints are sometimes available as a builtin debugging
444
features with some chips.  Typically these work by having dedicated
445
register into which the breakpoint address may be stored.  If the PC
446
(shorthand for "program counter") ever matches a value in a breakpoint
447
registers, the CPU raises an exception and reports it to GDB.
448
 
449
   Another possibility is when an emulator is in use; many emulators
450
include circuitry that watches the address lines coming out from the
451
processor, and force it to stop if the address matches a breakpoint's
452
address.
453
 
454
   A third possibility is that the target already has the ability to do
455
breakpoints somehow; for instance, a ROM monitor may do its own
456
software breakpoints.  So although these are not literally "hardware
457
breakpoints", from GDB's point of view they work the same; GDB need not
458
do anything more than set the breakpoint and wait for something to
459
happen.
460
 
461
   Since they depend on hardware resources, hardware breakpoints may be
462
limited in number; when the user asks for more, GDB will start trying
463
to set software breakpoints.  (On some architectures, notably the
464
32-bit x86 platforms, GDB cannot always know whether there's enough
465
hardware resources to insert all the hardware breakpoints and
466
watchpoints.  On those platforms, GDB prints an error message only when
467
the program being debugged is continued.)
468
 
469
   Software breakpoints require GDB to do somewhat more work.  The
470
basic theory is that GDB will replace a program instruction with a
471
trap, illegal divide, or some other instruction that will cause an
472
exception, and then when it's encountered, GDB will take the exception
473
and stop the program.  When the user says to continue, GDB will restore
474
the original instruction, single-step, re-insert the trap, and continue
475
on.
476
 
477
   Since it literally overwrites the program being tested, the program
478
area must be writable, so this technique won't work on programs in ROM.
479
It can also distort the behavior of programs that examine themselves,
480
although such a situation would be highly unusual.
481
 
482
   Also, the software breakpoint instruction should be the smallest
483
size of instruction, so it doesn't overwrite an instruction that might
484
be a jump target, and cause disaster when the program jumps into the
485
middle of the breakpoint instruction.  (Strictly speaking, the
486
breakpoint must be no larger than the smallest interval between
487
instructions that may be jump targets; perhaps there is an architecture
488
where only even-numbered instructions may jumped to.)  Note that it's
489
possible for an instruction set not to have any instructions usable for
490
a software breakpoint, although in practice only the ARC has failed to
491
define such an instruction.
492
 
493
   Basic breakpoint object handling is in `breakpoint.c'.  However,
494
much of the interesting breakpoint action is in `infrun.c'.
495
 
496
`target_remove_breakpoint (BP_TGT)'
497
`target_insert_breakpoint (BP_TGT)'
498
     Insert or remove a software breakpoint at address
499
     `BP_TGT->placed_address'.  Returns zero for success, non-zero for
500
     failure.  On input, BP_TGT contains the address of the breakpoint,
501
     and is otherwise initialized to zero.  The fields of the `struct
502
     bp_target_info' pointed to by BP_TGT are updated to contain other
503
     information about the breakpoint on output.  The field
504
     `placed_address' may be updated if the breakpoint was placed at a
505
     related address; the field `shadow_contents' contains the real
506
     contents of the bytes where the breakpoint has been inserted, if
507
     reading memory would return the breakpoint instead of the
508
     underlying memory; the field `shadow_len' is the length of memory
509
     cached in `shadow_contents', if any; and the field `placed_size'
510
     is optionally set and used by the target, if it could differ from
511
     `shadow_len'.
512
 
513
     For example, the remote target `Z0' packet does not require
514
     shadowing memory, so `shadow_len' is left at zero.  However, the
515
     length reported by `gdbarch_breakpoint_from_pc' is cached in
516
     `placed_size', so that a matching `z0' packet can be used to
517
     remove the breakpoint.
518
 
519
`target_remove_hw_breakpoint (BP_TGT)'
520
`target_insert_hw_breakpoint (BP_TGT)'
521
     Insert or remove a hardware-assisted breakpoint at address
522
     `BP_TGT->placed_address'.  Returns zero for success, non-zero for
523
     failure.  See `target_insert_breakpoint' for a description of the
524
     `struct bp_target_info' pointed to by BP_TGT; the
525
     `shadow_contents' and `shadow_len' members are not used for
526
     hardware breakpoints, but `placed_size' may be.
527
 
528
3.3 Single Stepping
529
===================
530
 
531
3.4 Signal Handling
532
===================
533
 
534
3.5 Thread Handling
535
===================
536
 
537
3.6 Inferior Function Calls
538
===========================
539
 
540
3.7 Longjmp Support
541
===================
542
 
543
GDB has support for figuring out that the target is doing a `longjmp'
544
and for stopping at the target of the jump, if we are stepping.  This
545
is done with a few specialized internal breakpoints, which are visible
546
in the output of the `maint info breakpoint' command.
547
 
548
   To make this work, you need to define a function called
549
`gdbarch_get_longjmp_target', which will examine the `jmp_buf'
550
structure and extract the `longjmp' target address.  Since `jmp_buf' is
551
target specific and typically defined in a target header not available
552
to GDB, you will need to determine the offset of the PC manually and
553
return that; many targets define a `jb_pc_offset' field in the tdep
554
structure to save the value once calculated.
555
 
556
3.8 Watchpoints
557
===============
558
 
559
Watchpoints are a special kind of breakpoints (*note breakpoints:
560
Algorithms.) which break when data is accessed rather than when some
561
instruction is executed.  When you have data which changes without your
562
knowing what code does that, watchpoints are the silver bullet to hunt
563
down and kill such bugs.
564
 
565
   Watchpoints can be either hardware-assisted or not; the latter type
566
is known as "software watchpoints."  GDB always uses hardware-assisted
567
watchpoints if they are available, and falls back on software
568
watchpoints otherwise.  Typical situations where GDB will use software
569
watchpoints are:
570
 
571
   * The watched memory region is too large for the underlying hardware
572
     watchpoint support.  For example, each x86 debug register can
573
     watch up to 4 bytes of memory, so trying to watch data structures
574
     whose size is more than 16 bytes will cause GDB to use software
575
     watchpoints.
576
 
577
   * The value of the expression to be watched depends on data held in
578
     registers (as opposed to memory).
579
 
580
   * Too many different watchpoints requested.  (On some architectures,
581
     this situation is impossible to detect until the debugged program
582
     is resumed.)  Note that x86 debug registers are used both for
583
     hardware breakpoints and for watchpoints, so setting too many
584
     hardware breakpoints might cause watchpoint insertion to fail.
585
 
586
   * No hardware-assisted watchpoints provided by the target
587
     implementation.
588
 
589
   Software watchpoints are very slow, since GDB needs to single-step
590
the program being debugged and test the value of the watched
591
expression(s) after each instruction.  The rest of this section is
592
mostly irrelevant for software watchpoints.
593
 
594
   When the inferior stops, GDB tries to establish, among other
595
possible reasons, whether it stopped due to a watchpoint being hit.  It
596
first uses `STOPPED_BY_WATCHPOINT' to see if any watchpoint was hit.
597
If not, all watchpoint checking is skipped.
598
 
599
   Then GDB calls `target_stopped_data_address' exactly once.  This
600
method returns the address of the watchpoint which triggered, if the
601
target can determine it.  If the triggered address is available, GDB
602
compares the address returned by this method with each watched memory
603
address in each active watchpoint.  For data-read and data-access
604
watchpoints, GDB announces every watchpoint that watches the triggered
605
address as being hit.  For this reason, data-read and data-access
606
watchpoints _require_ that the triggered address be available; if not,
607
read and access watchpoints will never be considered hit.  For
608
data-write watchpoints, if the triggered address is available, GDB
609
considers only those watchpoints which match that address; otherwise,
610
GDB considers all data-write watchpoints.  For each data-write
611
watchpoint that GDB considers, it evaluates the expression whose value
612
is being watched, and tests whether the watched value has changed.
613
Watchpoints whose watched values have changed are announced as hit.
614
 
615
   GDB uses several macros and primitives to support hardware
616
watchpoints:
617
 
618
`TARGET_CAN_USE_HARDWARE_WATCHPOINT (TYPE, COUNT, OTHER)'
619
     Return the number of hardware watchpoints of type TYPE that are
620
     possible to be set.  The value is positive if COUNT watchpoints of
621
     this type can be set, zero if setting watchpoints of this type is
622
     not supported, and negative if COUNT is more than the maximum
623
     number of watchpoints of type TYPE that can be set.  OTHER is
624
     non-zero if other types of watchpoints are currently enabled (there
625
     are architectures which cannot set watchpoints of different types
626
     at the same time).
627
 
628
`TARGET_REGION_OK_FOR_HW_WATCHPOINT (ADDR, LEN)'
629
     Return non-zero if hardware watchpoints can be used to watch a
630
     region whose address is ADDR and whose length in bytes is LEN.
631
 
632
`target_insert_watchpoint (ADDR, LEN, TYPE)'
633
`target_remove_watchpoint (ADDR, LEN, TYPE)'
634
     Insert or remove a hardware watchpoint starting at ADDR, for LEN
635
     bytes.  TYPE is the watchpoint type, one of the possible values of
636
     the enumerated data type `target_hw_bp_type', defined by
637
     `breakpoint.h' as follows:
638
 
639
           enum target_hw_bp_type
640
             {
641
               hw_write   = 0, /* Common (write) HW watchpoint */
642
               hw_read    = 1, /* Read    HW watchpoint */
643
               hw_access  = 2, /* Access (read or write) HW watchpoint */
644
               hw_execute = 3  /* Execute HW breakpoint */
645
             };
646
 
647
     These two macros should return 0 for success, non-zero for failure.
648
 
649
`target_stopped_data_address (ADDR_P)'
650
     If the inferior has some watchpoint that triggered, place the
651
     address associated with the watchpoint at the location pointed to
652
     by ADDR_P and return non-zero.  Otherwise, return zero.  This is
653
     required for data-read and data-access watchpoints.  It is not
654
     required for data-write watchpoints, but GDB uses it to improve
655
     handling of those also.
656
 
657
     GDB will only call this method once per watchpoint stop,
658
     immediately after calling `STOPPED_BY_WATCHPOINT'.  If the
659
     target's watchpoint indication is sticky, i.e., stays set after
660
     resuming, this method should clear it.  For instance, the x86 debug
661
     control register has sticky triggered flags.
662
 
663
`target_watchpoint_addr_within_range (TARGET, ADDR, START, LENGTH)'
664
     Check whether ADDR (as returned by `target_stopped_data_address')
665
     lies within the hardware-defined watchpoint region described by
666
     START and LENGTH.  This only needs to be provided if the
667
     granularity of a watchpoint is greater than one byte, i.e., if the
668
     watchpoint can also trigger on nearby addresses outside of the
669
     watched region.
670
 
671
`HAVE_STEPPABLE_WATCHPOINT'
672
     If defined to a non-zero value, it is not necessary to disable a
673
     watchpoint to step over it.  Like
674
     `gdbarch_have_nonsteppable_watchpoint', this is usually set when
675
     watchpoints trigger at the instruction which will perform an
676
     interesting read or write.  It should be set if there is a
677
     temporary disable bit which allows the processor to step over the
678
     interesting instruction without raising the watchpoint exception
679
     again.
680
 
681
`int gdbarch_have_nonsteppable_watchpoint (GDBARCH)'
682
     If it returns a non-zero value, GDB should disable a watchpoint to
683
     step the inferior over it.  This is usually set when watchpoints
684
     trigger at the instruction which will perform an interesting read
685
     or write.
686
 
687
`HAVE_CONTINUABLE_WATCHPOINT'
688
     If defined to a non-zero value, it is possible to continue the
689
     inferior after a watchpoint has been hit.  This is usually set
690
     when watchpoints trigger at the instruction following an
691
     interesting read or write.
692
 
693
`STOPPED_BY_WATCHPOINT (WAIT_STATUS)'
694
     Return non-zero if stopped by a watchpoint.  WAIT_STATUS is of the
695
     type `struct target_waitstatus', defined by `target.h'.  Normally,
696
     this macro is defined to invoke the function pointed to by the
697
     `to_stopped_by_watchpoint' member of the structure (of the type
698
     `target_ops', defined on `target.h') that describes the
699
     target-specific operations; `to_stopped_by_watchpoint' ignores the
700
     WAIT_STATUS argument.
701
 
702
     GDB does not require the non-zero value returned by
703
     `STOPPED_BY_WATCHPOINT' to be 100% correct, so if a target cannot
704
     determine for sure whether the inferior stopped due to a
705
     watchpoint, it could return non-zero "just in case".
706
 
707
3.8.1 Watchpoints and Threads
708
-----------------------------
709
 
710
GDB only supports process-wide watchpoints, which trigger in all
711
threads.  GDB uses the thread ID to make watchpoints act as if they
712
were thread-specific, but it cannot set hardware watchpoints that only
713
trigger in a specific thread.  Therefore, even if the target supports
714
threads, per-thread debug registers, and watchpoints which only affect
715
a single thread, it should set the per-thread debug registers for all
716
threads to the same value.  On GNU/Linux native targets, this is
717
accomplished by using `ALL_LWPS' in `target_insert_watchpoint' and
718
`target_remove_watchpoint' and by using `linux_set_new_thread' to
719
register a handler for newly created threads.
720
 
721
   GDB's GNU/Linux support only reports a single event at a time,
722
although multiple events can trigger simultaneously for multi-threaded
723
programs.  When multiple events occur, `linux-nat.c' queues subsequent
724
events and returns them the next time the program is resumed.  This
725
means that `STOPPED_BY_WATCHPOINT' and `target_stopped_data_address'
726
only need to consult the current thread's state--the thread indicated
727
by `inferior_ptid'.  If two threads have hit watchpoints
728
simultaneously, those routines will be called a second time for the
729
second thread.
730
 
731
3.8.2 x86 Watchpoints
732
---------------------
733
 
734
The 32-bit Intel x86 (a.k.a. ia32) processors feature special debug
735
registers designed to facilitate debugging.  GDB provides a generic
736
library of functions that x86-based ports can use to implement support
737
for watchpoints and hardware-assisted breakpoints.  This subsection
738
documents the x86 watchpoint facilities in GDB.
739
 
740
   (At present, the library functions read and write debug registers
741
directly, and are thus only available for native configurations.)
742
 
743
   To use the generic x86 watchpoint support, a port should do the
744
following:
745
 
746
   * Define the macro `I386_USE_GENERIC_WATCHPOINTS' somewhere in the
747
     target-dependent headers.
748
 
749
   * Include the `config/i386/nm-i386.h' header file _after_ defining
750
     `I386_USE_GENERIC_WATCHPOINTS'.
751
 
752
   * Add `i386-nat.o' to the value of the Make variable `NATDEPFILES'
753
     (*note NATDEPFILES: Native Debugging.).
754
 
755
   * Provide implementations for the `I386_DR_LOW_*' macros described
756
     below.  Typically, each macro should call a target-specific
757
     function which does the real work.
758
 
759
   The x86 watchpoint support works by maintaining mirror images of the
760
debug registers.  Values are copied between the mirror images and the
761
real debug registers via a set of macros which each target needs to
762
provide:
763
 
764
`I386_DR_LOW_SET_CONTROL (VAL)'
765
     Set the Debug Control (DR7) register to the value VAL.
766
 
767
`I386_DR_LOW_SET_ADDR (IDX, ADDR)'
768
     Put the address ADDR into the debug register number IDX.
769
 
770
`I386_DR_LOW_RESET_ADDR (IDX)'
771
     Reset (i.e. zero out) the address stored in the debug register
772
     number IDX.
773
 
774
`I386_DR_LOW_GET_STATUS'
775
     Return the value of the Debug Status (DR6) register.  This value is
776
     used immediately after it is returned by `I386_DR_LOW_GET_STATUS',
777
     so as to support per-thread status register values.
778
 
779
   For each one of the 4 debug registers (whose indices are from 0 to 3)
780
that store addresses, a reference count is maintained by GDB, to allow
781
sharing of debug registers by several watchpoints.  This allows users
782
to define several watchpoints that watch the same expression, but with
783
different conditions and/or commands, without wasting debug registers
784
which are in short supply.  GDB maintains the reference counts
785
internally, targets don't have to do anything to use this feature.
786
 
787
   The x86 debug registers can each watch a region that is 1, 2, or 4
788
bytes long.  The ia32 architecture requires that each watched region be
789
appropriately aligned: 2-byte region on 2-byte boundary, 4-byte region
790
on 4-byte boundary.  However, the x86 watchpoint support in GDB can
791
watch unaligned regions and regions larger than 4 bytes (up to 16
792
bytes) by allocating several debug registers to watch a single region.
793
This allocation of several registers per a watched region is also done
794
automatically without target code intervention.
795
 
796
   The generic x86 watchpoint support provides the following API for the
797
GDB's application code:
798
 
799
`i386_region_ok_for_watchpoint (ADDR, LEN)'
800
     The macro `TARGET_REGION_OK_FOR_HW_WATCHPOINT' is set to call this
801
     function.  It counts the number of debug registers required to
802
     watch a given region, and returns a non-zero value if that number
803
     is less than 4, the number of debug registers available to x86
804
     processors.
805
 
806
`i386_stopped_data_address (ADDR_P)'
807
     The target function `target_stopped_data_address' is set to call
808
     this function.  This function examines the breakpoint condition
809
     bits in the DR6 Debug Status register, as returned by the
810
     `I386_DR_LOW_GET_STATUS' macro, and returns the address associated
811
     with the first bit that is set in DR6.
812
 
813
`i386_stopped_by_watchpoint (void)'
814
     The macro `STOPPED_BY_WATCHPOINT' is set to call this function.
815
     The argument passed to `STOPPED_BY_WATCHPOINT' is ignored.  This
816
     function examines the breakpoint condition bits in the DR6 Debug
817
     Status register, as returned by the `I386_DR_LOW_GET_STATUS'
818
     macro, and returns true if any bit is set.  Otherwise, false is
819
     returned.
820
 
821
`i386_insert_watchpoint (ADDR, LEN, TYPE)'
822
`i386_remove_watchpoint (ADDR, LEN, TYPE)'
823
     Insert or remove a watchpoint.  The macros
824
     `target_insert_watchpoint' and `target_remove_watchpoint' are set
825
     to call these functions.  `i386_insert_watchpoint' first looks for
826
     a debug register which is already set to watch the same region for
827
     the same access types; if found, it just increments the reference
828
     count of that debug register, thus implementing debug register
829
     sharing between watchpoints.  If no such register is found, the
830
     function looks for a vacant debug register, sets its mirrored
831
     value to ADDR, sets the mirrored value of DR7 Debug Control
832
     register as appropriate for the LEN and TYPE parameters, and then
833
     passes the new values of the debug register and DR7 to the
834
     inferior by calling `I386_DR_LOW_SET_ADDR' and
835
     `I386_DR_LOW_SET_CONTROL'.  If more than one debug register is
836
     required to cover the given region, the above process is repeated
837
     for each debug register.
838
 
839
     `i386_remove_watchpoint' does the opposite: it resets the address
840
     in the mirrored value of the debug register and its read/write and
841
     length bits in the mirrored value of DR7, then passes these new
842
     values to the inferior via `I386_DR_LOW_RESET_ADDR' and
843
     `I386_DR_LOW_SET_CONTROL'.  If a register is shared by several
844
     watchpoints, each time a `i386_remove_watchpoint' is called, it
845
     decrements the reference count, and only calls
846
     `I386_DR_LOW_RESET_ADDR' and `I386_DR_LOW_SET_CONTROL' when the
847
     count goes to zero.
848
 
849
`i386_insert_hw_breakpoint (BP_TGT)'
850
`i386_remove_hw_breakpoint (BP_TGT)'
851
     These functions insert and remove hardware-assisted breakpoints.
852
     The macros `target_insert_hw_breakpoint' and
853
     `target_remove_hw_breakpoint' are set to call these functions.
854
     The argument is a `struct bp_target_info *', as described in the
855
     documentation for `target_insert_breakpoint'.  These functions
856
     work like `i386_insert_watchpoint' and `i386_remove_watchpoint',
857
     respectively, except that they set up the debug registers to watch
858
     instruction execution, and each hardware-assisted breakpoint
859
     always requires exactly one debug register.
860
 
861
`i386_cleanup_dregs (void)'
862
     This function clears all the reference counts, addresses, and
863
     control bits in the mirror images of the debug registers.  It
864
     doesn't affect the actual debug registers in the inferior process.
865
 
866
*Notes:*
867
  1. x86 processors support setting watchpoints on I/O reads or writes.
868
     However, since no target supports this (as of March 2001), and
869
     since `enum target_hw_bp_type' doesn't even have an enumeration
870
     for I/O watchpoints, this feature is not yet available to GDB
871
     running on x86.
872
 
873
  2. x86 processors can enable watchpoints locally, for the current task
874
     only, or globally, for all the tasks.  For each debug register,
875
     there's a bit in the DR7 Debug Control register that determines
876
     whether the associated address is watched locally or globally.  The
877
     current implementation of x86 watchpoint support in GDB always
878
     sets watchpoints to be locally enabled, since global watchpoints
879
     might interfere with the underlying OS and are probably
880
     unavailable in many platforms.
881
 
882
3.9 Checkpoints
883
===============
884
 
885
In the abstract, a checkpoint is a point in the execution history of
886
the program, which the user may wish to return to at some later time.
887
 
888
   Internally, a checkpoint is a saved copy of the program state,
889
including whatever information is required in order to restore the
890
program to that state at a later time.  This can be expected to include
891
the state of registers and memory, and may include external state such
892
as the state of open files and devices.
893
 
894
   There are a number of ways in which checkpoints may be implemented
895
in gdb, e.g. as corefiles, as forked processes, and as some opaque
896
method implemented on the target side.
897
 
898
   A corefile can be used to save an image of target memory and register
899
state, which can in principle be restored later -- but corefiles do not
900
typically include information about external entities such as open
901
files.  Currently this method is not implemented in gdb.
902
 
903
   A forked process can save the state of user memory and registers, as
904
well as some subset of external (kernel) state.  This method is used to
905
implement checkpoints on Linux, and in principle might be used on other
906
systems.
907
 
908
   Some targets, e.g. simulators, might have their own built-in method
909
for saving checkpoints, and gdb might be able to take advantage of that
910
capability without necessarily knowing any details of how it is done.
911
 
912
3.10 Observing changes in GDB internals
913
=======================================
914
 
915
In order to function properly, several modules need to be notified when
916
some changes occur in the GDB internals.  Traditionally, these modules
917
have relied on several paradigms, the most common ones being hooks and
918
gdb-events.  Unfortunately, none of these paradigms was versatile
919
enough to become the standard notification mechanism in GDB.  The fact
920
that they only supported one "client" was also a strong limitation.
921
 
922
   A new paradigm, based on the Observer pattern of the `Design
923
Patterns' book, has therefore been implemented.  The goal was to provide
924
a new interface overcoming the issues with the notification mechanisms
925
previously available.  This new interface needed to be strongly typed,
926
easy to extend, and versatile enough to be used as the standard
927
interface when adding new notifications.
928
 
929 342 jeremybenn
   See *note GDB Observers:: for a brief description of the observers
930 330 jeremybenn
currently implemented in GDB. The rationale for the current
931
implementation is also briefly discussed.
932
 
933

934
File: gdbint.info,  Node: User Interface,  Next: libgdb,  Prev: Algorithms,  Up: Top
935
 
936
4 User Interface
937
****************
938
 
939
GDB has several user interfaces, of which the traditional command-line
940
interface is perhaps the most familiar.
941
 
942
4.1 Command Interpreter
943
=======================
944
 
945
The command interpreter in GDB is fairly simple.  It is designed to
946
allow for the set of commands to be augmented dynamically, and also has
947
a recursive subcommand capability, where the first argument to a
948
command may itself direct a lookup on a different command list.
949
 
950
   For instance, the `set' command just starts a lookup on the
951
`setlist' command list, while `set thread' recurses to the
952
`set_thread_cmd_list'.
953
 
954
   To add commands in general, use `add_cmd'.  `add_com' adds to the
955
main command list, and should be used for those commands.  The usual
956
place to add commands is in the `_initialize_XYZ' routines at the ends
957
of most source files.
958
 
959
   To add paired `set' and `show' commands, use `add_setshow_cmd' or
960
`add_setshow_cmd_full'.  The former is a slightly simpler interface
961
which is useful when you don't need to further modify the new command
962
structures, while the latter returns the new command structures for
963
manipulation.
964
 
965
   Before removing commands from the command set it is a good idea to
966
deprecate them for some time.  Use `deprecate_cmd' on commands or
967
aliases to set the deprecated flag.  `deprecate_cmd' takes a `struct
968
cmd_list_element' as it's first argument.  You can use the return value
969
from `add_com' or `add_cmd' to deprecate the command immediately after
970
it is created.
971
 
972
   The first time a command is used the user will be warned and offered
973
a replacement (if one exists). Note that the replacement string passed
974
to `deprecate_cmd' should be the full name of the command, i.e., the
975
entire string the user should type at the command line.
976
 
977
4.2 UI-Independent Output--the `ui_out' Functions
978
=================================================
979
 
980
The `ui_out' functions present an abstraction level for the GDB output
981
code.  They hide the specifics of different user interfaces supported
982
by GDB, and thus free the programmer from the need to write several
983
versions of the same code, one each for every UI, to produce output.
984
 
985
4.2.1 Overview and Terminology
986
------------------------------
987
 
988
In general, execution of each GDB command produces some sort of output,
989
and can even generate an input request.
990
 
991
   Output can be generated for the following purposes:
992
 
993
   * to display a _result_ of an operation;
994
 
995
   * to convey _info_ or produce side-effects of a requested operation;
996
 
997
   * to provide a _notification_ of an asynchronous event (including
998
     progress indication of a prolonged asynchronous operation);
999
 
1000
   * to display _error messages_ (including warnings);
1001
 
1002
   * to show _debug data_;
1003
 
1004
   * to _query_ or prompt a user for input (a special case).
1005
 
1006
This section mainly concentrates on how to build result output,
1007
although some of it also applies to other kinds of output.
1008
 
1009
   Generation of output that displays the results of an operation
1010
involves one or more of the following:
1011
 
1012
   * output of the actual data
1013
 
1014
   * formatting the output as appropriate for console output, to make it
1015
     easily readable by humans
1016
 
1017
   * machine oriented formatting-a more terse formatting to allow for
1018
     easy parsing by programs which read GDB's output
1019
 
1020
   * annotation, whose purpose is to help legacy GUIs to identify
1021
     interesting parts in the output
1022
 
1023
   The `ui_out' routines take care of the first three aspects.
1024
Annotations are provided by separate annotation routines.  Note that use
1025
of annotations for an interface between a GUI and GDB is deprecated.
1026
 
1027
   Output can be in the form of a single item, which we call a "field";
1028
a "list" consisting of identical fields; a "tuple" consisting of
1029
non-identical fields; or a "table", which is a tuple consisting of a
1030
header and a body.  In a BNF-like form:
1031
 
1032
` ==>'
1033
     `
'
1034
 
1035
`
==>'
1036
     `{  }'
1037
 
1038
` ==>'
1039
     `  '</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1040</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1041</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`<body> ==>'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1042</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `{<row>}'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1043</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1044</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>4.2.2 General Conventions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1045</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1046</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1047</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Most `ui_out' routines are of type `void', the exceptions are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1048</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ui_out_stream_new' (which returns a pointer to the newly created</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1049</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>object) and the `make_cleanup' routines.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1050</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1051</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The first parameter is always the `ui_out' vector object, a pointer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1052</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to a `struct ui_out'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1053</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1054</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The FORMAT parameter is like in `printf' family of functions.  When</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1055</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>it is present, there must also be a variable list of arguments</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1056</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>sufficient used to satisfy the `%' specifiers in the supplied format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1057</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1058</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   When a character string argument is not used in a `ui_out' function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1059</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>call, a `NULL' pointer has to be supplied instead.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1060</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1061</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>4.2.3 Table, Tuple and List Functions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1062</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1063</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1064</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>This section introduces `ui_out' routines for building lists, tuples</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1065</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>and tables.  The routines to output the actual data items (fields) are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1066</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>presented in the next section.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1067</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1068</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   To recap: A "tuple" is a sequence of "fields", each field containing</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1069</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>information about an object; a "list" is a sequence of fields where</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1070</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>each field describes an identical object.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1071</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1072</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Use the "table" functions when your output consists of a list of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1073</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>rows (tuples) and the console output should include a heading.  Use this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1074</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>even when you are listing just one object but you still want the header.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1075</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1076</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Tables can not be nested.  Tuples and lists can be nested up to a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1077</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>maximum of five levels.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1078</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1079</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The overall structure of the table output code is something like</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1080</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>this:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1081</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1082</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ui_out_table_begin</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1083</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         ui_out_table_header</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1084</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1085</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         ui_out_table_body</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1086</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_tuple_begin</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1087</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             ui_out_field_*</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1088</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1089</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_tuple_end</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1090</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1091</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ui_out_table_end</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1092</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1093</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Here is the description of table-, tuple- and list-related `ui_out'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1094</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1095</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1096</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_table_begin (struct ui_out *UIOUT, int</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1097</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          NBROFCOLS, int NR_ROWS, const char *TBLID)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1098</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The function `ui_out_table_begin' marks the beginning of the output</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1099</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     of a table.  It should always be called before any other `ui_out'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1100</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function for a given table.  NBROFCOLS is the number of columns in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1101</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the table. NR_ROWS is the number of rows in the table.  TBLID is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1102</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     an optional string identifying the table.  The string pointed to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1103</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     by TBLID is copied by the implementation of `ui_out_table_begin',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1104</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     so the application can free the string if it was `malloc'ed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1105</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1106</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The companion function `ui_out_table_end', described below, marks</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1107</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the end of the table's output.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1108</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1109</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_table_header (struct ui_out *UIOUT, int</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1110</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          WIDTH, enum ui_align ALIGNMENT, const char *COLHDR)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1111</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `ui_out_table_header' provides the header information for a single</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1112</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     table column.  You call this function several times, one each for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1113</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     every column of the table, after `ui_out_table_begin', but before</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1114</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `ui_out_table_body'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1115</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1116</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The value of WIDTH gives the column width in characters.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1117</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     value of ALIGNMENT is one of `left', `center', and `right', and it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1118</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     specifies how to align the header: left-justify, center, or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1119</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     right-justify it.  COLHDR points to a string that specifies the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1120</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     column header; the implementation copies that string, so column</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1121</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     header strings in `malloc'ed storage can be freed after the call.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1122</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1123</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_table_body (struct ui_out *UIOUT)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1124</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function delimits the table header from the table body.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1125</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1126</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_table_end (struct ui_out *UIOUT)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1127</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function signals the end of a table's output.  It should be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1128</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     called after the table body has been produced by the list and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1129</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     field output functions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1130</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1131</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     There should be exactly one call to `ui_out_table_end' for each</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1132</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     call to `ui_out_table_begin', otherwise the `ui_out' functions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1133</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     will signal an internal error.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1134</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1135</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The output of the tuples that represent the table rows must follow</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1136</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the call to `ui_out_table_body' and precede the call to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1137</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ui_out_table_end'.  You build a tuple by calling `ui_out_tuple_begin'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1138</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>and `ui_out_tuple_end', with suitable calls to functions which actually</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1139</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>output fields between them.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1140</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1141</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_tuple_begin (struct ui_out *UIOUT, const char</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1142</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *ID)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1143</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function marks the beginning of a tuple output.  ID points to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1144</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     an optional string that identifies the tuple; it is copied by the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1145</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     implementation, and so strings in `malloc'ed storage can be freed</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1146</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     after the call.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1147</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1148</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_tuple_end (struct ui_out *UIOUT)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1149</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function signals an end of a tuple output.  There should be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1150</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     exactly one call to `ui_out_tuple_end' for each call to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1151</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `ui_out_tuple_begin', otherwise an internal GDB error will be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1152</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     signaled.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1153</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1154</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: struct cleanup * make_cleanup_ui_out_tuple_begin_end</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1155</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          (struct ui_out *UIOUT, const char *ID)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1156</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function first opens the tuple and then establishes a cleanup</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1157</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (*note Cleanups: Coding.) to close the tuple.  It provides a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1158</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     convenient and correct implementation of the non-portable(1) code</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1159</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     sequence:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1160</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          struct cleanup *old_cleanup;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1161</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          ui_out_tuple_begin (uiout, "...");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1162</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          old_cleanup = make_cleanup ((void(*)(void *)) ui_out_tuple_end,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1163</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                                      uiout);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1164</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1165</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_list_begin (struct ui_out *UIOUT, const char</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1166</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *ID)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1167</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function marks the beginning of a list output.  ID points to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1168</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     an optional string that identifies the list; it is copied by the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1169</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     implementation, and so strings in `malloc'ed storage can be freed</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1170</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     after the call.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1171</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1172</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_list_end (struct ui_out *UIOUT)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1173</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function signals an end of a list output.  There should be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1174</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     exactly one call to `ui_out_list_end' for each call to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1175</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `ui_out_list_begin', otherwise an internal GDB error will be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1176</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     signaled.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1177</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1178</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: struct cleanup * make_cleanup_ui_out_list_begin_end</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1179</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          (struct ui_out *UIOUT, const char *ID)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1180</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Similar to `make_cleanup_ui_out_tuple_begin_end', this function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1181</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     opens a list and then establishes cleanup (*note Cleanups: Coding.)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1182</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     that will close the list.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1183</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1184</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>4.2.4 Item Output Functions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1185</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1186</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1187</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The functions described below produce output for the actual data items,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1188</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>or fields, which contain information about the object.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1189</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1190</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Choose the appropriate function accordingly to your particular needs.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1191</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1192</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_field_fmt (struct ui_out *UIOUT, char</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1193</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *FLDNAME, char *FORMAT, ...)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1194</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This is the most general output function.  It produces the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1195</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     representation of the data in the variable-length argument list</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1196</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     according to formatting specifications in FORMAT, a `printf'-like</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1197</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     format string.  The optional argument FLDNAME supplies the name of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1198</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the field.  The data items themselves are supplied as additional</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1199</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     arguments after FORMAT.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1200</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1201</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This generic function should be used only when it is not possible</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1202</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     to use one of the specialized versions (see below).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1203</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1204</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_field_int (struct ui_out *UIOUT, const char</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1205</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *FLDNAME, int VALUE)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1206</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function outputs a value of an `int' variable.  It uses the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1207</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `"%d"' output conversion specification.  FLDNAME specifies the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1208</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     name of the field.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1209</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1210</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_field_fmt_int (struct ui_out *UIOUT, int</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1211</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          WIDTH, enum ui_align ALIGNMENT, const char *FLDNAME, int</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1212</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          VALUE)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1213</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function outputs a value of an `int' variable.  It differs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1214</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     from `ui_out_field_int' in that the caller specifies the desired</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1215</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     WIDTH and ALIGNMENT of the output.  FLDNAME specifies the name of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1216</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the field.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1217</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1218</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_field_core_addr (struct ui_out *UIOUT, const</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1219</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          char *FLDNAME, struct gdbarch *GDBARCH, CORE_ADDR ADDRESS)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1220</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function outputs an address as appropriate for GDBARCH.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1221</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1222</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_field_string (struct ui_out *UIOUT, const</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1223</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          char *FLDNAME, const char *STRING)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1224</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function outputs a string using the `"%s"' conversion</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1225</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     specification.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1226</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1227</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Sometimes, there's a need to compose your output piece by piece using</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1228</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions that operate on a stream, such as `value_print' or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1229</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`fprintf_symbol_filtered'.  These functions accept an argument of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1230</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>type `struct ui_file *', a pointer to a `ui_file' object used to store</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1231</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the data stream used for the output.  When you use one of these</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1232</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions, you need a way to pass their results stored in a `ui_file'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1233</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>object to the `ui_out' functions.  To this end, you first create a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1234</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ui_stream' object by calling `ui_out_stream_new', pass the `stream'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1235</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>member of that `ui_stream' object to `value_print' and similar</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1236</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions, and finally call `ui_out_field_stream' to output the field</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1237</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>you constructed.  When the `ui_stream' object is no longer needed, you</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1238</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>should destroy it and free its memory by calling `ui_out_stream_delete'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1239</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1240</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: struct ui_stream * ui_out_stream_new (struct ui_out</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1241</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *UIOUT)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1242</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function creates a new `ui_stream' object which uses the same</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1243</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     output methods as the `ui_out' object whose pointer is passed in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1244</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     UIOUT.  It returns a pointer to the newly created `ui_stream'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1245</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     object.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1246</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1247</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_stream_delete (struct ui_stream *STREAMBUF)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1248</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This functions destroys a `ui_stream' object specified by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1249</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     STREAMBUF.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1250</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1251</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_field_stream (struct ui_out *UIOUT, const</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1252</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          char *FIELDNAME, struct ui_stream *STREAMBUF)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1253</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function consumes all the data accumulated in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1254</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `streambuf->stream' and outputs it like `ui_out_field_string'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1255</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     does.  After a call to `ui_out_field_stream', the accumulated data</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1256</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     no longer exists, but the stream is still valid and may be used</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1257</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     for producing more fields.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1258</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1259</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   *Important:* If there is any chance that your code could bail out</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1260</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>before completing output generation and reaching the point where</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1261</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ui_out_stream_delete' is called, it is necessary to set up a cleanup,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1262</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to avoid leaking memory and other resources.  Here's a skeleton code to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1263</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>do that:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1264</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1265</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>      struct ui_stream *mybuf = ui_out_stream_new (uiout);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1266</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>      struct cleanup *old = make_cleanup (ui_out_stream_delete, mybuf);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1267</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>      ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1268</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>      do_cleanups (old);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1269</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1270</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If the function already has the old cleanup chain set (for other</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1271</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>kinds of cleanups), you just have to add your cleanup to it:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1272</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1273</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       mybuf = ui_out_stream_new (uiout);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1274</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       make_cleanup (ui_out_stream_delete, mybuf);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1275</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1276</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Note that with cleanups in place, you should not call</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1277</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ui_out_stream_delete' directly, or you would attempt to free the same</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1278</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>buffer twice.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1279</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1280</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>4.2.5 Utility Output Functions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1281</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1282</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1283</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_field_skip (struct ui_out *UIOUT, const char</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1284</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *FLDNAME)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1285</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function skips a field in a table.  Use it if you have to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1286</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     leave an empty field without disrupting the table alignment.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1287</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     argument FLDNAME specifies a name for the (missing) filed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1288</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1289</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_text (struct ui_out *UIOUT, const char</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1290</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *STRING)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1291</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function outputs the text in STRING in a way that makes it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1292</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     easy to be read by humans.  For example, the console</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1293</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     implementation of this method filters the text through a built-in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1294</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     pager, to prevent it from scrolling off the visible portion of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1295</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     screen.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1296</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1297</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Use this function for printing relatively long chunks of text</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1298</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     around the actual field data: the text it produces is not aligned</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1299</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     according to the table's format.  Use `ui_out_field_string' to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1300</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     output a string field, and use `ui_out_message', described below,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1301</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     to output short messages.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1302</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1303</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_spaces (struct ui_out *UIOUT, int NSPACES)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1304</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function outputs NSPACES spaces.  It is handy to align the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1305</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     text produced by `ui_out_text' with the rest of the table or list.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1306</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1307</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_message (struct ui_out *UIOUT, int VERBOSITY,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1308</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          const char *FORMAT, ...)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1309</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function produces a formatted message, provided that the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1310</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     current verbosity level is at least as large as given by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1311</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     VERBOSITY.  The current verbosity level is specified by the user</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1312</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     with the `set verbositylevel' command.(2)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1313</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1314</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_wrap_hint (struct ui_out *UIOUT, char *INDENT)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1315</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function gives the console output filter (a paging filter) a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1316</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     hint of where to break lines which are too long.  Ignored for all</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1317</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     other output consumers.  INDENT, if non-`NULL', is the string to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1318</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     be printed to indent the wrapped text on the next line; it must</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1319</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     remain accessible until the next call to `ui_out_wrap_hint', or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1320</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     until an explicit newline is produced by one of the other</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1321</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     functions.  If INDENT is `NULL', the wrapped text will not be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1322</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     indented.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1323</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1324</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void ui_out_flush (struct ui_out *UIOUT)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1325</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function flushes whatever output has been accumulated so far,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1326</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     if the UI buffers output.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1327</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1328</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>4.2.6 Examples of Use of `ui_out' functions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1329</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1330</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1331</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>This section gives some practical examples of using the `ui_out'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1332</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions to generalize the old console-oriented code in GDB.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1333</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>examples all come from functions defined on the `breakpoints.c' file.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1334</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1335</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   This example, from the `breakpoint_1' function, shows how to produce</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1336</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>a table.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1337</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1338</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The original code was:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1339</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1340</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>      if (!found_a_breakpoint++)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1341</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1342</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          annotate_breakpoints_headers ();</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1343</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1344</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          annotate_field (0);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1345</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          printf_filtered ("Num ");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1346</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          annotate_field (1);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1347</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          printf_filtered ("Type           ");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1348</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          annotate_field (2);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1349</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          printf_filtered ("Disp ");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1350</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          annotate_field (3);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1351</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          printf_filtered ("Enb ");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1352</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          if (addressprint)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1353</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1354</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>              annotate_field (4);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1355</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>              printf_filtered ("Address    ");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1356</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1357</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          annotate_field (5);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1358</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          printf_filtered ("What\n");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1359</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1360</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          annotate_breakpoints_table ();</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1361</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1362</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1363</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Here's the new version:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1364</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1365</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       nr_printable_breakpoints = ...;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1366</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1367</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (addressprint)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1368</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         ui_out_table_begin (ui, 6, nr_printable_breakpoints, "BreakpointTable");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1369</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       else</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1370</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         ui_out_table_begin (ui, 5, nr_printable_breakpoints, "BreakpointTable");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1371</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1372</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (nr_printable_breakpoints > 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1373</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         annotate_breakpoints_headers ();</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1374</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (nr_printable_breakpoints > 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1375</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         annotate_field (0);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1376</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ui_out_table_header (uiout, 3, ui_left, "number", "Num");                /* 1 */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1377</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (nr_printable_breakpoints > 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1378</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         annotate_field (1);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1379</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ui_out_table_header (uiout, 14, ui_left, "type", "Type");                /* 2 */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1380</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (nr_printable_breakpoints > 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1381</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         annotate_field (2);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1382</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ui_out_table_header (uiout, 4, ui_left, "disp", "Disp");         /* 3 */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1383</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (nr_printable_breakpoints > 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1384</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         annotate_field (3);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1385</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ui_out_table_header (uiout, 3, ui_left, "enabled", "Enb");       /* 4 */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1386</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (addressprint)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1387</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1388</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          if (nr_printable_breakpoints > 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1389</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            annotate_field (4);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1390</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          if (print_address_bits <= 32)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1391</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            ui_out_table_header (uiout, 10, ui_left, "addr", "Address");/* 5 */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1392</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          else</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1393</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            ui_out_table_header (uiout, 18, ui_left, "addr", "Address");/* 5 */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1394</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1395</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (nr_printable_breakpoints > 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1396</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         annotate_field (5);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1397</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ui_out_table_header (uiout, 40, ui_noalign, "what", "What");     /* 6 */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1398</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ui_out_table_body (uiout);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1399</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (nr_printable_breakpoints > 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1400</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         annotate_breakpoints_table ();</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1401</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1402</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   This example, from the `print_one_breakpoint' function, shows how to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1403</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>produce the actual data for the table whose structure was defined in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1404</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the above example.  The original code was:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1405</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1406</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        annotate_record ();</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1407</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        annotate_field (0);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1408</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        printf_filtered ("%-3d ", b->number);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1409</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        annotate_field (1);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1410</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        if ((int)b->type > (sizeof(bptypes)/sizeof(bptypes[0]))</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1411</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            || ((int) b->type != bptypes[(int) b->type].type))</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1412</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          internal_error ("bptypes table does not describe type #%d.",</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1413</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                          (int)b->type);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1414</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        printf_filtered ("%-14s ", bptypes[(int)b->type].description);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1415</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        annotate_field (2);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1416</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        printf_filtered ("%-4s ", bpdisps[(int)b->disposition]);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1417</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        annotate_field (3);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1418</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        printf_filtered ("%-3c ", bpenables[(int)b->enable]);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1419</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1420</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1421</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   This is the new version:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1422</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1423</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        annotate_record ();</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1424</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        ui_out_tuple_begin (uiout, "bkpt");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1425</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        annotate_field (0);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1426</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        ui_out_field_int (uiout, "number", b->number);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1427</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        annotate_field (1);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1428</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        if (((int) b->type > (sizeof (bptypes) / sizeof (bptypes[0])))</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1429</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            || ((int) b->type != bptypes[(int) b->type].type))</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1430</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          internal_error ("bptypes table does not describe type #%d.",</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1431</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                          (int) b->type);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1432</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        ui_out_field_string (uiout, "type", bptypes[(int)b->type].description);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1433</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        annotate_field (2);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1434</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        ui_out_field_string (uiout, "disp", bpdisps[(int)b->disposition]);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1435</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        annotate_field (3);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1436</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        ui_out_field_fmt (uiout, "enabled", "%c", bpenables[(int)b->enable]);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1437</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1438</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1439</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   This example, also from `print_one_breakpoint', shows how to produce</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1440</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>a complicated output field using the `print_expression' functions which</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1441</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>requires a stream to be passed.  It also shows how to automate stream</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1442</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>destruction with cleanups.  The original code was:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1443</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1444</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         annotate_field (5);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1445</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         print_expression (b->exp, gdb_stdout);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1446</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1447</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The new version is:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1448</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1449</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       struct ui_stream *stb = ui_out_stream_new (uiout);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1450</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       struct cleanup *old_chain = make_cleanup_ui_out_stream_delete (stb);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1451</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1452</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       annotate_field (5);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1453</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       print_expression (b->exp, stb->stream);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1454</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ui_out_field_stream (uiout, "what", local_stream);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1455</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1456</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   This example, also from `print_one_breakpoint', shows how to use</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1457</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ui_out_text' and `ui_out_field_string'.  The original code was:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1458</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1459</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       annotate_field (5);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1460</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (b->dll_pathname == NULL)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1461</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         printf_filtered ("<any library> ");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1462</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       else</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1463</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         printf_filtered ("library \"%s\" ", b->dll_pathname);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1464</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1465</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   It became:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1466</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1467</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       annotate_field (5);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1468</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (b->dll_pathname == NULL)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1469</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1470</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_field_string (uiout, "what", "<any library>");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1471</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_spaces (uiout, 1);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1472</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1473</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       else</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1474</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1475</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_text (uiout, "library \"");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1476</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_field_string (uiout, "what", b->dll_pathname);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1477</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_text (uiout, "\" ");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1478</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1479</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1480</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The following example from `print_one_breakpoint' shows how to use</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1481</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ui_out_field_int' and `ui_out_spaces'.  The original code was:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1482</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1483</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       annotate_field (5);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1484</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (b->forked_inferior_pid != 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1485</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         printf_filtered ("process %d ", b->forked_inferior_pid);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1486</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1487</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   It became:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1488</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1489</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       annotate_field (5);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1490</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (b->forked_inferior_pid != 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1491</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1492</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_text (uiout, "process ");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1493</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_field_int (uiout, "what", b->forked_inferior_pid);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1494</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_spaces (uiout, 1);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1495</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1496</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1497</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Here's an example of using `ui_out_field_string'.  The original code</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1498</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>was:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1499</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1500</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       annotate_field (5);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1501</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (b->exec_pathname != NULL)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1502</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         printf_filtered ("program \"%s\" ", b->exec_pathname);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1503</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1504</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   It became:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1505</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1506</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       annotate_field (5);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1507</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (b->exec_pathname != NULL)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1508</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1509</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_text (uiout, "program \"");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1510</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_field_string (uiout, "what", b->exec_pathname);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1511</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           ui_out_text (uiout, "\" ");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1512</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1513</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1514</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Finally, here's an example of printing an address.  The original</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1515</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>code:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1516</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1517</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       annotate_field (4);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1518</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       printf_filtered ("%s ",</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1519</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             hex_string_custom ((unsigned long) b->address, 8));</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1520</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1521</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   It became:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1522</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1523</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       annotate_field (4);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1524</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ui_out_field_core_addr (uiout, "Address", b->address);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1525</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1526</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>4.3 Console Printing</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1527</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>====================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1528</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1529</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>4.4 TUI</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1530</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=======</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1531</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1532</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------- Footnotes ----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1533</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1534</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   (1) The function cast is not portable ISO C.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1535</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1536</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   (2) As of this writing (April 2001), setting verbosity level is not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1537</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>yet implemented, and is always returned as zero.  So calling</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1538</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ui_out_message' with a VERBOSITY argument more than zero will cause</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1539</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the message to never be printed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1540</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1541</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1542</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: libgdb,  Next: Values,  Prev: User Interface,  Up: Top</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1543</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1544</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>5 libgdb</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1545</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>********</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1546</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1547</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>5.1 libgdb 1.0</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1548</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==============</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1549</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1550</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`libgdb' 1.0 was an abortive project of years ago.  The theory was to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1551</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>provide an API to GDB's functionality.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1552</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1553</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>5.2 libgdb 2.0</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1554</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==============</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1555</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1556</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`libgdb' 2.0 is an ongoing effort to update GDB so that is better able</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1557</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to support graphical and other environments.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1558</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1559</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Since `libgdb' development is on-going, its architecture is still</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1560</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>evolving.  The following components have so far been identified:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1561</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1562</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Observer - `gdb-events.h'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1563</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1564</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Builder - `ui-out.h'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1565</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1566</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Event Loop - `event-loop.h'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1567</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1568</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Library - `gdb.h'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1569</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1570</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The model that ties these components together is described below.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1571</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1572</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>5.3 The `libgdb' Model</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1573</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>======================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1574</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1575</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>A client of `libgdb' interacts with the library in two ways.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1576</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1577</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * As an observer (using `gdb-events') receiving notifications from</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1578</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `libgdb' of any internal state changes (break point changes, run</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1579</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     state, etc).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1580</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1581</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * As a client querying `libgdb' (using the `ui-out' builder) to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1582</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     obtain various status values from GDB.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1583</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1584</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Since `libgdb' could have multiple clients (e.g., a GUI supporting</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1585</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the existing GDB CLI), those clients must co-operate when controlling</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1586</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`libgdb'.  In particular, a client must ensure that `libgdb' is idle</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1587</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(i.e. no other client is using `libgdb') before responding to a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1588</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb-event' by making a query.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1589</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1590</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>5.4 CLI support</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1591</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>===============</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1592</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1593</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>At present GDB's CLI is very much entangled in with the core of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1594</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`libgdb'.  Consequently, a client wishing to include the CLI in their</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1595</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>interface needs to carefully co-ordinate its own and the CLI's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1596</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>requirements.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1597</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1598</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   It is suggested that the client set `libgdb' up to be bi-modal</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1599</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(alternate between CLI and client query modes).  The notes below sketch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1600</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>out the theory:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1601</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1602</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The client registers itself as an observer of `libgdb'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1603</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1604</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The client create and install `cli-out' builder using its own</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1605</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     versions of the `ui-file' `gdb_stderr', `gdb_stdtarg' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1606</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdb_stdout' streams.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1607</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1608</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The client creates a separate custom `ui-out' builder that is only</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1609</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     used while making direct queries to `libgdb'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1610</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1611</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   When the client receives input intended for the CLI, it simply</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1612</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>passes it along.  Since the `cli-out' builder is installed by default,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1613</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>all the CLI output in response to that command is routed (pronounced</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1614</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>rooted) through to the client controlled `gdb_stdout' et. al. streams.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1615</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>At the same time, the client is kept abreast of internal changes by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1616</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>virtue of being a `libgdb' observer.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1617</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1618</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The only restriction on the client is that it must wait until</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1619</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`libgdb' becomes idle before initiating any queries (using the client's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1620</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>custom builder).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1621</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1622</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>5.5 `libgdb' components</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1623</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=======================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1624</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1625</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Observer - `gdb-events.h'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1626</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1627</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1628</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb-events' provides the client with a very raw mechanism that can be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1629</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>used to implement an observer.  At present it only allows for one</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1630</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>observer and that observer must, internally, handle the need to delay</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1631</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the processing of any event notifications until after `libgdb' has</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1632</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>finished the current command.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1633</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1634</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Builder - `ui-out.h'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1635</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1636</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1637</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ui-out' provides the infrastructure necessary for a client to create a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1638</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>builder.  That builder is then passed down to `libgdb' when doing any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1639</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>queries.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1640</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1641</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Event Loop - `event-loop.h'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1642</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1643</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1644</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`event-loop', currently non-re-entrant, provides a simple event loop.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1645</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>A client would need to either plug its self into this loop or,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1646</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>implement a new event-loop that GDB would use.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1647</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1648</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The event-loop will eventually be made re-entrant.  This is so that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1649</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB can better handle the problem of some commands blocking instead of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1650</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>returning.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1651</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1652</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Library - `gdb.h'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1653</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1654</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1655</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`libgdb' is the most obvious component of this system.  It provides the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1656</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>query interface.  Each function is parameterized by a `ui-out' builder.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1657</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The result of the query is constructed using that builder before the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1658</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>query function returns.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1659</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1660</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1661</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Values,  Next: Stack Frames,  Prev: libgdb,  Up: Top</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1662</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1663</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>6 Values</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1664</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>********</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1665</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1666</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>6.1 Values</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1667</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==========</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1668</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1669</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB uses `struct value', or "values", as an internal abstraction for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1670</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the representation of a variety of inferior objects and GDB convenience</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1671</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>objects.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1672</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1673</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Values have an associated `struct type', that describes a virtual</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1674</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>view of the raw data or object stored in or accessed through the value.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1675</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1676</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A value is in addition discriminated by its lvalue-ness, given its</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1677</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`enum lval_type' enumeration type:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1678</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1679</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>``not_lval''</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1680</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This value is not an lval.  It can't be assigned to.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1681</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1682</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>``lval_memory''</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1683</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This value represents an object in memory.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1684</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1685</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>``lval_register''</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1686</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This value represents an object that lives in a register.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1687</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1688</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>``lval_internalvar''</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1689</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Represents the value of an internal variable.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1690</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1691</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>``lval_internalvar_component''</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1692</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Represents part of a GDB internal variable.  E.g., a structure</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1693</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     field.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1694</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1695</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>``lval_computed''</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1696</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     These are "computed" values.  They allow creating specialized value</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1697</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     objects for specific purposes, all abstracted away from the core</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1698</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     value support code.  The creator of such a value writes specialized</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1699</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     functions to handle the reading and writing to/from the value's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1700</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     backend data, and optionally, a "copy operator" and a "destructor".</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1701</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1702</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Pointers to these functions are stored in a `struct lval_funcs'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1703</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     instance (declared in `value.h'), and passed to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1704</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `allocate_computed_value' function, as in the example below.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1705</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1706</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          static void</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1707</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          nil_value_read (struct value *v)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1708</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1709</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            /* This callback reads data from some backend, and stores it in V.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1710</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               In this case, we always read null data.  You'll want to fill in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1711</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               something more interesting.  */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1712</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1713</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            memset (value_contents_all_raw (v),</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1714</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                    value_offset (v),</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1715</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                    TYPE_LENGTH (value_type (v)));</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1716</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1717</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1718</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          static void</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1719</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          nil_value_write (struct value *v, struct value *fromval)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1720</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1721</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            /* Takes the data from FROMVAL and stores it in the backend of V.  */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1722</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1723</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            to_oblivion (value_contents_all_raw (fromval),</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1724</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                         value_offset (v),</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1725</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                         TYPE_LENGTH (value_type (fromval)));</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1726</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1727</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1728</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          static struct lval_funcs nil_value_funcs =</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1729</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1730</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>              nil_value_read,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1731</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>              nil_value_write</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1732</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            };</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1733</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1734</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          struct value *</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1735</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          make_nil_value (void)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1736</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1737</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             struct type *type;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1738</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             struct value *v;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1739</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1740</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             type = make_nils_type ();</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1741</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             v = allocate_computed_value (type, &nil_value_funcs, NULL);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1742</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1743</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             return v;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1744</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1745</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1746</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     See the implementation of the `$_siginfo' convenience variable in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1747</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `infrun.c' as a real example use of lval_computed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1748</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1749</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1750</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1751</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Stack Frames,  Next: Symbol Handling,  Prev: Values,  Up: Top</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1752</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1753</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>7 Stack Frames</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1754</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>**************</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1755</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1756</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>A frame is a construct that GDB uses to keep track of calling and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1757</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>called functions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1758</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1759</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB's frame model, a fresh design, was implemented with the need to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1760</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>support DWARF's Call Frame Information in mind.  In fact, the term</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1761</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"unwind" is taken directly from that specification.  Developers wishing</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1762</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to learn more about unwinders, are encouraged to read the DWARF</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1763</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>specification, available from `http://www.dwarfstd.org'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1764</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1765</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB's model is that you find a frame's registers by "unwinding" them</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1766</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>from the next younger frame.  That is, `get_frame_register' which</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1767</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>returns the value of a register in frame #1 (the next-to-youngest</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1768</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame), is implemented by calling frame #0's `frame_register_unwind'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1769</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(the youngest frame).  But then the obvious question is: how do you</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1770</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>access the registers of the youngest frame itself?</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1771</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1772</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   To answer this question, GDB has the "sentinel" frame, the "-1st"</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1773</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame.  Unwinding registers from the sentinel frame gives you the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1774</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>current values of the youngest real frame's registers.  If F is a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1775</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>sentinel frame, then `get_frame_type (F) == SENTINEL_FRAME'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1776</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1777</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>7.1 Selecting an Unwinder</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1778</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1779</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1780</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The architecture registers a list of frame unwinders (`struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1781</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame_unwind'), using the functions `frame_unwind_prepend_unwinder' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1782</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`frame_unwind_append_unwinder'.  Each unwinder includes a sniffer.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1783</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Whenever GDB needs to unwind a frame (to fetch the previous frame's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1784</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>registers or the current frame's ID), it calls registered sniffers in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1785</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>order to find one which recognizes the frame.  The first time a sniffer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1786</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>returns non-zero, the corresponding unwinder is assigned to the frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1787</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1788</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>7.2 Unwinding the Frame ID</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1789</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1790</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1791</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Every frame has an associated ID, of type `struct frame_id'.  The ID</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1792</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>includes the stack base and function start address for the frame.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1793</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>ID persists through the entire life of the frame, including while other</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1794</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>called frames are running; it is used to locate an appropriate `struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1795</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame_info' from the cache.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1796</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1797</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Every time the inferior stops, and at various other times, the frame</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1798</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>cache is flushed.  Because of this, parts of GDB which need to keep</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1799</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>track of individual frames cannot use pointers to `struct frame_info'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1800</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>A frame ID provides a stable reference to a frame, even when the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1801</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>unwinder must be run again to generate a new `struct frame_info' for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1802</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the same frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1803</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1804</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The frame's unwinder's `this_id' method is called to find the ID.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1805</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Note that this is different from register unwinding, where the next</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1806</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame's `prev_register' is called to unwind this frame's registers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1807</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1808</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Both stack base and function address are required to identify the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1809</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame, because a recursive function has the same function address for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1810</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>two consecutive frames and a leaf function may have the same stack</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1811</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>address as its caller.  On some platforms, a third address is part of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1812</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the ID to further disambiguate frames--for instance, on IA-64 the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1813</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>separate register stack address is included in the ID.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1814</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1815</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   An invalid frame ID (`outer_frame_id') returned from the `this_id'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1816</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>method means to stop unwinding after this frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1817</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1818</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   `null_frame_id' is another invalid frame ID which should be used</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1819</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>when there is no frame.  For instance, certain breakpoints are attached</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1820</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to a specific frame, and that frame is identified through its frame ID</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1821</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(we use this to implement the "finish" command).  Using `null_frame_id'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1822</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>as the frame ID for a given breakpoint means that the breakpoint is not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1823</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>specific to any frame.  The `this_id' method should never return</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1824</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`null_frame_id'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1825</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1826</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>7.3 Unwinding Registers</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1827</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=======================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1828</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1829</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Each unwinder includes a `prev_register' method.  This method takes a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1830</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame, an associated cache pointer, and a register number.  It returns</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1831</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>a `struct value *' describing the requested register, as saved by this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1832</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame.  This is the value of the register that is current in this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1833</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame's caller.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1834</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1835</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The returned value must have the same type as the register.  It may</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1836</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>have any lvalue type.  In most circumstances one of these routines will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1837</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>generate the appropriate value:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1838</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1839</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`frame_unwind_got_optimized'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1840</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This register was not saved.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1841</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1842</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`frame_unwind_got_register'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1843</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This register was copied into another register in this frame.  This</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1844</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     is also used for unchanged registers; they are "copied" into the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1845</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     same register.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1846</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1847</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`frame_unwind_got_memory'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1848</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This register was saved in memory.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1849</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1850</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`frame_unwind_got_constant'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1851</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This register was not saved, but the unwinder can compute the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1852</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     previous value some other way.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1853</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1854</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`frame_unwind_got_address'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1855</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Same as `frame_unwind_got_constant', except that the value is a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1856</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     target address.  This is frequently used for the stack pointer,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1857</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     which is not explicitly saved but has a known offset from this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1858</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     frame's stack pointer.  For architectures with a flat unified</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1859</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     address space, this is generally the same as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1860</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `frame_unwind_got_constant'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1861</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1862</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1863</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Symbol Handling,  Next: Language Support,  Prev: Stack Frames,  Up: Top</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1864</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1865</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8 Symbol Handling</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1866</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>*****************</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1867</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1868</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Symbols are a key part of GDB's operation.  Symbols include variables,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1869</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions, and types.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1870</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1871</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Symbol information for a large program can be truly massive, and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1872</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>reading of symbol information is one of the major performance</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1873</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>bottlenecks in GDB; it can take many minutes to process it all.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1874</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Studies have shown that nearly all the time spent is computational,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1875</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>rather than file reading.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1876</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1877</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   One of the ways for GDB to provide a good user experience is to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1878</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>start up quickly, taking no more than a few seconds.  It is simply not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1879</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>possible to process all of a program's debugging info in that time, and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1880</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>so we attempt to handle symbols incrementally.  For instance, we create</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1881</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"partial symbol tables" consisting of only selected symbols, and only</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1882</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>expand them to full symbol tables when necessary.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1883</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1884</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.1 Symbol Reading</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1885</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1886</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1887</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB reads symbols from "symbol files".  The usual symbol file is the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1888</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>file containing the program which GDB is debugging.  GDB can be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1889</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>directed to use a different file for symbols (with the `symbol-file'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1890</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>command), and it can also read more symbols via the `add-file' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1891</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`load' commands. In addition, it may bring in more symbols while</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1892</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>loading shared libraries.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1893</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1894</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Symbol files are initially opened by code in `symfile.c' using the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1895</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>BFD library (*note Support Libraries::).  BFD identifies the type of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1896</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the file by examining its header.  `find_sym_fns' then uses this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1897</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>identification to locate a set of symbol-reading functions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1898</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1899</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Symbol-reading modules identify themselves to GDB by calling</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1900</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`add_symtab_fns' during their module initialization.  The argument to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1901</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`add_symtab_fns' is a `struct sym_fns' which contains the name (or name</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1902</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>prefix) of the symbol format, the length of the prefix, and pointers to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1903</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>four functions.  These functions are called at various times to process</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1904</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>symbol files whose identification matches the specified prefix.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1905</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1906</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The functions supplied by each module are:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1907</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1908</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`XYZ_symfile_init(struct sym_fns *sf)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1909</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Called from `symbol_file_add' when we are about to read a new</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1910</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     symbol file.  This function should clean up any internal state</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1911</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (possibly resulting from half-read previous files, for example)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1912</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     and prepare to read a new symbol file.  Note that the symbol file</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1913</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     which we are reading might be a new "main" symbol file, or might</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1914</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     be a secondary symbol file whose symbols are being added to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1915</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     existing symbol table.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1916</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1917</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The argument to `XYZ_symfile_init' is a newly allocated `struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1918</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     sym_fns' whose `bfd' field contains the BFD for the new symbol</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1919</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     file being read.  Its `private' field has been zeroed, and can be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1920</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     modified as desired.  Typically, a struct of private information</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1921</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     will be `malloc''d, and a pointer to it will be placed in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1922</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `private' field.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1923</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1924</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     There is no result from `XYZ_symfile_init', but it can call</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1925</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `error' if it detects an unavoidable problem.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1926</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1927</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`XYZ_new_init()'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1928</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Called from `symbol_file_add' when discarding existing symbols.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1929</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function needs only handle the symbol-reading module's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1930</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     internal state; the symbol table data structures visible to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1931</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     rest of GDB will be discarded by `symbol_file_add'.  It has no</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1932</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     arguments and no result.  It may be called after</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1933</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `XYZ_symfile_init', if a new symbol table is being read, or may be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1934</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     called alone if all symbols are simply being discarded.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1935</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1936</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`XYZ_symfile_read(struct sym_fns *sf, CORE_ADDR addr, int mainline)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1937</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Called from `symbol_file_add' to actually read the symbols from a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1938</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     symbol-file into a set of psymtabs or symtabs.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1939</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1940</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `sf' points to the `struct sym_fns' originally passed to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1941</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `XYZ_sym_init' for possible initialization.  `addr' is the offset</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1942</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     between the file's specified start address and its true address in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1943</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     memory.  `mainline' is 1 if this is the main symbol table being</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1944</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     read, and 0 if a secondary symbol file (e.g., shared library or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1945</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     dynamically loaded file) is being read.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1946</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1947</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   In addition, if a symbol-reading module creates psymtabs when</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1948</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>XYZ_symfile_read is called, these psymtabs will contain a pointer to a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1949</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>function `XYZ_psymtab_to_symtab', which can be called from any point in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1950</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the GDB symbol-handling code.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1951</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1952</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`XYZ_psymtab_to_symtab (struct partial_symtab *pst)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1953</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Called from `psymtab_to_symtab' (or the `PSYMTAB_TO_SYMTAB' macro)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1954</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     if the psymtab has not already been read in and had its</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1955</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `pst->symtab' pointer set.  The argument is the psymtab to be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1956</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     fleshed-out into a symtab.  Upon return, `pst->readin' should have</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1957</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     been set to 1, and `pst->symtab' should contain a pointer to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1958</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     new corresponding symtab, or zero if there were no symbols in that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1959</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     part of the symbol file.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1960</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1961</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.2 Partial Symbol Tables</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1962</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1963</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1964</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB has three types of symbol tables:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1965</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1966</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Full symbol tables ("symtabs").  These contain the main</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1967</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     information about symbols and addresses.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1968</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1969</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Partial symbol tables ("psymtabs").  These contain enough</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1970</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     information to know when to read the corresponding part of the full</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1971</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     symbol table.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1972</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1973</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Minimal symbol tables ("msymtabs").  These contain information</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1974</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     gleaned from non-debugging symbols.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1975</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1976</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   This section describes partial symbol tables.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1977</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1978</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A psymtab is constructed by doing a very quick pass over an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1979</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>executable file's debugging information.  Small amounts of information</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1980</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are extracted--enough to identify which parts of the symbol table will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1981</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>need to be re-read and fully digested later, when the user needs the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1982</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>information.  The speed of this pass causes GDB to start up very</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1983</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>quickly.  Later, as the detailed rereading occurs, it occurs in small</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1984</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>pieces, at various times, and the delay therefrom is mostly invisible to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1985</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the user.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1986</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1987</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The symbols that show up in a file's psymtab should be, roughly,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1988</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>those visible to the debugger's user when the program is not running</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1989</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>code from that file.  These include external symbols and types, static</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1990</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>symbols and types, and `enum' values declared at file scope.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1991</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1992</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The psymtab also contains the range of instruction addresses that the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1993</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>full symbol table would represent.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1994</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1995</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The idea is that there are only two ways for the user (or much of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1996</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>code in the debugger) to reference a symbol:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1997</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1998</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * By its address (e.g., execution stops at some address which is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>1999</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     inside a function in this file).  The address will be noticed to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2000</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     be in the range of this psymtab, and the full symtab will be read</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2001</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     in.  `find_pc_function', `find_pc_line', and other `find_pc_...'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2002</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     functions handle this.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2003</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2004</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * By its name (e.g., the user asks to print a variable, or set a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2005</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoint on a function).  Global names and file-scope names will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2006</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     be found in the psymtab, which will cause the symtab to be pulled</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2007</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     in.  Local names will have to be qualified by a global name, or a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2008</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     file-scope name, in which case we will have already read in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2009</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     symtab as we evaluated the qualifier.  Or, a local symbol can be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2010</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     referenced when we are "in" a local scope, in which case the first</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2011</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     case applies.  `lookup_symbol' does most of the work here.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2012</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2013</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The only reason that psymtabs exist is to cause a symtab to be read</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2014</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>in at the right moment.  Any symbol that can be elided from a psymtab,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2015</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>while still causing that to happen, should not appear in it.  Since</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2016</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>psymtabs don't have the idea of scope, you can't put local symbols in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2017</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>them anyway.  Psymtabs don't have the idea of the type of a symbol,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2018</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>either, so types need not appear, unless they will be referenced by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2019</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>name.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2020</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2021</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   It is a bug for GDB to behave one way when only a psymtab has been</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2022</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>read, and another way if the corresponding symtab has been read in.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2023</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Such bugs are typically caused by a psymtab that does not contain all</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2024</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the visible symbols, or which has the wrong instruction address ranges.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2025</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2026</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The psymtab for a particular section of a symbol file (objfile)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2027</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>could be thrown away after the symtab has been read in.  The symtab</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2028</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>should always be searched before the psymtab, so the psymtab will never</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2029</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>be used (in a bug-free environment).  Currently, psymtabs are allocated</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2030</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>on an obstack, and all the psymbols themselves are allocated in a pair</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2031</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>of large arrays on an obstack, so there is little to be gained by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2032</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>trying to free them unless you want to do a lot more work.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2033</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2034</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Whether or not psymtabs are created depends on the objfile's symbol</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2035</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>reader.  The core of GDB hides the details of partial symbols and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2036</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>partial symbol tables behind a set of function pointers known as the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2037</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"quick symbol functions".  These are documented in `symfile.h'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2038</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2039</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.3 Types</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2040</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=========</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2041</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2042</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Fundamental Types (e.g., `FT_VOID', `FT_BOOLEAN').</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2043</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2044</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2045</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>These are the fundamental types that GDB uses internally.  Fundamental</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2046</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>types from the various debugging formats (stabs, ELF, etc) are mapped</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2047</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>into one of these.  They are basically a union of all fundamental types</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2048</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>that GDB knows about for all the languages that GDB knows about.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2049</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2050</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Type Codes (e.g., `TYPE_CODE_PTR', `TYPE_CODE_ARRAY').</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2051</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------------------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2052</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2053</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Each time GDB builds an internal type, it marks it with one of these</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2054</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>types.  The type may be a fundamental type, such as `TYPE_CODE_INT', or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2055</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>a derived type, such as `TYPE_CODE_PTR' which is a pointer to another</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2056</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>type.  Typically, several `FT_*' types map to one `TYPE_CODE_*' type,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2057</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>and are distinguished by other members of the type struct, such as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2058</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>whether the type is signed or unsigned, and how many bits it uses.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2059</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2060</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Builtin Types (e.g., `builtin_type_void', `builtin_type_char').</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2061</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------------------------------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2062</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2063</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>These are instances of type structs that roughly correspond to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2064</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>fundamental types and are created as global types for GDB to use for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2065</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>various ugly historical reasons.  We eventually want to eliminate</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2066</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>these.  Note for example that `builtin_type_int' initialized in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2067</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdbtypes.c' is basically the same as a `TYPE_CODE_INT' type that is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2068</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>initialized in `c-lang.c' for an `FT_INTEGER' fundamental type.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2069</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>difference is that the `builtin_type' is not associated with any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2070</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>particular objfile, and only one instance exists, while `c-lang.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2071</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>builds as many `TYPE_CODE_INT' types as needed, with each one</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2072</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>associated with some particular objfile.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2073</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2074</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.4 Object File Formats</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2075</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=======================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2076</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2077</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.4.1 a.out</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2078</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2079</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2080</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The `a.out' format is the original file format for Unix.  It consists</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2081</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>of three sections: `text', `data', and `bss', which are for program</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2082</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>code, initialized data, and uninitialized data, respectively.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2083</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2084</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The `a.out' format is so simple that it doesn't have any reserved</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2085</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>place for debugging information.  (Hey, the original Unix hackers used</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2086</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`adb', which is a machine-language debugger!)  The only debugging</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2087</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>format for `a.out' is stabs, which is encoded as a set of normal</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2088</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>symbols with distinctive attributes.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2089</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2090</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The basic `a.out' reader is in `dbxread.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2091</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2092</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.4.2 COFF</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2093</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2094</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2095</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The COFF format was introduced with System V Release 3 (SVR3) Unix.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2096</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>COFF files may have multiple sections, each prefixed by a header.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2097</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>number of sections is limited.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2098</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2099</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The COFF specification includes support for debugging.  Although this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2100</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>was a step forward, the debugging information was woefully limited.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2101</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>For instance, it was not possible to represent code that came from an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2102</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>included file.  GNU's COFF-using configs often use stabs-type info,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2103</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>encapsulated in special sections.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2104</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2105</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The COFF reader is in `coffread.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2106</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2107</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.4.3 ECOFF</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2108</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2109</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2110</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>ECOFF is an extended COFF originally introduced for Mips and Alpha</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2111</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>workstations.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2112</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2113</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The basic ECOFF reader is in `mipsread.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2114</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2115</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.4.4 XCOFF</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2116</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2117</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2118</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The IBM RS/6000 running AIX uses an object file format called XCOFF.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2119</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The COFF sections, symbols, and line numbers are used, but debugging</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2120</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>symbols are `dbx'-style stabs whose strings are located in the `.debug'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2121</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>section (rather than the string table).  For more information, see</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2122</td>
         <td><a id="l2121-rev" class="blame-revision" href="/websvn/revision?repname=openrisc&path=%2Fopenrisc%2Ftrunk%2Fgnu-stable%2Fgdb-7.2%2Fgdb%2Fdoc%2F&rev=342">342</a></td>
         <td>jeremybenn</td>
         <td class="code"><pre><code>*note Top: (stabs)Top.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2123</td>
         <td><a id="l2122-rev" class="blame-revision" href="/websvn/revision?repname=openrisc&path=%2Fopenrisc%2Ftrunk%2Fgnu-stable%2Fgdb-7.2%2Fgdb%2Fdoc%2F&rev=330">330</a></td>
         <td>jeremybenn</td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2124</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The shared library scheme has a clean interface for figuring out what</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2125</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>shared libraries are in use, but the catch is that everything which</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2126</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>refers to addresses (symbol tables and breakpoints at least) needs to be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2127</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>relocated for both shared libraries and the main executable.  At least</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2128</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>using the standard mechanism this can only be done once the program has</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2129</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>been run (or the core file has been read).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2130</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2131</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.4.5 PE</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2132</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2133</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2134</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Windows 95 and NT use the PE ("Portable Executable") format for their</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2135</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>executables.  PE is basically COFF with additional headers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2136</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2137</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   While BFD includes special PE support, GDB needs only the basic COFF</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2138</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>reader.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2139</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2140</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.4.6 ELF</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2141</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2142</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2143</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The ELF format came with System V Release 4 (SVR4) Unix.  ELF is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2144</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>similar to COFF in being organized into a number of sections, but it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2145</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>removes many of COFF's limitations.  Debugging info may be either stabs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2146</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>encapsulated in ELF sections, or more commonly these days, DWARF.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2147</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2148</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The basic ELF reader is in `elfread.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2149</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2150</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.4.7 SOM</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2151</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2152</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2153</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>SOM is HP's object file and debug format (not to be confused with IBM's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2154</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>SOM, which is a cross-language ABI).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2155</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2156</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The SOM reader is in `somread.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2157</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2158</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.5 Debugging File Formats</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2159</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2160</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2161</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>This section describes characteristics of debugging information that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2162</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are independent of the object file format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2163</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2164</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.5.1 stabs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2165</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2166</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2167</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`stabs' started out as special symbols within the `a.out' format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2168</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Since then, it has been encapsulated into other file formats, such as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2169</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>COFF and ELF.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2170</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2171</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   While `dbxread.c' does some of the basic stab processing, including</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2172</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>for encapsulated versions, `stabsread.c' does the real work.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2173</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2174</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.5.2 COFF</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2175</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2176</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2177</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The basic COFF definition includes debugging information.  The level of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2178</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>support is minimal and non-extensible, and is not often used.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2179</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2180</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.5.3 Mips debug (Third Eye)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2181</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>----------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2182</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2183</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>ECOFF includes a definition of a special debug format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2184</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2185</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The file `mdebugread.c' implements reading for this format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2186</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2187</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.5.4 DWARF 2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2188</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2189</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2190</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>DWARF 2 is an improved but incompatible version of DWARF 1.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2191</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2192</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The DWARF 2 reader is in `dwarf2read.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2193</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2194</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.5.5 Compressed DWARF 2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2195</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2196</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2197</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Compressed DWARF 2 is not technically a separate debugging format, but</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2198</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>merely DWARF 2 debug information that has been compressed.  In this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2199</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>format, every object-file section holding DWARF 2 debugging information</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2200</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>is compressed and prepended with a header.  (The section is also</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2201</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>typically renamed, so a section called `.debug_info' in a DWARF 2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2202</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>binary would be called `.zdebug_info' in a compressed DWARF 2 binary.)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2203</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The header is 12 bytes long:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2204</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2205</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * 4 bytes: the literal string "ZLIB"</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2206</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2207</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * 8 bytes: the uncompressed size of the section, in big-endian byte</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2208</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     order.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2209</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2210</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The same reader is used for both compressed an normal DWARF 2 info.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2211</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Section decompression is done in `zlib_decompress_section' in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2212</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`dwarf2read.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2213</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2214</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.5.6 DWARF 3</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2215</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2216</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2217</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>DWARF 3 is an improved version of DWARF 2.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2218</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2219</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.5.7 SOM</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2220</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2221</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2222</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Like COFF, the SOM definition includes debugging information.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2223</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2224</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.6 Adding a New Symbol Reader to GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2225</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=====================================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2226</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2227</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>If you are using an existing object file format (`a.out', COFF, ELF,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2228</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>etc), there is probably little to be done.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2229</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2230</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If you need to add a new object file format, you must first add it to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2231</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>BFD.  This is beyond the scope of this document.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2232</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2233</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   You must then arrange for the BFD code to provide access to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2234</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>debugging symbols.  Generally GDB will have to call swapping routines</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2235</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>from BFD and a few other BFD internal routines to locate the debugging</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2236</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>information.  As much as possible, GDB should not depend on the BFD</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2237</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>internal data structures.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2238</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2239</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   For some targets (e.g., COFF), there is a special transfer vector</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2240</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>used to call swapping routines, since the external data structures on</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2241</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>various platforms have different sizes and layouts.  Specialized</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2242</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>routines that will only ever be implemented by one object file format</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2243</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>may be called directly.  This interface should be described in a file</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2244</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`bfd/libXYZ.h', which is included by GDB.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2245</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2246</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>8.7 Memory Management for Symbol Files</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2247</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>======================================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2248</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2249</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Most memory associated with a loaded symbol file is stored on its</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2250</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`objfile_obstack'.  This includes symbols, types, namespace data, and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2251</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>other information produced by the symbol readers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2252</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2253</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Because this data lives on the objfile's obstack, it is automatically</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2254</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>released when the objfile is unloaded or reloaded.  Therefore one</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2255</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>objfile must not reference symbol or type data from another objfile;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2256</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>they could be unloaded at different times.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2257</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2258</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   User convenience variables, et cetera, have associated types.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2259</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Normally these types live in the associated objfile.  However, when the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2260</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>objfile is unloaded, those types are deep copied to global memory, so</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2261</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>that the values of the user variables and history items are not lost.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2262</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2263</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2264</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Language Support,  Next: Host Definition,  Prev: Symbol Handling,  Up: Top</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2265</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2266</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>9 Language Support</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2267</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>******************</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2268</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2269</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB's language support is mainly driven by the symbol reader, although</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2270</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>it is possible for the user to set the source language manually.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2271</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2272</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB chooses the source language by looking at the extension of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2273</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>file recorded in the debug info; `.c' means C, `.f' means Fortran, etc.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2274</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>It may also use a special-purpose language identifier if the debug</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2275</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>format supports it, like with DWARF.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2276</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2277</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>9.1 Adding a Source Language to GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2278</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>===================================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2279</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2280</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>To add other languages to GDB's expression parser, follow the following</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2281</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>steps:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2282</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2283</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_Create the expression parser._</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2284</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This should reside in a file `LANG-exp.y'.  Routines for building</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2285</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     parsed expressions into a `union exp_element' list are in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2286</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `parse.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2287</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2288</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Since we can't depend upon everyone having Bison, and YACC produces</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2289</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     parsers that define a bunch of global names, the following lines</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2290</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     *must* be included at the top of the YACC parser, to prevent the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2291</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     various parsers from defining the same global names:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2292</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2293</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yyparse         LANG_parse</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2294</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yylex           LANG_lex</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2295</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yyerror         LANG_error</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2296</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yylval          LANG_lval</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2297</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yychar          LANG_char</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2298</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yydebug         LANG_debug</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2299</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yypact          LANG_pact</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2300</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yyr1            LANG_r1</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2301</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yyr2            LANG_r2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2302</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yydef           LANG_def</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2303</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yychk           LANG_chk</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2304</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yypgo           LANG_pgo</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2305</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yyact           LANG_act</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2306</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yyexca          LANG_exca</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2307</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yyerrflag       LANG_errflag</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2308</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          #define yynerrs         LANG_nerrs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2309</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2310</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     At the bottom of your parser, define a `struct language_defn' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2311</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     initialize it with the right values for your language.  Define an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2312</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `initialize_LANG' routine and have it call</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2313</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `add_language(LANG_language_defn)' to tell the rest of GDB that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2314</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     your language exists.  You'll need some other supporting variables</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2315</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     and functions, which will be used via pointers from your</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2316</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `LANG_language_defn'.  See the declaration of `struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2317</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     language_defn' in `language.h', and the other `*-exp.y' files, for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2318</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     more information.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2319</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2320</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_Add any evaluation routines, if necessary_</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2321</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If you need new opcodes (that represent the operations of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2322</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     language), add them to the enumerated type in `expression.h'.  Add</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2323</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     support code for these operations in the `evaluate_subexp' function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2324</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     defined in the file `eval.c'.  Add cases for new opcodes in two</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2325</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     functions from `parse.c': `prefixify_subexp' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2326</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `length_of_subexp'.  These compute the number of `exp_element's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2327</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     that a given operation takes up.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2328</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2329</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_Update some existing code_</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2330</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Add an enumerated identifier for your language to the enumerated</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2331</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     type `enum language' in `defs.h'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2332</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2333</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Update the routines in `language.c' so your language is included.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2334</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     These routines include type predicates and such, which (in some</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2335</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     cases) are language dependent.  If your language does not appear</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2336</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     in the switch statement, an error is reported.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2337</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2338</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Also included in `language.c' is the code that updates the variable</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2339</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `current_language', and the routines that translate the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2340</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `language_LANG' enumerated identifier into a printable string.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2341</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2342</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Update the function `_initialize_language' to include your</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2343</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     language.  This function picks the default language upon startup,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2344</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     so is dependent upon which languages that GDB is built for.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2345</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2346</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Update `allocate_symtab' in `symfile.c' and/or symbol-reading code</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2347</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     so that the language of each symtab (source file) is set properly.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2348</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This is used to determine the language to use at each stack frame</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2349</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     level.  Currently, the language is set based upon the extension of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2350</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the source file.  If the language can be better inferred from the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2351</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     symbol information, please set the language of the symtab in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2352</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     symbol-reading code.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2353</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2354</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Add helper code to `print_subexp' (in `expprint.c') to handle any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2355</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     new expression opcodes you have added to `expression.h'.  Also,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2356</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     add the printed representations of your operators to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2357</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `op_print_tab'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2358</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2359</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_Add a place of call_</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2360</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Add a call to `LANG_parse()' and `LANG_error' in `parse_exp_1'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2361</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (defined in `parse.c').</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2362</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2363</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_Edit `Makefile.in'_</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2364</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Add dependencies in `Makefile.in'.  Make sure you update the macro</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2365</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     variables such as `HFILES' and `OBJS', otherwise your code may not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2366</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     get linked in, or, worse yet, it may not get `tar'red into the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2367</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     distribution!</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2368</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2369</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2370</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Host Definition,  Next: Target Architecture Definition,  Prev: Language Support,  Up: Top</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2371</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2372</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>10 Host Definition</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2373</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>******************</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2374</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2375</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>With the advent of Autoconf, it's rarely necessary to have host</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2376</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>definition machinery anymore.  The following information is provided,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2377</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>mainly, as an historical reference.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2378</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2379</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>10.1 Adding a New Host</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2380</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>======================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2381</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2382</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB's host configuration support normally happens via Autoconf.  New</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2383</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>host-specific definitions should not be needed.  Older hosts GDB still</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2384</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>use the host-specific definitions and files listed below, but these</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2385</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>mostly exist for historical reasons, and will eventually disappear.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2386</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2387</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb/config/ARCH/XYZ.mh'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2388</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This file is a Makefile fragment that once contained both host and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2389</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     native configuration information (*note Native Debugging::) for the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2390</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     machine XYZ.  The host configuration information is now handled by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2391</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Autoconf.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2392</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2393</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Host configuration information included definitions for `CC',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2394</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `SYSV_DEFINE', `XM_CFLAGS', `XM_ADD_FILES', `XM_CLIBS',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2395</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `XM_CDEPS', etc.; see `Makefile.in'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2396</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2397</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     New host-only configurations do not need this file.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2398</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2399</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2400</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   (Files named `gdb/config/ARCH/xm-XYZ.h' were once used to define</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2401</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>host-specific macros, but were no longer needed and have all been</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2402</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>removed.)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2403</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2404</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Generic Host Support Files</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2405</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2406</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2407</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>There are some "generic" versions of routines that can be used by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2408</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>various systems.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2409</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2410</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ser-unix.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2411</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This contains serial line support for Unix systems.  It is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2412</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     included by default on all Unix-like hosts.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2413</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2414</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ser-pipe.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2415</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This contains serial pipe support for Unix systems.  It is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2416</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     included by default on all Unix-like hosts.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2417</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2418</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ser-mingw.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2419</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This contains serial line support for 32-bit programs running under</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2420</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Windows using MinGW.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2421</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2422</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ser-go32.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2423</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This contains serial line support for 32-bit programs running</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2424</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     under DOS, using the DJGPP (a.k.a. GO32) execution environment.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2425</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2426</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ser-tcp.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2427</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This contains generic TCP support using sockets.  It is included by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2428</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     default on all Unix-like hosts and with MinGW.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2429</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2430</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>10.2 Host Conditionals</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2431</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>======================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2432</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2433</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>When GDB is configured and compiled, various macros are defined or left</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2434</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>undefined, to control compilation based on the attributes of the host</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2435</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>system.  While formerly they could be set in host-specific header</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2436</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>files, at present they can be changed only by setting `CFLAGS' when</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2437</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>building, or by editing the source code.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2438</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2439</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   These macros and their meanings (or if the meaning is not documented</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2440</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>here, then one of the source files where they are used is indicated)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2441</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2442</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2443</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDBINIT_FILENAME'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2444</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The default name of GDB's initialization file (normally</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2445</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `.gdbinit').</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2446</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2447</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SIGWINCH_HANDLER'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2448</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If your host defines `SIGWINCH', you can define this to be the name</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2449</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     of a function to be called if `SIGWINCH' is received.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2450</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2451</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SIGWINCH_HANDLER_BODY'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2452</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this to expand into code that will define the function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2453</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     named by the expansion of `SIGWINCH_HANDLER'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2454</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2455</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`CRLF_SOURCE_FILES'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2456</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this if host files use `\r\n' rather than `\n' as a line</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2457</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     terminator.  This will cause source file listings to omit `\r'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2458</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     characters when printing and it will allow `\r\n' line endings of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2459</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     files which are "sourced" by gdb.  It must be possible to open</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2460</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     files in binary mode using `O_BINARY' or, for fopen, `"rb"'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2461</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2462</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`DEFAULT_PROMPT'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2463</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The default value of the prompt string (normally `"(gdb) "').</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2464</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2465</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`DEV_TTY'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2466</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The name of the generic TTY device, defaults to `"/dev/tty"'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2467</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2468</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`ISATTY'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2469</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Substitute for isatty, if not available.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2470</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2471</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`FOPEN_RB'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2472</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this if binary files are opened the same way as text files.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2473</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2474</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`CC_HAS_LONG_LONG'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2475</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this if the host C compiler supports `long long'.  This is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2476</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     set by the `configure' script.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2477</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2478</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`PRINTF_HAS_LONG_LONG'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2479</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this if the host can handle printing of long long integers</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2480</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     via the printf format conversion specifier `ll'.  This is set by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2481</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the `configure' script.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2482</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2483</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`LSEEK_NOT_LINEAR'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2484</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this if `lseek (n)' does not necessarily move to byte number</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2485</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `n' in the file.  This is only used when reading source files.  It</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2486</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     is normally faster to define `CRLF_SOURCE_FILES' when possible.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2487</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2488</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`lint'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2489</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this to help placate `lint' in some situations.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2490</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2491</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`volatile'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2492</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this to override the defaults of `__volatile__' or `/**/'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2493</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2494</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2495</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Target Architecture Definition,  Next: Target Descriptions,  Prev: Host Definition,  Up: Top</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2496</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2497</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11 Target Architecture Definition</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2498</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>*********************************</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2499</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2500</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB's target architecture defines what sort of machine-language</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2501</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>programs GDB can work with, and how it works with them.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2502</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2503</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The target architecture object is implemented as the C structure</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2504</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`struct gdbarch *'.  The structure, and its methods, are generated</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2505</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>using the Bourne shell script `gdbarch.sh'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2506</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2507</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Menu:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2508</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2509</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* OS ABI Variant Handling::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2510</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Initialize New Architecture::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2511</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Registers and Memory::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2512</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Pointers and Addresses::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2513</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Address Classes::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2514</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Register Representation::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2515</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Frame Interpretation::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2516</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Inferior Call Setup::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2517</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Adding support for debugging core files::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2518</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Defining Other Architecture Features::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2519</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Adding a New Target::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2520</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2521</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2522</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: OS ABI Variant Handling,  Next: Initialize New Architecture,  Up: Target Architecture Definition</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2523</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2524</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.1 Operating System ABI Variant Handling</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2525</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==========================================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2526</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2527</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB provides a mechanism for handling variations in OS ABIs.  An OS ABI</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2528</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>variant may have influence over any number of variables in the target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2529</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture definition.  There are two major components in the OS ABI</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2530</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>mechanism: sniffers and handlers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2531</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2532</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A "sniffer" examines a file matching a BFD architecture/flavour pair</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2533</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(the architecture may be wildcarded) in an attempt to determine the OS</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2534</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>ABI of that file.  Sniffers with a wildcarded architecture are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2535</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>considered to be "generic", while sniffers for a specific architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2536</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are considered to be "specific".  A match from a specific sniffer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2537</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>overrides a match from a generic sniffer.  Multiple sniffers for an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2538</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture/flavour may exist, in order to differentiate between two</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2539</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>different operating systems which use the same basic file format.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2540</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>OS ABI framework provides a generic sniffer for ELF-format files which</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2541</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>examines the `EI_OSABI' field of the ELF header, as well as note</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2542</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>sections known to be used by several operating systems.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2543</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2544</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A "handler" is used to fine-tune the `gdbarch' structure for the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2545</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>selected OS ABI.  There may be only one handler for a given OS ABI for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2546</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>each BFD architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2547</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2548</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The following OS ABI variants are defined in `defs.h':</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2549</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2550</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_UNINITIALIZED'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2551</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Used for struct gdbarch_info if ABI is still uninitialized.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2552</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2553</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_UNKNOWN'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2554</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The ABI of the inferior is unknown.  The default `gdbarch'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2555</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     settings for the architecture will be used.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2556</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2557</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_SVR4'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2558</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     UNIX System V Release 4.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2559</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2560</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_HURD'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2561</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     GNU using the Hurd kernel.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2562</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2563</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_SOLARIS'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2564</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Sun Solaris.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2565</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2566</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_OSF1'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2567</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     OSF/1, including Digital UNIX and Compaq Tru64 UNIX.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2568</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2569</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_LINUX'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2570</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     GNU using the Linux kernel.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2571</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2572</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_FREEBSD_AOUT'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2573</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     FreeBSD using the `a.out' executable format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2574</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2575</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_FREEBSD_ELF'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2576</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     FreeBSD using the ELF executable format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2577</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2578</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_NETBSD_AOUT'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2579</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     NetBSD using the `a.out' executable format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2580</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2581</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_NETBSD_ELF'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2582</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     NetBSD using the ELF executable format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2583</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2584</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_OPENBSD_ELF'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2585</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     OpenBSD using the ELF executable format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2586</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2587</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_WINCE'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2588</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Windows CE.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2589</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2590</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_GO32'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2591</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     DJGPP.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2592</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2593</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_IRIX'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2594</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Irix.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2595</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2596</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_INTERIX'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2597</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Interix (Posix layer for MS-Windows systems).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2598</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2599</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_HPUX_ELF'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2600</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     HP/UX using the ELF executable format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2601</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2602</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_HPUX_SOM'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2603</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     HP/UX using the SOM executable format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2604</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2605</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_QNXNTO'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2606</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     QNX Neutrino.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2607</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2608</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_CYGWIN'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2609</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Cygwin.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2610</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2611</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GDB_OSABI_AIX'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2612</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     AIX.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2613</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2614</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2615</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Here are the functions that make up the OS ABI framework:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2616</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2617</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: const char * gdbarch_osabi_name (enum gdb_osabi OSABI)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2618</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Return the name of the OS ABI corresponding to OSABI.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2619</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2620</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void gdbarch_register_osabi (enum bfd_architecture ARCH,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2621</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          unsigned long MACHINE, enum gdb_osabi OSABI, void</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2622</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          (*INIT_OSABI)(struct gdbarch_info INFO, struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2623</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH))</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2624</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Register the OS ABI handler specified by INIT_OSABI for the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2625</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     architecture, machine type and OS ABI specified by ARCH, MACHINE</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2626</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     and OSABI.  In most cases, a value of zero for the machine type,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2627</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     which implies the architecture's default machine type, will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2628</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     suffice.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2629</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2630</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void gdbarch_register_osabi_sniffer (enum</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2631</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          bfd_architecture ARCH, enum bfd_flavour FLAVOUR, enum</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2632</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          gdb_osabi (*SNIFFER)(bfd *ABFD))</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2633</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Register the OS ABI file sniffer specified by SNIFFER for the BFD</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2634</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     architecture/flavour pair specified by ARCH and FLAVOUR.  If ARCH</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2635</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     is `bfd_arch_unknown', the sniffer is considered to be generic,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2636</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     and is allowed to examine FLAVOUR-flavoured files for any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2637</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2638</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2639</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: enum gdb_osabi gdbarch_lookup_osabi (bfd *ABFD)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2640</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Examine the file described by ABFD to determine its OS ABI.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2641</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     value `GDB_OSABI_UNKNOWN' is returned if the OS ABI cannot be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2642</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     determined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2643</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2644</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void gdbarch_init_osabi (struct gdbarch info INFO, struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2645</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          gdbarch *GDBARCH, enum gdb_osabi OSABI)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2646</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Invoke the OS ABI handler corresponding to OSABI to fine-tune the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2647</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch' structure specified by GDBARCH.  If a handler</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2648</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     corresponding to OSABI has not been registered for GDBARCH's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2649</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     architecture, a warning will be issued and the debugging session</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2650</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     will continue with the defaults already established for GDBARCH.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2651</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2652</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void generic_elf_osabi_sniff_abi_tag_sections (bfd *ABFD,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2653</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          asection *SECT, void *OBJ)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2654</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Helper routine for ELF file sniffers.  Examine the file described</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2655</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     by ABFD and look at ABI tag note sections to determine the OS ABI</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2656</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     from the note.  This function should be called via</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2657</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `bfd_map_over_sections'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2658</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2659</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2660</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Initialize New Architecture,  Next: Registers and Memory,  Prev: OS ABI Variant Handling,  Up: Target Architecture Definition</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2661</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2662</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.2 Initializing a New Architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2663</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>====================================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2664</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2665</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Menu:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2666</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2667</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* How an Architecture is Represented::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2668</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Looking Up an Existing Architecture::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2669</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Creating a New Architecture::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2670</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2671</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2672</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: How an Architecture is Represented,  Next: Looking Up an Existing Architecture,  Up: Initialize New Architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2673</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2674</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.2.1 How an Architecture is Represented</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2675</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2676</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2677</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Each `gdbarch' is associated with a single BFD architecture, via a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2678</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`bfd_arch_ARCH' in the `bfd_architecture' enumeration.  The `gdbarch'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2679</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>is registered by a call to `register_gdbarch_init', usually from the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2680</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>file's `_initialize_FILENAME' routine, which will be automatically</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2681</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>called during GDB startup.  The arguments are a BFD architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2682</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>constant and an initialization function.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2683</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2684</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A GDB description for a new architecture, ARCH is created by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2685</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>defining a global function `_initialize_ARCH_tdep', by convention in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2686</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the source file `ARCH-tdep.c'.  For example, in the case of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2687</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>OpenRISC 1000, this function is called `_initialize_or1k_tdep' and is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2688</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>found in the file `or1k-tdep.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2689</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2690</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The resulting object files containing the implementation of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2691</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`_initialize_ARCH_tdep' function are specified in the GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2692</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`configure.tgt' file, which includes a large case statement pattern</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2693</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>matching against the `--target' option of the `configure' script.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2694</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>new `struct gdbarch' is created within the `_initialize_ARCH_tdep'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2695</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>function by calling `gdbarch_register':</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2696</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2697</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     void gdbarch_register (enum bfd_architecture    ARCHITECTURE,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2698</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                            gdbarch_init_ftype      *INIT_FUNC,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2699</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                            gdbarch_dump_tdep_ftype *TDEP_DUMP_FUNC);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2700</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2701</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The ARCHITECTURE will identify the unique BFD to be associated with</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2702</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>this `gdbarch'.  The INIT_FUNC funciton is called to create and return</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2703</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the new `struct gdbarch'.  The TDEP_DUMP_FUNC function will dump the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2704</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>target specific details associated with this architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2705</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2706</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   For example the function `_initialize_or1k_tdep' creates its</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2707</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture for 32-bit OpenRISC 1000 architectures by calling:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2708</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2709</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     gdbarch_register (bfd_arch_or32, or1k_gdbarch_init, or1k_dump_tdep);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2710</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2711</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2712</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Looking Up an Existing Architecture,  Next: Creating a New Architecture,  Prev: How an Architecture is Represented,  Up: Initialize New Architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2713</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2714</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.2.2 Looking Up an Existing Architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2715</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2716</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2717</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The initialization function has this prototype:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2718</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2719</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     static struct gdbarch *</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2720</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ARCH_gdbarch_init (struct gdbarch_info INFO,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2721</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                              struct gdbarch_list *ARCHES)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2722</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2723</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The INFO argument contains parameters used to select the correct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2724</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture, and ARCHES is a list of architectures which have already</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2725</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>been created with the same `bfd_arch_ARCH' value.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2726</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2727</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The initialization function should first make sure that INFO is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2728</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>acceptable, and return `NULL' if it is not.  Then, it should search</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2729</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>through ARCHES for an exact match to INFO, and return one if found.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2730</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Lastly, if no exact match was found, it should create a new</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2731</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture based on INFO and return it.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2732</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2733</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The lookup is done using `gdbarch_list_lookup_by_info'.  It is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2734</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>passed the list of existing architectures, ARCHES, and the `struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2735</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>gdbarch_info', INFO, and returns the first matching architecture it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2736</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>finds, or `NULL' if none are found.  If an architecture is found it can</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2737</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>be returned as the result from the initialization function, otherwise a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2738</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>new `struct gdbach' will need to be created.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2739</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2740</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The struct gdbarch_info has the following components:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2741</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2742</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     struct gdbarch_info</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2743</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2744</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        const struct bfd_arch_info *bfd_arch_info;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2745</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        int                         byte_order;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2746</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        bfd                        *abfd;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2747</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        struct gdbarch_tdep_info   *tdep_info;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2748</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        enum gdb_osabi              osabi;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2749</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        const struct target_desc   *target_desc;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2750</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     };</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2751</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2752</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The `bfd_arch_info' member holds the key details about the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2753</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture.  The `byte_order' member is a value in an enumeration</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2754</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>indicating the endianism.  The `abfd' member is a pointer to the full</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2755</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>BFD, the `tdep_info' member is additional custom target specific</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2756</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>information, `osabi' identifies which (if any) of a number of operating</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2757</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>specific ABIs are used by this architecture and the `target_desc'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2758</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>member is a set of name-value pairs with information about register</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2759</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>usage in this target.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2760</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2761</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   When the `struct gdbarch' initialization function is called, not all</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2762</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the fields are provided--only those which can be deduced from the BFD.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2763</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The `struct gdbarch_info', INFO is used as a look-up key with the list</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2764</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>of existing architectures, ARCHES to see if a suitable architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2765</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>already exists.  The TDEP_INFO, OSABI and TARGET_DESC fields may be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2766</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>added before this lookup to refine the search.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2767</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2768</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Only information in INFO should be used to choose the new</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2769</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture.  Historically, INFO could be sparse, and defaults would</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2770</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>be collected from the first element on ARCHES.  However, GDB now fills</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2771</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>in INFO more thoroughly, so new `gdbarch' initialization functions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2772</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>should not take defaults from ARCHES.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2773</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2774</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2775</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Creating a New Architecture,  Prev: Looking Up an Existing Architecture,  Up: Initialize New Architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2776</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2777</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.2.3 Creating a New Architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2778</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>----------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2779</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2780</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>If no architecture is found, then a new architecture must be created,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2781</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>by calling `gdbarch_alloc' using the supplied `struct gdbarch_info' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2782</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>any additional custom target specific information in a `struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2783</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>gdbarch_tdep'.  The prototype for `gdbarch_alloc' is:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2784</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2785</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     struct gdbarch *gdbarch_alloc (const struct gdbarch_info *INFO,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2786</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                                    struct gdbarch_tdep       *TDEP);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2787</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2788</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The newly created struct gdbarch must then be populated.  Although</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2789</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>there are default values, in most cases they are not what is required.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2790</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2791</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   For each element, X, there is are a pair of corresponding accessor</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2792</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions, one to set the value of that element, `set_gdbarch_X', the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2793</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>second to either get the value of an element (if it is a variable) or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2794</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to apply the element (if it is a function), `gdbarch_X'.  Note that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2795</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>both accessor functions take a pointer to the `struct gdbarch' as first</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2796</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>argument.  Populating the new `gdbarch' should use the `set_gdbarch'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2797</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2798</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2799</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The following sections identify the main elements that should be set</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2800</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>in this way.  This is not the complete list, but represents the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2801</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions and elements that must commonly be specified for a new</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2802</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture.  Many of the functions and variables are described in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2803</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>header file `gdbarch.h'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2804</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2805</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   This is the main work in defining a new architecture.  Implementing</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2806</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the set of functions to populate the `struct gdbarch'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2807</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2808</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   `struct gdbarch_tdep' is not defined within GDB--it is up to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2809</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>user to define this struct if it is needed to hold custom target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2810</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>information that is not covered by the standard `struct gdbarch'. For</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2811</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>example with the OpenRISC 1000 architecture it is used to hold the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2812</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>number of matchpoints available in the target (along with other</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2813</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>information).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2814</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2815</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If there is no additional target specific information, it can be set</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2816</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to `NULL'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2817</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2818</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2819</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Registers and Memory,  Next: Pointers and Addresses,  Prev: Initialize New Architecture,  Up: Target Architecture Definition</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2820</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2821</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.3 Registers and Memory</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2822</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2823</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2824</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB's model of the target machine is rather simple.  GDB assumes the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2825</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>machine includes a bank of registers and a block of memory.  Each</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2826</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>register may have a different size.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2827</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2828</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB does not have a magical way to match up with the compiler's idea</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2829</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>of which registers are which; however, it is critical that they do</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2830</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>match up accurately.  The only way to make this work is to get accurate</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2831</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>information about the order that the compiler uses, and to reflect that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2832</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>in the `gdbarch_register_name' and related functions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2833</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2834</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB can handle big-endian, little-endian, and bi-endian</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2835</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architectures.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2836</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2837</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2838</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Pointers and Addresses,  Next: Address Classes,  Prev: Registers and Memory,  Up: Target Architecture Definition</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2839</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2840</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.4 Pointers Are Not Always Addresses</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2841</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>======================================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2842</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2843</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>On almost all 32-bit architectures, the representation of a pointer is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2844</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>indistinguishable from the representation of some fixed-length number</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2845</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>whose value is the byte address of the object pointed to.  On such</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2846</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>machines, the words "pointer" and "address" can be used interchangeably.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2847</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>However, architectures with smaller word sizes are often cramped for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2848</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>address space, so they may choose a pointer representation that breaks</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2849</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>this identity, and allows a larger code address space.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2850</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2851</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   For example, the Renesas D10V is a 16-bit VLIW processor whose</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2852</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>instructions are 32 bits long(1).  If the D10V used ordinary byte</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2853</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>addresses to refer to code locations, then the processor would only be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2854</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>able to address 64kb of instructions.  However, since instructions must</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2855</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>be aligned on four-byte boundaries, the low two bits of any valid</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2856</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>instruction's byte address are always zero--byte addresses waste two</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2857</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>bits.  So instead of byte addresses, the D10V uses word addresses--byte</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2858</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>addresses shifted right two bits--to refer to code.  Thus, the D10V can</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2859</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>use 16-bit words to address 256kb of code space.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2860</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2861</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   However, this means that code pointers and data pointers have</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2862</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>different forms on the D10V.  The 16-bit word `0xC020' refers to byte</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2863</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>address `0xC020' when used as a data address, but refers to byte address</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2864</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`0x30080' when used as a code address.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2865</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2866</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   (The D10V also uses separate code and data address spaces, which also</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2867</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>affects the correspondence between pointers and addresses, but we're</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2868</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>going to ignore that here; this example is already too long.)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2869</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2870</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   To cope with architectures like this--the D10V is not the only</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2871</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>one!--GDB tries to distinguish between "addresses", which are byte</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2872</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>numbers, and "pointers", which are the target's representation of an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2873</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>address of a particular type of data.  In the example above, `0xC020'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2874</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>is the pointer, which refers to one of the addresses `0xC020' or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2875</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`0x30080', depending on the type imposed upon it.  GDB provides</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2876</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions for turning a pointer into an address and vice versa, in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2877</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>appropriate way for the current architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2878</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2879</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Unfortunately, since addresses and pointers are identical on almost</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2880</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>all processors, this distinction tends to bit-rot pretty quickly.  Thus,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2881</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>each time you port GDB to an architecture which does distinguish</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2882</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>between pointers and addresses, you'll probably need to clean up some</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2883</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture-independent code.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2884</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2885</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Here are functions which convert between pointers and addresses:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2886</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2887</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: CORE_ADDR extract_typed_address (void *BUF, struct type</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2888</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *TYPE)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2889</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Treat the bytes at BUF as a pointer or reference of type TYPE, and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2890</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     return the address it represents, in a manner appropriate for the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2891</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     current architecture.  This yields an address GDB can use to read</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2892</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     target memory, disassemble, etc.  Note that BUF refers to a buffer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2893</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     in GDB's memory, not the inferior's.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2894</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2895</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     For example, if the current architecture is the Intel x86, this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2896</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function extracts a little-endian integer of the appropriate</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2897</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     length from BUF and returns it.  However, if the current</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2898</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     architecture is the D10V, this function will return a 16-bit</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2899</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     integer extracted from BUF, multiplied by four if TYPE is a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2900</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     pointer to a function.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2901</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2902</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If TYPE is not a pointer or reference type, then this function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2903</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     will signal an internal error.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2904</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2905</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: CORE_ADDR store_typed_address (void *BUF, struct type</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2906</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *TYPE, CORE_ADDR ADDR)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2907</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Store the address ADDR in BUF, in the proper format for a pointer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2908</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     of type TYPE in the current architecture.  Note that BUF refers to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2909</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     a buffer in GDB's memory, not the inferior's.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2910</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2911</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     For example, if the current architecture is the Intel x86, this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2912</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function stores ADDR unmodified as a little-endian integer of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2913</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     appropriate length in BUF.  However, if the current architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2914</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     is the D10V, this function divides ADDR by four if TYPE is a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2915</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     pointer to a function, and then stores it in BUF.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2916</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2917</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If TYPE is not a pointer or reference type, then this function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2918</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     will signal an internal error.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2919</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2920</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: CORE_ADDR value_as_address (struct value *VAL)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2921</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Assuming that VAL is a pointer, return the address it represents,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2922</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     as appropriate for the current architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2923</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2924</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function actually works on integral values, as well as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2925</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     pointers.  For pointers, it performs architecture-specific</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2926</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     conversions as described above for `extract_typed_address'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2927</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2928</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: CORE_ADDR value_from_pointer (struct type *TYPE,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2929</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          CORE_ADDR ADDR)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2930</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Create and return a value representing a pointer of type TYPE to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2931</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the address ADDR, as appropriate for the current architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2932</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function performs architecture-specific conversions as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2933</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     described above for `store_typed_address'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2934</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2935</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Here are two functions which architectures can define to indicate the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2936</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>relationship between pointers and addresses.  These have default</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2937</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>definitions, appropriate for architectures on which all pointers are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2938</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>simple unsigned byte addresses.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2939</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2940</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: CORE_ADDR gdbarch_pointer_to_address (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2941</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, struct type *TYPE, char *BUF)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2942</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Assume that BUF holds a pointer of type TYPE, in the appropriate</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2943</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     format for the current architecture.  Return the byte address the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2944</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     pointer refers to.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2945</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2946</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function may safely assume that TYPE is either a pointer or a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2947</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     C++ reference type.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2948</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2949</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: void gdbarch_address_to_pointer (struct gdbarch *GDBARCH,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2950</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          struct type *TYPE, char *BUF, CORE_ADDR ADDR)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2951</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Store in BUF a pointer of type TYPE representing the address ADDR,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2952</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     in the appropriate format for the current architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2953</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2954</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function may safely assume that TYPE is either a pointer or a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2955</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     C++ reference type.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2956</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2957</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   ---------- Footnotes ----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2958</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2959</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   (1) Some D10V instructions are actually pairs of 16-bit</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2960</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>sub-instructions.  However, since you can't jump into the middle of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2961</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>such a pair, code addresses can only refer to full 32 bit instructions,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2962</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>which is what matters in this explanation.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2963</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2964</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2965</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Address Classes,  Next: Register Representation,  Prev: Pointers and Addresses,  Up: Target Architecture Definition</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2966</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2967</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.5 Address Classes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2968</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>====================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2969</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2970</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Sometimes information about different kinds of addresses is available</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2971</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>via the debug information.  For example, some programming environments</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2972</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>define addresses of several different sizes.  If the debug information</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2973</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>distinguishes these kinds of address classes through either the size</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2974</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>info (e.g, `DW_AT_byte_size' in DWARF 2) or through an explicit address</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2975</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>class attribute (e.g, `DW_AT_address_class' in DWARF 2), the following</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2976</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>macros should be defined in order to disambiguate these types within</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2977</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB as well as provide the added information to a GDB user when</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2978</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>printing type expressions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2979</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2980</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: int gdbarch_address_class_type_flags (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2981</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, int BYTE_SIZE, int DWARF2_ADDR_CLASS)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2982</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Returns the type flags needed to construct a pointer type whose</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2983</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     size is BYTE_SIZE and whose address class is DWARF2_ADDR_CLASS.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2984</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function is normally called from within a symbol reader.  See</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2985</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `dwarf2read.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2986</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2987</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: char * gdbarch_address_class_type_flags_to_name (struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2988</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          gdbarch *GDBARCH, int TYPE_FLAGS)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2989</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Given the type flags representing an address class qualifier,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2990</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     return its name.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2991</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2992</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Function: int gdbarch_address_class_name_to_type_flags (struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2993</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          gdbarch *GDBARCH, int NAME, int *TYPE_FLAGS_PTR)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2994</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Given an address qualifier name, set the `int' referenced by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2995</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     TYPE_FLAGS_PTR to the type flags for that address class qualifier.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2996</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2997</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Since the need for address classes is rather rare, none of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2998</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>address class functions are defined by default.  Predicate functions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>2999</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are provided to detect when they are defined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3000</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3001</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Consider a hypothetical architecture in which addresses are normally</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3002</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>32-bits wide, but 16-bit addresses are also supported.  Furthermore,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3003</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>suppose that the DWARF 2 information for this architecture simply uses</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3004</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>a `DW_AT_byte_size' value of 2 to indicate the use of one of these</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3005</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"short" pointers.  The following functions could be defined to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3006</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>implement the address class functions:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3007</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3008</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     somearch_address_class_type_flags (int byte_size,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3009</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                                        int dwarf2_addr_class)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3010</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3011</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (byte_size == 2)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3012</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         return TYPE_FLAG_ADDRESS_CLASS_1;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3013</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       else</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3014</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         return 0;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3015</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3016</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3017</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     static char *</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3018</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     somearch_address_class_type_flags_to_name (int type_flags)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3019</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3020</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (type_flags & TYPE_FLAG_ADDRESS_CLASS_1)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3021</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         return "short";</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3022</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       else</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3023</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         return NULL;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3024</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3025</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3026</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     int</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3027</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     somearch_address_class_name_to_type_flags (char *name,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3028</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                                                int *type_flags_ptr)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3029</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3030</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (strcmp (name, "short") == 0)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3031</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3032</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           *type_flags_ptr = TYPE_FLAG_ADDRESS_CLASS_1;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3033</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           return 1;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3034</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3035</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       else</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3036</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         return 0;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3037</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3038</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3039</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The qualifier `@short' is used in GDB's type expressions to indicate</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3040</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the presence of one of these "short" pointers.  For example if the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3041</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>debug information indicates that `short_ptr_var' is one of these short</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3042</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>pointers, GDB might show the following behavior:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3043</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3044</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (gdb) ptype short_ptr_var</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3045</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     type = int * @short</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3046</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3047</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3048</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Register Representation,  Next: Frame Interpretation,  Prev: Address Classes,  Up: Target Architecture Definition</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3049</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3050</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.6 Register Representation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3051</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>============================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3052</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3053</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Menu:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3054</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3055</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Raw and Cooked Registers::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3056</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Register Architecture Functions & Variables::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3057</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Register Information Functions::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3058</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Register and Memory Data::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3059</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Register Caching::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3060</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3061</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3062</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Raw and Cooked Registers,  Next: Register Architecture Functions & Variables,  Up: Register Representation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3063</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3064</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.6.1 Raw and Cooked Registers</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3065</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3066</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3067</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB considers registers to be a set with members numbered linearly from</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3068</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3069</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>registers, the second part to any "pseudo-registers".  Pseudo-registers</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3070</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>have no independent physical existence, but are useful representations</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3071</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>of information within the architecture.  For example the OpenRISC 1000</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3072</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture has up to 32 general purpose registers, which are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3073</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>typically represented as 32-bit (or 64-bit) integers.  However the GPRs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3074</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are also used as operands to the floating point operations, and it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3075</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>could be convenient to define a set of pseudo-registers, to show the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3076</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GPRs represented as floating point values.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3077</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3078</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   For any architecture, the implementer will decide on a mapping from</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3079</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>hardware to GDB register numbers.  The registers corresponding to real</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3080</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>hardware are referred to as "raw" registers, the remaining registers are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3081</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"pseudo-registers".  The total register set (raw and pseudo) is called</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3082</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the "cooked" register set.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3083</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3084</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3085</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Register Architecture Functions & Variables,  Next: Register Information Functions,  Prev: Raw and Cooked Registers,  Up: Register Representation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3086</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3087</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.6.2 Functions and Variables Specifying the Register Architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3088</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------------------------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3089</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3090</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>These `struct gdbarch' functions and variables specify the number and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3091</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>type of registers in the architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3092</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3093</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: CORE_ADDR read_pc (struct regcache *REGCACHE)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3094</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3095</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: void write_pc (struct regcache *REGCACHE,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3096</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          CORE_ADDR VAL)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3097</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Read or write the program counter.  The default value of both</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3098</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     functions is `NULL' (no function available).  If the program</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3099</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     counter is just an ordinary register, it can be specified in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3100</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `struct gdbarch' instead (see `pc_regnum' below) and it will be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3101</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     read or written using the standard routines to access registers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3102</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function need only be specified if the program counter is not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3103</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     an ordinary register.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3104</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3105</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Any register information can be obtained using the supplied</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3106</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register cache, REGCACHE.  *Note Register Caching: Register</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3107</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Caching.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3108</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3109</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3110</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: void pseudo_register_read (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3111</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, struct regcache *REGCACHE, int REGNUM, const</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3112</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          gdb_byte *BUF)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3113</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3114</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: void pseudo_register_write (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3115</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, struct regcache *REGCACHE, int REGNUM, const</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3116</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          gdb_byte *BUF)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3117</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     These functions should be defined if there are any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3118</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     pseudo-registers.  The default value is `NULL'.  REGNUM is the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3119</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     number of the register to read or write (which will be a "cooked"</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3120</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register number) and BUF is the buffer where the value read will be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3121</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     placed, or from which the value to be written will be taken.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3122</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     value in the buffer may be converted to or from a signed or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3123</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     unsigned integral value using one of the utility functions (*note</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3124</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Using Different Register and Memory Data Representations: Register</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3125</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     and Memory Data.).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3126</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3127</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The access should be for the specified architecture, GDBARCH.  Any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3128</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register information can be obtained using the supplied register</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3129</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     cache, REGCACHE.  *Note Register Caching: Register Caching.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3130</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3131</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3132</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Variable: int sp_regnum</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3133</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This specifies the register holding the stack pointer, which may</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3134</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     be a raw or pseudo-register.  It defaults to -1 (not defined), but</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3135</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     it is an error for it not to be defined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3136</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3137</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The value of the stack pointer register can be accessed withing</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3138</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     GDB as the variable `$sp'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3139</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3140</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3141</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Variable: int pc_regnum</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3142</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This specifies the register holding the program counter, which may</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3143</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     be a raw or pseudo-register.  It defaults to -1 (not defined).  If</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3144</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `pc_regnum' is not defined, then the functions `read_pc' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3145</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `write_pc' (see above) must be defined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3146</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3147</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The value of the program counter (whether defined as a register, or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3148</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     through `read_pc' and `write_pc') can be accessed withing GDB as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3149</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the variable `$pc'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3150</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3151</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3152</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Variable: int ps_regnum</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3153</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This specifies the register holding the processor status (often</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3154</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     called the status register), which may be a raw or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3155</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     pseudo-register.  It defaults to -1 (not defined).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3156</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3157</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If defined, the value of this register can be accessed withing GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3158</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     as the variable `$ps'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3159</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3160</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3161</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Variable: int fp0_regnum</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3162</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This specifies the first floating point register.  It defaults to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3163</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     0.  `fp0_regnum' is not needed unless the target offers support</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3164</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     for floating point.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3165</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3166</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3167</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3168</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Register Information Functions,  Next: Register and Memory Data,  Prev: Register Architecture Functions & Variables,  Up: Register Representation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3169</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3170</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.6.3 Functions Giving Register Information</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3171</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3172</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3173</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>These functions return information about registers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3174</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3175</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: const char * register_name (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3176</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, int REGNUM)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3177</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function should convert a register number (raw or pseudo) to a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3178</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register name (as a C `const char *').  This is used both to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3179</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     determine the name of a register for output and to work out the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3180</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     meaning of any register names used as input.  The function may</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3181</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     also return `NULL', to indicate that REGNUM is not a valid</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3182</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3183</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3184</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     For example with the OpenRISC 1000, GDB registers 0-31 are the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3185</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     General Purpose Registers, register 32 is the program counter and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3186</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register 33 is the supervision register (i.e. the processor status</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3187</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register), which map to the strings `"gpr00"' through `"gpr31"',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3188</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `"pc"' and `"sr"' respectively. This means that the GDB command</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3189</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `print $gpr5' should print the value of the OR1K general purpose</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3190</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register 5(1).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3191</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3192</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The default value for this function is `NULL', meaning undefined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3193</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     It should always be defined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3194</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3195</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The access should be for the specified architecture, GDBARCH.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3196</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3197</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3198</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: struct type * register_type (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3199</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, int REGNUM)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3200</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Given a register number, this function identifies the type of data</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3201</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     it may be holding, specified as a `struct type'.  GDB allows</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3202</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     creation of arbitrary types, but a number of built in types are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3203</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     provided (`builtin_type_void', `builtin_type_int32' etc), together</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3204</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     with functions to derive types from these.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3205</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3206</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Typically the program counter will have a type of "pointer to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3207</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function" (it points to code), the frame pointer and stack pointer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3208</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     will have types of "pointer to void" (they point to data on the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3209</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     stack) and all other integer registers will have a type of 32-bit</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3210</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     integer or 64-bit integer.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3211</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3212</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This information guides the formatting when displaying register</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3213</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     information.  The default value is `NULL' meaning no information is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3214</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     available to guide formatting when displaying registers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3215</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3216</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3217</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: void print_registers_info (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3218</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, struct ui_file *FILE, struct frame_info *FRAME, int</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3219</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          REGNUM, int ALL)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3220</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this function to print out one or all of the registers for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3221</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the GDB `info registers' command.  The default value is the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3222</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function `default_print_registers_info', which uses the register</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3223</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     type information (see `register_type' above) to determine how each</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3224</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register should be printed.  Define a custom version of this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3225</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function for fuller control over how the registers are displayed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3226</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3227</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The access should be for the specified architecture, GDBARCH, with</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3228</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     output to the the file specified by the User Interface Independent</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3229</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Output file handle, FILE (*note UI-Independent Output--the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3230</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `ui_out' Functions: UI-Independent Output.).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3231</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3232</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The registers should show their values in the frame specified by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3233</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     FRAME.  If REGNUM is -1 and ALL is zero, then all the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3234</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     "significant" registers should be shown (the implementer should</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3235</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     decide which registers are "significant"). Otherwise only the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3236</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     value of the register specified by REGNUM should be output.  If</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3237</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     REGNUM is -1 and ALL is non-zero (true), then the value of all</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3238</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     registers should be shown.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3239</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3240</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     By default `default_print_registers_info' prints one register per</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3241</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     line, and if ALL is zero omits floating-point registers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3242</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3243</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3244</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: void print_float_info (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3245</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, struct ui_file *FILE, struct frame_info *FRAME,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3246</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          const char *ARGS)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3247</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this function to provide output about the floating point</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3248</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     unit and registers for the GDB `info float' command respectively.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3249</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The default value is `NULL' (not defined), meaning no information</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3250</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     will be provided.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3251</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3252</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The GDBARCH and FILE and FRAME arguments have the same meaning as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3253</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     in the `print_registers_info' function above. The string ARGS</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3254</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     contains any supplementary arguments to the `info float' command.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3255</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3256</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this function if the target supports floating point</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3257</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     operations.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3258</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3259</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3260</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: void print_vector_info (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3261</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, struct ui_file *FILE, struct frame_info *FRAME,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3262</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          const char *ARGS)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3263</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this function to provide output about the vector unit and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3264</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     registers for the GDB `info vector' command respectively.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3265</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     default value is `NULL' (not defined), meaning no information will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3266</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     be provided.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3267</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3268</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The GDBARCH, FILE and FRAME arguments have the same meaning as in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3269</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the `print_registers_info' function above.  The string ARGS</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3270</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     contains any supplementary arguments to the `info vector' command.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3271</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3272</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this function if the target supports vector operations.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3273</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3274</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3275</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: int register_reggroup_p (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3276</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, int REGNUM, struct reggroup *GROUP)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3277</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     GDB groups registers into different categories (general, vector,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3278</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     floating point etc).  This function, given a register, REGNUM, and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3279</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     group, GROUP, returns 1 (true) if the register is in the group and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3280</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3281</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3282</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The information should be for the specified architecture, GDBARCH</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3283</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3284</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The default value is the function `default_register_reggroup_p'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3285</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     which will do a reasonable job based on the type of the register</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3286</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (see the function `register_type' above), with groups for general</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3287</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     purpose registers, floating point registers, vector registers and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3288</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     raw (i.e not pseudo) registers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3289</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3290</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3291</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   ---------- Footnotes ----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3292</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3293</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   (1) Historically, GDB always had a concept of a frame pointer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3294</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>register, which could be accessed via the GDB variable, `$fp'.  That</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3295</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>concept is now deprecated, recognizing that not all architectures have</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3296</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>a frame pointer.  However if an architecture does have a frame pointer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3297</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>register, and defines a register or pseudo-register with the name</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3298</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`"fp"', then that register will be used as the value of the `$fp'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3299</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>variable.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3300</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3301</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3302</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Register and Memory Data,  Next: Register Caching,  Prev: Register Information Functions,  Up: Register Representation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3303</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3304</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.6.4 Using Different Register and Memory Data Representations</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3305</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------------------------------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3306</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3307</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Some architectures have different representations of data objects,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3308</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>depending whether the object is held in a register or memory.  For</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3309</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>example:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3310</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3311</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The Alpha architecture can represent 32 bit integer values in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3312</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     floating-point registers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3313</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3314</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The x86 architecture supports 80-bit floating-point registers.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3315</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `long double' data type occupies 96 bits in memory but only 80</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3316</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     bits when stored in a register.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3317</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3318</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3319</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   In general, the register representation of a data type is determined</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3320</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>by the architecture, or GDB's interface to the architecture, while the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3321</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>memory representation is determined by the Application Binary Interface.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3322</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3323</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   For almost all data types on almost all architectures, the two</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3324</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>representations are identical, and no special handling is needed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3325</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>However, they do occasionally differ.  An architecture may define the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3326</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>following `struct gdbarch' functions to request conversions between the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3327</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>register and memory representations of a data type:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3328</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3329</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: int gdbarch_convert_register_p (struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3330</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          gdbarch *GDBARCH, int REG)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3331</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Return non-zero (true) if the representation of a data value</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3332</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     stored in this register may be different to the representation of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3333</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     that same data value when stored in memory.  The default value is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3334</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `NULL' (undefined).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3335</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3336</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If this function is defined and returns non-zero, the `struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3337</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     gdbarch' functions `gdbarch_register_to_value' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3338</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_value_to_register' (see below) should be used to perform</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3339</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     any necessary conversion.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3340</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3341</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If defined, this function should return zero for the register's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3342</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     native type, when no conversion is necessary.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3343</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3344</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: void gdbarch_register_to_value (struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3345</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          gdbarch *GDBARCH, int REG, struct type *TYPE, char *FROM,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3346</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          char *TO)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3347</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Convert the value of register number REG to a data object of type</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3348</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     TYPE.  The buffer at FROM holds the register's value in raw</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3349</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     format; the converted value should be placed in the buffer at TO.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3350</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3351</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          _Note:_ `gdbarch_register_to_value' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3352</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          `gdbarch_value_to_register' take their REG and TYPE arguments</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3353</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          in different orders.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3354</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3355</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_register_to_value' should only be used with registers for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3356</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     which the `gdbarch_convert_register_p' function returns a non-zero</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3357</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     value.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3358</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3359</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3360</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: void gdbarch_value_to_register (struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3361</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          gdbarch *GDBARCH, struct type *TYPE, int REG, char *FROM,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3362</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          char *TO)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3363</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Convert a data value of type TYPE to register number REG' raw</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3364</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     format.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3365</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3366</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          _Note:_ `gdbarch_register_to_value' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3367</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          `gdbarch_value_to_register' take their REG and TYPE arguments</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3368</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          in different orders.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3369</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3370</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_value_to_register' should only be used with registers for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3371</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     which the `gdbarch_convert_register_p' function returns a non-zero</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3372</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     value.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3373</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3374</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3375</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3376</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Register Caching,  Prev: Register and Memory Data,  Up: Register Representation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3377</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3378</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.6.5 Register Caching</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3379</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3380</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3381</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Caching of registers is used, so that the target does not need to be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3382</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>accessed and reanalyzed multiple times for each register in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3383</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>circumstances where the register value cannot have changed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3384</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3385</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB provides `struct regcache', associated with a particular `struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3386</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>gdbarch' to hold the cached values of the raw registers.  A set of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3387</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions is provided to access both the raw registers (with `raw' in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3388</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>their name) and the full set of cooked registers (with `cooked' in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3389</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>their name).  Functions are provided to ensure the register cache is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3390</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>kept synchronized with the values of the actual registers in the target.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3391</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3392</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Accessing registers through the `struct regcache' routines will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3393</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>ensure that the appropriate `struct gdbarch' functions are called when</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3394</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>necessary to access the underlying target architecture.  In general</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3395</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>users should use the "cooked" functions, since these will map to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3396</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"raw" functions automatically as appropriate.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3397</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3398</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The two key functions are `regcache_cooked_read' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3399</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`regcache_cooked_write' which read or write a register from or to a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3400</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>byte buffer (type `gdb_byte *').  For convenience the wrapper functions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3401</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`regcache_cooked_read_signed', `regcache_cooked_read_unsigned',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3402</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`regcache_cooked_write_signed' and `regcache_cooked_write_unsigned' are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3403</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>provided, which read or write the value using the buffer and convert to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3404</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>or from an integral value as appropriate.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3405</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3406</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3407</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: Frame Interpretation,  Next: Inferior Call Setup,  Prev: Register Representation,  Up: Target Architecture Definition</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3408</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3409</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.7 Frame Interpretation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3410</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3411</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3412</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Menu:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3413</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3414</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* All About Stack Frames::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3415</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Frame Handling Terminology::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3416</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Prologue Caches::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3417</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Functions and Variable to Analyze Frames::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3418</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Functions to Access Frame Data::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3419</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Analyzing Stacks---Frame Sniffers::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3420</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3421</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3422</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>File: gdbint.info,  Node: All About Stack Frames,  Next: Frame Handling Terminology,  Up: Frame Interpretation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3423</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3424</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.7.1 All About Stack Frames</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3425</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3426</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3427</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB needs to understand the stack on which local (automatic) variables</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3428</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are stored.  The area of the stack containing all the local variables</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3429</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>for a function invocation is known as the "stack frame" for that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3430</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>function (or colloquially just as the "frame").  In turn the function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3431</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>that called the function will have its stack frame, and so on back</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3432</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>through the chain of functions that have been called.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3433</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3434</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Almost all architectures have one register dedicated to point to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3435</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>end of the stack (the "stack pointer").  Many have a second register</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3436</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>which points to the start of the currently active stack frame (the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3437</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"frame pointer").  The specific arrangements for an architecture are a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3438</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>key part of the ABI.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3439</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3440</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A diagram helps to explain this.  Here is a simple program to compute</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3441</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>factorials:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3442</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3443</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     #include <stdio.h></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3444</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     int fact (int n)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3445</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3446</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       if (0 == n)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3447</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3448</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           return 1;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3449</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3450</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       else</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3451</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3452</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           return n * fact (n - 1);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3453</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3454</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3455</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3456</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     main ()</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3457</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3458</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       int i;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3459</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3460</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       for (i = 0; i < 10; i++)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3461</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3462</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           int   f = fact (i);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3463</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           printf ("%d! = %d\n", i, f);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3464</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>         }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3465</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3466</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3467</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Consider the state of the stack when the code reaches line 6 after</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3468</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the main program has called `fact (3)'.  The chain of function calls</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3469</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>will be `main ()', `fact (3)', `fact (2)', `fact (1)' and `fact (0)'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3470</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3471</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   In this illustration the stack is falling (as used for example by the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3472</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>OpenRISC 1000 ABI).  The stack pointer (SP) is at the end of the stack</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3473</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(lowest address) and the frame pointer (FP) is at the highest address</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3474</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>in the current stack frame.  The following diagram shows how the stack</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3475</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>looks.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3476</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3477</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3478</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Frame             |   |  |            |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3479</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Number          - |   |  |============|       int fact (int n)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3480</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  |   |  |   i = 3    |       {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3481</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  |   |  |------------|         if (0 == n) {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3482</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  |   |  |   f = ?    |           return  1;  <-------- PC</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3483</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  #4 main()   <   |   |  |------------|        }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3484</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  |   |  |            |         else {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3485</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  |  -+->|------------|   --->    return n * fact (n - 1);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3486</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |   -+-+--+-----o      |  |      }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3487</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                =   | |  |============|  |    }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3488</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |    | |  |   n = 3    |  |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3489</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |    | |  |------------|  |    main ()</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3490</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  #3 fact (3) <     | |  |     o---------+-   {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3491</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |   -+-+->|------------|  | |    int  i;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3492</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  | |  --+-----o      |  | |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3493</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                = | |    |============|  | |    for (i = 0; i < 10; i++) {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3494</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  | |    |   n = 2    |  |  ->    int  f = fact (i);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3495</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  | |    |------------|  |        printf (\"%d! = %d\\n\", i , f);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3496</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  #2 fact (2) <   | |    |     o------+--|      }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3497</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  | |  ->|------------|  |    }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3498</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  |  -+--+-----o      |  |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3499</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                = |   |  |============|  |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3500</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  |   |  |   n = 1    |  |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3501</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  |   |  |------------|  |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3502</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  #1 fact (1) <   |   |  |     o------+--|</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3503</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |  |   |  |------------|  |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3504</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |   ---|--+-----o      |<-+------- FP</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3505</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                =     |  |============|  |                   |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3506</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |      |  |   n = 0    |  |                   |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3507</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |      |  |------------|  |                   |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3508</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  #0 fact (0) <       |  |     o---------                    |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3509</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |      |  |------------|                      |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3510</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |       --+-----o      |<--------- SP         |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3511</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                =        |============|                      |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3512</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |         |  Red Zone  |                      v</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3513</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |         \\/\\/\\/\\/\\/\\/\\/                 Direction of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3514</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  #-1         <          \\/\\/\\/\\/\\/\\/\\/                 stack growth</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3515</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>               |         |            |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3516</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"�]</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3517</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3518</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>In each stack frame, offset 0 from the stack pointer is the frame</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3519</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>pointer of the previous frame and offset 4 (this is illustrating a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3520</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>32-bit architecture) from the stack pointer is the return address.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3521</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Local variables are indexed from the frame pointer, with negative</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3522</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3523</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the argument N.  In the `main' function, offset -4 from the frame</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3524</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>pointer is the local variable I and offset -8 from the frame pointer is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3525</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the local variable F(1).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3526</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3527</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   It is very easy to get confused when examining stacks.  GDB has</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3528</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>terminology it uses rigorously throughout.  The stack frame of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3529</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3530</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>zero.  In this example frame #0 is the stack frame of the call to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3531</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`fact (0)'.  The stack frame of its calling function (`fact (1)' in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3532</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>this case) is numbered #1 and so on back through the chain of calls.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3533</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3534</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The main GDB data structure describing frames is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3535</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`struct frame_info'.  It is not used directly, but only via its</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3536</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3537</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>registers in the frame and a pointer to the code of the function with</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3538</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3539</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>linked list of `frame_info' structs.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3540</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3541</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   ---------- Footnotes ----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3542</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3543</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3544</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Good optimizing compilers would not put anything on the stack for such</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3545</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>simple functions.  Indeed they might eliminate the recursion and use of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3546</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3547</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3548</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3549</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3550</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3551</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.7.2 Frame Handling Terminology</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3552</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3553</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3554</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3555</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>some precise terminology.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3556</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3557</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3558</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3559</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The "NEXT" frame, also sometimes called the inner or newer frame</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3560</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     is the frame of the function called by the function of THIS frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3561</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3562</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3563</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     frame is the frame of the function which called the function of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3564</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     THIS frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3565</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3566</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3567</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3568</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Frames: All About Stack Frames.), if THIS frame is #3 (the call to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3569</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`fact (3)'), the NEXT frame is frame #2 (the call to `fact (2)') and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3570</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the PREVIOUS frame is frame #4 (the call to `main ()').</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3571</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3572</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The "innermost" frame is the frame of the current executing</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3573</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>function, or where the program stopped, in this example, in the middle</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3574</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>of the call to `fact (0))'.  It is always numbered frame #0.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3575</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3576</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The "base" of a frame is the address immediately before the start of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3577</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3578</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>stack) this will be the lowest address and for a stack which grows up</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3579</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>in memory (a "rising" stack) this will be the highest address in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3580</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3581</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3582</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB functions to analyze the stack are typically given a pointer to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3583</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the NEXT frame to determine information about THIS frame.  Information</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3584</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3585</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame are stored in this stack frame.  In this example the frame</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3586</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>pointer of the PREVIOUS frame is stored at offset 0 from the stack</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3587</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>pointer of THIS frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3588</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3589</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3590</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to work out information about THIS frame is referred to as "unwinding".</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3591</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The GDB functions involved in this typically include unwind in their</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3592</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>name.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3593</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3594</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The process of analyzing a target to determine the information that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3595</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3596</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>that carry this out are called sniffers and typically include sniffer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3597</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>in their name.  More than one sniffer may be required to extract all</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3598</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the information for a particular frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3599</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3600</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Because so many functions work using the NEXT frame, there is an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3601</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>issue about addressing the innermost frame--it has no NEXT frame.  To</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3602</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3603</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3604</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3605</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3606</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3607</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.7.3 Prologue Caches</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3608</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>----------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3609</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3610</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>All the frame sniffing functions typically examine the code at the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3611</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3612</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>registers.  The ABI will save old values and set new values of key</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3613</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>registers at the start of each function in what is known as the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3614</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>function "prologue".</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3615</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3616</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   For any particular stack frame this data does not change, so all the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3617</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>standard unwinding functions, in addition to receiving a pointer to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3618</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3619</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>cache" as their second argument.  This can be used to store values</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3620</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>associated with a particular frame, for reuse on subsequent calls</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3621</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>involving the same frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3622</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3623</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   It is up to the user to define the structure used (it is a `void *'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3624</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>pointer) and arrange allocation and deallocation of storage.  However</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3625</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>for general use, GDB provides `struct trad_frame_cache', with a set of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3626</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3627</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>THIS frame, the base address of the frame, a pointer to the struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3628</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`frame_info' for the NEXT frame and details of where the registers of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3629</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the PREVIOUS frame may be found in THIS frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3630</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3631</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Typically the first time any sniffer function is called with NEXT</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3632</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>frame, the prologue sniffer for THIS frame will be `NULL'.  The sniffer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3633</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3634</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>populate it.  Subsequent calls using the same NEXT frame will pass in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3635</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>this prologue cache, so the data can be returned with no additional</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3636</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3637</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3638</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3639</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3640</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3641</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.7.4 Functions and Variable to Analyze Frames</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3642</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3643</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3644</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>These struct `gdbarch' functions and variable should be defined to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3645</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>provide analysis of the stack frame and allow it to be adjusted as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3646</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>required.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3647</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3648</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: CORE_ADDR skip_prologue (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3649</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, CORE_ADDR PC)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3650</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3651</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function which sets up the stack frame, saves the return address</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3652</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     etc.  The code representing the behavior of the function starts</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3653</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     after the prologue.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3654</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3655</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function skips past the prologue of a function if the program</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3656</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     counter, PC, is within the prologue of a function.  The result is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3657</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3658</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     optimizing compilers, this may be a far from trivial exercise.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3659</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     However the required information may be within the binary as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3660</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     DWARF2 debugging information, making the job much easier.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3661</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3662</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3663</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     always be provided, but can take advantage of DWARF2 debugging</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3664</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     information, if that is available.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3665</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3666</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3667</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: int inner_than (CORE_ADDR LHS, CORE_ADDR RHS)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3668</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Given two frame or stack pointers, return non-zero (true) if the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3669</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     first represents the "inner" stack frame and 0 (false) otherwise.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3670</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3671</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     grows up in memory (rising stack) or grows down in memory (falling</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3672</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     stack).  *Note All About Stack Frames: All About Stack Frames, for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3673</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     an explanation of "inner" frames.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3674</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3675</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The default value of this function is `NULL' and it should always</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3676</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3677</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3678</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     growing down in memory) or `core_addr_greaterthan' (for stacks</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3679</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     growing up in memory).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3680</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3681</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3682</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: CORE_ADDR frame_align (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3683</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, CORE_ADDR ADDRESS)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3684</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The architecture may have constraints on how its frames are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3685</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3686</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     to be double-word aligned, but 32-bit versions of the architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3687</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     allocate single-word values to the stack.  Thus extra padding may</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3688</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3689</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3690</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Given a proposed address for the stack pointer, this function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3691</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     returns a suitably aligned address (by expanding the stack frame).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3692</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3693</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The default value is `NULL' (undefined).  This function should be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3694</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3695</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3696</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     stacks) and `align_up' (for rising stacks) will facilitate the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3697</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     implementation of this function.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3698</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3699</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3700</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3701</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Some ABIs reserve space beyond the end of the stack for use by leaf</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3702</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     functions without prologue or epilogue or by exception handlers</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3703</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (for example the OpenRISC 1000).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3704</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3705</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This is known as a "red zone" (AMD terminology).  The AMD64 (nee</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3706</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     x86-64) ABI documentation refers to the "red zone" when describing</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3707</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     this scratch area.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3708</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3709</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3710</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3711</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (see `frame_align' above for an explanation of stack frame</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3712</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     alignment).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3713</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3714</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3715</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3716</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3717</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3718</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.7.5 Functions to Access Frame Data</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3719</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3720</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3721</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>These functions provide access to key registers and arguments in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3722</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>stack frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3723</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3724</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: CORE_ADDR unwind_pc (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3725</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, struct frame_info *NEXT_FRAME)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3726</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function is given a pointer to the NEXT stack frame (*note</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3727</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3728</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     represented) and returns the value of the program counter in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3729</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     PREVIOUS frame (i.e. the frame of the function that called THIS</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3730</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3731</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3732</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The implementation, which must be frame agnostic (work with any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3733</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     frame), is typically no more than:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3734</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3735</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3736</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          pc = frame_unwind_register_unsigned (next_frame, ARCH_PC_REGNUM);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3737</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          return gdbarch_addr_bits_remove (gdbarch, pc);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3738</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3739</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3740</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: CORE_ADDR unwind_sp (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3741</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, struct frame_info *NEXT_FRAME)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3742</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function is given a pointer to the NEXT stack frame (*note</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3743</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3744</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     represented) and returns the value of the stack pointer in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3745</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     PREVIOUS frame (i.e. the frame of the function that called THIS</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3746</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3747</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3748</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The implementation, which must be frame agnostic (work with any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3749</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     frame), is typically no more than:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3750</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3751</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3752</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          sp = frame_unwind_register_unsigned (next_frame, ARCH_SP_REGNUM);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3753</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          return gdbarch_addr_bits_remove (gdbarch, sp);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3754</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3755</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3756</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: int frame_num_args (struct gdbarch *GDBARCH,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3757</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          struct frame_info *THIS_FRAME)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3758</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3759</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     About Stack Frames: All About Stack Frames. for how frames are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3760</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     represented), and returns the number of arguments that are being</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3761</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     passed, or -1 if not known.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3762</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3763</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3764</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     of arguments passed on any stack frame is always unknown.  For many</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3765</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     architectures this will be a suitable default.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3766</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3767</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3768</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3769</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3770</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3771</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.7.6 Analyzing Stacks--Frame Sniffers</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3772</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3773</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3774</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>When a program stops, GDB needs to construct the chain of struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3775</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`frame_info' representing the state of the stack using appropriate</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3776</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"sniffers".</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3777</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3778</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Each architecture requires appropriate sniffers, but they do not form</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3779</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3780</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>required and a sniffer may be suitable for more than one</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3781</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`struct gdbarch'.  Instead sniffers are associated with architectures</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3782</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3783</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3784</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `frame_unwind_append_sniffer' is used to add a new sniffer to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3785</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3786</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3787</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `frame_base_append_sniffer' is used to add a new sniffer which can</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3788</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3789</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3790</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `frame_base_set_default' is used to specify the default base</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3791</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     sniffer.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3792</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3793</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3794</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   These functions all take a reference to `struct gdbarch', so they</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3795</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3796</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>in the `gdbarch' initialization function, after the `gdbarch' struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3797</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>has been set up.  Unless a default has been set, the most recently</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3798</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>appended sniffer will be tried first.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3799</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3800</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The main frame unwinding sniffer (as set by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3801</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`frame_unwind_append_sniffer)' returns a structure specifying a set of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3802</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>sniffing functions:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3803</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3804</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     struct frame_unwind</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3805</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3806</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        enum frame_type            type;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3807</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        frame_this_id_ftype       *this_id;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3808</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        frame_prev_register_ftype *prev_register;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3809</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        const struct frame_data   *unwind_data;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3810</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3811</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        frame_prev_pc_ftype       *prev_pc;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3812</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        frame_dealloc_cache_ftype *dealloc_cache;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3813</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     };</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3814</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3815</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The `type' field indicates the type of frame this sniffer can</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3816</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3817</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Creating Dummy Frames.), signal handler or sentinel.  Signal handlers</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3818</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>sometimes have their own simplified stack structure for efficiency, so</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3819</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>may need their own handlers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3820</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3821</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The `unwind_data' field holds additional information which may be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3822</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>relevant to particular types of frame.  For example it may hold</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3823</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>additional information for signal handler frames.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3824</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3825</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3826</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>information when given a pointer to the NEXT stack frame.  Not all</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3827</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions need be provided.  If an entry is `NULL', the next sniffer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3828</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3829</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3830</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `this_id' determines the stack pointer and function (code entry</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3831</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3832</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3833</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `prev_register' determines where the values of registers for the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3834</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3835</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3836</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `sniffer' takes a look at THIS frame's registers to determine if</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3837</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     this is the appropriate unwinder.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3838</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3839</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3840</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     needed if the program counter is not an ordinary register (*note</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3841</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Functions and Variables Specifying the Register Architecture:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3842</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Register Architecture Functions & Variables.).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3843</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3844</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3845</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     prologue cache for this frame (*note Prologue Caches: Prologue</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3846</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Caches.).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3847</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3848</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3849</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   In general it is only the `this_id' and `prev_register' fields that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3850</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>need be defined for custom sniffers.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3851</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3852</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3853</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`struct frame_base', which refers to the corresponding `frame_unwind'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3854</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>struct and whose fields refer to functions yielding various addresses</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3855</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>within the frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3856</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3857</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     struct frame_base</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3858</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3859</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        const struct frame_unwind *unwind;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3860</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3861</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        frame_this_locals_ftype   *this_locals;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3862</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        frame_this_args_ftype     *this_args;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3863</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     };</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3864</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3865</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   All the functions referred to take a pointer to the NEXT frame as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3866</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>argument. The function referred to by `this_base' returns the base</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3867</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3868</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>returns the base address of local variables in THIS frame and the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3869</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>function referred to by `this_args' returns the base address of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3870</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>function arguments in this frame.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3871</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3872</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   As described above, the base address of a frame is the address</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3873</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>immediately before the start of the NEXT frame.  For a falling stack,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3874</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3875</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the highest address in the frame.  For most architectures the same</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3876</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3877</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>which case the same function can be used for all three entries(1).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3878</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3879</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   ---------- Footnotes ----------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3880</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3881</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   (1) It is worth noting that if it cannot be determined in any other</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3882</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>way (for example by there being a register with the name `"fp"'), then</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3883</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the result of the `this_base' function will be used as the value of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3884</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3885</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(for example with the OpenRISC 1000, this value is the stack pointer,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3886</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`$sp').  In this case a register (raw or pseudo) with the name `"fp"'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3887</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3888</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3889</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3890</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3891</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3892</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3893</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3894</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3895</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3896</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3897</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* About Dummy Frames::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3898</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3899</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3900</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3901</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3902</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3903</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.8.1 About Dummy Frames</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3904</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3905</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3906</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3907</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`call' or `print' commands).  These functions may be breakpointed, and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3908</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>it is essential that if a function does hit a breakpoint, commands like</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3909</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`backtrace' work correctly.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3910</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3911</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3912</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>been called from the point where GDB had previously stopped.  This</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3913</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>requires that GDB can set up stack frames appropriate for such function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3914</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3915</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3916</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3917</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3918</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3919</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.8.2 Functions Creating Dummy Frames</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3920</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3921</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3922</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The following functions provide the functionality to set up such</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3923</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"dummy" stack frames.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3924</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3925</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: CORE_ADDR push_dummy_call (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3926</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, struct value *FUNCTION, struct regcache *REGCACHE,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3927</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          CORE_ADDR BP_ADDR, int NARGS, struct value **ARGS, CORE_ADDR</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3928</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          SP, int STRUCT_RETURN, CORE_ADDR STRUCT_ADDR)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3929</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3930</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     to be called.  `push_dummy_call' is given the arguments to be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3931</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     passed and must copy them into registers or push them on to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3932</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     stack as appropriate for the ABI.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3933</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3934</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     FUNCTION is a pointer to the function that will be called and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3935</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     REGCACHE the register cache from which values should be obtained.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3936</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     BP_ADDR is the address to which the function should return (which</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3937</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     is breakpointed, so GDB can regain control, hence the name).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3938</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3939</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     containing the argument values.  STRUCT_RETURN is non-zero (true)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3940</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     if the function returns a structure, and if so STRUCT_ADDR is the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3941</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     address in which the structure should be returned.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3942</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3943</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     After calling this function, GDB will pass control to the target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3944</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     at the address of the function, which will find the stack and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3945</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     registers set up just as expected.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3946</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3947</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3948</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function is not defined, then GDB will not allow the user to call</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3949</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     functions within the target being debugged.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3950</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3951</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3952</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: struct frame_id unwind_dummy_id (struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3953</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          gdbarch *GDBARCH, struct frame_info *NEXT_FRAME)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3954</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This is the inverse of `push_dummy_call' which restores the stack</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3955</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3956</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     using a dummy stack frame.  The result is a `struct frame_id',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3957</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     which contains the value of the stack pointer and program counter</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3958</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     to be used.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3959</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3960</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3961</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     frame is the frame of the dummy function, which can be unwound, to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3962</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     yield the required stack pointer and program counter from the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3963</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3964</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3965</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The default value is `NULL' (undefined).  If `push_dummy_call' is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3966</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     defined, then this function should also be defined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3967</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3968</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3969</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: CORE_ADDR push_dummy_code (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3970</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, CORE_ADDR SP, CORE_ADDR FUNADDR, struct value</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3971</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          **ARGS, int NARGS, struct type *VALUE_TYPE, CORE_ADDR</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3972</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *REAL_PC, CORE_ADDR *BP_ADDR, struct regcache *REGCACHE)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3973</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If this function is not defined (its default value is `NULL'), a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3974</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3975</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     on the target as its return address.  A temporary breakpoint will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3976</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     be set there, so the location must be writable and have room for a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3977</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoint.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3978</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3979</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3980</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     writable (in ROM possibly), or the ABI might require code to be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3981</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     executed on return from a call to unwind the stack before the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3982</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoint is encountered.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3983</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3984</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If either of these is the case, then push_dummy_code should be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3985</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     defined to push an instruction sequence onto the end of the stack</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3986</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     to which the dummy call should return.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3987</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3988</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The arguments are essentially the same as those to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3989</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `push_dummy_call'.  However the function is provided with the type</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3990</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     of the function result, VALUE_TYPE, BP_ADDR is used to return a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3991</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3992</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     inserted) and REAL PC is used to specify the resume address when</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3993</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     starting the call sequence.  The function should return the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3994</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3995</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3996</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          _Note:_ This does require that code in the stack can be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3997</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          executed.  Some Harvard architectures may not allow this.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3998</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>3999</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4000</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4001</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4002</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4003</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.9 Adding support for debugging core files</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4004</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4005</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4006</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The prerequisite for adding core file support in GDB is to have core</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4007</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>file support in BFD.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4008</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4009</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Once BFD support is available, writing the apropriate</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4010</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`regset_from_core_section' architecture function should be all that is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4011</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4012</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4013</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4014</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4015</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4016</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>11.10 Defining Other Architecture Features</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4017</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==========================================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4018</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4019</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>This section describes other functions and values in `gdbarch',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4020</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>together with some useful macros, that you can use to define the target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4021</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4022</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4023</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`CORE_ADDR gdbarch_addr_bits_remove (GDBARCH, ADDR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4024</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4025</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     really part of the address, then this function is used to zero</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4026</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     those bits in ADDR.  This is only used for addresses of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4027</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     instructions, and even then not in all contexts.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4028</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4029</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     For example, the two low-order bits of the PC on the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4030</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Hewlett-Packard PA 2.0 architecture contain the privilege level of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4031</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the corresponding instruction.  Since instructions must always be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4032</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     aligned on four-byte boundaries, the processor masks out these</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4033</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     bits to generate the actual address of the instruction.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4034</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_addr_bits_remove' would then for example look like that:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4035</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4036</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4037</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            return (addr &= ~0x3);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4038</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4039</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4040</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int address_class_name_to_type_flags (GDBARCH, NAME, TYPE_FLAGS_PTR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4041</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4042</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     referenced by TYPE_FLAGS_PTR to the mask representing the qualifier</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4043</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     and return 1.  If NAME is not a valid address class qualifier name,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4044</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     return 0.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4045</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4046</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4047</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `TYPE_FLAG_ADDRESS_CLASS_1', `TYPE_FLAG_ADDRESS_CLASS_2', or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4048</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     possibly some combination of these values or'd together.  *Note</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4049</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Address Classes: Target Architecture Definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4050</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4051</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int address_class_name_to_type_flags_p (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4052</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Predicate which indicates whether</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4053</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `address_class_name_to_type_flags' has been defined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4054</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4055</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_address_class_type_flags (GDBARCH, BYTE_SIZE, DWARF2_ADDR_CLASS)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4056</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Given a pointers byte size (as described by the debug information)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4057</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     and the possible `DW_AT_address_class' value, return the type flags</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4058</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     used by GDB to represent this address class.  The value returned</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4059</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4060</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `TYPE_FLAG_ADDRESS_CLASS_2', or possibly some combination of these</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4061</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     values or'd together.  *Note Address Classes: Target Architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4062</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4063</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4064</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_address_class_type_flags_p (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4065</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Predicate which indicates whether</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4066</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_address_class_type_flags_p' has been defined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4067</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4068</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`const char *gdbarch_address_class_type_flags_to_name (GDBARCH, TYPE_FLAGS)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4069</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Return the name of the address class qualifier associated with the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4070</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     type flags given by TYPE_FLAGS.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4071</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4072</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4073</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Predicate which indicates whether</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4074</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_address_class_type_flags_to_name' has been defined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4075</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     *Note Address Classes: Target Architecture Definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4076</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4077</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`void gdbarch_address_to_pointer (GDBARCH, TYPE, BUF, ADDR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4078</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Store in BUF a pointer of type TYPE representing the address ADDR,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4079</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4080</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function may safely assume that TYPE is either a pointer or a C++</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4081</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     reference type.  *Note Pointers Are Not Always Addresses: Target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4082</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Architecture Definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4083</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4084</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4085</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Used to notify if the compiler promotes a `short' or `char'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4086</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     parameter to an `int', but still reports the parameter as its</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4087</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     original type, rather than the promoted type.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4088</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4089</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdbarch_bits_big_endian (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4090</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4091</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     match the endianism of the target byte order.  A value of 1 means</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4092</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     that the bits are numbered in a big-endian bit order, 0 means</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4093</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     little-endian.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4094</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4095</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4096</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Calling set_gdbarch_bits_big_endian with a value of 1 indicates</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4097</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     that the bits in the target are numbered in a big-endian bit</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4098</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     order, 0 indicates little-endian.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4099</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4100</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`BREAKPOINT'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4101</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This is the character array initializer for the bit pattern to put</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4102</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     into memory where a breakpoint is set.  Although it's common to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4103</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4104</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     instance, the bit pattern could be an invalid instruction.  The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4105</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoint must be no longer than the shortest instruction of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4106</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4107</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4108</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `BREAKPOINT' has been deprecated in favor of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4109</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_breakpoint_from_pc'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4110</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4111</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`BIG_BREAKPOINT'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4112</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`LITTLE_BREAKPOINT'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4113</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4114</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4115</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `BIG_BREAKPOINT' and `LITTLE_BREAKPOINT' have been deprecated in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4116</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     favor of `gdbarch_breakpoint_from_pc'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4117</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4118</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`const gdb_byte *gdbarch_breakpoint_from_pc (GDBARCH, PCPTR, LENPTR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4119</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Use the program counter to determine the contents and size of a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4120</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoint instruction.  It returns a pointer to a static string</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4121</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     of bytes that encode a breakpoint instruction, stores the length</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4122</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4123</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     necessary) to point to the actual memory location where the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4124</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoint should be inserted.  May return `NULL' to indicate that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4125</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     software breakpoints are not supported.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4126</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4127</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4128</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     it's not required; for instance, the bit pattern could be an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4129</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     invalid instruction.  The breakpoint must be no longer than the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4130</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     shortest instruction of the architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4131</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4132</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Provided breakpoint bytes can be also used by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4133</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `bp_loc_is_permanent' to detect permanent breakpoints.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4134</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4135</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     copy if it was called for a location with permanent breakpoint as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4136</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4137</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     arbitrary parameter value.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4138</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4139</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Replaces all the other BREAKPOINT macros.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4140</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4141</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_memory_insert_breakpoint (GDBARCH, BP_TGT)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4142</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdbarch_memory_remove_breakpoint (GDBARCH, BP_TGT)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4143</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Insert or remove memory based breakpoints.  Reasonable defaults</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4144</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (`default_memory_insert_breakpoint' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4145</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `default_memory_remove_breakpoint' respectively) have been</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4146</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     provided so that it is not necessary to set these for most</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4147</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4148</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_memory_insert_breakpoint' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4149</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_memory_remove_breakpoint' will likely have instructions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4150</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     that are oddly sized or are not stored in a conventional manner.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4151</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4152</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4153</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     custom breakpoint insertion and removal routines if</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4154</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_breakpoint_from_pc' needs to read the target's memory for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4155</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     some reason.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4156</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4157</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`CORE_ADDR gdbarch_adjust_breakpoint_address (GDBARCH, BPADDR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4158</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4159</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoint address adjusted to account for architectural</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4160</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     constraints on breakpoint placement.  This method is not needed by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4161</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     most targets.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4162</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4163</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The FR-V target (see `frv-tdep.c') requires this method.  The FR-V</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4164</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4165</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     are grouped (packed) together into an aggregate instruction or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4166</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     instruction bundle.  When the processor executes one of these</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4167</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     bundles, the component instructions are executed in parallel.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4168</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4169</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     In the course of optimization, the compiler may group instructions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4170</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     from distinct source statements into the same bundle.  The line</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4171</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     number information associated with one of the latter statements</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4172</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     will likely refer to some instruction other than the first one in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4173</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the bundle.  So, if the user attempts to place a breakpoint on one</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4174</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     of these latter statements, GDB must be careful to _not_ place the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4175</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     break instruction on any instruction other than the first one in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4176</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4177</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     bundle execute in parallel, so the _first_ instruction is the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4178</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     instruction at the lowest address and has nothing to do with</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4179</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     execution order.)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4180</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4181</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The FR-V's `gdbarch_adjust_breakpoint_address' method will adjust a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4182</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoint's address by scanning backwards for the beginning of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4183</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the bundle, returning the address of the bundle.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4184</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4185</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4186</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     user's expectation, GDB prints a warning when an adjusted</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4187</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoint is initially set and each time that that breakpoint is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4188</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4189</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4190</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_call_dummy_location (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4191</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4192</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4193</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This method has been replaced by `gdbarch_push_dummy_code' (*note</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4194</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     gdbarch_push_dummy_code::).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4195</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4196</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_cannot_fetch_register (GDBARCH, REGUM)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4197</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function should return nonzero if REGNO cannot be fetched</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4198</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     from an inferior process.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4199</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4200</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4201</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function should return nonzero if REGNO should not be written</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4202</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4203</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     status words, and other special registers.  This function returns</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4204</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     0 as default so that GDB will assume that all registers may be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4205</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     written.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4206</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4207</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4208</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Return non-zero if register REGNUM represents data values of type</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4209</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     TYPE in a non-standard form.  *Note Using Different Register and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4210</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Memory Data Representations: Target Architecture Definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4211</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4212</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4213</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function returns the number of the first floating point</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4214</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register, if the machine has such registers.  Otherwise, it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4215</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     returns -1.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4216</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4217</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`CORE_ADDR gdbarch_decr_pc_after_break (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4218</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4219</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     after the program encounters a breakpoint.  This is often the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4220</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     number of bytes in `BREAKPOINT', though not always.  For most</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4221</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     targets this value will be 0.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4222</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4223</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4224</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If defined, this should evaluate to 1 if ADDR is in a shared</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4225</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     library in which breakpoints cannot be set and so should be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4226</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     disabled.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4227</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4228</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_dwarf2_reg_to_regnum (GDBARCH, DWARF2_REGNR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4229</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Convert DWARF2 register number DWARF2_REGNR into GDB regnum.  If</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4230</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     not defined, no conversion will be performed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4231</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4232</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_ecoff_reg_to_regnum (GDBARCH, ECOFF_REGNR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4233</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Convert ECOFF register number  ECOFF_REGNR into GDB regnum.  If</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4234</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     not defined, no conversion will be performed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4235</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4236</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GCC_COMPILED_FLAG_SYMBOL'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4237</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`GCC2_COMPILED_FLAG_SYMBOL'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4238</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4239</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     for to detect that GCC compiled the file.  The default symbols are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4240</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gcc_compiled.' and `gcc2_compiled.', respectively.  (Currently</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4241</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     only defined for the Delta 68.)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4242</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4243</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdbarch_get_longjmp_target'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4244</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This function determines the target PC address that `longjmp' will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4245</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     jump to, assuming that we have just stopped at a `longjmp'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4246</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoint.  It takes a `CORE_ADDR *' as argument, and stores the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4247</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     target PC value through this pointer.  It examines the current</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4248</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     state of the machine as needed, typically by using a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4249</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4250</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     like to get the offset from the target's `jmpbuf.h', that header</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4251</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     file cannot be assumed to be available when building a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4252</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     cross-debugger.)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4253</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4254</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`DEPRECATED_IBM6000_TARGET'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4255</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4256</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     conditional should be eliminated (FIXME) and replaced by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4257</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     feature-specific macros.  It was introduced in haste and we are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4258</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     repenting at leisure.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4259</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4260</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4261</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     An x86-based target can define this to use the generic x86</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4262</td>
         <td><a id="l4261-rev" class="blame-revision" href="/websvn/revision?repname=openrisc&path=%2Fopenrisc%2Ftrunk%2Fgnu-stable%2Fgdb-7.2%2Fgdb%2Fdoc%2F&rev=342">342</a></td>
         <td>jeremybenn</td>
         <td class="code"><pre><code>     watchpoint support; see *note I386_USE_GENERIC_WATCHPOINTS:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4263</td>
         <td><a id="l4262-rev" class="blame-revision" href="/websvn/revision?repname=openrisc&path=%2Fopenrisc%2Ftrunk%2Fgnu-stable%2Fgdb-7.2%2Fgdb%2Fdoc%2F&rev=330">330</a></td>
         <td>jeremybenn</td>
         <td class="code"><pre><code>     Algorithms.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4264</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4265</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdbarch_in_function_epilogue_p (GDBARCH, ADDR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4266</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4267</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function.  The epilogue of a function is defined as the part of a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4268</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function where the stack frame of the function already has been</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4269</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     destroyed up to the final `return from function call' instruction.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4270</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4271</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_in_solib_return_trampoline (GDBARCH, PC, NAME)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4272</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this function to return nonzero if the program is stopped</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4273</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     in the trampoline that returns from a shared library.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4274</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4275</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`target_so_ops.in_dynsym_resolve_code (PC)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4276</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this to return nonzero if the program is stopped in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4277</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     dynamic linker.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4278</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4279</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SKIP_SOLIB_RESOLVER (PC)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4280</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this to evaluate to the (nonzero) address at which execution</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4281</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4282</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function.  A zero value indicates that it is not important or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4283</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     necessary to set a breakpoint to get through the dynamic linker</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4284</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     and that single stepping will suffice.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4285</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4286</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4287</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this when the architecture needs to handle non-pointer to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4288</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     address conversions specially.  Converts that value to an address</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4289</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     according to the current architectures conventions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4290</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4291</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     _Pragmatics: When the user copies a well defined expression from</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4292</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     their source code and passes it, as a parameter, to GDB's `print'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4293</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     command, they should get the same value as would have been</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4294</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     computed by the target program.  Any deviation from this rule can</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4295</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     cause major confusion and annoyance, and needs to be justified</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4296</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     carefully.  In other words, GDB doesn't really have the freedom to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4297</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     do these conversions in clever and useful ways.  It has, however,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4298</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     been pointed out that users aren't complaining about how GDB casts</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4299</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4300</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     address from a disassembly listing and give it to `x/i'.  Adding</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4301</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     an architecture method like `gdbarch_integer_to_address' certainly</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4302</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4303</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4304</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     *Note Pointers Are Not Always Addresses: Target Architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4305</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4306</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4307</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`CORE_ADDR gdbarch_pointer_to_address (GDBARCH, TYPE, BUF)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4308</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4309</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     format for the current architecture.  Return the byte address the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4310</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     pointer refers to.  *Note Pointers Are Not Always Addresses:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4311</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Target Architecture Definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4312</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4313</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4314</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Convert the raw contents of register REGNUM into a value of type</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4315</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     TYPE.  *Note Using Different Register and Memory Data</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4316</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Representations: Target Architecture Definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4317</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4318</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4319</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Convert the value of register REG from its raw form to its virtual</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4320</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     form.  *Note Raw and Virtual Register Representations: Target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4321</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Architecture Definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4322</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4323</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4324</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Convert the value of register REG from its virtual form to its raw</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4325</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     form.  *Note Raw and Virtual Register Representations: Target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4326</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Architecture Definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4327</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4328</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`const struct regset *regset_from_core_section (struct gdbarch * GDBARCH, const char * SECT_NAME, size_t SECT_SIZE)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4329</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Return the appropriate register set for a core file section with</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4330</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     name SECT_NAME and size SECT_SIZE.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4331</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4332</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SOFTWARE_SINGLE_STEP_P()'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4333</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this as 1 if the target does not have a hardware single-step</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4334</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     mechanism.  The macro `SOFTWARE_SINGLE_STEP' must also be defined.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4335</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4336</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SOFTWARE_SINGLE_STEP(SIGNAL, INSERT_BREAKPOINTS_P)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4337</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4338</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     INSERT_BREAKPOINTS_P) breakpoints at each possible destinations of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4339</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the next instruction.  See `sparc-tdep.c' and `rs6000-tdep.c' for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4340</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     examples.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4341</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4342</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`set_gdbarch_sofun_address_maybe_missing (GDBARCH, SET)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4343</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Somebody clever observed that, the more actual addresses you have</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4344</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4345</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     relocating them.  So whenever there's some other way the debugger</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4346</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     could find the address it needs, you should omit it from the debug</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4347</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     info, to make linking faster.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4348</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4349</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Calling `set_gdbarch_sofun_address_maybe_missing' with a non-zero</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4350</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     argument SET indicates that a particular set of hacks of this sort</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4351</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4352</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     debugging information.  `N_SO' stabs mark the beginning and ending</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4353</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4354</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     mark the starts and ends of functions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4355</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4356</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     In this case, GDB assumes two things:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4357</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4358</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        * `N_FUN' stabs have an address of zero.  Instead of using those</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4359</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          addresses, you should find the address where the function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4360</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          starts by taking the function name from the stab, and then</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4361</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4362</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          table).  In other words, the stab has the name, and the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4363</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          linker/assembler symbol table is the only place that carries</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4364</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          the address.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4365</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4366</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4367</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          the `N_FUN' stabs that appear before and after the `N_SO'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4368</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          stab, and guess the starting and ending addresses of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4369</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          compilation unit from them.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4370</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4371</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_stabs_argument_has_addr (GDBARCH, TYPE)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4372</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this function to return nonzero if a function argument of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4373</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     type TYPE is passed by reference instead of value.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4374</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4375</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`CORE_ADDR gdbarch_push_dummy_call (GDBARCH, FUNCTION, REGCACHE, BP_ADDR, NARGS, ARGS, SP, STRUCT_RETURN, STRUCT_ADDR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4376</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4377</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function onto the stack.  In addition to pushing NARGS, the code</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4378</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     should push STRUCT_ADDR (when STRUCT_RETURN is non-zero), and the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4379</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     return address (BP_ADDR).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4380</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4381</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     FUNCTION is a pointer to a `struct value'; on architectures that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4382</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4383</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     value.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4384</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4385</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Returns the updated top-of-stack pointer.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4386</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4387</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4388</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Given a stack based call dummy, push the instruction sequence</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4389</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (including space for a breakpoint) to which the called function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4390</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     should return.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4391</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4392</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Set BP_ADDR to the address at which the breakpoint instruction</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4393</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     should be inserted, REAL_PC to the resume address when starting</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4394</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the call sequence, and return the updated inner-most stack address.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4395</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4396</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     By default, the stack is grown sufficient to hold a frame-aligned</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4397</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4398</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     reserved for that breakpoint, and REAL_PC set to FUNADDR.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4399</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4400</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This method replaces `gdbarch_call_dummy_location (GDBARCH)'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4401</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4402</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_sdb_reg_to_regnum (GDBARCH, SDB_REGNR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4403</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Use this function to convert sdb register SDB_REGNR into GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4404</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     regnum.  If not defined, no conversion will be done.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4405</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4406</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`enum return_value_convention gdbarch_return_value (struct gdbarch *GDBARCH, struct type *VALTYPE, struct regcache *REGCACHE, void *READBUF, const void *WRITEBUF)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4407</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Given a function with a return-value of type RETTYPE, return which</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4408</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     return-value convention that function would use.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4409</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4410</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     GDB currently recognizes two function return-value conventions:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4411</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4412</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     in registers; and `RETURN_VALUE_STRUCT_CONVENTION' where the return</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4413</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     value is found in memory and the address of that memory location is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4414</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4415</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4416</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If the register convention is being used, and WRITEBUF is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4417</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     non-`NULL', also copy the return-value in WRITEBUF into REGCACHE.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4418</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4419</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4420</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     non-`NULL', also copy the return value from REGCACHE into READBUF</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4421</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (REGCACHE contains a copy of the registers from the just returned</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4422</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4423</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4424</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     _Maintainer note: This method replaces separate predicate, extract,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4425</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     store methods.  By having only one method, the logic needed to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4426</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4427</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     one place.  If GDB were written in an OO language, this method</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4428</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     would instead return an object that knew how to perform the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4429</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     register return-value extract and store._</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4430</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4431</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     _Maintainer note: This method does not take a GCC_P parameter, and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4432</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4433</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     requires per-compiler or per-function information be identified,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4434</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     then the replacement of RETTYPE with `struct value' FUNCTION</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4435</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     should be pursued._</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4436</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4437</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4438</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the inner most frame.  While replacing REGCACHE with a `struct</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4439</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     frame_info' FRAME parameter would remove that limitation there has</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4440</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     yet to be a demonstrated need for such a change._</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4441</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4442</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`void gdbarch_skip_permanent_breakpoint (GDBARCH, REGCACHE)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4443</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Advance the inferior's PC past a permanent breakpoint.  GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4444</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     normally steps over a breakpoint by removing it, stepping one</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4445</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     instruction, and re-inserting the breakpoint.  However, permanent</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4446</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     breakpoints are hardwired into the inferior, and can't be removed,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4447</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     so this strategy doesn't work.  Calling</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4448</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4449</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     so that execution will resume just after the breakpoint.  This</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4450</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     function does the right thing even when the breakpoint is in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4451</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     delay slot of a branch or jump.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4452</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4453</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4454</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If the target machine has trampoline code that sits between</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4455</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     callers and the functions being called, then define this function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4456</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     to return a new PC that is at the start of the real function.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4457</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4458</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_deprecated_fp_regnum (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4459</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If the frame pointer is in a register, use this function to return</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4460</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the number of that register.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4461</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4462</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_stab_reg_to_regnum (GDBARCH, STAB_REGNR)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4463</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Use this function to convert stab register STAB_REGNR into GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4464</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     regnum.  If not defined, no conversion will be done.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4465</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4466</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SYMBOL_RELOADING_DEFAULT'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4467</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The default value of the "symbol-reloading" variable.  (Never</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4468</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4469</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4470</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`TARGET_CHAR_BIT'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4471</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Number of bits in a char; defaults to 8.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4472</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4473</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_char_signed (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4474</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Non-zero if `char' is normally signed on this architecture; zero if</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4475</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     it should be unsigned.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4476</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4477</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The ISO C standard requires the compiler to treat `char' as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4478</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4479</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     character in the standard execution set is supposed to be positive.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4480</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Most compilers treat `char' as signed, but `char' is unsigned on</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4481</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the IBM S/390, RS6000, and PowerPC targets.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4482</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4483</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_double_bit (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4484</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Number of bits in a double float; defaults to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4485</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4486</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4487</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_float_bit (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4488</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4489</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4490</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_int_bit (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4491</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Number of bits in an integer; defaults to `4 * TARGET_CHAR_BIT'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4492</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4493</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_long_bit (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4494</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Number of bits in a long integer; defaults to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4495</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `4 * TARGET_CHAR_BIT'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4496</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4497</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_long_double_bit (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4498</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Number of bits in a long double float; defaults to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4499</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `2 * gdbarch_double_bit (GDBARCH)'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4500</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4501</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_long_long_bit (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4502</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Number of bits in a long long integer; defaults to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4503</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `2 * gdbarch_long_bit (GDBARCH)'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4504</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4505</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_ptr_bit (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4506</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Number of bits in a pointer; defaults to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4507</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_int_bit (GDBARCH)'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4508</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4509</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_short_bit (GDBARCH)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4510</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Number of bits in a short integer; defaults to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4511</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `2 * TARGET_CHAR_BIT'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4512</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4513</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`void gdbarch_virtual_frame_pointer (GDBARCH, PC, FRAME_REGNUM, FRAME_OFFSET)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4514</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Returns a `(REGISTER, OFFSET)' pair representing the virtual frame</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4515</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4516</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     are not used, a default definition simply returns</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4517</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdbarch_deprecated_fp_regnum' (or `gdbarch_sp_regnum', if no</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4518</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     frame pointer is defined), with an offset of zero.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4519</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4520</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4521</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If non-zero, the target has support for hardware-assisted</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4522</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     watchpoints.  *Note watchpoints: Algorithms, for more details and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4523</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     other related macros.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4524</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4525</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`int gdbarch_print_insn (GDBARCH, VMA, INFO)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4526</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This is the function used by GDB to print an assembly instruction.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4527</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     It prints the instruction at address VMA in debugged memory and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4528</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     returns the length of the instruction, in bytes.  This usually</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4529</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     points to a function in the `opcodes' library (*note Opcodes:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4530</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4531</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `disassemble_info') defined in the header file</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4532</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `include/dis-asm.h', and used to pass information to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4533</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     instruction decoding routine.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4534</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4535</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`frame_id gdbarch_dummy_id (GDBARCH, FRAME)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4536</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4537</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     inferior function call's dummy frame.  The value returned must</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4538</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     match the dummy frame stack value previously saved by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4539</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `call_function_by_hand'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4540</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4541</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4542</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4543</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     *Note Using Different Register and Memory Data Representations:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4544</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4545</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4546</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4547</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Motorola M68K target conditionals.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4548</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4549</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`BPT_VECTOR'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4550</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this to be the 4-bit location of the breakpoint trap</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4551</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4552</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4553</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`REMOTE_BPT_VECTOR'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4554</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Defaults to `1'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4555</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4556</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4557</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4558</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4559</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4560</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4561</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4562</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4563</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The following files add a target to GDB:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4564</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4565</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb/TTT-tdep.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4566</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Contains any miscellaneous code required for this target machine.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4567</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     On some machines it doesn't exist at all.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4568</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4569</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb/ARCH-tdep.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4570</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4571</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4572</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     machine's processor chip (registers, stack, etc.).  It can be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4573</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     shared among many targets that use the same processor architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4574</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4575</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4576</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   (Target header files such as `gdb/config/ARCH/tm-TTT.h',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4577</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb/config/ARCH/tm-ARCH.h', and `config/tm-OS.h' are no longer used.)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4578</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4579</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A GDB description for a new architecture, arch is created by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4580</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4581</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the source file `ARCH-tdep.c'.  For example, in the case of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4582</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>OpenRISC 1000, this function is called `_initialize_or1k_tdep' and is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4583</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>found in the file `or1k-tdep.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4584</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4585</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The object file resulting from compiling this source file, which will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4586</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4587</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>specified in the GDB `configure.tgt' file, which includes a large case</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4588</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>statement pattern matching against the `--target' option of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4589</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`configure' script.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4590</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4591</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     _Note:_ If the architecture requires multiple source files, the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4592</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4593</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     However if there are header files, the dependencies on these will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4594</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     not be picked up from the entries in `configure.tgt'. The</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4595</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `Makefile.in' file will need extending to show these dependencies.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4596</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4597</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A new struct gdbarch, defining the new architecture, is created</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4598</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>within the `_initialize_ARCH_tdep' function by calling</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4599</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdbarch_register':</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4600</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4601</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     void gdbarch_register (enum bfd_architecture    architecture,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4602</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                            gdbarch_init_ftype      *init_func,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4603</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4604</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4605</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   This function has been described fully in an earlier section.  *Note</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4606</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>How an Architecture is Represented: How an Architecture is Represented.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4607</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4608</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The new `struct gdbarch' should contain implementations of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4609</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4610</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the basic layout of the target machine's processor chip (registers,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4611</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>stack, etc.).  It can be shared among many targets that use the same</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4612</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4613</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4614</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4615</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4616</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4617</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>12 Target Descriptions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4618</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>**********************</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4619</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4620</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The target architecture definition (*note Target Architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4621</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Definition::) contains GDB's hard-coded knowledge about an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4622</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture.  For some platforms, it is handy to have more flexible</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4623</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4624</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>a processor or development board.  "Target descriptions" provide a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4625</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>mechanism for the user to tell GDB more about what their target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4626</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>supports, or for the target to tell GDB directly.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4627</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4628</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4629</td>
         <td><a id="l4628-rev" class="blame-revision" href="/websvn/revision?repname=openrisc&path=%2Fopenrisc%2Ftrunk%2Fgnu-stable%2Fgdb-7.2%2Fgdb%2Fdoc%2F&rev=342">342</a></td>
         <td>jeremybenn</td>
         <td class="code"><pre><code>selecting target descriptions, see *note Target Descriptions:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4630</td>
         <td><a id="l4629-rev" class="blame-revision" href="/websvn/revision?repname=openrisc&path=%2Fopenrisc%2Ftrunk%2Fgnu-stable%2Fgdb-7.2%2Fgdb%2Fdoc%2F&rev=330">330</a></td>
         <td>jeremybenn</td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4631</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>about the GDB internals.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4632</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4633</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4634</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4635</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Target Descriptions Implementation::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4636</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4637</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4638</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4639</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4640</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4641</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>12.1 Target Descriptions Implementation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4642</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=======================================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4643</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4644</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4645</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>existing target, it discards any existing target description and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4646</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>reverts to a default gdbarch.  Then, after connecting, it looks for a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4647</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>new target description by calling `target_find_description'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4648</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4649</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A description may come from a user specified file (XML), the remote</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4650</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4651</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`to_read_description' routine in the target vector.  For instance, the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4652</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>remote target supports guessing whether a MIPS target is 32-bit or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4653</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>64-bit based on the size of the `g' packet.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4654</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4655</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If any target description is found, GDB creates a new gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4656</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>incorporating the description by calling `gdbarch_update_p'.  Any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4657</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`<architecture>' element is handled first, to determine which</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4658</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture's gdbarch initialization routine is called to create the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4659</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>new architecture.  Then the initialization routine is called, and has a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4660</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4661</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the target description.  For instance, it can recognize any properties</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4662</td>
         <td><a id="l4661-rev" class="blame-revision" href="/websvn/revision?repname=openrisc&path=%2Fopenrisc%2Ftrunk%2Fgnu-stable%2Fgdb-7.2%2Fgdb%2Fdoc%2F&rev=342">342</a></td>
         <td>jeremybenn</td>
         <td class="code"><pre><code>set by a `to_read_description' routine.  Also see *note Adding Target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4663</td>
         <td><a id="l4662-rev" class="blame-revision" href="/websvn/revision?repname=openrisc&path=%2Fopenrisc%2Ftrunk%2Fgnu-stable%2Fgdb-7.2%2Fgdb%2Fdoc%2F&rev=330">330</a></td>
         <td>jeremybenn</td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4664</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4665</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4666</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4667</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4668</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>12.2 Adding Target Described Register Support</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4669</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=============================================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4670</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4671</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Target descriptions can report additional registers specific to an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4672</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>instance of the target.  But it takes a little work in the architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4673</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>specific routines to support this.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4674</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4675</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A target description must either have no registers or a complete</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4676</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>set--this avoids complexity in trying to merge standard registers with</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4677</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4678</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to validate that a description with registers has everything it needs.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4679</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>To keep architecture code simple, the same mechanism is used to assign</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4680</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4681</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4682</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If `tdesc_has_registers' returns 1, the description contains</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4683</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4684</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4685</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4686</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     searching for a matching gdbarch or allocating a new one.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4687</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4688</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4689</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4690</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Use `tdesc_numbered_register' and `tdesc_numbered_register_choices'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4691</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     to locate the expected registers in the standard features.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4692</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4693</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Return `NULL' if a required feature is missing, or if any standard</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4694</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     feature is missing expected registers.  This will produce a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4695</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4696</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4697</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Free the allocated data before returning, unless</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4698</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4699</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4700</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Call `set_gdbarch_num_regs' as usual, with a number higher than any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4701</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4702</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4703</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Call `tdesc_use_registers' after creating a new gdbarch, before</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4704</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     returning it.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4705</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4706</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4707</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   After `tdesc_use_registers' has been called, the architecture's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4708</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4709</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>will not be called; that information will be taken from the target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4710</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4711</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>registers in the description.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4712</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4713</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Pseudo-registers require some extra care:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4714</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4715</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Using `tdesc_numbered_register' allows the architecture to give</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4716</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     constant register numbers to standard architectural registers, e.g.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4717</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4718</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     always numbered above `num_regs', which may be increased by the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4719</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     description, constant numbers can not be used for pseudos.  They</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4720</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     must be numbered relative to `num_regs' instead.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4721</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4722</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The description will not describe pseudo-registers, so the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4723</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     architecture must call `set_tdesc_pseudo_register_name',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4724</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `set_tdesc_pseudo_register_type', and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4725</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4726</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4727</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     internal register numbers, so the same routines used for the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4728</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     gdbarch equivalents are usually suitable.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4729</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4730</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4731</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4732</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4733</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4734</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>13 Target Vector Definition</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4735</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>***************************</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4736</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4737</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The target vector defines the interface between GDB's abstract handling</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4738</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4739</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>control over a process or a serial port.  GDB includes some 30-40</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4740</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4741</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>only a few of them.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4742</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4743</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4744</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4745</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Managing Execution State::</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4746</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4747</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4748</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4749</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4750</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4751</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>13.1 Managing Execution State</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4752</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=============================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4753</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4754</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>A target vector can be completely inactive (not pushed on the target</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4755</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>stack), active but not running (pushed, but not connected to a fully</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4756</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4757</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>inferior).  Most targets are only completely inactive or completely</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4758</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>active, but some support persistent connections to a target even when</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4759</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the target has exited or not yet started.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4760</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4761</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   For example, connecting to the simulator using `target sim' does not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4762</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4763</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>until `run'.  Similarly, after `kill', the program can not continue</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4764</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>executing.  But in both cases GDB remains connected to the simulator,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4765</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>and target-specific commands are directed to the simulator.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4766</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4767</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4768</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>onto the stack in its `to_open' routine (by calling `push_target'), and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4769</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>unpush itself from the stack in its `to_mourn_inferior' routine (by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4770</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>calling `unpush_target').</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4771</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4772</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A target which supports both partial and complete activation should</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4773</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>still call `push_target' in `to_open', but not call `unpush_target' in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4774</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`to_mourn_inferior'.  Instead, it should call either</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4775</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`target_mark_running' or `target_mark_exited' in its `to_open',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4776</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>depending on whether the target is fully active after connection.  It</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4777</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>should also call `target_mark_running' any time the inferior becomes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4778</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>fully active (e.g. in `to_create_inferior' and `to_attach'), and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4779</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4780</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`to_mourn_inferior').  The target should also make sure to call</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4781</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`target_mourn_inferior' from its `to_kill', to return the target to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4782</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4783</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4784</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4785</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4786</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4787</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>13.2 Existing Targets</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4788</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4789</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4790</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4791</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4792</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4793</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4794</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4795</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>13.2.2 Standard Protocol and Remote Stubs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4796</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4797</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4798</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB's file `remote.c' talks a serial protocol to code that runs in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4799</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>target system.  GDB provides several sample "stubs" that can be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4800</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>integrated into target programs or operating systems for this purpose;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4801</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4802</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>emulators, and simulators already have a GDB stub built into them, and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4803</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>maintenance of the remote protocol must be careful to preserve</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4804</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>compatibility.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4805</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4806</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4807</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>target code.  What follows is a discussion of integrating the SPARC</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4808</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>stub into a complicated operating system (rather than a simple</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4809</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4810</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4811</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The trap handling code in the stub assumes the following upon entry</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4812</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4813</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4814</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4815</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     trap;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4816</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4817</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  2. traps are disabled;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4818</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4819</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  3. you are in the correct trap window.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4820</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4821</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   As long as your trap handler can guarantee those conditions, then</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4822</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>there is no reason why you shouldn't be able to "share" traps with the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4823</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>stub.  The stub has no requirement that it be jumped to directly from</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4824</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4825</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>which is provided by the external environment.  For instance, this could</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4826</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>set up the hardware traps to actually execute code which calls the stub</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4827</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>first, and then transfers to its own trap handler.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4828</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4829</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   For the most point, there probably won't be much of an issue with</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4830</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"sharing" traps, as the traps we use are usually not used by the kernel,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4831</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>and often indicate unrecoverable error conditions.  Anyway, this is all</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4832</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4833</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>trap for us is for `ta 1'.  Without that, we can't single step or do</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4834</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>breakpoints.  Everything else is unnecessary for the proper operation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4835</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4836</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4837</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   From reading the stub, it's probably not obvious how breakpoints</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4838</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4839</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4840</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>13.2.3 ROM Monitor Interface</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4841</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4842</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4843</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>13.2.4 Custom Protocols</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4844</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4845</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4846</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>13.2.5 Transport Layer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4847</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4848</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4849</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>13.2.6 Builtin Simulator</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4850</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4851</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4852</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4853</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4854</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4855</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4856</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>*******************</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4857</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4858</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Several files control GDB's configuration for native support:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4859</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4860</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb/config/ARCH/XYZ.mh'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4861</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Specifies Makefile fragments needed by a _native_ configuration on</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4862</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     machine XYZ.  In particular, this lists the required</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4863</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     native-dependent object files, by defining `NATDEPFILES=...'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4864</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4865</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     XYZ, by defining `NAT_FILE= nm-XYZ.h'.  You can also define</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4866</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `NAT_CFLAGS', `NAT_ADD_FILES', `NAT_CLIBS', `NAT_CDEPS',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4867</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `NAT_GENERATED_FILES', etc.; see `Makefile.in'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4868</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4869</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     _Maintainer's note: The `.mh' suffix is because this file</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4870</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4871</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     machine XYZ.  While the file is no longer used for this purpose,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4872</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the `.mh' suffix remains.  Perhaps someone will eventually rename</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4873</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     these fragments so that they have a `.mn' suffix._</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4874</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4875</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4876</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (`nm.h' is a link to this file, created by `configure').  Contains</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4877</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     C macro definitions describing the native system environment, such</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4878</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     as child process control and core file support.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4879</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4880</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb/XYZ-nat.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4881</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Contains any miscellaneous C code required for this native support</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4882</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     of this machine.  On some machines it doesn't exist at all.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4883</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4884</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   There are some "generic" versions of routines that can be used by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4885</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4886</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>defined in your `nm-XYZ.h' file.  If these routines work for the XYZ</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4887</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>host, you can just include the generic file's name (with `.o', not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4888</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`.c') in `NATDEPFILES'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4889</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4890</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4891</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>need to write routines that perform the same functions as the generic</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4892</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>file.  Put them into `XYZ-nat.c', and put `XYZ-nat.o' into</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4893</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`NATDEPFILES'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4894</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4895</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4896</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This contains the _target_ops vector_ that supports Unix child</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4897</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     processes on systems which use ptrace and wait to control the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4898</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     child.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4899</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4900</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`procfs.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4901</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This contains the _target_ops vector_ that supports Unix child</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4902</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     processes on systems which use /proc to control the child.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4903</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4904</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`fork-child.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4905</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This does the low-level grunge that uses Unix system calls to do a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4906</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     "fork and exec" to start up a child process.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4907</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4908</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`infptrace.c'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4909</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This is the low level interface to inferior processes for systems</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4910</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4911</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4912</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>14.1 ptrace</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4913</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4914</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4915</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>14.2 /proc</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4916</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4917</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4918</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>14.3 win32</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4919</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4920</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4921</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>14.4 shared libraries</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4922</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4923</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4924</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>14.5 Native Conditionals</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4925</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4926</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4927</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4928</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>undefined, to control compilation when the host and target systems are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4929</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the same.  These macros should be defined (or left undefined) in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4930</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`nm-SYSTEM.h'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4931</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4932</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4933</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     An x86-based machine can define this to use the generic x86</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4934</td>
         <td><a id="l4933-rev" class="blame-revision" href="/websvn/revision?repname=openrisc&path=%2Fopenrisc%2Ftrunk%2Fgnu-stable%2Fgdb-7.2%2Fgdb%2Fdoc%2F&rev=342">342</a></td>
         <td>jeremybenn</td>
         <td class="code"><pre><code>     watchpoint support; see *note I386_USE_GENERIC_WATCHPOINTS:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4935</td>
         <td><a id="l4934-rev" class="blame-revision" href="/websvn/revision?repname=openrisc&path=%2Fopenrisc%2Ftrunk%2Fgnu-stable%2Fgdb-7.2%2Fgdb%2Fdoc%2F&rev=330">330</a></td>
         <td>jeremybenn</td>
         <td class="code"><pre><code>     Algorithms.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4936</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4937</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SOLIB_ADD (FILENAME, FROM_TTY, TARG, READSYMS)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4938</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4939</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     symbols in FILENAME to be added to GDB's symbol table.  If</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4940</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     READSYMS is zero symbols are not read but any necessary low level</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4941</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     processing for FILENAME is still done.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4942</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4943</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SOLIB_CREATE_INFERIOR_HOOK'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4944</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Define this to expand into any shared-library-relocation code that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4945</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     you want to be run just after the child process has been forked.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4946</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4947</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`START_INFERIOR_TRAPS_EXPECTED'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4948</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4949</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4950</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If the actual number of traps is something other than 2, then</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4951</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     define this macro to expand into the number expected.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4952</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4953</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4954</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4955</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4956</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4957</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>15 Support Libraries</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4958</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4959</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4960</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4961</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>========</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4962</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4963</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>BFD provides support for GDB in several ways:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4964</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4965</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4966</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     BFD will identify a variety of file types, including a.out, coff,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4967</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     and several variants thereof, as well as several kinds of core</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4968</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     files.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4969</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4970</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_access to sections of files_</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4971</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     BFD parses the file headers to determine the names, virtual</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4972</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4973</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     sections in files (such as the text section or the data section).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4974</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     GDB simply calls BFD to read or write section X at byte offset Y</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4975</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     for length Z.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4976</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4977</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_specialized core file support_</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4978</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4979</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     in a core file, the signal with which the program failed, and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4980</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     whether a core file matches (i.e. could be a core dump of) a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4981</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     particular executable file.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4982</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4983</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_locating the symbol information_</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4984</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     GDB uses an internal interface of BFD to determine where to find</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4985</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4986</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     itself handles the reading of symbols, since BFD does not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4987</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     "understand" debug symbols, but GDB uses BFD's cached information</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4988</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4989</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4990</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>15.2 opcodes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4991</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4992</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4993</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The opcodes library provides GDB's disassembler.  (It's a separate</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4994</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4995</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4996</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>15.3 readline</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4997</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=============</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4998</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>4999</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The `readline' library provides a set of functions for use by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5000</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>applications that allow users to edit command lines as they are typed</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5001</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5002</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5003</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>15.4 libiberty</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5004</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==============</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5005</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5006</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The `libiberty' library provides a set of functions and features that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5007</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>integrate and improve on functionality found in modern operating</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5008</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>systems.  Broadly speaking, such features can be divided into three</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5009</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>groups: supplemental functions (functions that may be missing in some</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5010</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5011</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>uniform and easier to use interface for commonly used standard</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5012</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions), and extensions (which provide additional functionality</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5013</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>beyond standard functions).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5014</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5015</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5016</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>instance the C++ demangler, the IEEE floating format support functions,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5017</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the input options parser `getopt', the `obstack' extension, and other</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5018</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5019</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5020</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>15.4.1 `obstacks' in GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5021</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5022</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5023</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The obstack mechanism provides a convenient way to allocate and free</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5024</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5025</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>like a stack.  Objects (of any nature, size and alignment) are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5026</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>allocated and freed in a LIFO fashion on an obstack (see `libiberty''s</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5027</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>documentation for a more detailed explanation of `obstacks').</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5028</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5029</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The most noticeable use of the `obstacks' in GDB is in object files.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5030</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>There is an obstack associated with each internal representation of an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5031</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>object file.  Lots of things get allocated on these `obstacks':</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5032</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>dictionary entries, blocks, blockvectors, symbols, minimal symbols,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5033</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>types, vectors of fundamental types, class fields of types, object</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5034</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>files section lists, object files section offset lists, line tables,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5035</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>symbol tables, partial symbol tables, string tables, symbol table</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5036</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5037</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>import and export lists (som), unwind information (hppa), dwarf2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5038</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>location expressions data.  Plus various strings such as directory</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5039</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>names strings, debug format strings, names of types.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5040</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5041</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   An essential and convenient property of all data on `obstacks' is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5042</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>that memory for it gets allocated (with `obstack_alloc') at various</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5043</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>times during a debugging session, but it is released all at once using</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5044</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the `obstack_free' function.  The `obstack_free' function takes a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5045</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>pointer to where in the stack it must start the deletion from (much</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5046</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>like the cleanup chains have a pointer to where to start the cleanups).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5047</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Because of the stack like structure of the `obstacks', this allows to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5048</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>free only a top portion of the obstack.  There are a few instances in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5049</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB where such thing happens.  Calls to `obstack_free' are done after</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5050</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>some local data is allocated to the obstack.  Only the local data is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5051</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5052</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the `obstack_alloc' and the `obstack_free' allocates anything else on</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5053</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the same obstack.  For this reason it is best and safest to use</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5054</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>temporary `obstacks'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5055</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5056</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5057</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>under the condition that we know the `obstacks' memory is no longer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5058</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>needed.  In GDB we get rid of the `obstacks' only when we get rid of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5059</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5060</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5061</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5062</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==============</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5063</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5064</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Regex conditionals.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5065</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5066</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`C_ALLOCA'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5067</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5068</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`NFAILURES'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5069</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5070</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`RE_NREGS'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5071</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5072</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SIGN_EXTEND_CHAR'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5073</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5074</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SWITCH_ENUM_BUG'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5075</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5076</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SYNTAX_TABLE'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5077</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5078</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`Sword'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5079</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5080</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5081</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5082</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>15.6 Array Containers</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5083</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=====================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5084</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5085</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Often it is necessary to manipulate a dynamic array of a set of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5086</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>objects.  C forces some bookkeeping on this, which can get cumbersome</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5087</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5088</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>using a typesafe vector type.  The functions defined will be inlined</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5089</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>when compiling, and so the abstraction cost should be zero.  Domain</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5090</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>checks are added to detect programming errors.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5091</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5092</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   An example use would be an array of symbols or section information.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5093</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The array can be grown as symbols are read in (or preallocated), and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5094</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5095</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>bookkeeping.  Because the arrays are type safe, there is no danger of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5096</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>accidentally mixing up the contents.  Think of these as C++ templates,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5097</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>but implemented in C.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5098</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5099</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Because of the different behavior of structure objects, scalar</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5100</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>objects and of pointers, there are three flavors of vector, one for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5101</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>each of these variants.  Both the structure object and pointer variants</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5102</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>pass pointers to objects around -- in the former case the pointers are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5103</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5104</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>dereferenced and the objects copied into the vector.  The scalar object</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5105</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>variant is suitable for `int'-like objects, and the vector elements are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5106</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>returned by value.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5107</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5108</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5109</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>returns a boolean iteration condition and updates the iteration</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5110</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>variable passed by reference.  Because the iterator will be inlined,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5111</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the address-of can be optimized away.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5112</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5113</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The vectors are implemented using the trailing array idiom, thus they</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5114</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are not resizeable without changing the address of the vector object</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5115</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>itself.  This means you cannot have variables or fields of vector type</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5116</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-- always use a pointer to a vector.  The one exception is the final</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5117</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>field of a structure, which could be a vector type.  You will have to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5118</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>use the `embedded_size' & `embedded_init' calls to create such objects,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5119</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>and they will probably not be resizeable (so don't use the "safe"</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5120</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5121</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>pointer to an array of data), because, if we allow `NULL' to also</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5122</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>represent an empty vector, empty vectors occupy minimal space in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5123</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>structure containing them.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5124</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5125</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Each operation that increases the number of active elements is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5126</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>available in "quick" and "safe" variants.  The former presumes that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5127</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>there is sufficient allocated space for the operation to succeed (it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5128</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>dies if there is not).  The latter will reallocate the vector, if</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5129</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>needed.  Reallocation causes an exponential increase in vector size.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5130</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>If you know you will be adding N elements, it would be more efficient</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5131</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to use the reserve operation before adding the elements with the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5132</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>"quick" operation.  This will ensure there are at least as many</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5133</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>elements as you ask for, it will exponentially increase if there are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5134</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5135</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>but do not want the exponential increase (for instance, you know this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5136</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>is the last allocation), use a negative number for reservation.  You</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5137</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>can also create a vector of a specific size from the get go.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5138</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5139</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   You should prefer the push and pop operations, as they append and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5140</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>remove from the end of the vector.  If you need to remove several items</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5141</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>in one go, use the truncate operation.  The insert and remove</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5142</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>operations allow you to change elements in the middle of the vector.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5143</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>There are two remove operations, one which preserves the element</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5144</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>ordering `ordered_remove', and one which does not `unordered_remove'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5145</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5146</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>rather than invoke a memmove operation.  The `lower_bound' function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5147</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>will determine where to place an item in the array using insert that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5148</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>will maintain sorted order.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5149</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5150</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5151</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>accessor will return the address of the start of the vector.  Also the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5152</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`space' predicate will tell you whether there is spare capacity in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5153</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>vector.  You will not normally need to use these two functions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5154</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5155</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Vector types are defined using a `DEF_VEC_{O,P,I}(TYPENAME)' macro.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5156</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Variables of vector type are declared using a `VEC(TYPENAME)' macro.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5157</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The characters `O', `P' and `I' indicate whether TYPENAME is an object</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5158</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(`O'), pointer (`P') or integral (`I') type.  Be careful to pick the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5159</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5160</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the wrong one.  There is a check, which results in a compile-time</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5161</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5162</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`O' versions, as that is not possible in plain C.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5163</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5164</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   An example of their use would be,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5165</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5166</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     DEF_VEC_P(tree);   // non-managed tree vector.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5167</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5168</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     struct my_struct {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5169</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5170</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     };</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5171</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5172</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     struct my_struct *s;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5173</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5174</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5175</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     VEC_safe_push(tree, s->v, decl); // append some decl onto the end</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5176</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     for (ix = 0; VEC_iterate(tree, s->v, ix, elt); ix++)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5177</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5178</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5179</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The `vec.h' file provides details on how to invoke the various</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5180</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5181</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5182</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_length'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5183</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5184</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5185</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_empty'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5186</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Return true if the array has no elements.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5187</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5188</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_last'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5189</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_index'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5190</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Return the last or arbitrary item in the array.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5191</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5192</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_iterate'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5193</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Access an array element and indicate whether the array has been</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5194</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     traversed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5195</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5196</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_alloc'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5197</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_free'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5198</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Create and destroy an array.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5199</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5200</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5201</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_embedded_init'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5202</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Helpers for embedding an array as the final element of another</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5203</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5204</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5205</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_copy'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5206</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5207</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5208</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_space'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5209</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5210</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5211</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_reserve'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5212</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Ensure a certain amount of free space.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5213</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5214</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5215</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_safe_push'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5216</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Append to an array, either assuming the space is available, or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5217</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5218</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5219</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_pop'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5220</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5221</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5222</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_truncate'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5223</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5224</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5225</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_safe_grow'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5226</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5227</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5228</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_replace'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5229</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Overwrite an item in the array.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5230</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5231</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5232</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_safe_insert'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5233</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Insert an item into the middle of the array.  Either the space must</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5234</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     already exist, or the space is created.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5235</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5236</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_ordered_remove'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5237</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_unordered_remove'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5238</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5239</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5240</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_block_remove'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5241</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5242</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5243</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_address'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5244</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5245</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5246</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`VEC_lower_bound'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5247</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Binary search the array.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5248</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5249</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5250</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>15.7 include</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5251</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5252</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5253</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5254</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5255</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5256</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16 Coding</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5257</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5258</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5259</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>This chapter covers topics that are lower-level than the major</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5260</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5261</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5262</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.1 Cleanups</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5263</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5264</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5265</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Cleanups are a structured way to deal with things that need to be done</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5266</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>later.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5267</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5268</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   When your code does something (e.g., `xmalloc' some memory, or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5269</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`open' a file) that needs to be undone later (e.g., `xfree' the memory</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5270</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>or `close' the file), it can make a cleanup.  The cleanup will be done</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5271</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5272</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to the top level; when an error occurs and the stack is unwound; or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5273</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5274</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Alternatively you can elect to discard the cleanups you created.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5275</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5276</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5277</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5278</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`struct cleanup *OLD_CHAIN;'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5279</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Declare a variable which will hold a cleanup chain handle.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5280</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5281</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`OLD_CHAIN = make_cleanup (FUNCTION, ARG);'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5282</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Make a cleanup which will cause FUNCTION to be called with ARG (a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5283</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5284</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     later be passed to `do_cleanups' or `discard_cleanups'.  Unless</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5285</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     you are going to call `do_cleanups' or `discard_cleanups', you can</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5286</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ignore the result from `make_cleanup'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5287</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5288</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`do_cleanups (OLD_CHAIN);'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5289</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Do all cleanups added to the chain since the corresponding</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5290</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `make_cleanup' call was made.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5291</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5292</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`discard_cleanups (OLD_CHAIN);'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5293</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Same as `do_cleanups' except that it just removes the cleanups from</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5294</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the chain and does not call the specified functions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5295</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5296</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5297</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`make_cleanups' includes the cleanup passed to the call and any later</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5298</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>cleanups appended to the chain (but not yet discarded or performed).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5299</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>E.g.:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5300</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5301</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     make_cleanup (a, 0);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5302</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5303</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       struct cleanup *old = make_cleanup (b, 0);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5304</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5305</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5306</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       do_cleanups (old);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5307</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5308</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5309</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>will call `c()' and `b()' but will not call `a()'.  The cleanup that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5310</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>calls `a()' will remain in the cleanup chain, and will be done later</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5311</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>unless otherwise discarded.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5312</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5313</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5314</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>creates.  Failing to do this leads to non-deterministic behavior since</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5315</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the caller will arbitrarily do or discard your functions cleanups.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5316</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>This need leads to two common cleanup styles.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5317</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5318</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The first style is try/finally.  Before it exits, your code-block</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5319</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>calls `do_cleanups' with the old cleanup chain and thus ensures that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5320</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5321</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>following code-segment avoids a memory leak problem (even when `error'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5322</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>is called and a forced stack unwind occurs) by ensuring that the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5323</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`xfree' will always be called:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5324</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5325</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     struct cleanup *old = make_cleanup (null_cleanup, 0);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5326</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5327</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     make_cleanup (xfree, data);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5328</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ... blah blah ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5329</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     do_cleanups (old);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5330</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5331</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The second style is try/except.  Before it exits, your code-block</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5332</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5333</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>that any created cleanups are not performed.  For instance, the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5334</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>following code segment, ensures that the file will be closed but only</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5335</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>if there is an error:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5336</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5337</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     FILE *file = fopen ("afile", "r");</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5338</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5339</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ... blah blah ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5340</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     discard_cleanups (old);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5341</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     return file;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5342</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5343</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Some functions, e.g., `fputs_filtered()' or `error()', specify that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5344</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>they "should not be called when cleanups are not in place".  This means</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5345</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5346</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>interruption must be on the cleanup chain before you call these</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5347</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions, since they might never return to your code (they `longjmp'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5348</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5349</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5350</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.2 Per-architecture module data</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5351</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=================================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5352</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5353</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The multi-arch framework includes a mechanism for adding module</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5354</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5355</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture object.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5356</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5357</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A module registers one or more per-architecture data-pointers using:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5358</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5359</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: struct gdbarch_data *</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5360</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>gdbarch_data_register_pre_init (gdbarch_data_pre_init_ftype *PRE_INIT)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5361</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     PRE_INIT is used to, on-demand, allocate an initial value for a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5362</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     per-architecture data-pointer using the architecture's obstack</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5363</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5364</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     architecture creation, it is not parameterized with the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5365</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     architecture.  and must not call modules that use per-architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5366</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     data.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5367</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5368</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: struct gdbarch_data *</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5369</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>gdbarch_data_register_post_init (gdbarch_data_post_init_ftype</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5370</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *POST_INIT)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5371</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     POST_INIT is used to obtain an initial value for a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5372</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     per-architecture data-pointer _after_.  Since POST_INIT is always</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5373</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     called after architecture creation, it both receives the fully</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5374</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5375</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     per-architecture data (care needs to be taken to ensure that those</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5376</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     other modules do not try to call back to this module as that will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5377</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5378</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5379</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5380</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>identify the per-architecture data-pointer added for that module.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5381</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5382</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The per-architecture data-pointer is accessed using the function:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5383</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5384</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> -- Architecture Function: void * gdbarch_data (struct gdbarch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5385</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          *GDBARCH, struct gdbarch_data *DATA_HANDLE)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5386</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Given the architecture ARCH and module data handle DATA_HANDLE</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5387</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (returned by `gdbarch_data_register_pre_init' or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5388</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5389</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     current value of the per-architecture data-pointer.  If the data</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5390</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5391</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     corresponding PRE_INIT or POST_INIT method.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5392</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5393</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5394</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5395</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     struct nozel { int total; };</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5396</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     static struct gdbarch_data *nozel_handle;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5397</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5398</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A module can extend the architecture vector, adding additional</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5399</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>per-architecture data, using the PRE_INIT method.  The module's</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5400</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>per-architecture data is then initialized during architecture creation.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5401</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5402</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   In the below, the module's per-architecture _nozel_ is added.  An</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5403</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture can specify its nozel by calling `set_gdbarch_nozel' from</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5404</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdbarch_init'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5405</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5406</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     static void *</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5407</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     nozel_pre_init (struct obstack *obstack)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5408</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5409</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       struct nozel *data = OBSTACK_ZALLOC (obstack, struct nozel);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5410</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       return data;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5411</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5412</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5413</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     extern void</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5414</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     set_gdbarch_nozel (struct gdbarch *gdbarch, int total)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5415</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5416</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       struct nozel *data = gdbarch_data (gdbarch, nozel_handle);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5417</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       data->total = nozel;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5418</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5419</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5420</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A module can on-demand create architecture dependent data structures</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5421</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5422</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5423</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   In the below, the nozel's total is computed on-demand by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5424</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`nozel_post_init' using information obtained from the architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5425</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5426</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     static void *</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5427</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     nozel_post_init (struct gdbarch *gdbarch)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5428</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5429</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5430</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       nozel->total = gdbarch... (gdbarch);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5431</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       return data;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5432</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     }</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5433</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5434</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     extern int</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5435</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     nozel_total (struct gdbarch *gdbarch)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5436</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5437</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       struct nozel *data = gdbarch_data (gdbarch, nozel_handle);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5438</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>       return data->total;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5439</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5440</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5441</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.3 Wrapping Output Lines</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5442</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5443</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5444</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5445</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`fputs_demangled' needs only to have calls to `wrap_here' added in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5446</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>places that would be good breaking points.  The utility routines will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5447</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>take care of actually wrapping if the line width is exceeded.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5448</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5449</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The argument to `wrap_here' is an indentation string which is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5450</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5451</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>and used later.  It must remain valid until the next call to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5452</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`wrap_here' or until a newline has been printed through the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5453</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`*_filtered' functions.  Don't pass in a local variable and then return!</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5454</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5455</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5456</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>space.  If you call it before printing a space, make sure that your</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5457</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>indentation properly accounts for the leading space that will print if</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5458</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the line wraps there.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5459</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5460</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5461</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>finish by printing a newline, to flush the wrap buffer, before switching</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5462</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to unfiltered (`printf') output.  Symbol reading routines that print</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5463</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5464</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5465</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.4 GDB Coding Standards</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5466</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5467</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5468</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB follows the GNU coding standards, as described in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5469</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5470</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>from GNU archive sites.  GDB takes a strict interpretation of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5471</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>standard; in general, when the GNU standard recommends a practice but</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5472</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5473</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5474</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB follows an additional set of coding standards specific to GDB,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5475</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5476</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5477</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5478</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5479</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5480</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB assumes an ISO/IEC 9899:1990 (a.k.a. ISO C90) compliant compiler.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5481</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5482</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5483</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5484</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.4.2 Memory Management</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5485</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5486</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5487</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB does not use the functions `malloc', `realloc', `calloc', `free'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5488</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>and `asprintf'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5489</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5490</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB uses the functions `xmalloc', `xrealloc' and `xcalloc' when</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5491</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5492</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>return when the memory pool is empty.  Instead, they unwind the stack</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5493</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>using cleanups.  These functions return `NULL' when requested to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5494</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>allocate a chunk of memory of size zero.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5495</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5496</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   _Pragmatics: By using these functions, the need to check every</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5497</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5498</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>behavior._</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5499</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5500</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB does not use the function `free'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5501</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5502</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB uses the function `xfree' to return memory to the memory pool.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5503</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Consistent with ISO-C, this function ignores a request to free a `NULL'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5504</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5505</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5506</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   _Pragmatics: On some systems `free' fails when passed a `NULL'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5507</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5508</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5509</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB can use the non-portable function `alloca' for the allocation of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5510</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5511</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5512</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   _Pragmatics: This function is very non-portable.  Some systems</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5513</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5514</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5515</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB uses the string function `xstrdup' and the print function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5516</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5517</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5518</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   _Pragmatics: `asprintf' and `strdup' can fail.  Print functions such</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5519</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5520</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5521</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.4.3 Compiler Warnings</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5522</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5523</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5524</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5525</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`--disable-werror' when building GDB.  The exceptions are listed in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5526</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>file `gdb/MAINTAINERS'.  The default, when building with GCC, is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5527</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`--enable-werror'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5528</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5529</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   This option causes GDB (when built using GCC) to be compiled with a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5530</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5531</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>those flags are treated as errors.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5532</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5533</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5534</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5535</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`-Wall'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5536</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Recommended GCC warnings.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5537</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5538</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`-Wdeclaration-after-statement'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5539</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5540</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     but GCC 2.x and C89 do not.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5541</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5542</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`-Wpointer-arith'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5543</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5544</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`-Wformat-nonliteral'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5545</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Non-literal format strings, with a few exceptions, are bugs - they</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5546</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5547</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     GDB uses the `format printf' attribute on all `printf' like</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5548</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     functions this checks not just `printf' calls but also calls to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5549</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     functions such as `fprintf_unfiltered'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5550</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5551</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`-Wno-pointer-sign'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5552</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     In version 4.0, GCC began warning about pointer argument passing or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5553</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     assignment even when the source and destination differed only in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5554</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5555</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     between `char' and `unsigned char'.  In early 2006 the GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5556</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     developers decided correcting these warnings wasn't worth the time</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5557</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     it would take.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5558</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5559</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`-Wno-unused-parameter'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5560</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Due to the way that GDB is implemented many functions have unused</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5561</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5562</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `ATTRIBUTE_UNUSED' is not used as it leads to false negatives --</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5563</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     it is not an error to have `ATTRIBUTE_UNUSED' on a parameter that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5564</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     is being used.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5565</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5566</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`-Wno-unused'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5567</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5568</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5569</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     These are warnings which might be useful for GDB, but are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5570</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     currently too noisy to enable with `-Werror'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5571</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5572</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5573</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.4.4 Formatting</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5574</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5575</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5576</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The standard GNU recommendations for formatting must be followed</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5577</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5578</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5579</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A function declaration should not have its name in column zero.  A</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5580</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>function definition should have its name in column zero.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5581</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5582</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     /* Declaration */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5583</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     static void foo (void);</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5584</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     /* Definition */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5585</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5586</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     foo (void)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5587</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     {</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5588</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5589</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5590</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   _Pragmatics: This simplifies scripting.  Function definitions can be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5591</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>found using `^function-name'._</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5592</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5593</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5594</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>opening parenthesis of its argument list (except for macro definitions,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5595</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>as required by C).  There must not be a space after an open</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5596</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>paren/bracket or before a close paren/bracket.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5597</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5598</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   While additional whitespace is generally helpful for reading, do not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5599</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5600</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>whitespace after the end of a program line (as of 1/99, some 600 lines</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5601</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5602</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>difficulties for `diff' and `patch' utilities.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5603</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5604</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Pointers are declared using the traditional K&R C style:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5605</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5606</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     void *foo;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5607</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5608</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5609</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5610</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     void * foo;</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5611</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5612</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5613</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5614</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5615</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5616</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5617</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5618</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Block comments must appear in the following form, with no `/*'- or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5619</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`*/'-only lines, and no leading `*':</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5620</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5621</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     /* Wait for control to return from inferior to debugger.  If inferior</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5622</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5623</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        returning.  That is why there is a loop in this function.  When</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5624</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        this function actually returns it means the inferior should be left</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5625</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        stopped and GDB should read more commands.  */</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5626</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5627</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   (Note that this format is encouraged by Emacs; tabbing for a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5628</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>multi-line comment works correctly, and `M-q' fills the block</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5629</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5630</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5631</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Put a blank line between the block comments preceding function or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5632</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>variable definitions, and the definition itself.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5633</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5634</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5635</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>than trying to fit them into the 20 characters left at the end of a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5636</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>line, since either the comment or the code will inevitably get longer</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5637</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5638</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5639</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.4.6 C Usage</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5640</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5641</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5642</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Code must not depend on the sizes of C data types, the format of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5643</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>host's floating point numbers, the alignment of anything, or the order</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5644</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>of evaluation of expressions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5645</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5646</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5647</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>areas in GDB that might be affected by the overhead of a function call,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5648</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>mainly in symbol reading.  Most of GDB's performance is limited by the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5649</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>target interface (whether serial line or system call).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5650</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5651</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   However, use functions with moderation.  A thousand one-line</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5652</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions are just as hard to understand as a single thousand-line</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5653</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5654</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5655</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   _Macros are bad, M'kay._ (But if you have to use a macro, make sure</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5656</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5657</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5658</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Declarations like `struct foo *' should be used in preference to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5659</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5660</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5661</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.4.7 Function Prototypes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5662</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5663</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5664</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5665</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>function.  Prototypes for GDB functions must include both the argument</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5666</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>type and name, with the name matching that used in the actual function</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5667</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>definition.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5668</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5669</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5670</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>that callers include, except for `_initialize_*' functions, which must</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5671</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>be external so that `init.c' construction works, but shouldn't be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5672</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5673</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5674</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Where a source file needs a forward declaration of a static function,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5675</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5676</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5677</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.4.8 Internal Error Recovery</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5678</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5679</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5680</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>During its execution, GDB can encounter two types of errors.  User</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5681</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>errors and internal errors.  User errors include not only a user</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5682</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5683</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>object files and system errors when interacting with the target.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5684</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Internal errors include situations where GDB has detected, at run time,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5685</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5686</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5687</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5688</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb_assert'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5689</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5690</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB must not call `abort' or `assert'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5691</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5692</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5693</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>code detected a user error, recovered from it and issued a `warning' or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5694</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the code failed to correctly recover from the user error and issued an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5695</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5696</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5697</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5698</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5699</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5700</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5701</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5702</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.4.10 File Names</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5703</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5704</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5705</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Any file used when building the core of GDB must be in lower case.  Any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5706</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>file used when building the core of GDB must be 8.3 unique.  These</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5707</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>requirements apply to both source and generated files.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5708</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5709</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   _Pragmatics: The core of GDB must be buildable on many platforms</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5710</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>including DJGPP and MacOS/HFS.  Every time an unfriendly file is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5711</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5712</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>need to be modified accordingly.  Compare the convoluted conversion</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5713</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>process needed to transform `COPYING' into `copying.c' with the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5714</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5715</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5716</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5717</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>core of GDB) must be added to `gdb/config/djgpp/fnchange.lst'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5718</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5719</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   _Pragmatics: This is clearly a compromise._</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5720</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5721</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   When GDB has a local version of a system header file (ex `string.h')</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5722</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the file name based on the POSIX header prefixed with `gdb_'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5723</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(`gdb_string.h').  These headers should be relatively independent: they</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5724</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5725</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>host; they should include only system headers; they should refer only</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5726</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5727</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB and GDBSERVER.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5728</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5729</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5730</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5731</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5732</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5733</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5734</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>A `.c' file should include `defs.h' first.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5735</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5736</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A `.c' file should directly include the `.h' file of every</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5737</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>declaration and/or definition it directly refers to.  It cannot rely on</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5738</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>indirect inclusion.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5739</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5740</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5741</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>declaration and/or definition it directly refers to.  It cannot rely on</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5742</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5743</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>directly included.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5744</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5745</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   An external declaration should only appear in one include file.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5746</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5747</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   An external declaration should never appear in a `.c' file.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5748</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5749</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`-Wmissing-declaration'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5750</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5751</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A `typedef' definition should only appear in one include file.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5752</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5753</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   An opaque `struct' declaration can appear in multiple `.h' files.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5754</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5755</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>instead of an include.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5756</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5757</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   All `.h' files should be wrapped in:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5758</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5759</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5760</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     #define INCLUDE_FILE_NAME_H</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5761</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     header body</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5762</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5763</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5764</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>16.4.12 Clean Design and Portable Implementation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5765</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5766</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5767</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5768</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>semantics.  Some things are done in certain ways in GDB because long</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5769</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>experience has shown that the more obvious ways caused various kinds of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5770</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>trouble.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5771</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5772</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5773</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(including VALUEs, object files, and instructions).  Such things must</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5774</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>be byte-swapped using `SWAP_TARGET_AND_HOST' in GDB, or one of the swap</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5775</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>routines defined in `bfd.h', such as `bfd_get_32'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5776</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5777</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   You can't assume that you know what interface is being used to talk</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5778</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to the target system.  All references to the target must go through the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5779</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>current `target_ops' vector.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5780</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5781</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   You can't assume that the host and target machines are the same</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5782</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>machine (except in the "native" support modules).  In particular, you</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5783</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5784</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>on the host machine.  Target code must bring along its own header files</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5785</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>- written from scratch or explicitly donated by their owner, to avoid</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5786</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>copyright problems.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5787</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5788</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Insertion of new `#ifdef''s will be frowned upon.  It's much better</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5789</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>to write the code portably than to conditionalize it for various</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5790</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>systems.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5791</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5792</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   New `#ifdef''s which test for specific compilers or manufacturers or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5793</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>operating systems are unacceptable.  All `#ifdef''s should test for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5794</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>features.  The information about which configurations contain which</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5795</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>features should be segregated into the configuration files.  Experience</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5796</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>has proven far too often that a feature unique to one particular system</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5797</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5798</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>predefined macro for your current system will become worthless over</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5799</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>time, as new versions of your system come out that behave differently</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5800</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5801</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5802</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Adding code that handles specific architectures, operating systems,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5803</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>target interfaces, or hosts, is not acceptable in generic code.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5804</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5805</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   One particularly notorious area where system dependencies tend to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5806</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>creep in is handling of file names.  The mainline GDB code assumes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5807</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Posix semantics of file names: absolute file names begin with a forward</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5808</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>slash `/', slashes are used to separate leading directories,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5809</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5810</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>on non-Posix systems such as MS-Windows.  To avoid system-dependent</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5811</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>code where you need to take apart or construct a file name, use the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5812</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>following portable macros:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5813</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5814</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`HAVE_DOS_BASED_FILE_SYSTEM'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5815</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5816</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     whose filesystems belong to the MS-DOS/MS-Windows family.  Use this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5817</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     symbol to write conditional code which should only be compiled for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5818</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     such hosts.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5819</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5820</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5821</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Evaluates to a non-zero value if C is a directory separator</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5822</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     character.  On Unix and GNU/Linux systems, only a slash `/' is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5823</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     such a character, but on Windows, both `/' and `\' will pass.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5824</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5825</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`IS_ABSOLUTE_PATH (FILE)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5826</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5827</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     For Unix and GNU/Linux hosts, a name which begins with a slash `/'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5828</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     is absolute.  On DOS and Windows, `d:/foo' and `x:\bar' are also</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5829</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     absolute file names.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5830</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5831</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`FILENAME_CMP (F1, F2)'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5832</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5833</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     appropriate for the underlying host filesystem.  For Posix systems,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5834</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     this simply calls `strcmp'; on case-insensitive filesystems it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5835</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     will call `strcasecmp' instead.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5836</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5837</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5838</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Evaluates to a character which separates directories in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5839</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `PATH'-style lists, typically held in environment variables.  This</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5840</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     character is `:' on Unix, `;' on DOS and Windows.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5841</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5842</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`SLASH_STRING'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5843</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5844</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     absolute filename from leading directories and the file's basename.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5845</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `SLASH_STRING' is `"/"' on most systems, but might be `"\\"' for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5846</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     some Windows-based ports.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5847</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5848</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   In addition to using these macros, be sure to use portable library</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5849</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5850</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>basename part from a file name, use the `dirname' and `basename'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5851</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>library functions (available in `libiberty' for platforms which don't</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5852</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>provide them), instead of searching for a slash with `strrchr'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5853</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5854</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Another way to generalize GDB along a particular interface is with an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5855</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>attribute struct.  For example, GDB has been generalized to handle</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5856</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>multiple kinds of remote interfaces--not by `#ifdef's everywhere, but</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5857</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>by defining the `target_ops' structure and having a current target (as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5858</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>well as a stack of targets below it, for memory references).  Whenever</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5859</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>something needs to be done that depends on which remote interface we are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5860</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>using, a flag in the current target_ops structure is tested (e.g.,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5861</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`target_has_stack'), or a function is called through a pointer in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5862</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>current target_ops structure.  In this way, when a new remote interface</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5863</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5864</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>implements the new remote interface.  Other examples of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5865</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>attribute-structs are BFD access to multiple kinds of object file</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5866</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>formats, or GDB's access to multiple source languages.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5867</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5868</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Please avoid duplicating code.  For example, in GDB 3.x all the code</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5869</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>interfacing between `ptrace' and the rest of GDB was duplicated in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5870</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`*-dep.c', and so changing something was very painful.  In GDB 4.x,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5871</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5872</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>deal with variations between systems the same way any system-independent</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5873</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>file would (hooks, `#if defined', etc.), and machines which are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5874</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>radically different don't need to use `infptrace.c' at all.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5875</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5876</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   All debugging code must be controllable using the `set debug MODULE'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5877</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>command.  Do not use `printf' to print trace messages.  Use</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5878</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5879</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5880</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5881</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5882</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5883</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>17 Porting GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5884</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>**************</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5885</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5886</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Most of the work in making GDB compile on a new machine is in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5887</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>specifying the configuration of the machine.  Porting a new</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5888</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>architecture to GDB can be broken into a number of steps.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5889</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5890</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Ensure a BFD exists for executables of the target architecture in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5891</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the `bfd' directory.  If one does not exist, create one by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5892</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5893</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5894</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Implement a disassembler for the target architecture in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5895</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `opcodes' directory.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5896</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5897</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Define the target architecture in the `gdb' directory (*note</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5898</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5899</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the new target to `configure.tgt' with the names of the files that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5900</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     contain the code.  By convention the target architecture</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5901</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     definition for an architecture ARCH is placed in `ARCH-tdep.c'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5902</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5903</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Within `ARCH-tdep.c' define the function `_initialize_ARCH_tdep'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5904</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     which calls `gdbarch_register' to create the new `struct gdbarch'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5905</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     for the architecture.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5906</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5907</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * If a new remote target is needed, consider adding a new remote</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5908</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5909</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     if at all possible use the GDB _Remote Serial Protocol_ for this</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5910</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     and implement the server side protocol independently with the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5911</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     target.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5912</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5913</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * If desired implement a simulator in the `sim' directory.  This</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5914</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     should create the library `libsim.a' implementing the interface in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5915</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5916</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5917</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Build and test.  If desired, lobby the GDB steering group to have</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5918</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the new port included in the main distribution!</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5919</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5920</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5921</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     guide (*note Configuration Specific Information:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5922</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (gdb)Configuration Specific Information.).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5923</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5924</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5925</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5926</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5927</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5928</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>18 Versions and Branches</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5929</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5930</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5931</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>18.1 Versions</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5932</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5933</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5934</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB's version is determined by the file `gdb/version.in' and takes one</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5935</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>of the following forms:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5936</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5937</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>MAJOR.MINOR</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5938</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>MAJOR.MINOR.PATCHLEVEL</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5939</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     an official release (e.g., 6.2 or 6.2.1)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5940</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5941</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>MAJOR.MINOR.PATCHLEVEL.YYYYMMDD</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5942</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     a snapshot taken at YYYY-MM-DD-gmt (e.g., 6.1.50.20020302,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5943</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.1.90.20020304, or 6.1.0.20020308)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5944</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5945</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>MAJOR.MINOR.PATCHLEVEL.YYYYMMDD-cvs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5946</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     a CVS check out drawn on YYYY-MM-DD (e.g., 6.1.50.20020302-cvs,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5947</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.1.90.20020304-cvs, or 6.1.0.20020308-cvs)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5948</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5949</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>MAJOR.MINOR.PATCHLEVEL.YYYYMMDD (VENDOR)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5950</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     a vendor specific release of GDB, that while based on</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5951</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     MAJOR.MINOR.PATCHLEVEL.YYYYMMDD, may include additional changes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5952</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5953</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5954</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>most recent release branch, with a PATCHLEVEL of 50.  At the time each</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5955</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>new release branch is created, the mainline's MAJOR and MINOR version</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5956</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>numbers are updated.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5957</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5958</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   GDB's release branch is similar.  When the branch is cut, the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5959</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5960</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the branch, the PATCHLEVEL is incremented.  Once the first release</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5961</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(MAJOR.MINOR) has been made, the PATCHLEVEL is set to 0 and updates</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5962</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5963</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5964</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   For snapshots, and CVS check outs, it is also possible to identify</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5965</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5966</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5967</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>MAJOR.MINOR.50.YYYYMMDD</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5968</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     drawn from the HEAD of mainline CVS (e.g., 6.1.50.20020302)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5969</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5970</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5971</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>MAJOR.MINOR.91.YYYYMMDD ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5972</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     drawn from a release branch prior to the release (e.g.,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5973</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.1.90.20020304)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5974</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5975</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5976</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>MAJOR.MINOR.1.YYYYMMDD ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5977</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     drawn from a release branch after the release (e.g.,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5978</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.2.0.20020308)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5979</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5980</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If the previous GDB version is 6.1 and the current version is 6.2,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5981</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>then, substituting 6 for MAJOR and 1 or 2 for MINOR, here's an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5982</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>illustration of a typical sequence:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5983</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5984</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          <HEAD></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5985</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5986</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.1.50.20020302-cvs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5987</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5988</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             +--------------------------.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5989</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |                    <gdb_6_2-branch></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5990</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |                          |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5991</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.2.50.20020303-cvs        6.1.90 (draft #1)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5992</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |                          |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5993</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.2.50.20020304-cvs        6.1.90.20020304-cvs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5994</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |                          |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5995</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.2.50.20020305-cvs        6.1.91 (draft #2)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5996</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |                          |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5997</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.2.50.20020306-cvs        6.1.91.20020306-cvs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5998</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |                          |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>5999</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.2.50.20020307-cvs        6.2 (release)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6000</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |                          |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6001</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.2.50.20020308-cvs        6.2.0.20020308-cvs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6002</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |                          |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6003</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.2.50.20020309-cvs        6.2.1 (update)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6004</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |                          |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6005</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.2.50.20020310-cvs         <branch closed></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6006</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6007</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.2.50.20020311-cvs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6008</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6009</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             +--------------------------.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6010</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6011</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             |                          |</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6012</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     6.3.50.20020312-cvs        6.2.90 (draft #1)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6013</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6014</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6015</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>18.2 Release Branches</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6016</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6017</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6018</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB draws a release series (6.2, 6.2.1, ...) from a single release</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6019</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>branch, and identifies that branch using the CVS branch tags:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6020</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6021</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     gdb_MAJOR_MINOR-YYYYMMDD-branchpoint</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6022</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     gdb_MAJOR_MINOR-branch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6023</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     gdb_MAJOR_MINOR-YYYYMMDD-release</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6024</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6025</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6026</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>is made, both the branchpoint and release tags include the date that</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6027</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>they are cut (YYYYMMDD) in the tag.  The branch tag, denoting the head</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6028</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6029</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6030</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>18.3 Vendor Branches</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6031</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>====================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6032</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6033</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6034</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb/version.in' to include a vendor unique alphabetic identifier (an</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6035</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>official GDB release never uses alphabetic characters in its version</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6036</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6037</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6038</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>18.4 Experimental Branches</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6039</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6040</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6041</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>18.4.1 Guidelines</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6042</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6043</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6044</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6045</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>experimental development.  Branches make it possible for developers to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6046</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6047</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>developments.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6048</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6049</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The following are a set of guidelines for creating such branches:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6050</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6051</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6052</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The owner can set further policy for a branch, but may not change</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6053</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the ground rules.  In particular, they can set a policy for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6054</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     commits (be it adding more reviewers or deciding who can commit).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6055</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6056</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_all commits are posted_</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6057</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6058</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     patches mailing list <gdb-patches@sourceware.org>.  While</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6059</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     commentary on such changes are encouraged, people should remember</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6060</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     that the changes only apply to a branch.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6061</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6062</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6063</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This ensures that all changes belong to the Free Software</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6064</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Foundation, and avoids the possibility that the branch may become</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6065</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     contaminated.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6066</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6067</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6068</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     A focused branch has a single objective or goal, and does not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6069</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     contain unnecessary or irrelevant changes.  Cleanups, where</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6070</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     identified, being be pushed into the mainline as soon as possible.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6071</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6072</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6073</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This keeps the level of divergence under control.  It also keeps</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6074</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the pressure on developers to push cleanups and other stuff into</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6075</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the mainline.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6076</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6077</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_a branch shall contain the entire GDB module_</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6078</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The GDB module `gdb' should be specified when creating a branch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6079</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (branches of individual files should be avoided).  *Note Tags::.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6080</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6081</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6082</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6083</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the branch OWNER and branch NAME, e.g.,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6084</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `6.2.50.20030303_owner_name' or `6.2 (Owner Name)'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6085</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6086</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6087</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>18.4.2 Tags</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6088</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6089</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6090</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>To simplify the identification of GDB branches, the following branch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6091</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>tagging convention is strongly recommended:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6092</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6093</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`OWNER_NAME-YYYYMMDD-branchpoint'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6094</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`OWNER_NAME-YYYYMMDD-branch'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6095</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The branch point and corresponding branch tag.  YYYYMMDD is the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6096</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     date that the branch was created.  A branch is created using the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6097</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6098</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          cvs rtag OWNER_NAME-YYYYMMDD-branchpoint gdb</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6099</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          cvs rtag -b -r OWNER_NAME-YYYYMMDD-branchpoint \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6100</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>             OWNER_NAME-YYYYMMDD-branch gdb</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6101</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6102</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`OWNER_NAME-YYYYMMDD-mergepoint'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6103</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The tagged point, on the mainline, that was used when merging the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6104</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     branch on YYYYMMDD.  To merge in all changes since the branch was</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6105</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     cut, use a command sequence like:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6106</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          cvs rtag OWNER_NAME-YYYYMMDD-mergepoint gdb</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6107</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          cvs update \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6108</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6109</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6110</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Similar sequences can be used to just merge in changes since the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6111</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     last merge.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6112</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6113</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6114</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>For further information on CVS, see Concurrent Versions System</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6115</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6116</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6117</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6118</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6119</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6120</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>19 Start of New Year Procedure</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6121</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6122</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6123</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6124</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>performed:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6125</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6126</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Rotate the ChangeLog file</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6127</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6128</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     The current `ChangeLog' file should be renamed into</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6129</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `ChangeLog-YYYY' where YYYY is the year that has just passed.  A</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6130</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     new `ChangeLog' file should be created, and its contents should</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6131</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     contain a reference to the previous ChangeLog.  The following</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6132</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     should also be preserved at the end of the new ChangeLog, in order</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6133</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     to provide the appropriate settings when editing this file with</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6134</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Emacs:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6135</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          Local Variables:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6136</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          mode: change-log</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6137</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          left-margin: 8</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6138</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6139</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          version-control: never</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6140</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          coding: utf-8</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6141</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6142</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6143</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6144</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (`ChangeLog-YYYY') in `gdb/config/djgpp/fnchange.lst'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6145</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6146</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6147</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6148</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6149</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   file `top.c', function `print_gdb_version'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6150</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6151</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   file `gdbserver/server.c', function `gdbserver_version'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6152</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6153</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   file `gdbserver/gdbreplay.c', function `gdbreplay_version'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6154</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6155</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Run the `copyright.sh' script to add the new year in the copyright</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6156</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     notices of most source files.  This script requires Emacs 22 or</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6157</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     later to be installed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6158</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6159</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The new year also needs to be added manually in all other files</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6160</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6161</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   `*.s'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6162</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6163</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   `*.f'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6164</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6165</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   `*.f90'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6166</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6167</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   `*.igen'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6168</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6169</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   `*.ac'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6170</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6171</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   `*.texi'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6172</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6173</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   `*.texinfo'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6174</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6175</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   `*.tex'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6176</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6177</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6178</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6179</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        *   `*.1'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6180</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6181</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6182</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6183</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6184</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6185</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>20 Releasing GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6186</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6187</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6188</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>20.1 Branch Commit Policy</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6189</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6190</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6191</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6192</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>5.2 all used the below:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6193</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6194</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The `gdb/MAINTAINERS' file still holds.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6195</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6196</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Don't fix something on the branch unless/until it is also fixed in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6197</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the trunk.  If this isn't possible, mentioning it in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6198</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdb/PROBLEMS' file is better than committing a hack.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6199</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6200</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * When considering a patch for the branch, suggested criteria</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6201</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     include: Does it fix a build?  Does it fix the sequence `break</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6202</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6203</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6204</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The further a change is from the core of GDB, the less likely the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6205</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     change will worry anyone (e.g., target specific code).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6206</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6207</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Only post a proposal to change the core of GDB after you've sent</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6208</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     individual bribes to all the people listed in the `MAINTAINERS'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6209</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     file ;-)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6210</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6211</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6212</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functionality there is little chance that a broken change will be fatal.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6213</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>This means that changes such as adding a new architectures or (within</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6214</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6215</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6216</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>20.2 Obsoleting code</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6217</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>====================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6218</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6219</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Before anything else, poke the other developers (and around the source</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6220</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>code) to see if there is anything that can be removed from GDB (an old</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6221</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>target, an unused file).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6222</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6223</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Obsolete code is identified by adding an `OBSOLETE' prefix to every</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6224</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>line.  Doing this means that it is easy to identify something that has</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6225</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>been obsoleted when greping through the sources.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6226</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6227</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The process is done in stages -- this is mainly to ensure that the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6228</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>wider GDB community has a reasonable opportunity to respond.  Remember,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6229</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>everything on the Internet takes a week.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6230</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6231</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  1. Post the proposal on the GDB mailing list <gdb@sourceware.org></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6232</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6233</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     recommended.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6234</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6235</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6236</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6237</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6238</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     <gdb-announce@sourceware.org>.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6239</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6240</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6241</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6242</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  5. Go through and edit all relevant files and lines so that they are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6243</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6244</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6245</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6246</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     has been released.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6247</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6248</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  7. Remove the obsolete code.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6249</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6250</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_Maintainer note: While removing old code is regrettable it is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6251</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>hopefully better for GDB's long term development.  Firstly it helps the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6252</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6253</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>wrong.  Secondly since it removes any history associated with the file</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6254</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(effectively clearing the slate) the developer has a much freer hand</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6255</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6256</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6257</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>20.3 Before the Branch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6258</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>======================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6259</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6260</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6261</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>changes that become a pain to track once the branch is created.  For</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6262</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>instance, configuration problems that stop GDB from even building.  If</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6263</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6264</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6265</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Prompt for `gdb/NEWS'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6266</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6267</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6268</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>People always forget.  Send a post reminding them but also if you know</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6269</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>something interesting happened add it yourself.  The `schedule' script</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6270</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6271</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6272</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Review `gdb/README'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6273</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6274</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6275</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Grab one of the nightly snapshots and then walk through the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6276</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb/README' looking for anything that can be improved.  The `schedule'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6277</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6278</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6279</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6280</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6281</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6282</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>A number of files are taken from external repositories.  They include:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6283</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6284</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `texinfo/texinfo.tex'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6285</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6286</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `config.guess' et. al. (see the top-level `MAINTAINERS' file)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6287</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6288</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6289</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6290</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Check the ARI</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6291</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6292</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6293</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6294</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>number of errors and coding conventions.  The checks include things</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6295</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>like using `malloc' instead of `xmalloc' and file naming problems.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6296</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6297</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6298</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6299</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6300</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6301</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6302</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6303</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6304</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6305</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6306</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6307</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6308</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>20.4 Cut the Branch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6309</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6310</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6311</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Create the branch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6312</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6313</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6314</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  u=5.1</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6315</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  v=5.2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6316</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  V=`echo $v | sed 's/\./_/g'`</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6317</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  D=`date -u +%Y-%m-%d`</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6318</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  echo $u $V $D</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6319</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     5.1 5_2 2002-03-03</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6320</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  echo cvs -f -d :ext:sourceware.org:/cvs/src rtag \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6321</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     -D $D-gmt gdb_$V-$D-branchpoint insight</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6322</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     cvs -f -d :ext:sourceware.org:/cvs/src rtag</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6323</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     -D 2002-03-03-gmt gdb_5_2-2002-03-03-branchpoint insight</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6324</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  ^echo ^^</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6325</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6326</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  echo cvs -f -d :ext:sourceware.org:/cvs/src rtag \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6327</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     -b -r gdb_$V-$D-branchpoint gdb_$V-branch insight</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6328</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     cvs -f -d :ext:sourceware.org:/cvs/src rtag \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6329</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6330</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  ^echo ^^</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6331</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6332</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6333</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6334</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * By using `-D YYYY-MM-DD-gmt', the branch is forced to an exact</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6335</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6336</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6337</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6338</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     found.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6339</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6340</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * Insight, which includes GDB, is tagged at the same time.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6341</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6342</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `version.in' gets bumped to avoid version number conflicts.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6343</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6344</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6345</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6346</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Update `version.in'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6347</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6348</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6349</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  u=5.1</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6350</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  v=5.2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6351</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  V=`echo $v | sed 's/\./_/g'`</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6352</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  echo $u $v$V</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6353</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     5.1 5_2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6354</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  cd /tmp</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6355</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  echo cvs -f -d :ext:sourceware.org:/cvs/src co \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6356</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     -r gdb_$V-branch src/gdb/version.in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6357</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     cvs -f -d :ext:sourceware.org:/cvs/src co</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6358</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>      -r gdb_5_2-branch src/gdb/version.in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6359</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  ^echo ^^</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6360</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     U src/gdb/version.in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6361</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  cd src/gdb</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6362</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6363</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  cat version.in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6364</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     5.1.90-0000-00-00-cvs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6365</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6366</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6367</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `0000-00-00' is used as a date to pump prime the version.in update</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6368</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6369</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6370</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `.90' and the previous branch version are used as fairly arbitrary</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6371</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6372</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6373</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6374</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6375</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6376</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6377</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6378</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Tweak cron to track the new branch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6379</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6380</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6381</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6382</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>file needs to be updated so that:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6383</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6384</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * A daily timestamp is added to the file `version.in'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6385</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6386</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6387</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6388</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>See the file `gdbadmin/cron/README' for how to install the updated cron</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6389</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>table.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6390</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6391</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The file `gdbadmin/ss/README' should also be reviewed to reflect any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6392</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>changes.  That file is copied to both the branch/ and current/ snapshot</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6393</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6394</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6395</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Update the NEWS and README files</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6396</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6397</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6398</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The `NEWS' file needs to be updated so that on the branch it refers to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6399</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>_changes in the current release_ while on the trunk it also refers to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6400</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6401</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6402</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The `README' file needs to be updated so that it refers to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6403</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6404</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6405</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6406</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6407</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6408</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Send an announcement to the mailing lists:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6409</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6410</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6411</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6412</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * GDB Discussion mailing list <gdb@sourceware.org> and GDB Testers</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6413</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     mailing list <gdb-testers@sourceware.org></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6414</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6415</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   _Pragmatics: The branch creation is sent to the announce list to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6416</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6417</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>list are alerted._</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6418</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6419</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The announcement should include:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6420</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6421</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The branch tag.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6422</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6423</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * How to check out the branch using CVS.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6424</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6425</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The date/number of weeks until the release.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6426</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6427</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6428</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6429</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6430</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6431</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6432</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6433</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6434</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>20.6 Create a Release</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6435</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=====================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6436</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6437</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6438</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>down into a number of stages.  The first part addresses the technical</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6439</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6440</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>process of releasing that tar ball.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6441</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6442</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6443</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6444</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>20.6.1 Create a release candidate</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6445</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>---------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6446</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6447</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The objective at this stage is to create a set of tar balls that can be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6448</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>made available as a formal release (or as a less formal release</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6449</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6450</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6451</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Freeze the branch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6452</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6453</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6454</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Send out an e-mail notifying everyone that the branch is frozen to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6455</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6456</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6457</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Establish a few defaults.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6458</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>.........................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6459</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6460</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  b=gdb_5_2-branch</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6461</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  v=5.2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6462</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  t=/sourceware/snapshot-tmp/gdbadmin-tmp</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6463</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  echo $t/$b/$v</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6464</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     /sourceware/snapshot-tmp/gdbadmin-tmp/gdb_5_2-branch/5.2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6465</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  mkdir -p $t/$b/$v</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6466</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  cd $t/$b/$v</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6467</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  pwd</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6468</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6469</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  which autoconf</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6470</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6471</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6472</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6473</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Notes:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6474</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6475</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6476</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     version documented in the toplevel `README-maintainer-mode' file.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6477</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     It is very unlikely that the version of `autoconf' installed in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6478</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6479</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6480</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Check out the relevant modules:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6481</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>...............................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6482</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6483</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  for m in gdb insight</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6484</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6485</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ( mkdir -p $m && cd $m && cvs -q -f -d /cvs/src co -P -r $b $m )</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6486</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6487</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6488</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6489</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Note:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6490</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6491</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * The reading of `.cvsrc' is disabled (`-f') so that there isn't any</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6492</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     confusion between what is written here and what your local `cvs'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6493</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6494</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6495</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Update relevant files.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6496</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>......................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6497</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6498</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6499</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Major releases get their comments added as part of the mainline.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6500</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6501</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     were fixed.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6502</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6503</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Don't forget to include the `ChangeLog' entry.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6504</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6505</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  emacs gdb/src/gdb/NEWS</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6506</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6507</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          c-x 4 a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6508</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6509</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          c-x c-s c-x c-c</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6510</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  cp gdb/src/gdb/NEWS insight/src/gdb/NEWS</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6511</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6512</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6513</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6514</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     You'll need to update:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6515</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6516</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        * The version.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6517</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6518</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        * The update date.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6519</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6520</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        * Who did it.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6521</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6522</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  emacs gdb/src/gdb/README</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6523</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6524</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          c-x 4 a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6525</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6526</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          c-x c-s c-x c-c</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6527</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  cp gdb/src/gdb/README insight/src/gdb/README</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6528</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  cp gdb/src/gdb/ChangeLog insight/src/gdb/ChangeLog</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6529</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6530</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     _Maintainer note: Hopefully the `README' file was reviewed before</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6531</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the initial branch was cut so just a simple substitute is needed</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6532</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6533</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6534</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     _Maintainer note: Other projects generate `README' and `INSTALL'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6535</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     from the core documentation.  This might be worth pursuing._</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6536</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6537</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb/version.in'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6538</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  echo $v > gdb/src/gdb/version.in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6539</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  cat gdb/src/gdb/version.in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6540</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          5.2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6541</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  emacs gdb/src/gdb/version.in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6542</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6543</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          c-x 4 a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6544</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6545</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6546</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  cp gdb/src/gdb/version.in insight/src/gdb/version.in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6547</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  cp gdb/src/gdb/ChangeLog insight/src/gdb/ChangeLog</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6548</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6549</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6550</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6551</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>.................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6552</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6553</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>This is identical to the process used to create the daily snapshot.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6554</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6555</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6556</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     do</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6557</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ( cd $m/src && gmake -f src-release $m.tar )</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6558</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6559</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6560</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If the top level source directory does not have `src-release' (GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6561</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>version 5.3.1 or earlier), try these commands instead:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6562</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6563</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6564</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     do</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6565</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ( cd $m/src && gmake -f Makefile.in $m.tar )</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6566</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6567</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6568</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Check the source files</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6569</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>......................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6570</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6571</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>You're looking for files that have mysteriously disappeared.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6572</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`distclean' has the habit of deleting files it shouldn't.  Watch out</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6573</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>for the `version.in' update `cronjob'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6574</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6575</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  ( cd gdb/src && cvs -f -q -n update )</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6576</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     M djunpack.bat</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6577</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ? gdb-5.1.91.tar</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6578</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ? proto-toplev</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6579</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ... lots of generated files ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6580</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     M gdb/ChangeLog</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6581</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     M gdb/NEWS</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6582</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6583</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     M gdb/version.in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6584</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ... lots of generated files ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6585</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6586</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6587</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6588</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>generated (and yes `gdb.info-1' was also generated only something</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6589</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>strange with CVS means that they didn't get suppressed).  Fixing it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6590</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6591</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6592</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Create compressed versions of the release</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6593</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>.........................................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6594</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6595</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  cp */src/*.tar .</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6596</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  cp */src/*.bz2 .</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6597</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  ls -F</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6598</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     gdb/ gdb-5.2.tar insight/ insight-5.2.tar</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6599</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  for m in gdb insight</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6600</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     do</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6601</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6602</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     gzip -v -9 -c $m-$v.tar > $m-$v.tar.gz</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6603</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6604</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6605</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6606</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Note:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6607</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6608</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6609</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     in that mode, `gzip' does not know the name of the file and, hence,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6610</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     can not include it in the compressed file.  This is also why the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6611</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6612</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6613</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6614</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6615</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6616</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Pick a popular machine (Solaris/PPC?) and try the build on that.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6617</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6618</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  bunzip2 < gdb-5.2.tar.bz2 | tar xpf -</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6619</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  cd gdb-5.2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6620</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  ./configure</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6621</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  make</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6622</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6623</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  ./gdb/gdb ./gdb/gdb</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6624</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     GNU gdb 5.2</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6625</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6626</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6627</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Breakpoint 1 at 0x80732bc: file main.c, line 734.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6628</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (gdb)  run</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6629</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Starting program: /tmp/gdb-5.2/gdb/gdb</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6630</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6631</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Breakpoint 1, main (argc=1, argv=0xbffff8b4) at main.c:734</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6632</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6633</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     (gdb)  print args</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6634</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $1 = {argc = 136426532, argv = 0x821b7f0}</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6635</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6636</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6637</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6638</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>-----------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6639</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6640</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>If this is a release candidate then the only remaining steps are:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6641</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6642</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6643</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6644</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  2. Tweak `version.in' (and `ChangeLog' to read L.M.N-0000-00-00-cvs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6645</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6646</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6647</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  3. Make the release candidate available in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6648</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6649</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6650</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  4. Notify the relevant mailing lists ( <gdb@sourceware.org> and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6651</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6652</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6653</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6654</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------------------------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6655</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6656</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6657</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6658</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6659</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6660</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6661</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6662</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6663</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  cp *.bz2 *.gz ~ftp/pub/gdb/old-releases/</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6664</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6665</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6666</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Clean up the releases directory so that only the most recent releases</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6667</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6668</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6669</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6670</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  rm ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6671</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6672</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Update the file `README' and `.message' in the releases directory:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6673</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6674</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6675</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     ...</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6676</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  rm -f .message</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6677</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6678</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6679</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Update the web pages.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6680</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>.....................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6681</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6682</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`htdocs/download/ANNOUNCEMENT'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6683</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This file, which is posted as the official announcement, includes:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6684</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6685</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6686</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6687</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          earlier M.N release.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6688</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6689</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        * Errata.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6690</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6691</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`htdocs/index.html'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6692</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6693</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`htdocs/download/index.html'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6694</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     These files include:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6695</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        * Announcement of the most recent release.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6696</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6697</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>        * News entry (remember to update both the top level and the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6698</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          news directory).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6699</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     These pages also need to be regenerate using `index.sh'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6700</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6701</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`download/onlinedocs/'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6702</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6703</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     online docs from the `.tar.bz2'.  The best way is to look in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6704</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     output from one of the nightly `cron' jobs and then just edit</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6705</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     accordingly.  Something like:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6706</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6707</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  ~/ss/update-web-docs \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6708</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6709</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           $PWD/www \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6710</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           /www/sourceware/htdocs/gdb/download/onlinedocs \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6711</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6712</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6713</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`download/ari/'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6714</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Just like the online documentation.  Something like:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6715</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6716</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          $  /bin/sh ~/ss/update-web-ari \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6717</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6718</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6719</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           /www/sourceware/htdocs/gdb/download/ari \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6720</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>           gdb</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6721</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6722</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6723</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6724</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>.........................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6725</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6726</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6727</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6728</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Install the GDB tar ball on GNU</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6729</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6730</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6731</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>At the time of writing, the GNU machine was `gnudist.gnu.org' in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6732</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6733</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6734</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6735</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>.......................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6736</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6737</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Post the `ANNOUNCEMENT' file you created above to:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6738</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6739</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6740</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6741</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6742</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     day or so to let things get out)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6743</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6744</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6745</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6746</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6747</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>--------------</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6748</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6749</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6750</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6751</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6752</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>..........................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6753</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6754</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>In particular you'll need to commit any changes to:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6755</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6756</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `gdb/ChangeLog'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6757</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6758</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `gdb/version.in'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6759</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6760</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `gdb/NEWS'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6761</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6762</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6763</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6764</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6765</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>...............</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6766</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6767</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Something like:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6768</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6769</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  d=`date -u +%Y-%m-%d`</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6770</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6771</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     2002-01-24</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6772</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6773</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     $  ( cd insight/src && cvs -f -q tag gdb_5_2-$d-release )</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6774</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6775</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6776</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6777</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Mention the release on the trunk</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6778</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6779</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6780</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Just put something in the `ChangeLog' so that the trunk also indicates</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6781</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6782</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6783</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Restart `gdb/version.in'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6784</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>........................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6785</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6786</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>If `gdb/version.in' does not contain an ISO date such as `2002-01-24'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6787</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6788</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>release changes it can be set to `5.2.0_0000-00-00-cvs' which will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6789</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6790</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>process).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6791</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6792</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6793</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6794</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Merge into trunk</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6795</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6796</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6797</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The files committed to the branch may also need changes merged into the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6798</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6799</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6800</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Revise the release schedule</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6801</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>...........................</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6802</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6803</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Post a revised release schedule to GDB Discussion List</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6804</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6805</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>generated by running:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6806</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6807</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6808</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6809</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6810</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>of the most recent release.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6811</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6812</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6813</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6814</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6815</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6816</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6817</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6818</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6819</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6820</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6821</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6822</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>21 Testsuite</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6823</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>************</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6824</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6825</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The testsuite is an important component of the GDB package.  While it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6826</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6827</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>rarely sufficient; users typically use only a small subset of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6828</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>available commands, and it has proven all too common for a change to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6829</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>cause a significant regression that went unnoticed for some time.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6830</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6831</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The GDB testsuite uses the DejaGNU testing framework.  The tests</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6832</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>themselves are calls to various `Tcl' procs; the framework runs all the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6833</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6834</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6835</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>21.1 Using the Testsuite</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6836</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6837</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6838</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>To run the testsuite, simply go to the GDB object directory (or to the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6839</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>testsuite's objdir) and type `make check'.  This just sets up some</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6840</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6841</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the testsuite is running, you'll get mentions of which test file is in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6842</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6843</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>testsuite is finished, you'll get a summary that looks like this:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6844</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6845</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>                     === gdb Summary ===</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6846</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6847</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     # of expected passes            6016</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6848</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     # of unexpected failures        58</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6849</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6850</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     # of expected failures          183</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6851</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     # of unresolved testcases       3</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6852</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     # of untested testcases         5</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6853</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6854</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   To run a specific test script, type:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6855</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     make check RUNTESTFLAGS='TESTS'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6856</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   where TESTS is a list of test script file names, separated by spaces.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6857</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6858</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If you use GNU make, you can use its `-j' option to run the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6859</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>testsuite in parallel.  This can greatly reduce the amount of time it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6860</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>takes for the testsuite to run.  In this case, if you set</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6861</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`RUNTESTFLAGS' then, by default, the tests will be run serially even</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6862</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>under `-j'.  You can override this and force a parallel run by setting</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6863</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6864</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the parallel `make check' assumes that you want to run the entire</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6865</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>testsuite, so it is not compatible with some dejagnu options, like</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6866</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`--directory'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6867</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6868</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The ideal test run consists of expected passes only; however, reality</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6869</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>conspires to keep us from this ideal.  Unexpected failures indicate</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6870</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>real problems, whether in GDB or in the testsuite.  Expected failures</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6871</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are still failures, but ones which have been decided are too hard to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6872</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>deal with at the time; for instance, a test case might work everywhere</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6873</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>except on AIX, and there is no prospect of the AIX case being fixed in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6874</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the near future.  Expected failures should not be added lightly, since</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6875</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6876</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>expected fails that are passing for some reason, while unresolved and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6877</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>untested cases often indicate some minor catastrophe, such as the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6878</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>compiler being unable to deal with a test program.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6879</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6880</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   When making any significant change to GDB, you should run the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6881</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>testsuite before and after the change, to confirm that there are no</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6882</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>regressions.  Note that truly complete testing would require that you</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6883</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>run the testsuite with all supported configurations and a variety of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6884</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>compilers; however this is more than really necessary.  In many cases</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6885</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6886</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>options are to test one big-endian (Sparc) and one little-endian (x86)</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6887</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>host, a cross config with a builtin simulator (powerpc-eabi, mips-elf),</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6888</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>or a 64-bit host (Alpha).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6889</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6890</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If you add new functionality to GDB, please consider adding tests</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6891</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>for it as well; this way future GDB hackers can detect and fix their</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6892</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>changes that break the functionality you added.  Similarly, if you fix</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6893</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6894</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>test case for it.  Some cases are extremely difficult to test, such as</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6895</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>code that handles host OS failures or bugs in particular versions of</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6896</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>compilers, and it's OK not to try to write tests for all of those.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6897</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6898</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6899</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>some GDB test scripts do not work if the build machine and the host</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6900</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6901</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>give a result of "UNRESOLVED", like this:</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6902</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6903</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6904</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6905</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6906</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6907</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6908</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Several variables exist to modify the behavior of the testsuite.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6909</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6910</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `TRANSCRIPT'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6911</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6912</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6913</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     which the testsuite sends to GDB.  For example, if GDB crashes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6914</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     during testing, a transcript can be used to more easily</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6915</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     reconstruct the failure when running GDB under GDB.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6916</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6917</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     You can instruct the GDB testsuite to write transcripts by setting</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6918</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the DejaGNU variable `TRANSCRIPT' (to any value) before invoking</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6919</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `runtest' or `make check'.  The transcripts will be written into</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6920</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     DejaGNU's output directory.  One transcript will be made for each</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6921</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6922</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     an integer.  The first line of the transcript file will show how</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6923</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6924</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     to GDB.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6925</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6926</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6927</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6928</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6929</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     tests of completion can yield partial command lines.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6930</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6931</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `GDB'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6932</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6933</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Sometimes one wishes to test a different GDB than the one in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6934</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6935</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `/usr/bin/gdb'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6936</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6937</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          make check RUNTESTFLAGS=GDB=/usr/bin/gdb</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6938</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6939</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6940</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6941</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6942</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     different gdbserver.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6943</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6944</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          make check RUNTESTFLAGS="GDB=/usr/bin/gdb GDBSERVER=/usr/bin/gdbserver"</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6945</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6946</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `INTERNAL_GDBFLAGS'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6947</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6948</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     When running the testsuite normally one doesn't want whatever is in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6949</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6950</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     harness passes `-nx' to GDB.  One also doesn't want any windowed</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6951</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6952</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `INTERNAL_GDBFLAGS'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6953</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6954</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          set INTERNAL_GDBFLAGS "-nw -nx"</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6955</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6956</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This is all well and good, except when testing an installed GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6957</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     that has been configured with `--with-system-gdbinit'.  Here one</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6958</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6959</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `.gdbinit' file loaded.  This can be achieved by pointing `$HOME'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6960</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     at a directory without a `.gdbinit' and by overriding</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6961</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `INTERNAL_GDBFLAGS' and removing `-nx'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6962</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6963</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>          cd testsuite</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6964</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6965</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6966</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            GDBSERVER=/usr/bin/gdbserver \</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6967</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>            INTERNAL_GDBFLAGS=-nw</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6968</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6969</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6970</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   There are two ways to run the testsuite and pass additional</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6971</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6972</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the makefile variable `RUNTESTFLAGS'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6973</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6974</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6975</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6976</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The second is to cd to the `testsuite' directory and invoke the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6977</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>DejaGnu `runtest' command directly.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6978</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6979</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     cd testsuite</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6980</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     make site.exp</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6981</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6982</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6983</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>21.3 Testsuite Configuration</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6984</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>============================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6985</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6986</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>It is possible to adjust the behavior of the testsuite by defining the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6987</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6988</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>board file.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6989</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6990</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   * `gdb_test_timeout'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6991</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6992</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Defining this variable changes the default timeout duration used</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6993</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     during communication with GDB.  More specifically, the global</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6994</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6995</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     reset to `gdb_test_timeout' at the beginning of each testcase,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6996</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     making sure that any local change to `timeout' in a testcase does</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6997</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     not affect subsequent testcases.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6998</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>6999</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7000</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     than normal due to the testing environment, triggering unexpected</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7001</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `TIMEOUT' test failures.  Examples include when testing on a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7002</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     remote machine, or against a system where communications are slow.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7003</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7004</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     If not specifically defined, this variable gets automatically</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7005</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7006</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7007</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     the file `gdb/testsuite/config/unix.exp' that is part of the GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7008</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     test suite(1).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7009</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7010</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7011</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>21.4 Testsuite Organization</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7012</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>===========================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7013</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7014</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>The testsuite is entirely contained in `gdb/testsuite'.  While the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7015</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>testsuite includes some makefiles and configury, these are very minimal,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7016</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>and used for little besides cleaning up, since the tests themselves</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7017</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>handle the compilation of the programs that GDB will run.  The file</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7018</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7019</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB tests, while the directory `testsuite/config' contains</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7020</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>configuration-specific files, typically used for special-purpose</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7021</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>definitions of procs like `gdb_load' and `gdb_start'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7022</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7023</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The tests themselves are to be found in `testsuite/gdb.*' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7024</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7025</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>with `.exp'.  DejaGNU collects the test files by wildcarding in the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7026</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>test directories, so both subdirectories and individual files get</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7027</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>chosen and run in alphabetical order.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7028</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7029</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The following table lists the main types of subdirectories and what</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7030</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7031</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>located, and since each test file sets up its own compilation and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7032</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>execution environment, this organization is simply for convenience and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7033</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>intelligibility.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7034</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7035</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb.base'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7036</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     This is the base testsuite.  The tests in it should apply to all</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7037</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7038</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     here).  The test programs should be in the subset of C that is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7039</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     valid K&R, ANSI/ISO, and C++ (`#ifdef's are allowed if necessary,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7040</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     for instance for prototypes).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7041</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7042</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb.LANG'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7043</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Language-specific tests for any language LANG besides C.  Examples</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7044</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     are `gdb.cp' and `gdb.java'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7045</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7046</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7047</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Non-portable tests.  The tests are specific to a specific</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7048</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     configuration (host or target), such as HP-UX or eCos.  Example is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7049</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     `gdb.hp', for HP-UX.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7050</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7051</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb.COMPILER'</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7052</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Tests specific to a particular compiler.  As of this writing (June</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7053</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7054</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     that couldn't just as sensibly be made platform-specific, but one</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7055</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     could imagine a `gdb.gcc', for tests of GDB's handling of GCC</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7056</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     extensions.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7057</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7058</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7059</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     Tests that exercise a specific GDB subsystem in more depth.  For</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7060</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>     instance, `gdb.disasm' exercises various disassemblers, while</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7061</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7062</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7063</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>21.5 Writing Tests</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7064</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7065</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7066</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>In many areas, the GDB tests are already quite comprehensive; you</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7067</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>should be able to copy existing tests to handle new cases.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7068</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7069</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   You should try to use `gdb_test' whenever possible, since it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7070</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7071</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>However, it doesn't cost anything to add new test procedures; for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7072</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>instance, `gdb.base/exprs.exp' defines a `test_expr' that calls</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7073</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb_test' multiple times.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7074</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7075</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7076</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Even if GDB has several valid responses to a command, you can use</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7077</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`gdb_test_multiple'.  Like `gdb_test', `gdb_test_multiple' recognizes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7078</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>internal errors and unexpected prompts.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7079</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7080</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Do not write tests which expect a literal tab character from GDB.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7081</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>On some operating systems (e.g. OpenBSD) the TTY layer expands tabs to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7082</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>spaces, so by the time GDB's output reaches expect the tab is gone.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7083</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7084</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The source language programs do _not_ need to be in a consistent</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7085</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>style.  Since GDB is used to debug programs written in many different</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7086</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7087</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>instance, some GDB bugs involving the display of source lines would</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7088</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7089</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>uniformly.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7090</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7091</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7092</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7093</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   (1) If you are using a board file, it could override the test-suite</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7094</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7095</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7096</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7097</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7098</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7099</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>22 Hints</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7100</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7101</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7102</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7103</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>appear anywhere else in the directory.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7104</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7105</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7106</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7107</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>* Getting Started::             Getting started working on GDB</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7108</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7109</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7110</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7111</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7112</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7113</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>22.1 Getting Started</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7114</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>====================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7115</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7116</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB is a large and complicated program, and if you first starting to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7117</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>work on it, it can be hard to know where to start.  Fortunately, if you</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7118</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7119</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7120</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   This manual, the GDB Internals manual, has information which applies</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7121</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>generally to many parts of GDB.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7122</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7123</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Information about particular functions or data structures are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7124</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>located in comments with those functions or data structures.  If you</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7125</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>run across a function or a global variable which does not have a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7126</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7127</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>bug in GDB; feel free to submit a bug report, with a suggested comment</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7128</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>if you can figure out what the comment should say.  If you find a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7129</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>comment which is actually wrong, be especially sure to report that.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7130</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7131</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Comments explaining the function of macros defined in host, target,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7132</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>or native dependent files can be in several places.  Sometimes they are</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7133</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7134</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>macro is used.  Sometimes there is a header file which supplies a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7135</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>default definition of the macro, and the comment is there.  This manual</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7136</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>also documents all the available macros.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7137</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7138</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7139</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>internal symbol tables are stored (see `symtab.h', `gdbtypes.h'), you</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7140</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>will find it much easier to understand the code which uses and creates</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7141</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>those symbol tables.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7142</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7143</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   You may wish to process the information you are getting somehow, to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7144</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>enhance your understanding of it.  Summarize it, translate it to another</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7145</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>language, add some (perhaps trivial or non-useful) feature to GDB, use</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7146</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7147</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>and verify your prediction, etc.  If you are reading code and your eyes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7148</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are starting to glaze over, this is a sign you need to use a more active</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7149</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>approach.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7150</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7151</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Once you have a part of GDB to start with, you can find more</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7152</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>specifically the part you are looking for by stepping through each</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7153</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>function with the `next' command.  Do not use `step' or you will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7154</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>quickly get distracted; when the function you are stepping through</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7155</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>calls another function try only to get a big-picture understanding</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7156</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(perhaps using the comment at the beginning of the function being</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7157</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>called) of what it does.  This way you can identify which of the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7158</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>functions being called by the function you are stepping through is the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7159</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7160</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>structures generated at each stage, with reference to the comments in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7161</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the header files explaining what the data structures are supposed to</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7162</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>look like.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7163</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7164</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Of course, this same technique can be used if you are just reading</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7165</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7166</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>principle applies--when the code you are looking at calls something</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7167</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>else, just try to understand generally what the code being called does,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7168</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>rather than worrying about all its details.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7169</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7170</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   A good place to start when tracking down some particular area is with</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7171</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>a command which invokes that feature.  Suppose you want to know how</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7172</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>single-stepping works.  As a GDB user, you know that the `step' command</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7173</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>invokes single-stepping.  The command is invoked via command tables</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7174</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>(see `command.h'); by convention the function which actually performs</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7175</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>the command is formed by taking the name of the command and adding</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7176</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`_command', or in the case of an `info' subcommand, `_info'.  For</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7177</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7178</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`info display' command invokes `display_info'.  When this convention is</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7179</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>not followed, you might have to use `grep' or `M-x tags-search' in</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7180</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>emacs, or run GDB on itself and set a breakpoint in `execute_command'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7181</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7182</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If all of the above fail, it may be appropriate to ask for</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7183</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7184</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>was wondering if anyone could give me some tips about understanding</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7185</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB"--if we had some magic secret we would put it in this manual.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7186</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7187</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7188</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7189</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7190</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7191</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>22.2 Debugging GDB with itself</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7192</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>==============================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7193</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7194</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>If GDB is limping on your machine, this is the preferred way to get it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7195</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>fully functional.  Be warned that in some ancient Unix systems, like</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7196</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7197</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>debugged in another.  Rather than typing the command `./gdb ./gdb',</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7198</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>which works on Suns and such, you can copy `gdb' to `gdb2' and then</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7199</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>type `./gdb ./gdb2'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7200</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7201</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   When you run GDB in the GDB source directory, it will read a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7202</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7203</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>easier.  The `info' command, when executed without a subcommand in a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7204</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB being debugged by gdb, will pop you back up to the top level gdb.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7205</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>See `.gdbinit' for details.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7206</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7207</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7208</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>you configure your distribution; this will put the machine dependent</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7209</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>routines for your local machine where they will be accessed first by</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7210</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7211</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7212</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Also, make sure that you've either compiled GDB with your local cc,</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7213</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7214</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7215</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>22.3 Submitting Patches</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7216</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=======================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7217</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7218</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7219</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>GDB users.  In general we like to get well designed enhancements.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7220</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>Thanks also for checking in advance about the best way to transfer the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7221</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7222</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7223</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The GDB maintainers will only install "cleanly designed" patches.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7224</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>This manual summarizes what we believe to be clean design for GDB.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7225</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7226</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If the maintainers don't have time to put the patch in when it</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7227</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>arrives, or if there is any question about a patch, it goes into a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7228</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>large queue with everyone else's patches and bug reports.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7229</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7230</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The legal issue is that to incorporate substantial changes requires a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7231</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>copyright assignment from you and/or your employer, granting ownership</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7232</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>of the changes to the Free Software Foundation.  You can get the</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7233</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>standard documents for doing this by sending mail to `gnu@gnu.org' and</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7234</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>asking for it.  We recommend that people write in "All programs owned</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7235</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>by the Free Software Foundation" as "NAME OF PROGRAM", so that changes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7236</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>in many programs (not just GDB, but GAS, Emacs, GCC, etc) can be</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7237</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7238</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>bureaucracy and filed with the FSF.  We can't start merging changes</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7239</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>until this paperwork is received by the FSF (their rules, which we</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7240</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>follow since we maintain it for them).</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7241</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7242</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Technically, the easiest way to receive changes is to receive each</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7243</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>feature as a small context diff or unidiff, suitable for `patch'.  Each</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7244</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>message sent to me should include the changes to C code and header</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7245</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>files for a single feature, plus `ChangeLog' entries for each directory</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7246</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7247</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>manuals (`gdb/doc/gdb.texinfo' or `gdb/doc/gdbint.texinfo').  If there</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7248</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>are a lot of changes for a single feature, they can be split down into</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7249</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>multiple messages.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7250</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7251</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7252</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>sources with a single patch command, do some testing, and check it in.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7253</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>If you leave out the `ChangeLog', we have to write one.  If you leave</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7254</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>out the doc, we have to puzzle out what needs documenting.  Etc., etc.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7255</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7256</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   The reason to send each change in a separate message is that we will</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7257</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>not install some of the changes.  They'll be returned to you with</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7258</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>questions or comments.  If we're doing our job correctly, the message</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7259</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>back to you will say what you have to fix in order to make the change</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7260</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>acceptable.  The reason to have separate messages for separate features</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7261</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>is so that the acceptable changes can be installed while one or more</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7262</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7263</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>message, we tend to not put in the effort to sort out the acceptable</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7264</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>changes from the unacceptable, so none of the features get installed</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7265</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>until all are acceptable.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7266</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7267</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   If this sounds painful or authoritarian, well, it is.  But we get a</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7268</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>lot of bug reports and a lot of patches, and many of them don't get</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7269</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>installed because we don't have the time to finish the job that the bug</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7270</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>reporter or the contributor could have done.  Patches that arrive</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7271</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7272</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>they arrive.  The others go into a queue and get installed as time</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7273</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>permits, which, since the maintainers have many demands to meet, may not</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7274</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7275</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7276</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>   Please send patches directly to the GDB maintainers</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7277</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7278</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7279</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>22.4 Build Script</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7280</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>=================</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7281</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7282</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7283</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>`--enable-targets=all' set.  This builds GDB with all supported targets</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7284</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>activated.  This helps testing GDB when doing changes that affect more</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7285</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>than one architecture and is much faster than using `gdb_mbuild.sh'.</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7286</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>7287</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code> </code></pre></td>
      </tr>
   </tbody>
</table>


<script type='text/javascript'>
/* <![CDATA[ */
var rev = new Array();
var a = document.getElementsByTagName('a');
for (var i = 0; i < a.length; i++) {
  if (a[i].className == 'blame-revision') {
    var id = a[i].id;
    addEvent(a[i], 'mouseover', function() { mouseover(this) } );
    addEvent(a[i], 'mouseout', function() { mouseout(this) } );
  }
}

function mouseover(a) {
  // Find the revision by using the link
  var m = /rev=(\d+)/.exec(a.href);
  var r = m[1];

  div = document.createElement('div');
  div.className = 'blame-popup';
  div.innerHTML = rev[r];
  a.parentNode.appendChild(div);
}

function mouseout(a) {
  var div = a.parentNode.parentNode.getElementsByTagName('div');
  for (var i = 0; i < div.length; i++) {
    if (div[i].className = 'blame-popup') {
      div[i].parentNode.removeChild(div[i]);
    }
  }
}

function addEvent(obj, type, func) {
  if (obj.addEventListener) {
    obj.addEventListener(type, func, false);
    return true;
  } else if (obj.attachEvent) {
    return obj.attachEvent('on' + type, func);
  } else {
    return false;
  }
}
rev[342] = '<div class="info"><span class="date">2010-09-06 15:37:54 GMT<\/span><\/div><div class="msg">Various files regenerated as part of RC1 creation.<\/div>';
rev[330] = '<div class="info"><span class="date">2010-09-03 22:44:27 GMT<\/span><\/div><div class="msg">Baseline port of GDB 7.2 for OpenRISC 1000<\/div>';
/* ]]> */
</script>

</div>
</div>
<div id="websvnfooter">
    <p style="padding:0; margin:0"><small>powered by: <a href="http://www.websvn.info">WebSVN 2.1.0</a></small></p>
</div>
        </div>

                
        <div style="clear: both; margin-left: 200px;">
            <ins
                class="adsbygoogle"
                style="display:inline-block;width:728px;height:90px"
                data-ad-client="ca-pub-8561717607970465"
                data-ad-slot="4128044249"></ins>
            <script type="text/javascript">(adsbygoogle = window.adsbygoogle || []).push({});</script>
        </div>
        
            </div>
    <div class="bot">
        © copyright 1999-2024
OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.
    </div>
</div>

<!-- Old browser warning -->
<script type="text/javascript">
  if (!('borderImage' in document.createElement('div').style)) {
    var div = document.getElementById('old-browser-warning')
    div.innerHTML = '<b>Your browser is out-of-date!</b>        Update your browser to view this website correctly.'
    div.setAttribute('style', 'background-color: red; border-bottom: 2px solid black; margin: 0 -12px 12px -12px; padding: 12px; text-align: center;')
  }
</script>
<!-- /Old browser warning -->
<!-- Google search -->
<script type="text/javascript" src="//www.google.com/jsapi"></script>
<script type="text/javascript">google.load("elements", "1", {packages: "transliteration"});</script>
<script type="text/javascript" src="//www.google.com/coop/cse/t13n?form=cse-search-box&t13n_langs=en"></script>
<script type="text/javascript" src="//www.google.com/coop/cse/brand?form=cse-search-box&lang=en"></script>
<!-- /Google search -->

</body>
</html>