| 1 | \input texinfo @c -*- texinfo -*- |
| 2 | @setfilename gdbint.info |
| 3 | @include gdb-cfg.texi |
| 4 | @dircategory Programming & development tools. |
| 5 | @direntry |
| 6 | * Gdb-Internals: (gdbint). The GNU debugger's internals. |
| 7 | @end direntry |
| 8 | |
| 9 | @ifinfo |
| 10 | This file documents the internals of the GNU debugger @value{GDBN}. |
| 11 | Copyright 1990,1991,1992,1993,1994,1996,1998,1999,2000,2001,2002,2003 |
| 12 | Free Software Foundation, Inc. |
| 13 | Contributed by Cygnus Solutions. Written by John Gilmore. |
| 14 | Second Edition by Stan Shebs. |
| 15 | |
| 16 | Permission is granted to copy, distribute and/or modify this document |
| 17 | under the terms of the GNU Free Documentation License, Version 1.1 or |
| 18 | any later version published by the Free Software Foundation; with no |
| 19 | Invariant Sections, with the Front-Cover Texts being ``A GNU Manual,'' |
| 20 | and with the Back-Cover Texts as in (a) below. |
| 21 | |
| 22 | (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify |
| 23 | this GNU Manual, like GNU software. Copies published by the Free |
| 24 | Software Foundation raise funds for GNU development.'' |
| 25 | @end ifinfo |
| 26 | |
| 27 | @setchapternewpage off |
| 28 | @settitle @value{GDBN} Internals |
| 29 | |
| 30 | @syncodeindex fn cp |
| 31 | @syncodeindex vr cp |
| 32 | |
| 33 | @titlepage |
| 34 | @title @value{GDBN} Internals |
| 35 | @subtitle{A guide to the internals of the GNU debugger} |
| 36 | @author John Gilmore |
| 37 | @author Cygnus Solutions |
| 38 | @author Second Edition: |
| 39 | @author Stan Shebs |
| 40 | @author Cygnus Solutions |
| 41 | @page |
| 42 | @tex |
| 43 | \def\$#1${{#1}} % Kluge: collect RCS revision info without $...$ |
| 44 | \xdef\manvers{\$Revision$} % For use in headers, footers too |
| 45 | {\parskip=0pt |
| 46 | \hfill Cygnus Solutions\par |
| 47 | \hfill \manvers\par |
| 48 | \hfill \TeX{}info \texinfoversion\par |
| 49 | } |
| 50 | @end tex |
| 51 | |
| 52 | @vskip 0pt plus 1filll |
| 53 | Copyright @copyright{} 1990,1991,1992,1993,1994,1996,1998,1999,2000,2001, |
| 54 | 2002, 2003 Free Software Foundation, Inc. |
| 55 | |
| 56 | Permission is granted to copy, distribute and/or modify this document |
| 57 | under the terms of the GNU Free Documentation License, Version 1.1 or |
| 58 | any later version published by the Free Software Foundation; with no |
| 59 | Invariant Sections, with the Front-Cover Texts being ``A GNU Manual,'' |
| 60 | and with the Back-Cover Texts as in (a) below. |
| 61 | |
| 62 | (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify |
| 63 | this GNU Manual, like GNU software. Copies published by the Free |
| 64 | Software Foundation raise funds for GNU development.'' |
| 65 | @end titlepage |
| 66 | |
| 67 | @contents |
| 68 | |
| 69 | @node Top |
| 70 | @c Perhaps this should be the title of the document (but only for info, |
| 71 | @c not for TeX). Existing GNU manuals seem inconsistent on this point. |
| 72 | @top Scope of this Document |
| 73 | |
| 74 | This document documents the internals of the GNU debugger, @value{GDBN}. It |
| 75 | includes description of @value{GDBN}'s key algorithms and operations, as well |
| 76 | as the mechanisms that adapt @value{GDBN} to specific hosts and targets. |
| 77 | |
| 78 | @menu |
| 79 | * Requirements:: |
| 80 | * Overall Structure:: |
| 81 | * Algorithms:: |
| 82 | * User Interface:: |
| 83 | * libgdb:: |
| 84 | * Symbol Handling:: |
| 85 | * Language Support:: |
| 86 | * Host Definition:: |
| 87 | * Target Architecture Definition:: |
| 88 | * Target Vector Definition:: |
| 89 | * Native Debugging:: |
| 90 | * Support Libraries:: |
| 91 | * Coding:: |
| 92 | * Porting GDB:: |
| 93 | * Releasing GDB:: |
| 94 | * Testsuite:: |
| 95 | * Hints:: |
| 96 | |
| 97 | * GDB Observers:: @value{GDBN} Currently available observers |
| 98 | * GNU Free Documentation License:: The license for this documentation |
| 99 | * Index:: |
| 100 | @end menu |
| 101 | |
| 102 | @node Requirements |
| 103 | |
| 104 | @chapter Requirements |
| 105 | @cindex requirements for @value{GDBN} |
| 106 | |
| 107 | Before diving into the internals, you should understand the formal |
| 108 | requirements and other expectations for @value{GDBN}. Although some |
| 109 | of these may seem obvious, there have been proposals for @value{GDBN} |
| 110 | that have run counter to these requirements. |
| 111 | |
| 112 | First of all, @value{GDBN} is a debugger. It's not designed to be a |
| 113 | front panel for embedded systems. It's not a text editor. It's not a |
| 114 | shell. It's not a programming environment. |
| 115 | |
| 116 | @value{GDBN} is an interactive tool. Although a batch mode is |
| 117 | available, @value{GDBN}'s primary role is to interact with a human |
| 118 | programmer. |
| 119 | |
| 120 | @value{GDBN} should be responsive to the user. A programmer hot on |
| 121 | the trail of a nasty bug, and operating under a looming deadline, is |
| 122 | going to be very impatient of everything, including the response time |
| 123 | to debugger commands. |
| 124 | |
| 125 | @value{GDBN} should be relatively permissive, such as for expressions. |
| 126 | While the compiler should be picky (or have the option to be made |
| 127 | picky), since source code lives for a long time usually, the |
| 128 | programmer doing debugging shouldn't be spending time figuring out to |
| 129 | mollify the debugger. |
| 130 | |
| 131 | @value{GDBN} will be called upon to deal with really large programs. |
| 132 | Executable sizes of 50 to 100 megabytes occur regularly, and we've |
| 133 | heard reports of programs approaching 1 gigabyte in size. |
| 134 | |
| 135 | @value{GDBN} should be able to run everywhere. No other debugger is |
| 136 | available for even half as many configurations as @value{GDBN} |
| 137 | supports. |
| 138 | |
| 139 | |
| 140 | @node Overall Structure |
| 141 | |
| 142 | @chapter Overall Structure |
| 143 | |
| 144 | @value{GDBN} consists of three major subsystems: user interface, |
| 145 | symbol handling (the @dfn{symbol side}), and target system handling (the |
| 146 | @dfn{target side}). |
| 147 | |
| 148 | The user interface consists of several actual interfaces, plus |
| 149 | supporting code. |
| 150 | |
| 151 | The symbol side consists of object file readers, debugging info |
| 152 | interpreters, symbol table management, source language expression |
| 153 | parsing, type and value printing. |
| 154 | |
| 155 | The target side consists of execution control, stack frame analysis, and |
| 156 | physical target manipulation. |
| 157 | |
| 158 | The target side/symbol side division is not formal, and there are a |
| 159 | number of exceptions. For instance, core file support involves symbolic |
| 160 | elements (the basic core file reader is in BFD) and target elements (it |
| 161 | supplies the contents of memory and the values of registers). Instead, |
| 162 | this division is useful for understanding how the minor subsystems |
| 163 | should fit together. |
| 164 | |
| 165 | @section The Symbol Side |
| 166 | |
| 167 | The symbolic side of @value{GDBN} can be thought of as ``everything |
| 168 | you can do in @value{GDBN} without having a live program running''. |
| 169 | For instance, you can look at the types of variables, and evaluate |
| 170 | many kinds of expressions. |
| 171 | |
| 172 | @section The Target Side |
| 173 | |
| 174 | The target side of @value{GDBN} is the ``bits and bytes manipulator''. |
| 175 | Although it may make reference to symbolic info here and there, most |
| 176 | of the target side will run with only a stripped executable |
| 177 | available---or even no executable at all, in remote debugging cases. |
| 178 | |
| 179 | Operations such as disassembly, stack frame crawls, and register |
| 180 | display, are able to work with no symbolic info at all. In some cases, |
| 181 | such as disassembly, @value{GDBN} will use symbolic info to present addresses |
| 182 | relative to symbols rather than as raw numbers, but it will work either |
| 183 | way. |
| 184 | |
| 185 | @section Configurations |
| 186 | |
| 187 | @cindex host |
| 188 | @cindex target |
| 189 | @dfn{Host} refers to attributes of the system where @value{GDBN} runs. |
| 190 | @dfn{Target} refers to the system where the program being debugged |
| 191 | executes. In most cases they are the same machine, in which case a |
| 192 | third type of @dfn{Native} attributes come into play. |
| 193 | |
| 194 | Defines and include files needed to build on the host are host support. |
| 195 | Examples are tty support, system defined types, host byte order, host |
| 196 | float format. |
| 197 | |
| 198 | Defines and information needed to handle the target format are target |
| 199 | dependent. Examples are the stack frame format, instruction set, |
| 200 | breakpoint instruction, registers, and how to set up and tear down the stack |
| 201 | to call a function. |
| 202 | |
| 203 | Information that is only needed when the host and target are the same, |
| 204 | is native dependent. One example is Unix child process support; if the |
| 205 | host and target are not the same, doing a fork to start the target |
| 206 | process is a bad idea. The various macros needed for finding the |
| 207 | registers in the @code{upage}, running @code{ptrace}, and such are all |
| 208 | in the native-dependent files. |
| 209 | |
| 210 | Another example of native-dependent code is support for features that |
| 211 | are really part of the target environment, but which require |
| 212 | @code{#include} files that are only available on the host system. Core |
| 213 | file handling and @code{setjmp} handling are two common cases. |
| 214 | |
| 215 | When you want to make @value{GDBN} work ``native'' on a particular machine, you |
| 216 | have to include all three kinds of information. |
| 217 | |
| 218 | |
| 219 | @node Algorithms |
| 220 | |
| 221 | @chapter Algorithms |
| 222 | @cindex algorithms |
| 223 | |
| 224 | @value{GDBN} uses a number of debugging-specific algorithms. They are |
| 225 | often not very complicated, but get lost in the thicket of special |
| 226 | cases and real-world issues. This chapter describes the basic |
| 227 | algorithms and mentions some of the specific target definitions that |
| 228 | they use. |
| 229 | |
| 230 | @section Frames |
| 231 | |
| 232 | @cindex frame |
| 233 | @cindex call stack frame |
| 234 | A frame is a construct that @value{GDBN} uses to keep track of calling |
| 235 | and called functions. |
| 236 | |
| 237 | @findex create_new_frame |
| 238 | @vindex FRAME_FP |
| 239 | @code{FRAME_FP} in the machine description has no meaning to the |
| 240 | machine-independent part of @value{GDBN}, except that it is used when |
| 241 | setting up a new frame from scratch, as follows: |
| 242 | |
| 243 | @smallexample |
| 244 | create_new_frame (read_register (FP_REGNUM), read_pc ())); |
| 245 | @end smallexample |
| 246 | |
| 247 | @cindex frame pointer register |
| 248 | Other than that, all the meaning imparted to @code{FP_REGNUM} is |
| 249 | imparted by the machine-dependent code. So, @code{FP_REGNUM} can have |
| 250 | any value that is convenient for the code that creates new frames. |
| 251 | (@code{create_new_frame} calls @code{DEPRECATED_INIT_EXTRA_FRAME_INFO} |
| 252 | if it is defined; that is where you should use the @code{FP_REGNUM} |
| 253 | value, if your frames are nonstandard.) |
| 254 | |
| 255 | @cindex frame chain |
| 256 | Given a @value{GDBN} frame, define @code{DEPRECATED_FRAME_CHAIN} to |
| 257 | determine the address of the calling function's frame. This will be |
| 258 | used to create a new @value{GDBN} frame struct, and then |
| 259 | @code{DEPRECATED_INIT_EXTRA_FRAME_INFO} and |
| 260 | @code{DEPRECATED_INIT_FRAME_PC} will be called for the new frame. |
| 261 | |
| 262 | @section Breakpoint Handling |
| 263 | |
| 264 | @cindex breakpoints |
| 265 | In general, a breakpoint is a user-designated location in the program |
| 266 | where the user wants to regain control if program execution ever reaches |
| 267 | that location. |
| 268 | |
| 269 | There are two main ways to implement breakpoints; either as ``hardware'' |
| 270 | breakpoints or as ``software'' breakpoints. |
| 271 | |
| 272 | @cindex hardware breakpoints |
| 273 | @cindex program counter |
| 274 | Hardware breakpoints are sometimes available as a builtin debugging |
| 275 | features with some chips. Typically these work by having dedicated |
| 276 | register into which the breakpoint address may be stored. If the PC |
| 277 | (shorthand for @dfn{program counter}) |
| 278 | ever matches a value in a breakpoint registers, the CPU raises an |
| 279 | exception and reports it to @value{GDBN}. |
| 280 | |
| 281 | Another possibility is when an emulator is in use; many emulators |
| 282 | include circuitry that watches the address lines coming out from the |
| 283 | processor, and force it to stop if the address matches a breakpoint's |
| 284 | address. |
| 285 | |
| 286 | A third possibility is that the target already has the ability to do |
| 287 | breakpoints somehow; for instance, a ROM monitor may do its own |
| 288 | software breakpoints. So although these are not literally ``hardware |
| 289 | breakpoints'', from @value{GDBN}'s point of view they work the same; |
| 290 | @value{GDBN} need not do nothing more than set the breakpoint and wait |
| 291 | for something to happen. |
| 292 | |
| 293 | Since they depend on hardware resources, hardware breakpoints may be |
| 294 | limited in number; when the user asks for more, @value{GDBN} will |
| 295 | start trying to set software breakpoints. (On some architectures, |
| 296 | notably the 32-bit x86 platforms, @value{GDBN} cannot always know |
| 297 | whether there's enough hardware resources to insert all the hardware |
| 298 | breakpoints and watchpoints. On those platforms, @value{GDBN} prints |
| 299 | an error message only when the program being debugged is continued.) |
| 300 | |
| 301 | @cindex software breakpoints |
| 302 | Software breakpoints require @value{GDBN} to do somewhat more work. |
| 303 | The basic theory is that @value{GDBN} will replace a program |
| 304 | instruction with a trap, illegal divide, or some other instruction |
| 305 | that will cause an exception, and then when it's encountered, |
| 306 | @value{GDBN} will take the exception and stop the program. When the |
| 307 | user says to continue, @value{GDBN} will restore the original |
| 308 | instruction, single-step, re-insert the trap, and continue on. |
| 309 | |
| 310 | Since it literally overwrites the program being tested, the program area |
| 311 | must be writable, so this technique won't work on programs in ROM. It |
| 312 | can also distort the behavior of programs that examine themselves, |
| 313 | although such a situation would be highly unusual. |
| 314 | |
| 315 | Also, the software breakpoint instruction should be the smallest size of |
| 316 | instruction, so it doesn't overwrite an instruction that might be a jump |
| 317 | target, and cause disaster when the program jumps into the middle of the |
| 318 | breakpoint instruction. (Strictly speaking, the breakpoint must be no |
| 319 | larger than the smallest interval between instructions that may be jump |
| 320 | targets; perhaps there is an architecture where only even-numbered |
| 321 | instructions may jumped to.) Note that it's possible for an instruction |
| 322 | set not to have any instructions usable for a software breakpoint, |
| 323 | although in practice only the ARC has failed to define such an |
| 324 | instruction. |
| 325 | |
| 326 | @findex BREAKPOINT |
| 327 | The basic definition of the software breakpoint is the macro |
| 328 | @code{BREAKPOINT}. |
| 329 | |
| 330 | Basic breakpoint object handling is in @file{breakpoint.c}. However, |
| 331 | much of the interesting breakpoint action is in @file{infrun.c}. |
| 332 | |
| 333 | @section Single Stepping |
| 334 | |
| 335 | @section Signal Handling |
| 336 | |
| 337 | @section Thread Handling |
| 338 | |
| 339 | @section Inferior Function Calls |
| 340 | |
| 341 | @section Longjmp Support |
| 342 | |
| 343 | @cindex @code{longjmp} debugging |
| 344 | @value{GDBN} has support for figuring out that the target is doing a |
| 345 | @code{longjmp} and for stopping at the target of the jump, if we are |
| 346 | stepping. This is done with a few specialized internal breakpoints, |
| 347 | which are visible in the output of the @samp{maint info breakpoint} |
| 348 | command. |
| 349 | |
| 350 | @findex GET_LONGJMP_TARGET |
| 351 | To make this work, you need to define a macro called |
| 352 | @code{GET_LONGJMP_TARGET}, which will examine the @code{jmp_buf} |
| 353 | structure and extract the longjmp target address. Since @code{jmp_buf} |
| 354 | is target specific, you will need to define it in the appropriate |
| 355 | @file{tm-@var{target}.h} file. Look in @file{tm-sun4os4.h} and |
| 356 | @file{sparc-tdep.c} for examples of how to do this. |
| 357 | |
| 358 | @section Watchpoints |
| 359 | @cindex watchpoints |
| 360 | |
| 361 | Watchpoints are a special kind of breakpoints (@pxref{Algorithms, |
| 362 | breakpoints}) which break when data is accessed rather than when some |
| 363 | instruction is executed. When you have data which changes without |
| 364 | your knowing what code does that, watchpoints are the silver bullet to |
| 365 | hunt down and kill such bugs. |
| 366 | |
| 367 | @cindex hardware watchpoints |
| 368 | @cindex software watchpoints |
| 369 | Watchpoints can be either hardware-assisted or not; the latter type is |
| 370 | known as ``software watchpoints.'' @value{GDBN} always uses |
| 371 | hardware-assisted watchpoints if they are available, and falls back on |
| 372 | software watchpoints otherwise. Typical situations where @value{GDBN} |
| 373 | will use software watchpoints are: |
| 374 | |
| 375 | @itemize @bullet |
| 376 | @item |
| 377 | The watched memory region is too large for the underlying hardware |
| 378 | watchpoint support. For example, each x86 debug register can watch up |
| 379 | to 4 bytes of memory, so trying to watch data structures whose size is |
| 380 | more than 16 bytes will cause @value{GDBN} to use software |
| 381 | watchpoints. |
| 382 | |
| 383 | @item |
| 384 | The value of the expression to be watched depends on data held in |
| 385 | registers (as opposed to memory). |
| 386 | |
| 387 | @item |
| 388 | Too many different watchpoints requested. (On some architectures, |
| 389 | this situation is impossible to detect until the debugged program is |
| 390 | resumed.) Note that x86 debug registers are used both for hardware |
| 391 | breakpoints and for watchpoints, so setting too many hardware |
| 392 | breakpoints might cause watchpoint insertion to fail. |
| 393 | |
| 394 | @item |
| 395 | No hardware-assisted watchpoints provided by the target |
| 396 | implementation. |
| 397 | @end itemize |
| 398 | |
| 399 | Software watchpoints are very slow, since @value{GDBN} needs to |
| 400 | single-step the program being debugged and test the value of the |
| 401 | watched expression(s) after each instruction. The rest of this |
| 402 | section is mostly irrelevant for software watchpoints. |
| 403 | |
| 404 | @value{GDBN} uses several macros and primitives to support hardware |
| 405 | watchpoints: |
| 406 | |
| 407 | @table @code |
| 408 | @findex TARGET_HAS_HARDWARE_WATCHPOINTS |
| 409 | @item TARGET_HAS_HARDWARE_WATCHPOINTS |
| 410 | If defined, the target supports hardware watchpoints. |
| 411 | |
| 412 | @findex TARGET_CAN_USE_HARDWARE_WATCHPOINT |
| 413 | @item TARGET_CAN_USE_HARDWARE_WATCHPOINT (@var{type}, @var{count}, @var{other}) |
| 414 | Return the number of hardware watchpoints of type @var{type} that are |
| 415 | possible to be set. The value is positive if @var{count} watchpoints |
| 416 | of this type can be set, zero if setting watchpoints of this type is |
| 417 | not supported, and negative if @var{count} is more than the maximum |
| 418 | number of watchpoints of type @var{type} that can be set. @var{other} |
| 419 | is non-zero if other types of watchpoints are currently enabled (there |
| 420 | are architectures which cannot set watchpoints of different types at |
| 421 | the same time). |
| 422 | |
| 423 | @findex TARGET_REGION_OK_FOR_HW_WATCHPOINT |
| 424 | @item TARGET_REGION_OK_FOR_HW_WATCHPOINT (@var{addr}, @var{len}) |
| 425 | Return non-zero if hardware watchpoints can be used to watch a region |
| 426 | whose address is @var{addr} and whose length in bytes is @var{len}. |
| 427 | |
| 428 | @findex TARGET_REGION_SIZE_OK_FOR_HW_WATCHPOINT |
| 429 | @item TARGET_REGION_SIZE_OK_FOR_HW_WATCHPOINT (@var{size}) |
| 430 | Return non-zero if hardware watchpoints can be used to watch a region |
| 431 | whose size is @var{size}. @value{GDBN} only uses this macro as a |
| 432 | fall-back, in case @code{TARGET_REGION_OK_FOR_HW_WATCHPOINT} is not |
| 433 | defined. |
| 434 | |
| 435 | @findex TARGET_DISABLE_HW_WATCHPOINTS |
| 436 | @item TARGET_DISABLE_HW_WATCHPOINTS (@var{pid}) |
| 437 | Disables watchpoints in the process identified by @var{pid}. This is |
| 438 | used, e.g., on HP-UX which provides operations to disable and enable |
| 439 | the page-level memory protection that implements hardware watchpoints |
| 440 | on that platform. |
| 441 | |
| 442 | @findex TARGET_ENABLE_HW_WATCHPOINTS |
| 443 | @item TARGET_ENABLE_HW_WATCHPOINTS (@var{pid}) |
| 444 | Enables watchpoints in the process identified by @var{pid}. This is |
| 445 | used, e.g., on HP-UX which provides operations to disable and enable |
| 446 | the page-level memory protection that implements hardware watchpoints |
| 447 | on that platform. |
| 448 | |
| 449 | @findex target_insert_watchpoint |
| 450 | @findex target_remove_watchpoint |
| 451 | @item target_insert_watchpoint (@var{addr}, @var{len}, @var{type}) |
| 452 | @itemx target_remove_watchpoint (@var{addr}, @var{len}, @var{type}) |
| 453 | Insert or remove a hardware watchpoint starting at @var{addr}, for |
| 454 | @var{len} bytes. @var{type} is the watchpoint type, one of the |
| 455 | possible values of the enumerated data type @code{target_hw_bp_type}, |
| 456 | defined by @file{breakpoint.h} as follows: |
| 457 | |
| 458 | @smallexample |
| 459 | enum target_hw_bp_type |
| 460 | @{ |
| 461 | hw_write = 0, /* Common (write) HW watchpoint */ |
| 462 | hw_read = 1, /* Read HW watchpoint */ |
| 463 | hw_access = 2, /* Access (read or write) HW watchpoint */ |
| 464 | hw_execute = 3 /* Execute HW breakpoint */ |
| 465 | @}; |
| 466 | @end smallexample |
| 467 | |
| 468 | @noindent |
| 469 | These two macros should return 0 for success, non-zero for failure. |
| 470 | |
| 471 | @cindex insert or remove hardware breakpoint |
| 472 | @findex target_remove_hw_breakpoint |
| 473 | @findex target_insert_hw_breakpoint |
| 474 | @item target_remove_hw_breakpoint (@var{addr}, @var{shadow}) |
| 475 | @itemx target_insert_hw_breakpoint (@var{addr}, @var{shadow}) |
| 476 | Insert or remove a hardware-assisted breakpoint at address @var{addr}. |
| 477 | Returns zero for success, non-zero for failure. @var{shadow} is the |
| 478 | real contents of the byte where the breakpoint has been inserted; it |
| 479 | is generally not valid when hardware breakpoints are used, but since |
| 480 | no other code touches these values, the implementations of the above |
| 481 | two macros can use them for their internal purposes. |
| 482 | |
| 483 | @findex target_stopped_data_address |
| 484 | @item target_stopped_data_address () |
| 485 | If the inferior has some watchpoint that triggered, return the address |
| 486 | associated with that watchpoint. Otherwise, return zero. |
| 487 | |
| 488 | @findex DECR_PC_AFTER_HW_BREAK |
| 489 | @item DECR_PC_AFTER_HW_BREAK |
| 490 | If defined, @value{GDBN} decrements the program counter by the value |
| 491 | of @code{DECR_PC_AFTER_HW_BREAK} after a hardware break-point. This |
| 492 | overrides the value of @code{DECR_PC_AFTER_BREAK} when a breakpoint |
| 493 | that breaks is a hardware-assisted breakpoint. |
| 494 | |
| 495 | @findex HAVE_STEPPABLE_WATCHPOINT |
| 496 | @item HAVE_STEPPABLE_WATCHPOINT |
| 497 | If defined to a non-zero value, it is not necessary to disable a |
| 498 | watchpoint to step over it. |
| 499 | |
| 500 | @findex HAVE_NONSTEPPABLE_WATCHPOINT |
| 501 | @item HAVE_NONSTEPPABLE_WATCHPOINT |
| 502 | If defined to a non-zero value, @value{GDBN} should disable a |
| 503 | watchpoint to step the inferior over it. |
| 504 | |
| 505 | @findex HAVE_CONTINUABLE_WATCHPOINT |
| 506 | @item HAVE_CONTINUABLE_WATCHPOINT |
| 507 | If defined to a non-zero value, it is possible to continue the |
| 508 | inferior after a watchpoint has been hit. |
| 509 | |
| 510 | @findex CANNOT_STEP_HW_WATCHPOINTS |
| 511 | @item CANNOT_STEP_HW_WATCHPOINTS |
| 512 | If this is defined to a non-zero value, @value{GDBN} will remove all |
| 513 | watchpoints before stepping the inferior. |
| 514 | |
| 515 | @findex STOPPED_BY_WATCHPOINT |
| 516 | @item STOPPED_BY_WATCHPOINT (@var{wait_status}) |
| 517 | Return non-zero if stopped by a watchpoint. @var{wait_status} is of |
| 518 | the type @code{struct target_waitstatus}, defined by @file{target.h}. |
| 519 | @end table |
| 520 | |
| 521 | @subsection x86 Watchpoints |
| 522 | @cindex x86 debug registers |
| 523 | @cindex watchpoints, on x86 |
| 524 | |
| 525 | The 32-bit Intel x86 (a.k.a.@: ia32) processors feature special debug |
| 526 | registers designed to facilitate debugging. @value{GDBN} provides a |
| 527 | generic library of functions that x86-based ports can use to implement |
| 528 | support for watchpoints and hardware-assisted breakpoints. This |
| 529 | subsection documents the x86 watchpoint facilities in @value{GDBN}. |
| 530 | |
| 531 | To use the generic x86 watchpoint support, a port should do the |
| 532 | following: |
| 533 | |
| 534 | @itemize @bullet |
| 535 | @findex I386_USE_GENERIC_WATCHPOINTS |
| 536 | @item |
| 537 | Define the macro @code{I386_USE_GENERIC_WATCHPOINTS} somewhere in the |
| 538 | target-dependent headers. |
| 539 | |
| 540 | @item |
| 541 | Include the @file{config/i386/nm-i386.h} header file @emph{after} |
| 542 | defining @code{I386_USE_GENERIC_WATCHPOINTS}. |
| 543 | |
| 544 | @item |
| 545 | Add @file{i386-nat.o} to the value of the Make variable |
| 546 | @code{NATDEPFILES} (@pxref{Native Debugging, NATDEPFILES}) or |
| 547 | @code{TDEPFILES} (@pxref{Target Architecture Definition, TDEPFILES}). |
| 548 | |
| 549 | @item |
| 550 | Provide implementations for the @code{I386_DR_LOW_*} macros described |
| 551 | below. Typically, each macro should call a target-specific function |
| 552 | which does the real work. |
| 553 | @end itemize |
| 554 | |
| 555 | The x86 watchpoint support works by maintaining mirror images of the |
| 556 | debug registers. Values are copied between the mirror images and the |
| 557 | real debug registers via a set of macros which each target needs to |
| 558 | provide: |
| 559 | |
| 560 | @table @code |
| 561 | @findex I386_DR_LOW_SET_CONTROL |
| 562 | @item I386_DR_LOW_SET_CONTROL (@var{val}) |
| 563 | Set the Debug Control (DR7) register to the value @var{val}. |
| 564 | |
| 565 | @findex I386_DR_LOW_SET_ADDR |
| 566 | @item I386_DR_LOW_SET_ADDR (@var{idx}, @var{addr}) |
| 567 | Put the address @var{addr} into the debug register number @var{idx}. |
| 568 | |
| 569 | @findex I386_DR_LOW_RESET_ADDR |
| 570 | @item I386_DR_LOW_RESET_ADDR (@var{idx}) |
| 571 | Reset (i.e.@: zero out) the address stored in the debug register |
| 572 | number @var{idx}. |
| 573 | |
| 574 | @findex I386_DR_LOW_GET_STATUS |
| 575 | @item I386_DR_LOW_GET_STATUS |
| 576 | Return the value of the Debug Status (DR6) register. This value is |
| 577 | used immediately after it is returned by |
| 578 | @code{I386_DR_LOW_GET_STATUS}, so as to support per-thread status |
| 579 | register values. |
| 580 | @end table |
| 581 | |
| 582 | For each one of the 4 debug registers (whose indices are from 0 to 3) |
| 583 | that store addresses, a reference count is maintained by @value{GDBN}, |
| 584 | to allow sharing of debug registers by several watchpoints. This |
| 585 | allows users to define several watchpoints that watch the same |
| 586 | expression, but with different conditions and/or commands, without |
| 587 | wasting debug registers which are in short supply. @value{GDBN} |
| 588 | maintains the reference counts internally, targets don't have to do |
| 589 | anything to use this feature. |
| 590 | |
| 591 | The x86 debug registers can each watch a region that is 1, 2, or 4 |
| 592 | bytes long. The ia32 architecture requires that each watched region |
| 593 | be appropriately aligned: 2-byte region on 2-byte boundary, 4-byte |
| 594 | region on 4-byte boundary. However, the x86 watchpoint support in |
| 595 | @value{GDBN} can watch unaligned regions and regions larger than 4 |
| 596 | bytes (up to 16 bytes) by allocating several debug registers to watch |
| 597 | a single region. This allocation of several registers per a watched |
| 598 | region is also done automatically without target code intervention. |
| 599 | |
| 600 | The generic x86 watchpoint support provides the following API for the |
| 601 | @value{GDBN}'s application code: |
| 602 | |
| 603 | @table @code |
| 604 | @findex i386_region_ok_for_watchpoint |
| 605 | @item i386_region_ok_for_watchpoint (@var{addr}, @var{len}) |
| 606 | The macro @code{TARGET_REGION_OK_FOR_HW_WATCHPOINT} is set to call |
| 607 | this function. It counts the number of debug registers required to |
| 608 | watch a given region, and returns a non-zero value if that number is |
| 609 | less than 4, the number of debug registers available to x86 |
| 610 | processors. |
| 611 | |
| 612 | @findex i386_stopped_data_address |
| 613 | @item i386_stopped_data_address (void) |
| 614 | The macros @code{STOPPED_BY_WATCHPOINT} and |
| 615 | @code{target_stopped_data_address} are set to call this function. The |
| 616 | argument passed to @code{STOPPED_BY_WATCHPOINT} is ignored. This |
| 617 | function examines the breakpoint condition bits in the DR6 Debug |
| 618 | Status register, as returned by the @code{I386_DR_LOW_GET_STATUS} |
| 619 | macro, and returns the address associated with the first bit that is |
| 620 | set in DR6. |
| 621 | |
| 622 | @findex i386_insert_watchpoint |
| 623 | @findex i386_remove_watchpoint |
| 624 | @item i386_insert_watchpoint (@var{addr}, @var{len}, @var{type}) |
| 625 | @itemx i386_remove_watchpoint (@var{addr}, @var{len}, @var{type}) |
| 626 | Insert or remove a watchpoint. The macros |
| 627 | @code{target_insert_watchpoint} and @code{target_remove_watchpoint} |
| 628 | are set to call these functions. @code{i386_insert_watchpoint} first |
| 629 | looks for a debug register which is already set to watch the same |
| 630 | region for the same access types; if found, it just increments the |
| 631 | reference count of that debug register, thus implementing debug |
| 632 | register sharing between watchpoints. If no such register is found, |
| 633 | the function looks for a vacant debug register, sets its mirrored |
| 634 | value to @var{addr}, sets the mirrored value of DR7 Debug Control |
| 635 | register as appropriate for the @var{len} and @var{type} parameters, |
| 636 | and then passes the new values of the debug register and DR7 to the |
| 637 | inferior by calling @code{I386_DR_LOW_SET_ADDR} and |
| 638 | @code{I386_DR_LOW_SET_CONTROL}. If more than one debug register is |
| 639 | required to cover the given region, the above process is repeated for |
| 640 | each debug register. |
| 641 | |
| 642 | @code{i386_remove_watchpoint} does the opposite: it resets the address |
| 643 | in the mirrored value of the debug register and its read/write and |
| 644 | length bits in the mirrored value of DR7, then passes these new |
| 645 | values to the inferior via @code{I386_DR_LOW_RESET_ADDR} and |
| 646 | @code{I386_DR_LOW_SET_CONTROL}. If a register is shared by several |
| 647 | watchpoints, each time a @code{i386_remove_watchpoint} is called, it |
| 648 | decrements the reference count, and only calls |
| 649 | @code{I386_DR_LOW_RESET_ADDR} and @code{I386_DR_LOW_SET_CONTROL} when |
| 650 | the count goes to zero. |
| 651 | |
| 652 | @findex i386_insert_hw_breakpoint |
| 653 | @findex i386_remove_hw_breakpoint |
| 654 | @item i386_insert_hw_breakpoint (@var{addr}, @var{shadow} |
| 655 | @itemx i386_remove_hw_breakpoint (@var{addr}, @var{shadow}) |
| 656 | These functions insert and remove hardware-assisted breakpoints. The |
| 657 | macros @code{target_insert_hw_breakpoint} and |
| 658 | @code{target_remove_hw_breakpoint} are set to call these functions. |
| 659 | These functions work like @code{i386_insert_watchpoint} and |
| 660 | @code{i386_remove_watchpoint}, respectively, except that they set up |
| 661 | the debug registers to watch instruction execution, and each |
| 662 | hardware-assisted breakpoint always requires exactly one debug |
| 663 | register. |
| 664 | |
| 665 | @findex i386_stopped_by_hwbp |
| 666 | @item i386_stopped_by_hwbp (void) |
| 667 | This function returns non-zero if the inferior has some watchpoint or |
| 668 | hardware breakpoint that triggered. It works like |
| 669 | @code{i386_stopped_data_address}, except that it doesn't return the |
| 670 | address whose watchpoint triggered. |
| 671 | |
| 672 | @findex i386_cleanup_dregs |
| 673 | @item i386_cleanup_dregs (void) |
| 674 | This function clears all the reference counts, addresses, and control |
| 675 | bits in the mirror images of the debug registers. It doesn't affect |
| 676 | the actual debug registers in the inferior process. |
| 677 | @end table |
| 678 | |
| 679 | @noindent |
| 680 | @strong{Notes:} |
| 681 | @enumerate 1 |
| 682 | @item |
| 683 | x86 processors support setting watchpoints on I/O reads or writes. |
| 684 | However, since no target supports this (as of March 2001), and since |
| 685 | @code{enum target_hw_bp_type} doesn't even have an enumeration for I/O |
| 686 | watchpoints, this feature is not yet available to @value{GDBN} running |
| 687 | on x86. |
| 688 | |
| 689 | @item |
| 690 | x86 processors can enable watchpoints locally, for the current task |
| 691 | only, or globally, for all the tasks. For each debug register, |
| 692 | there's a bit in the DR7 Debug Control register that determines |
| 693 | whether the associated address is watched locally or globally. The |
| 694 | current implementation of x86 watchpoint support in @value{GDBN} |
| 695 | always sets watchpoints to be locally enabled, since global |
| 696 | watchpoints might interfere with the underlying OS and are probably |
| 697 | unavailable in many platforms. |
| 698 | @end enumerate |
| 699 | |
| 700 | @section Observing changes in @value{GDBN} internals |
| 701 | @cindex observer pattern interface |
| 702 | @cindex notifications about changes in internals |
| 703 | |
| 704 | In order to function properly, several modules need to be notified when |
| 705 | some changes occur in the @value{GDBN} internals. Traditionally, these |
| 706 | modules have relied on several paradigms, the most common ones being |
| 707 | hooks and gdb-events. Unfortunately, none of these paradigms was |
| 708 | versatile enough to become the standard notification mechanism in |
| 709 | @value{GDBN}. The fact that they only supported one ``client'' was also |
| 710 | a strong limitation. |
| 711 | |
| 712 | A new paradigm, based on the Observer pattern of the @cite{Design |
| 713 | Patterns} book, has therefore been implemented. The goal was to provide |
| 714 | a new interface overcoming the issues with the notification mechanisms |
| 715 | previously available. This new interface needed to be strongly typed, |
| 716 | easy to extend, and versatile enough to be used as the standard |
| 717 | interface when adding new notifications. |
| 718 | |
| 719 | See @ref{GDB Observers} for a brief description of the observers |
| 720 | currently implemented in GDB. The rationale for the current |
| 721 | implementation is also briefly discussed. |
| 722 | |
| 723 | @node User Interface |
| 724 | |
| 725 | @chapter User Interface |
| 726 | |
| 727 | @value{GDBN} has several user interfaces. Although the command-line interface |
| 728 | is the most common and most familiar, there are others. |
| 729 | |
| 730 | @section Command Interpreter |
| 731 | |
| 732 | @cindex command interpreter |
| 733 | @cindex CLI |
| 734 | The command interpreter in @value{GDBN} is fairly simple. It is designed to |
| 735 | allow for the set of commands to be augmented dynamically, and also |
| 736 | has a recursive subcommand capability, where the first argument to |
| 737 | a command may itself direct a lookup on a different command list. |
| 738 | |
| 739 | For instance, the @samp{set} command just starts a lookup on the |
| 740 | @code{setlist} command list, while @samp{set thread} recurses |
| 741 | to the @code{set_thread_cmd_list}. |
| 742 | |
| 743 | @findex add_cmd |
| 744 | @findex add_com |
| 745 | To add commands in general, use @code{add_cmd}. @code{add_com} adds to |
| 746 | the main command list, and should be used for those commands. The usual |
| 747 | place to add commands is in the @code{_initialize_@var{xyz}} routines at |
| 748 | the ends of most source files. |
| 749 | |
| 750 | @findex add_setshow_cmd |
| 751 | @findex add_setshow_cmd_full |
| 752 | To add paired @samp{set} and @samp{show} commands, use |
| 753 | @code{add_setshow_cmd} or @code{add_setshow_cmd_full}. The former is |
| 754 | a slightly simpler interface which is useful when you don't need to |
| 755 | further modify the new command structures, while the latter returns |
| 756 | the new command structures for manipulation. |
| 757 | |
| 758 | @cindex deprecating commands |
| 759 | @findex deprecate_cmd |
| 760 | Before removing commands from the command set it is a good idea to |
| 761 | deprecate them for some time. Use @code{deprecate_cmd} on commands or |
| 762 | aliases to set the deprecated flag. @code{deprecate_cmd} takes a |
| 763 | @code{struct cmd_list_element} as it's first argument. You can use the |
| 764 | return value from @code{add_com} or @code{add_cmd} to deprecate the |
| 765 | command immediately after it is created. |
| 766 | |
| 767 | The first time a command is used the user will be warned and offered a |
| 768 | replacement (if one exists). Note that the replacement string passed to |
| 769 | @code{deprecate_cmd} should be the full name of the command, i.e. the |
| 770 | entire string the user should type at the command line. |
| 771 | |
| 772 | @section UI-Independent Output---the @code{ui_out} Functions |
| 773 | @c This section is based on the documentation written by Fernando |
| 774 | @c Nasser <fnasser@redhat.com>. |
| 775 | |
| 776 | @cindex @code{ui_out} functions |
| 777 | The @code{ui_out} functions present an abstraction level for the |
| 778 | @value{GDBN} output code. They hide the specifics of different user |
| 779 | interfaces supported by @value{GDBN}, and thus free the programmer |
| 780 | from the need to write several versions of the same code, one each for |
| 781 | every UI, to produce output. |
| 782 | |
| 783 | @subsection Overview and Terminology |
| 784 | |
| 785 | In general, execution of each @value{GDBN} command produces some sort |
| 786 | of output, and can even generate an input request. |
| 787 | |
| 788 | Output can be generated for the following purposes: |
| 789 | |
| 790 | @itemize @bullet |
| 791 | @item |
| 792 | to display a @emph{result} of an operation; |
| 793 | |
| 794 | @item |
| 795 | to convey @emph{info} or produce side-effects of a requested |
| 796 | operation; |
| 797 | |
| 798 | @item |
| 799 | to provide a @emph{notification} of an asynchronous event (including |
| 800 | progress indication of a prolonged asynchronous operation); |
| 801 | |
| 802 | @item |
| 803 | to display @emph{error messages} (including warnings); |
| 804 | |
| 805 | @item |
| 806 | to show @emph{debug data}; |
| 807 | |
| 808 | @item |
| 809 | to @emph{query} or prompt a user for input (a special case). |
| 810 | @end itemize |
| 811 | |
| 812 | @noindent |
| 813 | This section mainly concentrates on how to build result output, |
| 814 | although some of it also applies to other kinds of output. |
| 815 | |
| 816 | Generation of output that displays the results of an operation |
| 817 | involves one or more of the following: |
| 818 | |
| 819 | @itemize @bullet |
| 820 | @item |
| 821 | output of the actual data |
| 822 | |
| 823 | @item |
| 824 | formatting the output as appropriate for console output, to make it |
| 825 | easily readable by humans |
| 826 | |
| 827 | @item |
| 828 | machine oriented formatting--a more terse formatting to allow for easy |
| 829 | parsing by programs which read @value{GDBN}'s output |
| 830 | |
| 831 | @item |
| 832 | annotation, whose purpose is to help legacy GUIs to identify interesting |
| 833 | parts in the output |
| 834 | @end itemize |
| 835 | |
| 836 | The @code{ui_out} routines take care of the first three aspects. |
| 837 | Annotations are provided by separate annotation routines. Note that use |
| 838 | of annotations for an interface between a GUI and @value{GDBN} is |
| 839 | deprecated. |
| 840 | |
| 841 | Output can be in the form of a single item, which we call a @dfn{field}; |
| 842 | a @dfn{list} consisting of identical fields; a @dfn{tuple} consisting of |
| 843 | non-identical fields; or a @dfn{table}, which is a tuple consisting of a |
| 844 | header and a body. In a BNF-like form: |
| 845 | |
| 846 | @table @code |
| 847 | @item <table> @expansion{} |
| 848 | @code{<header> <body>} |
| 849 | @item <header> @expansion{} |
| 850 | @code{@{ <column> @}} |
| 851 | @item <column> @expansion{} |
| 852 | @code{<width> <alignment> <title>} |
| 853 | @item <body> @expansion{} |
| 854 | @code{@{<row>@}} |
| 855 | @end table |
| 856 | |
| 857 | |
| 858 | @subsection General Conventions |
| 859 | |
| 860 | Most @code{ui_out} routines are of type @code{void}, the exceptions are |
| 861 | @code{ui_out_stream_new} (which returns a pointer to the newly created |
| 862 | object) and the @code{make_cleanup} routines. |
| 863 | |
| 864 | The first parameter is always the @code{ui_out} vector object, a pointer |
| 865 | to a @code{struct ui_out}. |
| 866 | |
| 867 | The @var{format} parameter is like in @code{printf} family of functions. |
| 868 | When it is present, there must also be a variable list of arguments |
| 869 | sufficient used to satisfy the @code{%} specifiers in the supplied |
| 870 | format. |
| 871 | |
| 872 | When a character string argument is not used in a @code{ui_out} function |
| 873 | call, a @code{NULL} pointer has to be supplied instead. |
| 874 | |
| 875 | |
| 876 | @subsection Table, Tuple and List Functions |
| 877 | |
| 878 | @cindex list output functions |
| 879 | @cindex table output functions |
| 880 | @cindex tuple output functions |
| 881 | This section introduces @code{ui_out} routines for building lists, |
| 882 | tuples and tables. The routines to output the actual data items |
| 883 | (fields) are presented in the next section. |
| 884 | |
| 885 | To recap: A @dfn{tuple} is a sequence of @dfn{fields}, each field |
| 886 | containing information about an object; a @dfn{list} is a sequence of |
| 887 | fields where each field describes an identical object. |
| 888 | |
| 889 | Use the @dfn{table} functions when your output consists of a list of |
| 890 | rows (tuples) and the console output should include a heading. Use this |
| 891 | even when you are listing just one object but you still want the header. |
| 892 | |
| 893 | @cindex nesting level in @code{ui_out} functions |
| 894 | Tables can not be nested. Tuples and lists can be nested up to a |
| 895 | maximum of five levels. |
| 896 | |
| 897 | The overall structure of the table output code is something like this: |
| 898 | |
| 899 | @smallexample |
| 900 | ui_out_table_begin |
| 901 | ui_out_table_header |
| 902 | @dots{} |
| 903 | ui_out_table_body |
| 904 | ui_out_tuple_begin |
| 905 | ui_out_field_* |
| 906 | @dots{} |
| 907 | ui_out_tuple_end |
| 908 | @dots{} |
| 909 | ui_out_table_end |
| 910 | @end smallexample |
| 911 | |
| 912 | Here is the description of table-, tuple- and list-related @code{ui_out} |
| 913 | functions: |
| 914 | |
| 915 | @deftypefun void ui_out_table_begin (struct ui_out *@var{uiout}, int @var{nbrofcols}, int @var{nr_rows}, const char *@var{tblid}) |
| 916 | The function @code{ui_out_table_begin} marks the beginning of the output |
| 917 | of a table. It should always be called before any other @code{ui_out} |
| 918 | function for a given table. @var{nbrofcols} is the number of columns in |
| 919 | the table. @var{nr_rows} is the number of rows in the table. |
| 920 | @var{tblid} is an optional string identifying the table. The string |
| 921 | pointed to by @var{tblid} is copied by the implementation of |
| 922 | @code{ui_out_table_begin}, so the application can free the string if it |
| 923 | was @code{malloc}ed. |
| 924 | |
| 925 | The companion function @code{ui_out_table_end}, described below, marks |
| 926 | the end of the table's output. |
| 927 | @end deftypefun |
| 928 | |
| 929 | @deftypefun void ui_out_table_header (struct ui_out *@var{uiout}, int @var{width}, enum ui_align @var{alignment}, const char *@var{colhdr}) |
| 930 | @code{ui_out_table_header} provides the header information for a single |
| 931 | table column. You call this function several times, one each for every |
| 932 | column of the table, after @code{ui_out_table_begin}, but before |
| 933 | @code{ui_out_table_body}. |
| 934 | |
| 935 | The value of @var{width} gives the column width in characters. The |
| 936 | value of @var{alignment} is one of @code{left}, @code{center}, and |
| 937 | @code{right}, and it specifies how to align the header: left-justify, |
| 938 | center, or right-justify it. @var{colhdr} points to a string that |
| 939 | specifies the column header; the implementation copies that string, so |
| 940 | column header strings in @code{malloc}ed storage can be freed after the |
| 941 | call. |
| 942 | @end deftypefun |
| 943 | |
| 944 | @deftypefun void ui_out_table_body (struct ui_out *@var{uiout}) |
| 945 | This function delimits the table header from the table body. |
| 946 | @end deftypefun |
| 947 | |
| 948 | @deftypefun void ui_out_table_end (struct ui_out *@var{uiout}) |
| 949 | This function signals the end of a table's output. It should be called |
| 950 | after the table body has been produced by the list and field output |
| 951 | functions. |
| 952 | |
| 953 | There should be exactly one call to @code{ui_out_table_end} for each |
| 954 | call to @code{ui_out_table_begin}, otherwise the @code{ui_out} functions |
| 955 | will signal an internal error. |
| 956 | @end deftypefun |
| 957 | |
| 958 | The output of the tuples that represent the table rows must follow the |
| 959 | call to @code{ui_out_table_body} and precede the call to |
| 960 | @code{ui_out_table_end}. You build a tuple by calling |
| 961 | @code{ui_out_tuple_begin} and @code{ui_out_tuple_end}, with suitable |
| 962 | calls to functions which actually output fields between them. |
| 963 | |
| 964 | @deftypefun void ui_out_tuple_begin (struct ui_out *@var{uiout}, const char *@var{id}) |
| 965 | This function marks the beginning of a tuple output. @var{id} points |
| 966 | to an optional string that identifies the tuple; it is copied by the |
| 967 | implementation, and so strings in @code{malloc}ed storage can be freed |
| 968 | after the call. |
| 969 | @end deftypefun |
| 970 | |
| 971 | @deftypefun void ui_out_tuple_end (struct ui_out *@var{uiout}) |
| 972 | This function signals an end of a tuple output. There should be exactly |
| 973 | one call to @code{ui_out_tuple_end} for each call to |
| 974 | @code{ui_out_tuple_begin}, otherwise an internal @value{GDBN} error will |
| 975 | be signaled. |
| 976 | @end deftypefun |
| 977 | |
| 978 | @deftypefun struct cleanup *make_cleanup_ui_out_tuple_begin_end (struct ui_out *@var{uiout}, const char *@var{id}) |
| 979 | This function first opens the tuple and then establishes a cleanup |
| 980 | (@pxref{Coding, Cleanups}) to close the tuple. It provides a convenient |
| 981 | and correct implementation of the non-portable@footnote{The function |
| 982 | cast is not portable ISO C.} code sequence: |
| 983 | @smallexample |
| 984 | struct cleanup *old_cleanup; |
| 985 | ui_out_tuple_begin (uiout, "..."); |
| 986 | old_cleanup = make_cleanup ((void(*)(void *)) ui_out_tuple_end, |
| 987 | uiout); |
| 988 | @end smallexample |
| 989 | @end deftypefun |
| 990 | |
| 991 | @deftypefun void ui_out_list_begin (struct ui_out *@var{uiout}, const char *@var{id}) |
| 992 | This function marks the beginning of a list output. @var{id} points to |
| 993 | an optional string that identifies the list; it is copied by the |
| 994 | implementation, and so strings in @code{malloc}ed storage can be freed |
| 995 | after the call. |
| 996 | @end deftypefun |
| 997 | |
| 998 | @deftypefun void ui_out_list_end (struct ui_out *@var{uiout}) |
| 999 | This function signals an end of a list output. There should be exactly |
| 1000 | one call to @code{ui_out_list_end} for each call to |
| 1001 | @code{ui_out_list_begin}, otherwise an internal @value{GDBN} error will |
| 1002 | be signaled. |
| 1003 | @end deftypefun |
| 1004 | |
| 1005 | @deftypefun struct cleanup *make_cleanup_ui_out_list_begin_end (struct ui_out *@var{uiout}, const char *@var{id}) |
| 1006 | Similar to @code{make_cleanup_ui_out_tuple_begin_end}, this function |
| 1007 | opens a list and then establishes cleanup (@pxref{Coding, Cleanups}) |
| 1008 | that will close the list.list. |
| 1009 | @end deftypefun |
| 1010 | |
| 1011 | @subsection Item Output Functions |
| 1012 | |
| 1013 | @cindex item output functions |
| 1014 | @cindex field output functions |
| 1015 | @cindex data output |
| 1016 | The functions described below produce output for the actual data |
| 1017 | items, or fields, which contain information about the object. |
| 1018 | |
| 1019 | Choose the appropriate function accordingly to your particular needs. |
| 1020 | |
| 1021 | @deftypefun void ui_out_field_fmt (struct ui_out *@var{uiout}, char *@var{fldname}, char *@var{format}, ...) |
| 1022 | This is the most general output function. It produces the |
| 1023 | representation of the data in the variable-length argument list |
| 1024 | according to formatting specifications in @var{format}, a |
| 1025 | @code{printf}-like format string. The optional argument @var{fldname} |
| 1026 | supplies the name of the field. The data items themselves are |
| 1027 | supplied as additional arguments after @var{format}. |
| 1028 | |
| 1029 | This generic function should be used only when it is not possible to |
| 1030 | use one of the specialized versions (see below). |
| 1031 | @end deftypefun |
| 1032 | |
| 1033 | @deftypefun void ui_out_field_int (struct ui_out *@var{uiout}, const char *@var{fldname}, int @var{value}) |
| 1034 | This function outputs a value of an @code{int} variable. It uses the |
| 1035 | @code{"%d"} output conversion specification. @var{fldname} specifies |
| 1036 | the name of the field. |
| 1037 | @end deftypefun |
| 1038 | |
| 1039 | @deftypefun void ui_out_field_fmt_int (struct ui_out *@var{uiout}, int @var{width}, enum ui_align @var{alignment}, const char *@var{fldname}, int @var{value}) |
| 1040 | This function outputs a value of an @code{int} variable. It differs from |
| 1041 | @code{ui_out_field_int} in that the caller specifies the desired @var{width} and @var{alignment} of the output. |
| 1042 | @var{fldname} specifies |
| 1043 | the name of the field. |
| 1044 | @end deftypefun |
| 1045 | |
| 1046 | @deftypefun void ui_out_field_core_addr (struct ui_out *@var{uiout}, const char *@var{fldname}, CORE_ADDR @var{address}) |
| 1047 | This function outputs an address. |
| 1048 | @end deftypefun |
| 1049 | |
| 1050 | @deftypefun void ui_out_field_string (struct ui_out *@var{uiout}, const char *@var{fldname}, const char *@var{string}) |
| 1051 | This function outputs a string using the @code{"%s"} conversion |
| 1052 | specification. |
| 1053 | @end deftypefun |
| 1054 | |
| 1055 | Sometimes, there's a need to compose your output piece by piece using |
| 1056 | functions that operate on a stream, such as @code{value_print} or |
| 1057 | @code{fprintf_symbol_filtered}. These functions accept an argument of |
| 1058 | the type @code{struct ui_file *}, a pointer to a @code{ui_file} object |
| 1059 | used to store the data stream used for the output. When you use one |
| 1060 | of these functions, you need a way to pass their results stored in a |
| 1061 | @code{ui_file} object to the @code{ui_out} functions. To this end, |
| 1062 | you first create a @code{ui_stream} object by calling |
| 1063 | @code{ui_out_stream_new}, pass the @code{stream} member of that |
| 1064 | @code{ui_stream} object to @code{value_print} and similar functions, |
| 1065 | and finally call @code{ui_out_field_stream} to output the field you |
| 1066 | constructed. When the @code{ui_stream} object is no longer needed, |
| 1067 | you should destroy it and free its memory by calling |
| 1068 | @code{ui_out_stream_delete}. |
| 1069 | |
| 1070 | @deftypefun struct ui_stream *ui_out_stream_new (struct ui_out *@var{uiout}) |
| 1071 | This function creates a new @code{ui_stream} object which uses the |
| 1072 | same output methods as the @code{ui_out} object whose pointer is |
| 1073 | passed in @var{uiout}. It returns a pointer to the newly created |
| 1074 | @code{ui_stream} object. |
| 1075 | @end deftypefun |
| 1076 | |
| 1077 | @deftypefun void ui_out_stream_delete (struct ui_stream *@var{streambuf}) |
| 1078 | This functions destroys a @code{ui_stream} object specified by |
| 1079 | @var{streambuf}. |
| 1080 | @end deftypefun |
| 1081 | |
| 1082 | @deftypefun void ui_out_field_stream (struct ui_out *@var{uiout}, const char *@var{fieldname}, struct ui_stream *@var{streambuf}) |
| 1083 | This function consumes all the data accumulated in |
| 1084 | @code{streambuf->stream} and outputs it like |
| 1085 | @code{ui_out_field_string} does. After a call to |
| 1086 | @code{ui_out_field_stream}, the accumulated data no longer exists, but |
| 1087 | the stream is still valid and may be used for producing more fields. |
| 1088 | @end deftypefun |
| 1089 | |
| 1090 | @strong{Important:} If there is any chance that your code could bail |
| 1091 | out before completing output generation and reaching the point where |
| 1092 | @code{ui_out_stream_delete} is called, it is necessary to set up a |
| 1093 | cleanup, to avoid leaking memory and other resources. Here's a |
| 1094 | skeleton code to do that: |
| 1095 | |
| 1096 | @smallexample |
| 1097 | struct ui_stream *mybuf = ui_out_stream_new (uiout); |
| 1098 | struct cleanup *old = make_cleanup (ui_out_stream_delete, mybuf); |
| 1099 | ... |
| 1100 | do_cleanups (old); |
| 1101 | @end smallexample |
| 1102 | |
| 1103 | If the function already has the old cleanup chain set (for other kinds |
| 1104 | of cleanups), you just have to add your cleanup to it: |
| 1105 | |
| 1106 | @smallexample |
| 1107 | mybuf = ui_out_stream_new (uiout); |
| 1108 | make_cleanup (ui_out_stream_delete, mybuf); |
| 1109 | @end smallexample |
| 1110 | |
| 1111 | Note that with cleanups in place, you should not call |
| 1112 | @code{ui_out_stream_delete} directly, or you would attempt to free the |
| 1113 | same buffer twice. |
| 1114 | |
| 1115 | @subsection Utility Output Functions |
| 1116 | |
| 1117 | @deftypefun void ui_out_field_skip (struct ui_out *@var{uiout}, const char *@var{fldname}) |
| 1118 | This function skips a field in a table. Use it if you have to leave |
| 1119 | an empty field without disrupting the table alignment. The argument |
| 1120 | @var{fldname} specifies a name for the (missing) filed. |
| 1121 | @end deftypefun |
| 1122 | |
| 1123 | @deftypefun void ui_out_text (struct ui_out *@var{uiout}, const char *@var{string}) |
| 1124 | This function outputs the text in @var{string} in a way that makes it |
| 1125 | easy to be read by humans. For example, the console implementation of |
| 1126 | this method filters the text through a built-in pager, to prevent it |
| 1127 | from scrolling off the visible portion of the screen. |
| 1128 | |
| 1129 | Use this function for printing relatively long chunks of text around |
| 1130 | the actual field data: the text it produces is not aligned according |
| 1131 | to the table's format. Use @code{ui_out_field_string} to output a |
| 1132 | string field, and use @code{ui_out_message}, described below, to |
| 1133 | output short messages. |
| 1134 | @end deftypefun |
| 1135 | |
| 1136 | @deftypefun void ui_out_spaces (struct ui_out *@var{uiout}, int @var{nspaces}) |
| 1137 | This function outputs @var{nspaces} spaces. It is handy to align the |
| 1138 | text produced by @code{ui_out_text} with the rest of the table or |
| 1139 | list. |
| 1140 | @end deftypefun |
| 1141 | |
| 1142 | @deftypefun void ui_out_message (struct ui_out *@var{uiout}, int @var{verbosity}, const char *@var{format}, ...) |
| 1143 | This function produces a formatted message, provided that the current |
| 1144 | verbosity level is at least as large as given by @var{verbosity}. The |
| 1145 | current verbosity level is specified by the user with the @samp{set |
| 1146 | verbositylevel} command.@footnote{As of this writing (April 2001), |
| 1147 | setting verbosity level is not yet implemented, and is always returned |
| 1148 | as zero. So calling @code{ui_out_message} with a @var{verbosity} |
| 1149 | argument more than zero will cause the message to never be printed.} |
| 1150 | @end deftypefun |
| 1151 | |
| 1152 | @deftypefun void ui_out_wrap_hint (struct ui_out *@var{uiout}, char *@var{indent}) |
| 1153 | This function gives the console output filter (a paging filter) a hint |
| 1154 | of where to break lines which are too long. Ignored for all other |
| 1155 | output consumers. @var{indent}, if non-@code{NULL}, is the string to |
| 1156 | be printed to indent the wrapped text on the next line; it must remain |
| 1157 | accessible until the next call to @code{ui_out_wrap_hint}, or until an |
| 1158 | explicit newline is produced by one of the other functions. If |
| 1159 | @var{indent} is @code{NULL}, the wrapped text will not be indented. |
| 1160 | @end deftypefun |
| 1161 | |
| 1162 | @deftypefun void ui_out_flush (struct ui_out *@var{uiout}) |
| 1163 | This function flushes whatever output has been accumulated so far, if |
| 1164 | the UI buffers output. |
| 1165 | @end deftypefun |
| 1166 | |
| 1167 | |
| 1168 | @subsection Examples of Use of @code{ui_out} functions |
| 1169 | |
| 1170 | @cindex using @code{ui_out} functions |
| 1171 | @cindex @code{ui_out} functions, usage examples |
| 1172 | This section gives some practical examples of using the @code{ui_out} |
| 1173 | functions to generalize the old console-oriented code in |
| 1174 | @value{GDBN}. The examples all come from functions defined on the |
| 1175 | @file{breakpoints.c} file. |
| 1176 | |
| 1177 | This example, from the @code{breakpoint_1} function, shows how to |
| 1178 | produce a table. |
| 1179 | |
| 1180 | The original code was: |
| 1181 | |
| 1182 | @smallexample |
| 1183 | if (!found_a_breakpoint++) |
| 1184 | @{ |
| 1185 | annotate_breakpoints_headers (); |
| 1186 | |
| 1187 | annotate_field (0); |
| 1188 | printf_filtered ("Num "); |
| 1189 | annotate_field (1); |
| 1190 | printf_filtered ("Type "); |
| 1191 | annotate_field (2); |
| 1192 | printf_filtered ("Disp "); |
| 1193 | annotate_field (3); |
| 1194 | printf_filtered ("Enb "); |
| 1195 | if (addressprint) |
| 1196 | @{ |
| 1197 | annotate_field (4); |
| 1198 | printf_filtered ("Address "); |
| 1199 | @} |
| 1200 | annotate_field (5); |
| 1201 | printf_filtered ("What\n"); |
| 1202 | |
| 1203 | annotate_breakpoints_table (); |
| 1204 | @} |
| 1205 | @end smallexample |
| 1206 | |
| 1207 | Here's the new version: |
| 1208 | |
| 1209 | @smallexample |
| 1210 | nr_printable_breakpoints = @dots{}; |
| 1211 | |
| 1212 | if (addressprint) |
| 1213 | ui_out_table_begin (ui, 6, nr_printable_breakpoints, "BreakpointTable"); |
| 1214 | else |
| 1215 | ui_out_table_begin (ui, 5, nr_printable_breakpoints, "BreakpointTable"); |
| 1216 | |
| 1217 | if (nr_printable_breakpoints > 0) |
| 1218 | annotate_breakpoints_headers (); |
| 1219 | if (nr_printable_breakpoints > 0) |
| 1220 | annotate_field (0); |
| 1221 | ui_out_table_header (uiout, 3, ui_left, "number", "Num"); /* 1 */ |
| 1222 | if (nr_printable_breakpoints > 0) |
| 1223 | annotate_field (1); |
| 1224 | ui_out_table_header (uiout, 14, ui_left, "type", "Type"); /* 2 */ |
| 1225 | if (nr_printable_breakpoints > 0) |
| 1226 | annotate_field (2); |
| 1227 | ui_out_table_header (uiout, 4, ui_left, "disp", "Disp"); /* 3 */ |
| 1228 | if (nr_printable_breakpoints > 0) |
| 1229 | annotate_field (3); |
| 1230 | ui_out_table_header (uiout, 3, ui_left, "enabled", "Enb"); /* 4 */ |
| 1231 | if (addressprint) |
| 1232 | @{ |
| 1233 | if (nr_printable_breakpoints > 0) |
| 1234 | annotate_field (4); |
| 1235 | if (TARGET_ADDR_BIT <= 32) |
| 1236 | ui_out_table_header (uiout, 10, ui_left, "addr", "Address");/* 5 */ |
| 1237 | else |
| 1238 | ui_out_table_header (uiout, 18, ui_left, "addr", "Address");/* 5 */ |
| 1239 | @} |
| 1240 | if (nr_printable_breakpoints > 0) |
| 1241 | annotate_field (5); |
| 1242 | ui_out_table_header (uiout, 40, ui_noalign, "what", "What"); /* 6 */ |
| 1243 | ui_out_table_body (uiout); |
| 1244 | if (nr_printable_breakpoints > 0) |
| 1245 | annotate_breakpoints_table (); |
| 1246 | @end smallexample |
| 1247 | |
| 1248 | This example, from the @code{print_one_breakpoint} function, shows how |
| 1249 | to produce the actual data for the table whose structure was defined |
| 1250 | in the above example. The original code was: |
| 1251 | |
| 1252 | @smallexample |
| 1253 | annotate_record (); |
| 1254 | annotate_field (0); |
| 1255 | printf_filtered ("%-3d ", b->number); |
| 1256 | annotate_field (1); |
| 1257 | if ((int)b->type > (sizeof(bptypes)/sizeof(bptypes[0])) |
| 1258 | || ((int) b->type != bptypes[(int) b->type].type)) |
| 1259 | internal_error ("bptypes table does not describe type #%d.", |
| 1260 | (int)b->type); |
| 1261 | printf_filtered ("%-14s ", bptypes[(int)b->type].description); |
| 1262 | annotate_field (2); |
| 1263 | printf_filtered ("%-4s ", bpdisps[(int)b->disposition]); |
| 1264 | annotate_field (3); |
| 1265 | printf_filtered ("%-3c ", bpenables[(int)b->enable]); |
| 1266 | @dots{} |
| 1267 | @end smallexample |
| 1268 | |
| 1269 | This is the new version: |
| 1270 | |
| 1271 | @smallexample |
| 1272 | annotate_record (); |
| 1273 | ui_out_tuple_begin (uiout, "bkpt"); |
| 1274 | annotate_field (0); |
| 1275 | ui_out_field_int (uiout, "number", b->number); |
| 1276 | annotate_field (1); |
| 1277 | if (((int) b->type > (sizeof (bptypes) / sizeof (bptypes[0]))) |
| 1278 | || ((int) b->type != bptypes[(int) b->type].type)) |
| 1279 | internal_error ("bptypes table does not describe type #%d.", |
| 1280 | (int) b->type); |
| 1281 | ui_out_field_string (uiout, "type", bptypes[(int)b->type].description); |
| 1282 | annotate_field (2); |
| 1283 | ui_out_field_string (uiout, "disp", bpdisps[(int)b->disposition]); |
| 1284 | annotate_field (3); |
| 1285 | ui_out_field_fmt (uiout, "enabled", "%c", bpenables[(int)b->enable]); |
| 1286 | @dots{} |
| 1287 | @end smallexample |
| 1288 | |
| 1289 | This example, also from @code{print_one_breakpoint}, shows how to |
| 1290 | produce a complicated output field using the @code{print_expression} |
| 1291 | functions which requires a stream to be passed. It also shows how to |
| 1292 | automate stream destruction with cleanups. The original code was: |
| 1293 | |
| 1294 | @smallexample |
| 1295 | annotate_field (5); |
| 1296 | print_expression (b->exp, gdb_stdout); |
| 1297 | @end smallexample |
| 1298 | |
| 1299 | The new version is: |
| 1300 | |
| 1301 | @smallexample |
| 1302 | struct ui_stream *stb = ui_out_stream_new (uiout); |
| 1303 | struct cleanup *old_chain = make_cleanup_ui_out_stream_delete (stb); |
| 1304 | ... |
| 1305 | annotate_field (5); |
| 1306 | print_expression (b->exp, stb->stream); |
| 1307 | ui_out_field_stream (uiout, "what", local_stream); |
| 1308 | @end smallexample |
| 1309 | |
| 1310 | This example, also from @code{print_one_breakpoint}, shows how to use |
| 1311 | @code{ui_out_text} and @code{ui_out_field_string}. The original code |
| 1312 | was: |
| 1313 | |
| 1314 | @smallexample |
| 1315 | annotate_field (5); |
| 1316 | if (b->dll_pathname == NULL) |
| 1317 | printf_filtered ("<any library> "); |
| 1318 | else |
| 1319 | printf_filtered ("library \"%s\" ", b->dll_pathname); |
| 1320 | @end smallexample |
| 1321 | |
| 1322 | It became: |
| 1323 | |
| 1324 | @smallexample |
| 1325 | annotate_field (5); |
| 1326 | if (b->dll_pathname == NULL) |
| 1327 | @{ |
| 1328 | ui_out_field_string (uiout, "what", "<any library>"); |
| 1329 | ui_out_spaces (uiout, 1); |
| 1330 | @} |
| 1331 | else |
| 1332 | @{ |
| 1333 | ui_out_text (uiout, "library \""); |
| 1334 | ui_out_field_string (uiout, "what", b->dll_pathname); |
| 1335 | ui_out_text (uiout, "\" "); |
| 1336 | @} |
| 1337 | @end smallexample |
| 1338 | |
| 1339 | The following example from @code{print_one_breakpoint} shows how to |
| 1340 | use @code{ui_out_field_int} and @code{ui_out_spaces}. The original |
| 1341 | code was: |
| 1342 | |
| 1343 | @smallexample |
| 1344 | annotate_field (5); |
| 1345 | if (b->forked_inferior_pid != 0) |
| 1346 | printf_filtered ("process %d ", b->forked_inferior_pid); |
| 1347 | @end smallexample |
| 1348 | |
| 1349 | It became: |
| 1350 | |
| 1351 | @smallexample |
| 1352 | annotate_field (5); |
| 1353 | if (b->forked_inferior_pid != 0) |
| 1354 | @{ |
| 1355 | ui_out_text (uiout, "process "); |
| 1356 | ui_out_field_int (uiout, "what", b->forked_inferior_pid); |
| 1357 | ui_out_spaces (uiout, 1); |
| 1358 | @} |
| 1359 | @end smallexample |
| 1360 | |
| 1361 | Here's an example of using @code{ui_out_field_string}. The original |
| 1362 | code was: |
| 1363 | |
| 1364 | @smallexample |
| 1365 | annotate_field (5); |
| 1366 | if (b->exec_pathname != NULL) |
| 1367 | printf_filtered ("program \"%s\" ", b->exec_pathname); |
| 1368 | @end smallexample |
| 1369 | |
| 1370 | It became: |
| 1371 | |
| 1372 | @smallexample |
| 1373 | annotate_field (5); |
| 1374 | if (b->exec_pathname != NULL) |
| 1375 | @{ |
| 1376 | ui_out_text (uiout, "program \""); |
| 1377 | ui_out_field_string (uiout, "what", b->exec_pathname); |
| 1378 | ui_out_text (uiout, "\" "); |
| 1379 | @} |
| 1380 | @end smallexample |
| 1381 | |
| 1382 | Finally, here's an example of printing an address. The original code: |
| 1383 | |
| 1384 | @smallexample |
| 1385 | annotate_field (4); |
| 1386 | printf_filtered ("%s ", |
| 1387 | local_hex_string_custom ((unsigned long) b->address, "08l")); |
| 1388 | @end smallexample |
| 1389 | |
| 1390 | It became: |
| 1391 | |
| 1392 | @smallexample |
| 1393 | annotate_field (4); |
| 1394 | ui_out_field_core_addr (uiout, "Address", b->address); |
| 1395 | @end smallexample |
| 1396 | |
| 1397 | |
| 1398 | @section Console Printing |
| 1399 | |
| 1400 | @section TUI |
| 1401 | |
| 1402 | @node libgdb |
| 1403 | |
| 1404 | @chapter libgdb |
| 1405 | |
| 1406 | @section libgdb 1.0 |
| 1407 | @cindex @code{libgdb} |
| 1408 | @code{libgdb} 1.0 was an abortive project of years ago. The theory was |
| 1409 | to provide an API to @value{GDBN}'s functionality. |
| 1410 | |
| 1411 | @section libgdb 2.0 |
| 1412 | @cindex @code{libgdb} |
| 1413 | @code{libgdb} 2.0 is an ongoing effort to update @value{GDBN} so that is |
| 1414 | better able to support graphical and other environments. |
| 1415 | |
| 1416 | Since @code{libgdb} development is on-going, its architecture is still |
| 1417 | evolving. The following components have so far been identified: |
| 1418 | |
| 1419 | @itemize @bullet |
| 1420 | @item |
| 1421 | Observer - @file{gdb-events.h}. |
| 1422 | @item |
| 1423 | Builder - @file{ui-out.h} |
| 1424 | @item |
| 1425 | Event Loop - @file{event-loop.h} |
| 1426 | @item |
| 1427 | Library - @file{gdb.h} |
| 1428 | @end itemize |
| 1429 | |
| 1430 | The model that ties these components together is described below. |
| 1431 | |
| 1432 | @section The @code{libgdb} Model |
| 1433 | |
| 1434 | A client of @code{libgdb} interacts with the library in two ways. |
| 1435 | |
| 1436 | @itemize @bullet |
| 1437 | @item |
| 1438 | As an observer (using @file{gdb-events}) receiving notifications from |
| 1439 | @code{libgdb} of any internal state changes (break point changes, run |
| 1440 | state, etc). |
| 1441 | @item |
| 1442 | As a client querying @code{libgdb} (using the @file{ui-out} builder) to |
| 1443 | obtain various status values from @value{GDBN}. |
| 1444 | @end itemize |
| 1445 | |
| 1446 | Since @code{libgdb} could have multiple clients (e.g. a GUI supporting |
| 1447 | the existing @value{GDBN} CLI), those clients must co-operate when |
| 1448 | controlling @code{libgdb}. In particular, a client must ensure that |
| 1449 | @code{libgdb} is idle (i.e. no other client is using @code{libgdb}) |
| 1450 | before responding to a @file{gdb-event} by making a query. |
| 1451 | |
| 1452 | @section CLI support |
| 1453 | |
| 1454 | At present @value{GDBN}'s CLI is very much entangled in with the core of |
| 1455 | @code{libgdb}. Consequently, a client wishing to include the CLI in |
| 1456 | their interface needs to carefully co-ordinate its own and the CLI's |
| 1457 | requirements. |
| 1458 | |
| 1459 | It is suggested that the client set @code{libgdb} up to be bi-modal |
| 1460 | (alternate between CLI and client query modes). The notes below sketch |
| 1461 | out the theory: |
| 1462 | |
| 1463 | @itemize @bullet |
| 1464 | @item |
| 1465 | The client registers itself as an observer of @code{libgdb}. |
| 1466 | @item |
| 1467 | The client create and install @code{cli-out} builder using its own |
| 1468 | versions of the @code{ui-file} @code{gdb_stderr}, @code{gdb_stdtarg} and |
| 1469 | @code{gdb_stdout} streams. |
| 1470 | @item |
| 1471 | The client creates a separate custom @code{ui-out} builder that is only |
| 1472 | used while making direct queries to @code{libgdb}. |
| 1473 | @end itemize |
| 1474 | |
| 1475 | When the client receives input intended for the CLI, it simply passes it |
| 1476 | along. Since the @code{cli-out} builder is installed by default, all |
| 1477 | the CLI output in response to that command is routed (pronounced rooted) |
| 1478 | through to the client controlled @code{gdb_stdout} et.@: al.@: streams. |
| 1479 | At the same time, the client is kept abreast of internal changes by |
| 1480 | virtue of being a @code{libgdb} observer. |
| 1481 | |
| 1482 | The only restriction on the client is that it must wait until |
| 1483 | @code{libgdb} becomes idle before initiating any queries (using the |
| 1484 | client's custom builder). |
| 1485 | |
| 1486 | @section @code{libgdb} components |
| 1487 | |
| 1488 | @subheading Observer - @file{gdb-events.h} |
| 1489 | @file{gdb-events} provides the client with a very raw mechanism that can |
| 1490 | be used to implement an observer. At present it only allows for one |
| 1491 | observer and that observer must, internally, handle the need to delay |
| 1492 | the processing of any event notifications until after @code{libgdb} has |
| 1493 | finished the current command. |
| 1494 | |
| 1495 | @subheading Builder - @file{ui-out.h} |
| 1496 | @file{ui-out} provides the infrastructure necessary for a client to |
| 1497 | create a builder. That builder is then passed down to @code{libgdb} |
| 1498 | when doing any queries. |
| 1499 | |
| 1500 | @subheading Event Loop - @file{event-loop.h} |
| 1501 | @c There could be an entire section on the event-loop |
| 1502 | @file{event-loop}, currently non-re-entrant, provides a simple event |
| 1503 | loop. A client would need to either plug its self into this loop or, |
| 1504 | implement a new event-loop that GDB would use. |
| 1505 | |
| 1506 | The event-loop will eventually be made re-entrant. This is so that |
| 1507 | @value{GDB} can better handle the problem of some commands blocking |
| 1508 | instead of returning. |
| 1509 | |
| 1510 | @subheading Library - @file{gdb.h} |
| 1511 | @file{libgdb} is the most obvious component of this system. It provides |
| 1512 | the query interface. Each function is parameterized by a @code{ui-out} |
| 1513 | builder. The result of the query is constructed using that builder |
| 1514 | before the query function returns. |
| 1515 | |
| 1516 | @node Symbol Handling |
| 1517 | |
| 1518 | @chapter Symbol Handling |
| 1519 | |
| 1520 | Symbols are a key part of @value{GDBN}'s operation. Symbols include variables, |
| 1521 | functions, and types. |
| 1522 | |
| 1523 | @section Symbol Reading |
| 1524 | |
| 1525 | @cindex symbol reading |
| 1526 | @cindex reading of symbols |
| 1527 | @cindex symbol files |
| 1528 | @value{GDBN} reads symbols from @dfn{symbol files}. The usual symbol |
| 1529 | file is the file containing the program which @value{GDBN} is |
| 1530 | debugging. @value{GDBN} can be directed to use a different file for |
| 1531 | symbols (with the @samp{symbol-file} command), and it can also read |
| 1532 | more symbols via the @samp{add-file} and @samp{load} commands, or while |
| 1533 | reading symbols from shared libraries. |
| 1534 | |
| 1535 | @findex find_sym_fns |
| 1536 | Symbol files are initially opened by code in @file{symfile.c} using |
| 1537 | the BFD library (@pxref{Support Libraries}). BFD identifies the type |
| 1538 | of the file by examining its header. @code{find_sym_fns} then uses |
| 1539 | this identification to locate a set of symbol-reading functions. |
| 1540 | |
| 1541 | @findex add_symtab_fns |
| 1542 | @cindex @code{sym_fns} structure |
| 1543 | @cindex adding a symbol-reading module |
| 1544 | Symbol-reading modules identify themselves to @value{GDBN} by calling |
| 1545 | @code{add_symtab_fns} during their module initialization. The argument |
| 1546 | to @code{add_symtab_fns} is a @code{struct sym_fns} which contains the |
| 1547 | name (or name prefix) of the symbol format, the length of the prefix, |
| 1548 | and pointers to four functions. These functions are called at various |
| 1549 | times to process symbol files whose identification matches the specified |
| 1550 | prefix. |
| 1551 | |
| 1552 | The functions supplied by each module are: |
| 1553 | |
| 1554 | @table @code |
| 1555 | @item @var{xyz}_symfile_init(struct sym_fns *sf) |
| 1556 | |
| 1557 | @cindex secondary symbol file |
| 1558 | Called from @code{symbol_file_add} when we are about to read a new |
| 1559 | symbol file. This function should clean up any internal state (possibly |
| 1560 | resulting from half-read previous files, for example) and prepare to |
| 1561 | read a new symbol file. Note that the symbol file which we are reading |
| 1562 | might be a new ``main'' symbol file, or might be a secondary symbol file |
| 1563 | whose symbols are being added to the existing symbol table. |
| 1564 | |
| 1565 | The argument to @code{@var{xyz}_symfile_init} is a newly allocated |
| 1566 | @code{struct sym_fns} whose @code{bfd} field contains the BFD for the |
| 1567 | new symbol file being read. Its @code{private} field has been zeroed, |
| 1568 | and can be modified as desired. Typically, a struct of private |
| 1569 | information will be @code{malloc}'d, and a pointer to it will be placed |
| 1570 | in the @code{private} field. |
| 1571 | |
| 1572 | There is no result from @code{@var{xyz}_symfile_init}, but it can call |
| 1573 | @code{error} if it detects an unavoidable problem. |
| 1574 | |
| 1575 | @item @var{xyz}_new_init() |
| 1576 | |
| 1577 | Called from @code{symbol_file_add} when discarding existing symbols. |
| 1578 | This function needs only handle the symbol-reading module's internal |
| 1579 | state; the symbol table data structures visible to the rest of |
| 1580 | @value{GDBN} will be discarded by @code{symbol_file_add}. It has no |
| 1581 | arguments and no result. It may be called after |
| 1582 | @code{@var{xyz}_symfile_init}, if a new symbol table is being read, or |
| 1583 | may be called alone if all symbols are simply being discarded. |
| 1584 | |
| 1585 | @item @var{xyz}_symfile_read(struct sym_fns *sf, CORE_ADDR addr, int mainline) |
| 1586 | |
| 1587 | Called from @code{symbol_file_add} to actually read the symbols from a |
| 1588 | symbol-file into a set of psymtabs or symtabs. |
| 1589 | |
| 1590 | @code{sf} points to the @code{struct sym_fns} originally passed to |
| 1591 | @code{@var{xyz}_sym_init} for possible initialization. @code{addr} is |
| 1592 | the offset between the file's specified start address and its true |
| 1593 | address in memory. @code{mainline} is 1 if this is the main symbol |
| 1594 | table being read, and 0 if a secondary symbol file (e.g. shared library |
| 1595 | or dynamically loaded file) is being read.@refill |
| 1596 | @end table |
| 1597 | |
| 1598 | In addition, if a symbol-reading module creates psymtabs when |
| 1599 | @var{xyz}_symfile_read is called, these psymtabs will contain a pointer |
| 1600 | to a function @code{@var{xyz}_psymtab_to_symtab}, which can be called |
| 1601 | from any point in the @value{GDBN} symbol-handling code. |
| 1602 | |
| 1603 | @table @code |
| 1604 | @item @var{xyz}_psymtab_to_symtab (struct partial_symtab *pst) |
| 1605 | |
| 1606 | Called from @code{psymtab_to_symtab} (or the @code{PSYMTAB_TO_SYMTAB} macro) if |
| 1607 | the psymtab has not already been read in and had its @code{pst->symtab} |
| 1608 | pointer set. The argument is the psymtab to be fleshed-out into a |
| 1609 | symtab. Upon return, @code{pst->readin} should have been set to 1, and |
| 1610 | @code{pst->symtab} should contain a pointer to the new corresponding symtab, or |
| 1611 | zero if there were no symbols in that part of the symbol file. |
| 1612 | @end table |
| 1613 | |
| 1614 | @section Partial Symbol Tables |
| 1615 | |
| 1616 | @value{GDBN} has three types of symbol tables: |
| 1617 | |
| 1618 | @itemize @bullet |
| 1619 | @cindex full symbol table |
| 1620 | @cindex symtabs |
| 1621 | @item |
| 1622 | Full symbol tables (@dfn{symtabs}). These contain the main |
| 1623 | information about symbols and addresses. |
| 1624 | |
| 1625 | @cindex psymtabs |
| 1626 | @item |
| 1627 | Partial symbol tables (@dfn{psymtabs}). These contain enough |
| 1628 | information to know when to read the corresponding part of the full |
| 1629 | symbol table. |
| 1630 | |
| 1631 | @cindex minimal symbol table |
| 1632 | @cindex minsymtabs |
| 1633 | @item |
| 1634 | Minimal symbol tables (@dfn{msymtabs}). These contain information |
| 1635 | gleaned from non-debugging symbols. |
| 1636 | @end itemize |
| 1637 | |
| 1638 | @cindex partial symbol table |
| 1639 | This section describes partial symbol tables. |
| 1640 | |
| 1641 | A psymtab is constructed by doing a very quick pass over an executable |
| 1642 | file's debugging information. Small amounts of information are |
| 1643 | extracted---enough to identify which parts of the symbol table will |
| 1644 | need to be re-read and fully digested later, when the user needs the |
| 1645 | information. The speed of this pass causes @value{GDBN} to start up very |
| 1646 | quickly. Later, as the detailed rereading occurs, it occurs in small |
| 1647 | pieces, at various times, and the delay therefrom is mostly invisible to |
| 1648 | the user. |
| 1649 | @c (@xref{Symbol Reading}.) |
| 1650 | |
| 1651 | The symbols that show up in a file's psymtab should be, roughly, those |
| 1652 | visible to the debugger's user when the program is not running code from |
| 1653 | that file. These include external symbols and types, static symbols and |
| 1654 | types, and @code{enum} values declared at file scope. |
| 1655 | |
| 1656 | The psymtab also contains the range of instruction addresses that the |
| 1657 | full symbol table would represent. |
| 1658 | |
| 1659 | @cindex finding a symbol |
| 1660 | @cindex symbol lookup |
| 1661 | The idea is that there are only two ways for the user (or much of the |
| 1662 | code in the debugger) to reference a symbol: |
| 1663 | |
| 1664 | @itemize @bullet |
| 1665 | @findex find_pc_function |
| 1666 | @findex find_pc_line |
| 1667 | @item |
| 1668 | By its address (e.g. execution stops at some address which is inside a |
| 1669 | function in this file). The address will be noticed to be in the |
| 1670 | range of this psymtab, and the full symtab will be read in. |
| 1671 | @code{find_pc_function}, @code{find_pc_line}, and other |
| 1672 | @code{find_pc_@dots{}} functions handle this. |
| 1673 | |
| 1674 | @cindex lookup_symbol |
| 1675 | @item |
| 1676 | By its name |
| 1677 | (e.g. the user asks to print a variable, or set a breakpoint on a |
| 1678 | function). Global names and file-scope names will be found in the |
| 1679 | psymtab, which will cause the symtab to be pulled in. Local names will |
| 1680 | have to be qualified by a global name, or a file-scope name, in which |
| 1681 | case we will have already read in the symtab as we evaluated the |
| 1682 | qualifier. Or, a local symbol can be referenced when we are ``in'' a |
| 1683 | local scope, in which case the first case applies. @code{lookup_symbol} |
| 1684 | does most of the work here. |
| 1685 | @end itemize |
| 1686 | |
| 1687 | The only reason that psymtabs exist is to cause a symtab to be read in |
| 1688 | at the right moment. Any symbol that can be elided from a psymtab, |
| 1689 | while still causing that to happen, should not appear in it. Since |
| 1690 | psymtabs don't have the idea of scope, you can't put local symbols in |
| 1691 | them anyway. Psymtabs don't have the idea of the type of a symbol, |
| 1692 | either, so types need not appear, unless they will be referenced by |
| 1693 | name. |
| 1694 | |
| 1695 | It is a bug for @value{GDBN} to behave one way when only a psymtab has |
| 1696 | been read, and another way if the corresponding symtab has been read |
| 1697 | in. Such bugs are typically caused by a psymtab that does not contain |
| 1698 | all the visible symbols, or which has the wrong instruction address |
| 1699 | ranges. |
| 1700 | |
| 1701 | The psymtab for a particular section of a symbol file (objfile) could be |
| 1702 | thrown away after the symtab has been read in. The symtab should always |
| 1703 | be searched before the psymtab, so the psymtab will never be used (in a |
| 1704 | bug-free environment). Currently, psymtabs are allocated on an obstack, |
| 1705 | and all the psymbols themselves are allocated in a pair of large arrays |
| 1706 | on an obstack, so there is little to be gained by trying to free them |
| 1707 | unless you want to do a lot more work. |
| 1708 | |
| 1709 | @section Types |
| 1710 | |
| 1711 | @unnumberedsubsec Fundamental Types (e.g., @code{FT_VOID}, @code{FT_BOOLEAN}). |
| 1712 | |
| 1713 | @cindex fundamental types |
| 1714 | These are the fundamental types that @value{GDBN} uses internally. Fundamental |
| 1715 | types from the various debugging formats (stabs, ELF, etc) are mapped |
| 1716 | into one of these. They are basically a union of all fundamental types |
| 1717 | that @value{GDBN} knows about for all the languages that @value{GDBN} |
| 1718 | knows about. |
| 1719 | |
| 1720 | @unnumberedsubsec Type Codes (e.g., @code{TYPE_CODE_PTR}, @code{TYPE_CODE_ARRAY}). |
| 1721 | |
| 1722 | @cindex type codes |
| 1723 | Each time @value{GDBN} builds an internal type, it marks it with one |
| 1724 | of these types. The type may be a fundamental type, such as |
| 1725 | @code{TYPE_CODE_INT}, or a derived type, such as @code{TYPE_CODE_PTR} |
| 1726 | which is a pointer to another type. Typically, several @code{FT_*} |
| 1727 | types map to one @code{TYPE_CODE_*} type, and are distinguished by |
| 1728 | other members of the type struct, such as whether the type is signed |
| 1729 | or unsigned, and how many bits it uses. |
| 1730 | |
| 1731 | @unnumberedsubsec Builtin Types (e.g., @code{builtin_type_void}, @code{builtin_type_char}). |
| 1732 | |
| 1733 | These are instances of type structs that roughly correspond to |
| 1734 | fundamental types and are created as global types for @value{GDBN} to |
| 1735 | use for various ugly historical reasons. We eventually want to |
| 1736 | eliminate these. Note for example that @code{builtin_type_int} |
| 1737 | initialized in @file{gdbtypes.c} is basically the same as a |
| 1738 | @code{TYPE_CODE_INT} type that is initialized in @file{c-lang.c} for |
| 1739 | an @code{FT_INTEGER} fundamental type. The difference is that the |
| 1740 | @code{builtin_type} is not associated with any particular objfile, and |
| 1741 | only one instance exists, while @file{c-lang.c} builds as many |
| 1742 | @code{TYPE_CODE_INT} types as needed, with each one associated with |
| 1743 | some particular objfile. |
| 1744 | |
| 1745 | @section Object File Formats |
| 1746 | @cindex object file formats |
| 1747 | |
| 1748 | @subsection a.out |
| 1749 | |
| 1750 | @cindex @code{a.out} format |
| 1751 | The @code{a.out} format is the original file format for Unix. It |
| 1752 | consists of three sections: @code{text}, @code{data}, and @code{bss}, |
| 1753 | which are for program code, initialized data, and uninitialized data, |
| 1754 | respectively. |
| 1755 | |
| 1756 | The @code{a.out} format is so simple that it doesn't have any reserved |
| 1757 | place for debugging information. (Hey, the original Unix hackers used |
| 1758 | @samp{adb}, which is a machine-language debugger!) The only debugging |
| 1759 | format for @code{a.out} is stabs, which is encoded as a set of normal |
| 1760 | symbols with distinctive attributes. |
| 1761 | |
| 1762 | The basic @code{a.out} reader is in @file{dbxread.c}. |
| 1763 | |
| 1764 | @subsection COFF |
| 1765 | |
| 1766 | @cindex COFF format |
| 1767 | The COFF format was introduced with System V Release 3 (SVR3) Unix. |
| 1768 | COFF files may have multiple sections, each prefixed by a header. The |
| 1769 | number of sections is limited. |
| 1770 | |
| 1771 | The COFF specification includes support for debugging. Although this |
| 1772 | was a step forward, the debugging information was woefully limited. For |
| 1773 | instance, it was not possible to represent code that came from an |
| 1774 | included file. |
| 1775 | |
| 1776 | The COFF reader is in @file{coffread.c}. |
| 1777 | |
| 1778 | @subsection ECOFF |
| 1779 | |
| 1780 | @cindex ECOFF format |
| 1781 | ECOFF is an extended COFF originally introduced for Mips and Alpha |
| 1782 | workstations. |
| 1783 | |
| 1784 | The basic ECOFF reader is in @file{mipsread.c}. |
| 1785 | |
| 1786 | @subsection XCOFF |
| 1787 | |
| 1788 | @cindex XCOFF format |
| 1789 | The IBM RS/6000 running AIX uses an object file format called XCOFF. |
| 1790 | The COFF sections, symbols, and line numbers are used, but debugging |
| 1791 | symbols are @code{dbx}-style stabs whose strings are located in the |
| 1792 | @code{.debug} section (rather than the string table). For more |
| 1793 | information, see @ref{Top,,,stabs,The Stabs Debugging Format}. |
| 1794 | |
| 1795 | The shared library scheme has a clean interface for figuring out what |
| 1796 | shared libraries are in use, but the catch is that everything which |
| 1797 | refers to addresses (symbol tables and breakpoints at least) needs to be |
| 1798 | relocated for both shared libraries and the main executable. At least |
| 1799 | using the standard mechanism this can only be done once the program has |
| 1800 | been run (or the core file has been read). |
| 1801 | |
| 1802 | @subsection PE |
| 1803 | |
| 1804 | @cindex PE-COFF format |
| 1805 | Windows 95 and NT use the PE (@dfn{Portable Executable}) format for their |
| 1806 | executables. PE is basically COFF with additional headers. |
| 1807 | |
| 1808 | While BFD includes special PE support, @value{GDBN} needs only the basic |
| 1809 | COFF reader. |
| 1810 | |
| 1811 | @subsection ELF |
| 1812 | |
| 1813 | @cindex ELF format |
| 1814 | The ELF format came with System V Release 4 (SVR4) Unix. ELF is similar |
| 1815 | to COFF in being organized into a number of sections, but it removes |
| 1816 | many of COFF's limitations. |
| 1817 | |
| 1818 | The basic ELF reader is in @file{elfread.c}. |
| 1819 | |
| 1820 | @subsection SOM |
| 1821 | |
| 1822 | @cindex SOM format |
| 1823 | SOM is HP's object file and debug format (not to be confused with IBM's |
| 1824 | SOM, which is a cross-language ABI). |
| 1825 | |
| 1826 | The SOM reader is in @file{hpread.c}. |
| 1827 | |
| 1828 | @subsection Other File Formats |
| 1829 | |
| 1830 | @cindex Netware Loadable Module format |
| 1831 | Other file formats that have been supported by @value{GDBN} include Netware |
| 1832 | Loadable Modules (@file{nlmread.c}). |
| 1833 | |
| 1834 | @section Debugging File Formats |
| 1835 | |
| 1836 | This section describes characteristics of debugging information that |
| 1837 | are independent of the object file format. |
| 1838 | |
| 1839 | @subsection stabs |
| 1840 | |
| 1841 | @cindex stabs debugging info |
| 1842 | @code{stabs} started out as special symbols within the @code{a.out} |
| 1843 | format. Since then, it has been encapsulated into other file |
| 1844 | formats, such as COFF and ELF. |
| 1845 | |
| 1846 | While @file{dbxread.c} does some of the basic stab processing, |
| 1847 | including for encapsulated versions, @file{stabsread.c} does |
| 1848 | the real work. |
| 1849 | |
| 1850 | @subsection COFF |
| 1851 | |
| 1852 | @cindex COFF debugging info |
| 1853 | The basic COFF definition includes debugging information. The level |
| 1854 | of support is minimal and non-extensible, and is not often used. |
| 1855 | |
| 1856 | @subsection Mips debug (Third Eye) |
| 1857 | |
| 1858 | @cindex ECOFF debugging info |
| 1859 | ECOFF includes a definition of a special debug format. |
| 1860 | |
| 1861 | The file @file{mdebugread.c} implements reading for this format. |
| 1862 | |
| 1863 | @subsection DWARF 1 |
| 1864 | |
| 1865 | @cindex DWARF 1 debugging info |
| 1866 | DWARF 1 is a debugging format that was originally designed to be |
| 1867 | used with ELF in SVR4 systems. |
| 1868 | |
| 1869 | @c GCC_PRODUCER |
| 1870 | @c GPLUS_PRODUCER |
| 1871 | @c LCC_PRODUCER |
| 1872 | @c If defined, these are the producer strings in a DWARF 1 file. All of |
| 1873 | @c these have reasonable defaults already. |
| 1874 | |
| 1875 | The DWARF 1 reader is in @file{dwarfread.c}. |
| 1876 | |
| 1877 | @subsection DWARF 2 |
| 1878 | |
| 1879 | @cindex DWARF 2 debugging info |
| 1880 | DWARF 2 is an improved but incompatible version of DWARF 1. |
| 1881 | |
| 1882 | The DWARF 2 reader is in @file{dwarf2read.c}. |
| 1883 | |
| 1884 | @subsection SOM |
| 1885 | |
| 1886 | @cindex SOM debugging info |
| 1887 | Like COFF, the SOM definition includes debugging information. |
| 1888 | |
| 1889 | @section Adding a New Symbol Reader to @value{GDBN} |
| 1890 | |
| 1891 | @cindex adding debugging info reader |
| 1892 | If you are using an existing object file format (@code{a.out}, COFF, ELF, etc), |
| 1893 | there is probably little to be done. |
| 1894 | |
| 1895 | If you need to add a new object file format, you must first add it to |
| 1896 | BFD. This is beyond the scope of this document. |
| 1897 | |
| 1898 | You must then arrange for the BFD code to provide access to the |
| 1899 | debugging symbols. Generally @value{GDBN} will have to call swapping routines |
| 1900 | from BFD and a few other BFD internal routines to locate the debugging |
| 1901 | information. As much as possible, @value{GDBN} should not depend on the BFD |
| 1902 | internal data structures. |
| 1903 | |
| 1904 | For some targets (e.g., COFF), there is a special transfer vector used |
| 1905 | to call swapping routines, since the external data structures on various |
| 1906 | platforms have different sizes and layouts. Specialized routines that |
| 1907 | will only ever be implemented by one object file format may be called |
| 1908 | directly. This interface should be described in a file |
| 1909 | @file{bfd/lib@var{xyz}.h}, which is included by @value{GDBN}. |
| 1910 | |
| 1911 | |
| 1912 | @node Language Support |
| 1913 | |
| 1914 | @chapter Language Support |
| 1915 | |
| 1916 | @cindex language support |
| 1917 | @value{GDBN}'s language support is mainly driven by the symbol reader, |
| 1918 | although it is possible for the user to set the source language |
| 1919 | manually. |
| 1920 | |
| 1921 | @value{GDBN} chooses the source language by looking at the extension |
| 1922 | of the file recorded in the debug info; @file{.c} means C, @file{.f} |
| 1923 | means Fortran, etc. It may also use a special-purpose language |
| 1924 | identifier if the debug format supports it, like with DWARF. |
| 1925 | |
| 1926 | @section Adding a Source Language to @value{GDBN} |
| 1927 | |
| 1928 | @cindex adding source language |
| 1929 | To add other languages to @value{GDBN}'s expression parser, follow the |
| 1930 | following steps: |
| 1931 | |
| 1932 | @table @emph |
| 1933 | @item Create the expression parser. |
| 1934 | |
| 1935 | @cindex expression parser |
| 1936 | This should reside in a file @file{@var{lang}-exp.y}. Routines for |
| 1937 | building parsed expressions into a @code{union exp_element} list are in |
| 1938 | @file{parse.c}. |
| 1939 | |
| 1940 | @cindex language parser |
| 1941 | Since we can't depend upon everyone having Bison, and YACC produces |
| 1942 | parsers that define a bunch of global names, the following lines |
| 1943 | @strong{must} be included at the top of the YACC parser, to prevent the |
| 1944 | various parsers from defining the same global names: |
| 1945 | |
| 1946 | @smallexample |
| 1947 | #define yyparse @var{lang}_parse |
| 1948 | #define yylex @var{lang}_lex |
| 1949 | #define yyerror @var{lang}_error |
| 1950 | #define yylval @var{lang}_lval |
| 1951 | #define yychar @var{lang}_char |
| 1952 | #define yydebug @var{lang}_debug |
| 1953 | #define yypact @var{lang}_pact |
| 1954 | #define yyr1 @var{lang}_r1 |
| 1955 | #define yyr2 @var{lang}_r2 |
| 1956 | #define yydef @var{lang}_def |
| 1957 | #define yychk @var{lang}_chk |
| 1958 | #define yypgo @var{lang}_pgo |
| 1959 | #define yyact @var{lang}_act |
| 1960 | #define yyexca @var{lang}_exca |
| 1961 | #define yyerrflag @var{lang}_errflag |
| 1962 | #define yynerrs @var{lang}_nerrs |
| 1963 | @end smallexample |
| 1964 | |
| 1965 | At the bottom of your parser, define a @code{struct language_defn} and |
| 1966 | initialize it with the right values for your language. Define an |
| 1967 | @code{initialize_@var{lang}} routine and have it call |
| 1968 | @samp{add_language(@var{lang}_language_defn)} to tell the rest of @value{GDBN} |
| 1969 | that your language exists. You'll need some other supporting variables |
| 1970 | and functions, which will be used via pointers from your |
| 1971 | @code{@var{lang}_language_defn}. See the declaration of @code{struct |
| 1972 | language_defn} in @file{language.h}, and the other @file{*-exp.y} files, |
| 1973 | for more information. |
| 1974 | |
| 1975 | @item Add any evaluation routines, if necessary |
| 1976 | |
| 1977 | @cindex expression evaluation routines |
| 1978 | @findex evaluate_subexp |
| 1979 | @findex prefixify_subexp |
| 1980 | @findex length_of_subexp |
| 1981 | If you need new opcodes (that represent the operations of the language), |
| 1982 | add them to the enumerated type in @file{expression.h}. Add support |
| 1983 | code for these operations in the @code{evaluate_subexp} function |
| 1984 | defined in the file @file{eval.c}. Add cases |
| 1985 | for new opcodes in two functions from @file{parse.c}: |
| 1986 | @code{prefixify_subexp} and @code{length_of_subexp}. These compute |
| 1987 | the number of @code{exp_element}s that a given operation takes up. |
| 1988 | |
| 1989 | @item Update some existing code |
| 1990 | |
| 1991 | Add an enumerated identifier for your language to the enumerated type |
| 1992 | @code{enum language} in @file{defs.h}. |
| 1993 | |
| 1994 | Update the routines in @file{language.c} so your language is included. |
| 1995 | These routines include type predicates and such, which (in some cases) |
| 1996 | are language dependent. If your language does not appear in the switch |
| 1997 | statement, an error is reported. |
| 1998 | |
| 1999 | @vindex current_language |
| 2000 | Also included in @file{language.c} is the code that updates the variable |
| 2001 | @code{current_language}, and the routines that translate the |
| 2002 | @code{language_@var{lang}} enumerated identifier into a printable |
| 2003 | string. |
| 2004 | |
| 2005 | @findex _initialize_language |
| 2006 | Update the function @code{_initialize_language} to include your |
| 2007 | language. This function picks the default language upon startup, so is |
| 2008 | dependent upon which languages that @value{GDBN} is built for. |
| 2009 | |
| 2010 | @findex allocate_symtab |
| 2011 | Update @code{allocate_symtab} in @file{symfile.c} and/or symbol-reading |
| 2012 | code so that the language of each symtab (source file) is set properly. |
| 2013 | This is used to determine the language to use at each stack frame level. |
| 2014 | Currently, the language is set based upon the extension of the source |
| 2015 | file. If the language can be better inferred from the symbol |
| 2016 | information, please set the language of the symtab in the symbol-reading |
| 2017 | code. |
| 2018 | |
| 2019 | @findex print_subexp |
| 2020 | @findex op_print_tab |
| 2021 | Add helper code to @code{print_subexp} (in @file{expprint.c}) to handle any new |
| 2022 | expression opcodes you have added to @file{expression.h}. Also, add the |
| 2023 | printed representations of your operators to @code{op_print_tab}. |
| 2024 | |
| 2025 | @item Add a place of call |
| 2026 | |
| 2027 | @findex parse_exp_1 |
| 2028 | Add a call to @code{@var{lang}_parse()} and @code{@var{lang}_error} in |
| 2029 | @code{parse_exp_1} (defined in @file{parse.c}). |
| 2030 | |
| 2031 | @item Use macros to trim code |
| 2032 | |
| 2033 | @cindex trimming language-dependent code |
| 2034 | The user has the option of building @value{GDBN} for some or all of the |
| 2035 | languages. If the user decides to build @value{GDBN} for the language |
| 2036 | @var{lang}, then every file dependent on @file{language.h} will have the |
| 2037 | macro @code{_LANG_@var{lang}} defined in it. Use @code{#ifdef}s to |
| 2038 | leave out large routines that the user won't need if he or she is not |
| 2039 | using your language. |
| 2040 | |
| 2041 | Note that you do not need to do this in your YACC parser, since if @value{GDBN} |
| 2042 | is not build for @var{lang}, then @file{@var{lang}-exp.tab.o} (the |
| 2043 | compiled form of your parser) is not linked into @value{GDBN} at all. |
| 2044 | |
| 2045 | See the file @file{configure.in} for how @value{GDBN} is configured |
| 2046 | for different languages. |
| 2047 | |
| 2048 | @item Edit @file{Makefile.in} |
| 2049 | |
| 2050 | Add dependencies in @file{Makefile.in}. Make sure you update the macro |
| 2051 | variables such as @code{HFILES} and @code{OBJS}, otherwise your code may |
| 2052 | not get linked in, or, worse yet, it may not get @code{tar}red into the |
| 2053 | distribution! |
| 2054 | @end table |
| 2055 | |
| 2056 | |
| 2057 | @node Host Definition |
| 2058 | |
| 2059 | @chapter Host Definition |
| 2060 | |
| 2061 | With the advent of Autoconf, it's rarely necessary to have host |
| 2062 | definition machinery anymore. The following information is provided, |
| 2063 | mainly, as an historical reference. |
| 2064 | |
| 2065 | @section Adding a New Host |
| 2066 | |
| 2067 | @cindex adding a new host |
| 2068 | @cindex host, adding |
| 2069 | @value{GDBN}'s host configuration support normally happens via Autoconf. |
| 2070 | New host-specific definitions should not be needed. Older hosts |
| 2071 | @value{GDBN} still use the host-specific definitions and files listed |
| 2072 | below, but these mostly exist for historical reasons, and will |
| 2073 | eventually disappear. |
| 2074 | |
| 2075 | @table @file |
| 2076 | @item gdb/config/@var{arch}/@var{xyz}.mh |
| 2077 | This file once contained both host and native configuration information |
| 2078 | (@pxref{Native Debugging}) for the machine @var{xyz}. The host |
| 2079 | configuration information is now handed by Autoconf. |
| 2080 | |
| 2081 | Host configuration information included a definition of |
| 2082 | @code{XM_FILE=xm-@var{xyz}.h} and possibly definitions for @code{CC}, |
| 2083 | @code{SYSV_DEFINE}, @code{XM_CFLAGS}, @code{XM_ADD_FILES}, |
| 2084 | @code{XM_CLIBS}, @code{XM_CDEPS}, etc.; see @file{Makefile.in}. |
| 2085 | |
| 2086 | New host only configurations do not need this file. |
| 2087 | |
| 2088 | @item gdb/config/@var{arch}/xm-@var{xyz}.h |
| 2089 | This file once contained definitions and includes required when hosting |
| 2090 | gdb on machine @var{xyz}. Those definitions and includes are now |
| 2091 | handled by Autoconf. |
| 2092 | |
| 2093 | New host and native configurations do not need this file. |
| 2094 | |
| 2095 | @emph{Maintainer's note: Some hosts continue to use the @file{xm-xyz.h} |
| 2096 | file to define the macros @var{HOST_FLOAT_FORMAT}, |
| 2097 | @var{HOST_DOUBLE_FORMAT} and @var{HOST_LONG_DOUBLE_FORMAT}. That code |
| 2098 | also needs to be replaced with either an Autoconf or run-time test.} |
| 2099 | |
| 2100 | @end table |
| 2101 | |
| 2102 | @subheading Generic Host Support Files |
| 2103 | |
| 2104 | @cindex generic host support |
| 2105 | There are some ``generic'' versions of routines that can be used by |
| 2106 | various systems. These can be customized in various ways by macros |
| 2107 | defined in your @file{xm-@var{xyz}.h} file. If these routines work for |
| 2108 | the @var{xyz} host, you can just include the generic file's name (with |
| 2109 | @samp{.o}, not @samp{.c}) in @code{XDEPFILES}. |
| 2110 | |
| 2111 | Otherwise, if your machine needs custom support routines, you will need |
| 2112 | to write routines that perform the same functions as the generic file. |
| 2113 | Put them into @code{@var{xyz}-xdep.c}, and put @code{@var{xyz}-xdep.o} |
| 2114 | into @code{XDEPFILES}. |
| 2115 | |
| 2116 | @table @file |
| 2117 | @cindex remote debugging support |
| 2118 | @cindex serial line support |
| 2119 | @item ser-unix.c |
| 2120 | This contains serial line support for Unix systems. This is always |
| 2121 | included, via the makefile variable @code{SER_HARDWIRE}; override this |
| 2122 | variable in the @file{.mh} file to avoid it. |
| 2123 | |
| 2124 | @item ser-go32.c |
| 2125 | This contains serial line support for 32-bit programs running under DOS, |
| 2126 | using the DJGPP (a.k.a.@: GO32) execution environment. |
| 2127 | |
| 2128 | @cindex TCP remote support |
| 2129 | @item ser-tcp.c |
| 2130 | This contains generic TCP support using sockets. |
| 2131 | @end table |
| 2132 | |
| 2133 | @section Host Conditionals |
| 2134 | |
| 2135 | When @value{GDBN} is configured and compiled, various macros are |
| 2136 | defined or left undefined, to control compilation based on the |
| 2137 | attributes of the host system. These macros and their meanings (or if |
| 2138 | the meaning is not documented here, then one of the source files where |
| 2139 | they are used is indicated) are: |
| 2140 | |
| 2141 | @ftable @code |
| 2142 | @item @value{GDBN}INIT_FILENAME |
| 2143 | The default name of @value{GDBN}'s initialization file (normally |
| 2144 | @file{.gdbinit}). |
| 2145 | |
| 2146 | @item NO_STD_REGS |
| 2147 | This macro is deprecated. |
| 2148 | |
| 2149 | @item NO_SYS_FILE |
| 2150 | Define this if your system does not have a @code{<sys/file.h>}. |
| 2151 | |
| 2152 | @item SIGWINCH_HANDLER |
| 2153 | If your host defines @code{SIGWINCH}, you can define this to be the name |
| 2154 | of a function to be called if @code{SIGWINCH} is received. |
| 2155 | |
| 2156 | @item SIGWINCH_HANDLER_BODY |
| 2157 | Define this to expand into code that will define the function named by |
| 2158 | the expansion of @code{SIGWINCH_HANDLER}. |
| 2159 | |
| 2160 | @item ALIGN_STACK_ON_STARTUP |
| 2161 | @cindex stack alignment |
| 2162 | Define this if your system is of a sort that will crash in |
| 2163 | @code{tgetent} if the stack happens not to be longword-aligned when |
| 2164 | @code{main} is called. This is a rare situation, but is known to occur |
| 2165 | on several different types of systems. |
| 2166 | |
| 2167 | @item CRLF_SOURCE_FILES |
| 2168 | @cindex DOS text files |
| 2169 | Define this if host files use @code{\r\n} rather than @code{\n} as a |
| 2170 | line terminator. This will cause source file listings to omit @code{\r} |
| 2171 | characters when printing and it will allow @code{\r\n} line endings of files |
| 2172 | which are ``sourced'' by gdb. It must be possible to open files in binary |
| 2173 | mode using @code{O_BINARY} or, for fopen, @code{"rb"}. |
| 2174 | |
| 2175 | @item DEFAULT_PROMPT |
| 2176 | @cindex prompt |
| 2177 | The default value of the prompt string (normally @code{"(gdb) "}). |
| 2178 | |
| 2179 | @item DEV_TTY |
| 2180 | @cindex terminal device |
| 2181 | The name of the generic TTY device, defaults to @code{"/dev/tty"}. |
| 2182 | |
| 2183 | @item FCLOSE_PROVIDED |
| 2184 | Define this if the system declares @code{fclose} in the headers included |
| 2185 | in @code{defs.h}. This isn't needed unless your compiler is unusually |
| 2186 | anal. |
| 2187 | |
| 2188 | @item FOPEN_RB |
| 2189 | Define this if binary files are opened the same way as text files. |
| 2190 | |
| 2191 | @item GETENV_PROVIDED |
| 2192 | Define this if the system declares @code{getenv} in its headers included |
| 2193 | in @code{defs.h}. This isn't needed unless your compiler is unusually |
| 2194 | anal. |
| 2195 | |
| 2196 | @item HAVE_MMAP |
| 2197 | @findex mmap |
| 2198 | In some cases, use the system call @code{mmap} for reading symbol |
| 2199 | tables. For some machines this allows for sharing and quick updates. |
| 2200 | |
| 2201 | @item HAVE_TERMIO |
| 2202 | Define this if the host system has @code{termio.h}. |
| 2203 | |
| 2204 | @item INT_MAX |
| 2205 | @itemx INT_MIN |
| 2206 | @itemx LONG_MAX |
| 2207 | @itemx UINT_MAX |
| 2208 | @itemx ULONG_MAX |
| 2209 | Values for host-side constants. |
| 2210 | |
| 2211 | @item ISATTY |
| 2212 | Substitute for isatty, if not available. |
| 2213 | |
| 2214 | @item LONGEST |
| 2215 | This is the longest integer type available on the host. If not defined, |
| 2216 | it will default to @code{long long} or @code{long}, depending on |
| 2217 | @code{CC_HAS_LONG_LONG}. |
| 2218 | |
| 2219 | @item CC_HAS_LONG_LONG |
| 2220 | @cindex @code{long long} data type |
| 2221 | Define this if the host C compiler supports @code{long long}. This is set |
| 2222 | by the @code{configure} script. |
| 2223 | |
| 2224 | @item PRINTF_HAS_LONG_LONG |
| 2225 | Define this if the host can handle printing of long long integers via |
| 2226 | the printf format conversion specifier @code{ll}. This is set by the |
| 2227 | @code{configure} script. |
| 2228 | |
| 2229 | @item HAVE_LONG_DOUBLE |
| 2230 | Define this if the host C compiler supports @code{long double}. This is |
| 2231 | set by the @code{configure} script. |
| 2232 | |
| 2233 | @item PRINTF_HAS_LONG_DOUBLE |
| 2234 | Define this if the host can handle printing of long double float-point |
| 2235 | numbers via the printf format conversion specifier @code{Lg}. This is |
| 2236 | set by the @code{configure} script. |
| 2237 | |
| 2238 | @item SCANF_HAS_LONG_DOUBLE |
| 2239 | Define this if the host can handle the parsing of long double |
| 2240 | float-point numbers via the scanf format conversion specifier |
| 2241 | @code{Lg}. This is set by the @code{configure} script. |
| 2242 | |
| 2243 | @item LSEEK_NOT_LINEAR |
| 2244 | Define this if @code{lseek (n)} does not necessarily move to byte number |
| 2245 | @code{n} in the file. This is only used when reading source files. It |
| 2246 | is normally faster to define @code{CRLF_SOURCE_FILES} when possible. |
| 2247 | |
| 2248 | @item L_SET |
| 2249 | This macro is used as the argument to @code{lseek} (or, most commonly, |
| 2250 | @code{bfd_seek}). FIXME, should be replaced by SEEK_SET instead, |
| 2251 | which is the POSIX equivalent. |
| 2252 | |
| 2253 | @item MMAP_BASE_ADDRESS |
| 2254 | When using HAVE_MMAP, the first mapping should go at this address. |
| 2255 | |
| 2256 | @item MMAP_INCREMENT |
| 2257 | when using HAVE_MMAP, this is the increment between mappings. |
| 2258 | |
| 2259 | @item NORETURN |
| 2260 | If defined, this should be one or more tokens, such as @code{volatile}, |
| 2261 | that can be used in both the declaration and definition of functions to |
| 2262 | indicate that they never return. The default is already set correctly |
| 2263 | if compiling with GCC. This will almost never need to be defined. |
| 2264 | |
| 2265 | @item ATTR_NORETURN |
| 2266 | If defined, this should be one or more tokens, such as |
| 2267 | @code{__attribute__ ((noreturn))}, that can be used in the declarations |
| 2268 | of functions to indicate that they never return. The default is already |
| 2269 | set correctly if compiling with GCC. This will almost never need to be |
| 2270 | defined. |
| 2271 | |
| 2272 | @item USE_MMALLOC |
| 2273 | @findex mmalloc |
| 2274 | @value{GDBN} will use the @code{mmalloc} library for memory allocation |
| 2275 | for symbol reading if this symbol is defined. Be careful defining it |
| 2276 | since there are systems on which @code{mmalloc} does not work for some |
| 2277 | reason. One example is the DECstation, where its RPC library can't |
| 2278 | cope with our redefinition of @code{malloc} to call @code{mmalloc}. |
| 2279 | When defining @code{USE_MMALLOC}, you will also have to set |
| 2280 | @code{MMALLOC} in the Makefile, to point to the @code{mmalloc} library. This |
| 2281 | define is set when you configure with @samp{--with-mmalloc}. |
| 2282 | |
| 2283 | @item NO_MMCHECK |
| 2284 | @findex mmcheck |
| 2285 | Define this if you are using @code{mmalloc}, but don't want the overhead |
| 2286 | of checking the heap with @code{mmcheck}. Note that on some systems, |
| 2287 | the C runtime makes calls to @code{malloc} prior to calling @code{main}, and if |
| 2288 | @code{free} is ever called with these pointers after calling |
| 2289 | @code{mmcheck} to enable checking, a memory corruption abort is certain |
| 2290 | to occur. These systems can still use @code{mmalloc}, but must define |
| 2291 | @code{NO_MMCHECK}. |
| 2292 | |
| 2293 | @item MMCHECK_FORCE |
| 2294 | Define this to 1 if the C runtime allocates memory prior to |
| 2295 | @code{mmcheck} being called, but that memory is never freed so we don't |
| 2296 | have to worry about it triggering a memory corruption abort. The |
| 2297 | default is 0, which means that @code{mmcheck} will only install the heap |
| 2298 | checking functions if there has not yet been any memory allocation |
| 2299 | calls, and if it fails to install the functions, @value{GDBN} will issue a |
| 2300 | warning. This is currently defined if you configure using |
| 2301 | @samp{--with-mmalloc}. |
| 2302 | |
| 2303 | @item NO_SIGINTERRUPT |
| 2304 | @findex siginterrupt |
| 2305 | Define this to indicate that @code{siginterrupt} is not available. |
| 2306 | |
| 2307 | @item SEEK_CUR |
| 2308 | @itemx SEEK_SET |
| 2309 | Define these to appropriate value for the system @code{lseek}, if not already |
| 2310 | defined. |
| 2311 | |
| 2312 | @item STOP_SIGNAL |
| 2313 | This is the signal for stopping @value{GDBN}. Defaults to |
| 2314 | @code{SIGTSTP}. (Only redefined for the Convex.) |
| 2315 | |
| 2316 | @item USE_O_NOCTTY |
| 2317 | Define this if the interior's tty should be opened with the @code{O_NOCTTY} |
| 2318 | flag. (FIXME: This should be a native-only flag, but @file{inflow.c} is |
| 2319 | always linked in.) |
| 2320 | |
| 2321 | @item USG |
| 2322 | Means that System V (prior to SVR4) include files are in use. (FIXME: |
| 2323 | This symbol is abused in @file{infrun.c}, @file{regex.c}, and |
| 2324 | @file{utils.c} for other things, at the moment.) |
| 2325 | |
| 2326 | @item lint |
| 2327 | Define this to help placate @code{lint} in some situations. |
| 2328 | |
| 2329 | @item volatile |
| 2330 | Define this to override the defaults of @code{__volatile__} or |
| 2331 | @code{/**/}. |
| 2332 | @end ftable |
| 2333 | |
| 2334 | |
| 2335 | @node Target Architecture Definition |
| 2336 | |
| 2337 | @chapter Target Architecture Definition |
| 2338 | |
| 2339 | @cindex target architecture definition |
| 2340 | @value{GDBN}'s target architecture defines what sort of |
| 2341 | machine-language programs @value{GDBN} can work with, and how it works |
| 2342 | with them. |
| 2343 | |
| 2344 | The target architecture object is implemented as the C structure |
| 2345 | @code{struct gdbarch *}. The structure, and its methods, are generated |
| 2346 | using the Bourne shell script @file{gdbarch.sh}. |
| 2347 | |
| 2348 | @section Operating System ABI Variant Handling |
| 2349 | @cindex OS ABI variants |
| 2350 | |
| 2351 | @value{GDBN} provides a mechanism for handling variations in OS |
| 2352 | ABIs. An OS ABI variant may have influence over any number of |
| 2353 | variables in the target architecture definition. There are two major |
| 2354 | components in the OS ABI mechanism: sniffers and handlers. |
| 2355 | |
| 2356 | A @dfn{sniffer} examines a file matching a BFD architecture/flavour pair |
| 2357 | (the architecture may be wildcarded) in an attempt to determine the |
| 2358 | OS ABI of that file. Sniffers with a wildcarded architecture are considered |
| 2359 | to be @dfn{generic}, while sniffers for a specific architecture are |
| 2360 | considered to be @dfn{specific}. A match from a specific sniffer |
| 2361 | overrides a match from a generic sniffer. Multiple sniffers for an |
| 2362 | architecture/flavour may exist, in order to differentiate between two |
| 2363 | different operating systems which use the same basic file format. The |
| 2364 | OS ABI framework provides a generic sniffer for ELF-format files which |
| 2365 | examines the @code{EI_OSABI} field of the ELF header, as well as note |
| 2366 | sections known to be used by several operating systems. |
| 2367 | |
| 2368 | @cindex fine-tuning @code{gdbarch} structure |
| 2369 | A @dfn{handler} is used to fine-tune the @code{gdbarch} structure for the |
| 2370 | selected OS ABI. There may be only one handler for a given OS ABI |
| 2371 | for each BFD architecture. |
| 2372 | |
| 2373 | The following OS ABI variants are defined in @file{osabi.h}: |
| 2374 | |
| 2375 | @table @code |
| 2376 | |
| 2377 | @findex GDB_OSABI_UNKNOWN |
| 2378 | @item GDB_OSABI_UNKNOWN |
| 2379 | The ABI of the inferior is unknown. The default @code{gdbarch} |
| 2380 | settings for the architecture will be used. |
| 2381 | |
| 2382 | @findex GDB_OSABI_SVR4 |
| 2383 | @item GDB_OSABI_SVR4 |
| 2384 | UNIX System V Release 4 |
| 2385 | |
| 2386 | @findex GDB_OSABI_HURD |
| 2387 | @item GDB_OSABI_HURD |
| 2388 | GNU using the Hurd kernel |
| 2389 | |
| 2390 | @findex GDB_OSABI_SOLARIS |
| 2391 | @item GDB_OSABI_SOLARIS |
| 2392 | Sun Solaris |
| 2393 | |
| 2394 | @findex GDB_OSABI_OSF1 |
| 2395 | @item GDB_OSABI_OSF1 |
| 2396 | OSF/1, including Digital UNIX and Compaq Tru64 UNIX |
| 2397 | |
| 2398 | @findex GDB_OSABI_LINUX |
| 2399 | @item GDB_OSABI_LINUX |
| 2400 | GNU using the Linux kernel |
| 2401 | |
| 2402 | @findex GDB_OSABI_FREEBSD_AOUT |
| 2403 | @item GDB_OSABI_FREEBSD_AOUT |
| 2404 | FreeBSD using the a.out executable format |
| 2405 | |
| 2406 | @findex GDB_OSABI_FREEBSD_ELF |
| 2407 | @item GDB_OSABI_FREEBSD_ELF |
| 2408 | FreeBSD using the ELF executable format |
| 2409 | |
| 2410 | @findex GDB_OSABI_NETBSD_AOUT |
| 2411 | @item GDB_OSABI_NETBSD_AOUT |
| 2412 | NetBSD using the a.out executable format |
| 2413 | |
| 2414 | @findex GDB_OSABI_NETBSD_ELF |
| 2415 | @item GDB_OSABI_NETBSD_ELF |
| 2416 | NetBSD using the ELF executable format |
| 2417 | |
| 2418 | @findex GDB_OSABI_WINCE |
| 2419 | @item GDB_OSABI_WINCE |
| 2420 | Windows CE |
| 2421 | |
| 2422 | @findex GDB_OSABI_GO32 |
| 2423 | @item GDB_OSABI_GO32 |
| 2424 | DJGPP |
| 2425 | |
| 2426 | @findex GDB_OSABI_NETWARE |
| 2427 | @item GDB_OSABI_NETWARE |
| 2428 | Novell NetWare |
| 2429 | |
| 2430 | @findex GDB_OSABI_ARM_EABI_V1 |
| 2431 | @item GDB_OSABI_ARM_EABI_V1 |
| 2432 | ARM Embedded ABI version 1 |
| 2433 | |
| 2434 | @findex GDB_OSABI_ARM_EABI_V2 |
| 2435 | @item GDB_OSABI_ARM_EABI_V2 |
| 2436 | ARM Embedded ABI version 2 |
| 2437 | |
| 2438 | @findex GDB_OSABI_ARM_APCS |
| 2439 | @item GDB_OSABI_ARM_APCS |
| 2440 | Generic ARM Procedure Call Standard |
| 2441 | |
| 2442 | @end table |
| 2443 | |
| 2444 | Here are the functions that make up the OS ABI framework: |
| 2445 | |
| 2446 | @deftypefun const char *gdbarch_osabi_name (enum gdb_osabi @var{osabi}) |
| 2447 | Return the name of the OS ABI corresponding to @var{osabi}. |
| 2448 | @end deftypefun |
| 2449 | |
| 2450 | @deftypefun void gdbarch_register_osabi (enum bfd_architecture @var{arch}, unsigned long @var{machine}, enum gdb_osabi @var{osabi}, void (*@var{init_osabi})(struct gdbarch_info @var{info}, struct gdbarch *@var{gdbarch})) |
| 2451 | Register the OS ABI handler specified by @var{init_osabi} for the |
| 2452 | architecture, machine type and OS ABI specified by @var{arch}, |
| 2453 | @var{machine} and @var{osabi}. In most cases, a value of zero for the |
| 2454 | machine type, which implies the architecture's default machine type, |
| 2455 | will suffice. |
| 2456 | @end deftypefun |
| 2457 | |
| 2458 | @deftypefun void gdbarch_register_osabi_sniffer (enum bfd_architecture @var{arch}, enum bfd_flavour @var{flavour}, enum gdb_osabi (*@var{sniffer})(bfd *@var{abfd})) |
| 2459 | Register the OS ABI file sniffer specified by @var{sniffer} for the |
| 2460 | BFD architecture/flavour pair specified by @var{arch} and @var{flavour}. |
| 2461 | If @var{arch} is @code{bfd_arch_unknown}, the sniffer is considered to |
| 2462 | be generic, and is allowed to examine @var{flavour}-flavoured files for |
| 2463 | any architecture. |
| 2464 | @end deftypefun |
| 2465 | |
| 2466 | @deftypefun enum gdb_osabi gdbarch_lookup_osabi (bfd *@var{abfd}) |
| 2467 | Examine the file described by @var{abfd} to determine its OS ABI. |
| 2468 | The value @code{GDB_OSABI_UNKNOWN} is returned if the OS ABI cannot |
| 2469 | be determined. |
| 2470 | @end deftypefun |
| 2471 | |
| 2472 | @deftypefun void gdbarch_init_osabi (struct gdbarch info @var{info}, struct gdbarch *@var{gdbarch}, enum gdb_osabi @var{osabi}) |
| 2473 | Invoke the OS ABI handler corresponding to @var{osabi} to fine-tune the |
| 2474 | @code{gdbarch} structure specified by @var{gdbarch}. If a handler |
| 2475 | corresponding to @var{osabi} has not been registered for @var{gdbarch}'s |
| 2476 | architecture, a warning will be issued and the debugging session will continue |
| 2477 | with the defaults already established for @var{gdbarch}. |
| 2478 | @end deftypefun |
| 2479 | |
| 2480 | @section Registers and Memory |
| 2481 | |
| 2482 | @value{GDBN}'s model of the target machine is rather simple. |
| 2483 | @value{GDBN} assumes the machine includes a bank of registers and a |
| 2484 | block of memory. Each register may have a different size. |
| 2485 | |
| 2486 | @value{GDBN} does not have a magical way to match up with the |
| 2487 | compiler's idea of which registers are which; however, it is critical |
| 2488 | that they do match up accurately. The only way to make this work is |
| 2489 | to get accurate information about the order that the compiler uses, |
| 2490 | and to reflect that in the @code{REGISTER_NAME} and related macros. |
| 2491 | |
| 2492 | @value{GDBN} can handle big-endian, little-endian, and bi-endian architectures. |
| 2493 | |
| 2494 | @section Pointers Are Not Always Addresses |
| 2495 | @cindex pointer representation |
| 2496 | @cindex address representation |
| 2497 | @cindex word-addressed machines |
| 2498 | @cindex separate data and code address spaces |
| 2499 | @cindex spaces, separate data and code address |
| 2500 | @cindex address spaces, separate data and code |
| 2501 | @cindex code pointers, word-addressed |
| 2502 | @cindex converting between pointers and addresses |
| 2503 | @cindex D10V addresses |
| 2504 | |
| 2505 | On almost all 32-bit architectures, the representation of a pointer is |
| 2506 | indistinguishable from the representation of some fixed-length number |
| 2507 | whose value is the byte address of the object pointed to. On such |
| 2508 | machines, the words ``pointer'' and ``address'' can be used interchangeably. |
| 2509 | However, architectures with smaller word sizes are often cramped for |
| 2510 | address space, so they may choose a pointer representation that breaks this |
| 2511 | identity, and allows a larger code address space. |
| 2512 | |
| 2513 | For example, the Mitsubishi D10V is a 16-bit VLIW processor whose |
| 2514 | instructions are 32 bits long@footnote{Some D10V instructions are |
| 2515 | actually pairs of 16-bit sub-instructions. However, since you can't |
| 2516 | jump into the middle of such a pair, code addresses can only refer to |
| 2517 | full 32 bit instructions, which is what matters in this explanation.}. |
| 2518 | If the D10V used ordinary byte addresses to refer to code locations, |
| 2519 | then the processor would only be able to address 64kb of instructions. |
| 2520 | However, since instructions must be aligned on four-byte boundaries, the |
| 2521 | low two bits of any valid instruction's byte address are always |
| 2522 | zero---byte addresses waste two bits. So instead of byte addresses, |
| 2523 | the D10V uses word addresses---byte addresses shifted right two bits---to |
| 2524 | refer to code. Thus, the D10V can use 16-bit words to address 256kb of |
| 2525 | code space. |
| 2526 | |
| 2527 | However, this means that code pointers and data pointers have different |
| 2528 | forms on the D10V. The 16-bit word @code{0xC020} refers to byte address |
| 2529 | @code{0xC020} when used as a data address, but refers to byte address |
| 2530 | @code{0x30080} when used as a code address. |
| 2531 | |
| 2532 | (The D10V also uses separate code and data address spaces, which also |
| 2533 | affects the correspondence between pointers and addresses, but we're |
| 2534 | going to ignore that here; this example is already too long.) |
| 2535 | |
| 2536 | To cope with architectures like this---the D10V is not the only |
| 2537 | one!---@value{GDBN} tries to distinguish between @dfn{addresses}, which are |
| 2538 | byte numbers, and @dfn{pointers}, which are the target's representation |
| 2539 | of an address of a particular type of data. In the example above, |
| 2540 | @code{0xC020} is the pointer, which refers to one of the addresses |
| 2541 | @code{0xC020} or @code{0x30080}, depending on the type imposed upon it. |
| 2542 | @value{GDBN} provides functions for turning a pointer into an address |
| 2543 | and vice versa, in the appropriate way for the current architecture. |
| 2544 | |
| 2545 | Unfortunately, since addresses and pointers are identical on almost all |
| 2546 | processors, this distinction tends to bit-rot pretty quickly. Thus, |
| 2547 | each time you port @value{GDBN} to an architecture which does |
| 2548 | distinguish between pointers and addresses, you'll probably need to |
| 2549 | clean up some architecture-independent code. |
| 2550 | |
| 2551 | Here are functions which convert between pointers and addresses: |
| 2552 | |
| 2553 | @deftypefun CORE_ADDR extract_typed_address (void *@var{buf}, struct type *@var{type}) |
| 2554 | Treat the bytes at @var{buf} as a pointer or reference of type |
| 2555 | @var{type}, and return the address it represents, in a manner |
| 2556 | appropriate for the current architecture. This yields an address |
| 2557 | @value{GDBN} can use to read target memory, disassemble, etc. Note that |
| 2558 | @var{buf} refers to a buffer in @value{GDBN}'s memory, not the |
| 2559 | inferior's. |
| 2560 | |
| 2561 | For example, if the current architecture is the Intel x86, this function |
| 2562 | extracts a little-endian integer of the appropriate length from |
| 2563 | @var{buf} and returns it. However, if the current architecture is the |
| 2564 | D10V, this function will return a 16-bit integer extracted from |
| 2565 | @var{buf}, multiplied by four if @var{type} is a pointer to a function. |
| 2566 | |
| 2567 | If @var{type} is not a pointer or reference type, then this function |
| 2568 | will signal an internal error. |
| 2569 | @end deftypefun |
| 2570 | |
| 2571 | @deftypefun CORE_ADDR store_typed_address (void *@var{buf}, struct type *@var{type}, CORE_ADDR @var{addr}) |
| 2572 | Store the address @var{addr} in @var{buf}, in the proper format for a |
| 2573 | pointer of type @var{type} in the current architecture. Note that |
| 2574 | @var{buf} refers to a buffer in @value{GDBN}'s memory, not the |
| 2575 | inferior's. |
| 2576 | |
| 2577 | For example, if the current architecture is the Intel x86, this function |
| 2578 | stores @var{addr} unmodified as a little-endian integer of the |
| 2579 | appropriate length in @var{buf}. However, if the current architecture |
| 2580 | is the D10V, this function divides @var{addr} by four if @var{type} is |
| 2581 | a pointer to a function, and then stores it in @var{buf}. |
| 2582 | |
| 2583 | If @var{type} is not a pointer or reference type, then this function |
| 2584 | will signal an internal error. |
| 2585 | @end deftypefun |
| 2586 | |
| 2587 | @deftypefun CORE_ADDR value_as_address (struct value *@var{val}) |
| 2588 | Assuming that @var{val} is a pointer, return the address it represents, |
| 2589 | as appropriate for the current architecture. |
| 2590 | |
| 2591 | This function actually works on integral values, as well as pointers. |
| 2592 | For pointers, it performs architecture-specific conversions as |
| 2593 | described above for @code{extract_typed_address}. |
| 2594 | @end deftypefun |
| 2595 | |
| 2596 | @deftypefun CORE_ADDR value_from_pointer (struct type *@var{type}, CORE_ADDR @var{addr}) |
| 2597 | Create and return a value representing a pointer of type @var{type} to |
| 2598 | the address @var{addr}, as appropriate for the current architecture. |
| 2599 | This function performs architecture-specific conversions as described |
| 2600 | above for @code{store_typed_address}. |
| 2601 | @end deftypefun |
| 2602 | |
| 2603 | |
| 2604 | @value{GDBN} also provides functions that do the same tasks, but assume |
| 2605 | that pointers are simply byte addresses; they aren't sensitive to the |
| 2606 | current architecture, beyond knowing the appropriate endianness. |
| 2607 | |
| 2608 | @deftypefun CORE_ADDR extract_address (void *@var{addr}, int len) |
| 2609 | Extract a @var{len}-byte number from @var{addr} in the appropriate |
| 2610 | endianness for the current architecture, and return it. Note that |
| 2611 | @var{addr} refers to @value{GDBN}'s memory, not the inferior's. |
| 2612 | |
| 2613 | This function should only be used in architecture-specific code; it |
| 2614 | doesn't have enough information to turn bits into a true address in the |
| 2615 | appropriate way for the current architecture. If you can, use |
| 2616 | @code{extract_typed_address} instead. |
| 2617 | @end deftypefun |
| 2618 | |
| 2619 | @deftypefun void store_address (void *@var{addr}, int @var{len}, LONGEST @var{val}) |
| 2620 | Store @var{val} at @var{addr} as a @var{len}-byte integer, in the |
| 2621 | appropriate endianness for the current architecture. Note that |
| 2622 | @var{addr} refers to a buffer in @value{GDBN}'s memory, not the |
| 2623 | inferior's. |
| 2624 | |
| 2625 | This function should only be used in architecture-specific code; it |
| 2626 | doesn't have enough information to turn a true address into bits in the |
| 2627 | appropriate way for the current architecture. If you can, use |
| 2628 | @code{store_typed_address} instead. |
| 2629 | @end deftypefun |
| 2630 | |
| 2631 | |
| 2632 | Here are some macros which architectures can define to indicate the |
| 2633 | relationship between pointers and addresses. These have default |
| 2634 | definitions, appropriate for architectures on which all pointers are |
| 2635 | simple unsigned byte addresses. |
| 2636 | |
| 2637 | @deftypefn {Target Macro} CORE_ADDR POINTER_TO_ADDRESS (struct type *@var{type}, char *@var{buf}) |
| 2638 | Assume that @var{buf} holds a pointer of type @var{type}, in the |
| 2639 | appropriate format for the current architecture. Return the byte |
| 2640 | address the pointer refers to. |
| 2641 | |
| 2642 | This function may safely assume that @var{type} is either a pointer or a |
| 2643 | C@t{++} reference type. |
| 2644 | @end deftypefn |
| 2645 | |
| 2646 | @deftypefn {Target Macro} void ADDRESS_TO_POINTER (struct type *@var{type}, char *@var{buf}, CORE_ADDR @var{addr}) |
| 2647 | Store in @var{buf} a pointer of type @var{type} representing the address |
| 2648 | @var{addr}, in the appropriate format for the current architecture. |
| 2649 | |
| 2650 | This function may safely assume that @var{type} is either a pointer or a |
| 2651 | C@t{++} reference type. |
| 2652 | @end deftypefn |
| 2653 | |
| 2654 | @section Address Classes |
| 2655 | @cindex address classes |
| 2656 | @cindex DW_AT_byte_size |
| 2657 | @cindex DW_AT_address_class |
| 2658 | |
| 2659 | Sometimes information about different kinds of addresses is available |
| 2660 | via the debug information. For example, some programming environments |
| 2661 | define addresses of several different sizes. If the debug information |
| 2662 | distinguishes these kinds of address classes through either the size |
| 2663 | info (e.g, @code{DW_AT_byte_size} in @w{DWARF 2}) or through an explicit |
| 2664 | address class attribute (e.g, @code{DW_AT_address_class} in @w{DWARF 2}), the |
| 2665 | following macros should be defined in order to disambiguate these |
| 2666 | types within @value{GDBN} as well as provide the added information to |
| 2667 | a @value{GDBN} user when printing type expressions. |
| 2668 | |
| 2669 | @deftypefn {Target Macro} int ADDRESS_CLASS_TYPE_FLAGS (int @var{byte_size}, int @var{dwarf2_addr_class}) |
| 2670 | Returns the type flags needed to construct a pointer type whose size |
| 2671 | is @var{byte_size} and whose address class is @var{dwarf2_addr_class}. |
| 2672 | This function is normally called from within a symbol reader. See |
| 2673 | @file{dwarf2read.c}. |
| 2674 | @end deftypefn |
| 2675 | |
| 2676 | @deftypefn {Target Macro} char *ADDRESS_CLASS_TYPE_FLAGS_TO_NAME (int @var{type_flags}) |
| 2677 | Given the type flags representing an address class qualifier, return |
| 2678 | its name. |
| 2679 | @end deftypefn |
| 2680 | @deftypefn {Target Macro} int ADDRESS_CLASS_NAME_to_TYPE_FLAGS (int @var{name}, int *var{type_flags_ptr}) |
| 2681 | Given an address qualifier name, set the @code{int} refererenced by @var{type_flags_ptr} to the type flags |
| 2682 | for that address class qualifier. |
| 2683 | @end deftypefn |
| 2684 | |
| 2685 | Since the need for address classes is rather rare, none of |
| 2686 | the address class macros defined by default. Predicate |
| 2687 | macros are provided to detect when they are defined. |
| 2688 | |
| 2689 | Consider a hypothetical architecture in which addresses are normally |
| 2690 | 32-bits wide, but 16-bit addresses are also supported. Furthermore, |
| 2691 | suppose that the @w{DWARF 2} information for this architecture simply |
| 2692 | uses a @code{DW_AT_byte_size} value of 2 to indicate the use of one |
| 2693 | of these "short" pointers. The following functions could be defined |
| 2694 | to implement the address class macros: |
| 2695 | |
| 2696 | @smallexample |
| 2697 | somearch_address_class_type_flags (int byte_size, |
| 2698 | int dwarf2_addr_class) |
| 2699 | @{ |
| 2700 | if (byte_size == 2) |
| 2701 | return TYPE_FLAG_ADDRESS_CLASS_1; |
| 2702 | else |
| 2703 | return 0; |
| 2704 | @} |
| 2705 | |
| 2706 | static char * |
| 2707 | somearch_address_class_type_flags_to_name (int type_flags) |
| 2708 | @{ |
| 2709 | if (type_flags & TYPE_FLAG_ADDRESS_CLASS_1) |
| 2710 | return "short"; |
| 2711 | else |
| 2712 | return NULL; |
| 2713 | @} |
| 2714 | |
| 2715 | int |
| 2716 | somearch_address_class_name_to_type_flags (char *name, |
| 2717 | int *type_flags_ptr) |
| 2718 | @{ |
| 2719 | if (strcmp (name, "short") == 0) |
| 2720 | @{ |
| 2721 | *type_flags_ptr = TYPE_FLAG_ADDRESS_CLASS_1; |
| 2722 | return 1; |
| 2723 | @} |
| 2724 | else |
| 2725 | return 0; |
| 2726 | @} |
| 2727 | @end smallexample |
| 2728 | |
| 2729 | The qualifier @code{@@short} is used in @value{GDBN}'s type expressions |
| 2730 | to indicate the presence of one of these "short" pointers. E.g, if |
| 2731 | the debug information indicates that @code{short_ptr_var} is one of these |
| 2732 | short pointers, @value{GDBN} might show the following behavior: |
| 2733 | |
| 2734 | @smallexample |
| 2735 | (gdb) ptype short_ptr_var |
| 2736 | type = int * @@short |
| 2737 | @end smallexample |
| 2738 | |
| 2739 | |
| 2740 | @section Raw and Virtual Register Representations |
| 2741 | @cindex raw register representation |
| 2742 | @cindex virtual register representation |
| 2743 | @cindex representations, raw and virtual registers |
| 2744 | |
| 2745 | @emph{Maintainer note: This section is pretty much obsolete. The |
| 2746 | functionality described here has largely been replaced by |
| 2747 | pseudo-registers and the mechanisms described in @ref{Target |
| 2748 | Architecture Definition, , Using Different Register and Memory Data |
| 2749 | Representations}. See also @uref{http://www.gnu.org/software/gdb/bugs/, |
| 2750 | Bug Tracking Database} and |
| 2751 | @uref{http://sources.redhat.com/gdb/current/ari/, ARI Index} for more |
| 2752 | up-to-date information.} |
| 2753 | |
| 2754 | Some architectures use one representation for a value when it lives in a |
| 2755 | register, but use a different representation when it lives in memory. |
| 2756 | In @value{GDBN}'s terminology, the @dfn{raw} representation is the one used in |
| 2757 | the target registers, and the @dfn{virtual} representation is the one |
| 2758 | used in memory, and within @value{GDBN} @code{struct value} objects. |
| 2759 | |
| 2760 | @emph{Maintainer note: Notice that the same mechanism is being used to |
| 2761 | both convert a register to a @code{struct value} and alternative |
| 2762 | register forms.} |
| 2763 | |
| 2764 | For almost all data types on almost all architectures, the virtual and |
| 2765 | raw representations are identical, and no special handling is needed. |
| 2766 | However, they do occasionally differ. For example: |
| 2767 | |
| 2768 | @itemize @bullet |
| 2769 | @item |
| 2770 | The x86 architecture supports an 80-bit @code{long double} type. However, when |
| 2771 | we store those values in memory, they occupy twelve bytes: the |
| 2772 | floating-point number occupies the first ten, and the final two bytes |
| 2773 | are unused. This keeps the values aligned on four-byte boundaries, |
| 2774 | allowing more efficient access. Thus, the x86 80-bit floating-point |
| 2775 | type is the raw representation, and the twelve-byte loosely-packed |
| 2776 | arrangement is the virtual representation. |
| 2777 | |
| 2778 | @item |
| 2779 | Some 64-bit MIPS targets present 32-bit registers to @value{GDBN} as 64-bit |
| 2780 | registers, with garbage in their upper bits. @value{GDBN} ignores the top 32 |
| 2781 | bits. Thus, the 64-bit form, with garbage in the upper 32 bits, is the |
| 2782 | raw representation, and the trimmed 32-bit representation is the |
| 2783 | virtual representation. |
| 2784 | @end itemize |
| 2785 | |
| 2786 | In general, the raw representation is determined by the architecture, or |
| 2787 | @value{GDBN}'s interface to the architecture, while the virtual representation |
| 2788 | can be chosen for @value{GDBN}'s convenience. @value{GDBN}'s register file, |
| 2789 | @code{registers}, holds the register contents in raw format, and the |
| 2790 | @value{GDBN} remote protocol transmits register values in raw format. |
| 2791 | |
| 2792 | Your architecture may define the following macros to request |
| 2793 | conversions between the raw and virtual format: |
| 2794 | |
| 2795 | @deftypefn {Target Macro} int REGISTER_CONVERTIBLE (int @var{reg}) |
| 2796 | Return non-zero if register number @var{reg}'s value needs different raw |
| 2797 | and virtual formats. |
| 2798 | |
| 2799 | You should not use @code{REGISTER_CONVERT_TO_VIRTUAL} for a register |
| 2800 | unless this macro returns a non-zero value for that register. |
| 2801 | @end deftypefn |
| 2802 | |
| 2803 | @deftypefn {Target Macro} int REGISTER_RAW_SIZE (int @var{reg}) |
| 2804 | The size of register number @var{reg}'s raw value. This is the number |
| 2805 | of bytes the register will occupy in @code{registers}, or in a @value{GDBN} |
| 2806 | remote protocol packet. |
| 2807 | @end deftypefn |
| 2808 | |
| 2809 | @deftypefn {Target Macro} int REGISTER_VIRTUAL_SIZE (int @var{reg}) |
| 2810 | The size of register number @var{reg}'s value, in its virtual format. |
| 2811 | This is the size a @code{struct value}'s buffer will have, holding that |
| 2812 | register's value. |
| 2813 | @end deftypefn |
| 2814 | |
| 2815 | @deftypefn {Target Macro} struct type *REGISTER_VIRTUAL_TYPE (int @var{reg}) |
| 2816 | This is the type of the virtual representation of register number |
| 2817 | @var{reg}. Note that there is no need for a macro giving a type for the |
| 2818 | register's raw form; once the register's value has been obtained, @value{GDBN} |
| 2819 | always uses the virtual form. |
| 2820 | @end deftypefn |
| 2821 | |
| 2822 | @deftypefn {Target Macro} void REGISTER_CONVERT_TO_VIRTUAL (int @var{reg}, struct type *@var{type}, char *@var{from}, char *@var{to}) |
| 2823 | Convert the value of register number @var{reg} to @var{type}, which |
| 2824 | should always be @code{REGISTER_VIRTUAL_TYPE (@var{reg})}. The buffer |
| 2825 | at @var{from} holds the register's value in raw format; the macro should |
| 2826 | convert the value to virtual format, and place it at @var{to}. |
| 2827 | |
| 2828 | Note that @code{REGISTER_CONVERT_TO_VIRTUAL} and |
| 2829 | @code{REGISTER_CONVERT_TO_RAW} take their @var{reg} and @var{type} |
| 2830 | arguments in different orders. |
| 2831 | |
| 2832 | You should only use @code{REGISTER_CONVERT_TO_VIRTUAL} with registers |
| 2833 | for which the @code{REGISTER_CONVERTIBLE} macro returns a non-zero |
| 2834 | value. |
| 2835 | @end deftypefn |
| 2836 | |
| 2837 | @deftypefn {Target Macro} void REGISTER_CONVERT_TO_RAW (struct type *@var{type}, int @var{reg}, char *@var{from}, char *@var{to}) |
| 2838 | Convert the value of register number @var{reg} to @var{type}, which |
| 2839 | should always be @code{REGISTER_VIRTUAL_TYPE (@var{reg})}. The buffer |
| 2840 | at @var{from} holds the register's value in raw format; the macro should |
| 2841 | convert the value to virtual format, and place it at @var{to}. |
| 2842 | |
| 2843 | Note that REGISTER_CONVERT_TO_VIRTUAL and REGISTER_CONVERT_TO_RAW take |
| 2844 | their @var{reg} and @var{type} arguments in different orders. |
| 2845 | @end deftypefn |
| 2846 | |
| 2847 | |
| 2848 | @section Using Different Register and Memory Data Representations |
| 2849 | @cindex register representation |
| 2850 | @cindex memory representation |
| 2851 | @cindex representations, register and memory |
| 2852 | @cindex register data formats, converting |
| 2853 | @cindex @code{struct value}, converting register contents to |
| 2854 | |
| 2855 | @emph{Maintainer's note: The way GDB manipulates registers is undergoing |
| 2856 | significant change. Many of the macros and functions refered to in this |
| 2857 | section are likely to be subject to further revision. See |
| 2858 | @uref{http://sources.redhat.com/gdb/current/ari/, A.R. Index} and |
| 2859 | @uref{http://www.gnu.org/software/gdb/bugs, Bug Tracking Database} for |
| 2860 | further information. cagney/2002-05-06.} |
| 2861 | |
| 2862 | Some architectures can represent a data object in a register using a |
| 2863 | form that is different to the objects more normal memory representation. |
| 2864 | For example: |
| 2865 | |
| 2866 | @itemize @bullet |
| 2867 | |
| 2868 | @item |
| 2869 | The Alpha architecture can represent 32 bit integer values in |
| 2870 | floating-point registers. |
| 2871 | |
| 2872 | @item |
| 2873 | The x86 architecture supports 80-bit floating-point registers. The |
| 2874 | @code{long double} data type occupies 96 bits in memory but only 80 bits |
| 2875 | when stored in a register. |
| 2876 | |
| 2877 | @end itemize |
| 2878 | |
| 2879 | In general, the register representation of a data type is determined by |
| 2880 | the architecture, or @value{GDBN}'s interface to the architecture, while |
| 2881 | the memory representation is determined by the Application Binary |
| 2882 | Interface. |
| 2883 | |
| 2884 | For almost all data types on almost all architectures, the two |
| 2885 | representations are identical, and no special handling is needed. |
| 2886 | However, they do occasionally differ. Your architecture may define the |
| 2887 | following macros to request conversions between the register and memory |
| 2888 | representations of a data type: |
| 2889 | |
| 2890 | @deftypefn {Target Macro} int CONVERT_REGISTER_P (int @var{reg}) |
| 2891 | Return non-zero if the representation of a data value stored in this |
| 2892 | register may be different to the representation of that same data value |
| 2893 | when stored in memory. |
| 2894 | |
| 2895 | When non-zero, the macros @code{REGISTER_TO_VALUE} and |
| 2896 | @code{VALUE_TO_REGISTER} are used to perform any necessary conversion. |
| 2897 | @end deftypefn |
| 2898 | |
| 2899 | @deftypefn {Target Macro} void REGISTER_TO_VALUE (int @var{reg}, struct type *@var{type}, char *@var{from}, char *@var{to}) |
| 2900 | Convert the value of register number @var{reg} to a data object of type |
| 2901 | @var{type}. The buffer at @var{from} holds the register's value in raw |
| 2902 | format; the converted value should be placed in the buffer at @var{to}. |
| 2903 | |
| 2904 | Note that @code{REGISTER_TO_VALUE} and @code{VALUE_TO_REGISTER} take |
| 2905 | their @var{reg} and @var{type} arguments in different orders. |
| 2906 | |
| 2907 | You should only use @code{REGISTER_TO_VALUE} with registers for which |
| 2908 | the @code{CONVERT_REGISTER_P} macro returns a non-zero value. |
| 2909 | @end deftypefn |
| 2910 | |
| 2911 | @deftypefn {Target Macro} void VALUE_TO_REGISTER (struct type *@var{type}, int @var{reg}, char *@var{from}, char *@var{to}) |
| 2912 | Convert a data value of type @var{type} to register number @var{reg}' |
| 2913 | raw format. |
| 2914 | |
| 2915 | Note that @code{REGISTER_TO_VALUE} and @code{VALUE_TO_REGISTER} take |
| 2916 | their @var{reg} and @var{type} arguments in different orders. |
| 2917 | |
| 2918 | You should only use @code{VALUE_TO_REGISTER} with registers for which |
| 2919 | the @code{CONVERT_REGISTER_P} macro returns a non-zero value. |
| 2920 | @end deftypefn |
| 2921 | |
| 2922 | @deftypefn {Target Macro} void REGISTER_CONVERT_TO_TYPE (int @var{regnum}, struct type *@var{type}, char *@var{buf}) |
| 2923 | See @file{mips-tdep.c}. It does not do what you want. |
| 2924 | @end deftypefn |
| 2925 | |
| 2926 | |
| 2927 | @section Frame Interpretation |
| 2928 | |
| 2929 | @section Inferior Call Setup |
| 2930 | |
| 2931 | @section Compiler Characteristics |
| 2932 | |
| 2933 | @section Target Conditionals |
| 2934 | |
| 2935 | This section describes the macros that you can use to define the target |
| 2936 | machine. |
| 2937 | |
| 2938 | @table @code |
| 2939 | |
| 2940 | @item ADDR_BITS_REMOVE (addr) |
| 2941 | @findex ADDR_BITS_REMOVE |
| 2942 | If a raw machine instruction address includes any bits that are not |
| 2943 | really part of the address, then define this macro to expand into an |
| 2944 | expression that zeroes those bits in @var{addr}. This is only used for |
| 2945 | addresses of instructions, and even then not in all contexts. |
| 2946 | |
| 2947 | For example, the two low-order bits of the PC on the Hewlett-Packard PA |
| 2948 | 2.0 architecture contain the privilege level of the corresponding |
| 2949 | instruction. Since instructions must always be aligned on four-byte |
| 2950 | boundaries, the processor masks out these bits to generate the actual |
| 2951 | address of the instruction. ADDR_BITS_REMOVE should filter out these |
| 2952 | bits with an expression such as @code{((addr) & ~3)}. |
| 2953 | |
| 2954 | @item ADDRESS_CLASS_NAME_TO_TYPE_FLAGS (@var{name}, @var{type_flags_ptr}) |
| 2955 | @findex ADDRESS_CLASS_NAME_TO_TYPE_FLAGS |
| 2956 | If @var{name} is a valid address class qualifier name, set the @code{int} |
| 2957 | referenced by @var{type_flags_ptr} to the mask representing the qualifier |
| 2958 | and return 1. If @var{name} is not a valid address class qualifier name, |
| 2959 | return 0. |
| 2960 | |
| 2961 | The value for @var{type_flags_ptr} should be one of |
| 2962 | @code{TYPE_FLAG_ADDRESS_CLASS_1}, @code{TYPE_FLAG_ADDRESS_CLASS_2}, or |
| 2963 | possibly some combination of these values or'd together. |
| 2964 | @xref{Target Architecture Definition, , Address Classes}. |
| 2965 | |
| 2966 | @item ADDRESS_CLASS_NAME_TO_TYPE_FLAGS_P () |
| 2967 | @findex ADDRESS_CLASS_NAME_TO_TYPE_FLAGS_P |
| 2968 | Predicate which indicates whether @code{ADDRESS_CLASS_NAME_TO_TYPE_FLAGS} |
| 2969 | has been defined. |
| 2970 | |
| 2971 | @item ADDRESS_CLASS_TYPE_FLAGS (@var{byte_size}, @var{dwarf2_addr_class}) |
| 2972 | @findex ADDRESS_CLASS_TYPE_FLAGS (@var{byte_size}, @var{dwarf2_addr_class}) |
| 2973 | Given a pointers byte size (as described by the debug information) and |
| 2974 | the possible @code{DW_AT_address_class} value, return the type flags |
| 2975 | used by @value{GDBN} to represent this address class. The value |
| 2976 | returned should be one of @code{TYPE_FLAG_ADDRESS_CLASS_1}, |
| 2977 | @code{TYPE_FLAG_ADDRESS_CLASS_2}, or possibly some combination of these |
| 2978 | values or'd together. |
| 2979 | @xref{Target Architecture Definition, , Address Classes}. |
| 2980 | |
| 2981 | @item ADDRESS_CLASS_TYPE_FLAGS_P () |
| 2982 | @findex ADDRESS_CLASS_TYPE_FLAGS_P |
| 2983 | Predicate which indicates whether @code{ADDRESS_CLASS_TYPE_FLAGS} has |
| 2984 | been defined. |
| 2985 | |
| 2986 | @item ADDRESS_CLASS_TYPE_FLAGS_TO_NAME (@var{type_flags}) |
| 2987 | @findex ADDRESS_CLASS_TYPE_FLAGS_TO_NAME |
| 2988 | Return the name of the address class qualifier associated with the type |
| 2989 | flags given by @var{type_flags}. |
| 2990 | |
| 2991 | @item ADDRESS_CLASS_TYPE_FLAGS_TO_NAME_P () |
| 2992 | @findex ADDRESS_CLASS_TYPE_FLAGS_TO_NAME_P |
| 2993 | Predicate which indicates whether @code{ADDRESS_CLASS_TYPE_FLAGS_TO_NAME} has |
| 2994 | been defined. |
| 2995 | @xref{Target Architecture Definition, , Address Classes}. |
| 2996 | |
| 2997 | @item ADDRESS_TO_POINTER (@var{type}, @var{buf}, @var{addr}) |
| 2998 | @findex ADDRESS_TO_POINTER |
| 2999 | Store in @var{buf} a pointer of type @var{type} representing the address |
| 3000 | @var{addr}, in the appropriate format for the current architecture. |
| 3001 | This macro may safely assume that @var{type} is either a pointer or a |
| 3002 | C@t{++} reference type. |
| 3003 | @xref{Target Architecture Definition, , Pointers Are Not Always Addresses}. |
| 3004 | |
| 3005 | @item BELIEVE_PCC_PROMOTION |
| 3006 | @findex BELIEVE_PCC_PROMOTION |
| 3007 | Define if the compiler promotes a @code{short} or @code{char} |
| 3008 | parameter to an @code{int}, but still reports the parameter as its |
| 3009 | original type, rather than the promoted type. |
| 3010 | |
| 3011 | @item BELIEVE_PCC_PROMOTION_TYPE |
| 3012 | @findex BELIEVE_PCC_PROMOTION_TYPE |
| 3013 | Define this if @value{GDBN} should believe the type of a @code{short} |
| 3014 | argument when compiled by @code{pcc}, but look within a full int space to get |
| 3015 | its value. Only defined for Sun-3 at present. |
| 3016 | |
| 3017 | @item BITS_BIG_ENDIAN |
| 3018 | @findex BITS_BIG_ENDIAN |
| 3019 | Define this if the numbering of bits in the targets does @strong{not} match the |
| 3020 | endianness of the target byte order. A value of 1 means that the bits |
| 3021 | are numbered in a big-endian bit order, 0 means little-endian. |
| 3022 | |
| 3023 | @item BREAKPOINT |
| 3024 | @findex BREAKPOINT |
| 3025 | This is the character array initializer for the bit pattern to put into |
| 3026 | memory where a breakpoint is set. Although it's common to use a trap |
| 3027 | instruction for a breakpoint, it's not required; for instance, the bit |
| 3028 | pattern could be an invalid instruction. The breakpoint must be no |
| 3029 | longer than the shortest instruction of the architecture. |
| 3030 | |
| 3031 | @code{BREAKPOINT} has been deprecated in favor of |
| 3032 | @code{BREAKPOINT_FROM_PC}. |
| 3033 | |
| 3034 | @item BIG_BREAKPOINT |
| 3035 | @itemx LITTLE_BREAKPOINT |
| 3036 | @findex LITTLE_BREAKPOINT |
| 3037 | @findex BIG_BREAKPOINT |
| 3038 | Similar to BREAKPOINT, but used for bi-endian targets. |
| 3039 | |
| 3040 | @code{BIG_BREAKPOINT} and @code{LITTLE_BREAKPOINT} have been deprecated in |
| 3041 | favor of @code{BREAKPOINT_FROM_PC}. |
| 3042 | |
| 3043 | @item REMOTE_BREAKPOINT |
| 3044 | @itemx LITTLE_REMOTE_BREAKPOINT |
| 3045 | @itemx BIG_REMOTE_BREAKPOINT |
| 3046 | @findex BIG_REMOTE_BREAKPOINT |
| 3047 | @findex LITTLE_REMOTE_BREAKPOINT |
| 3048 | @findex REMOTE_BREAKPOINT |
| 3049 | Similar to BREAKPOINT, but used for remote targets. |
| 3050 | |
| 3051 | @code{BIG_REMOTE_BREAKPOINT} and @code{LITTLE_REMOTE_BREAKPOINT} have been |
| 3052 | deprecated in favor of @code{BREAKPOINT_FROM_PC}. |
| 3053 | |
| 3054 | @item BREAKPOINT_FROM_PC (@var{pcptr}, @var{lenptr}) |
| 3055 | @findex BREAKPOINT_FROM_PC |
| 3056 | Use the program counter to determine the contents and size of a |
| 3057 | breakpoint instruction. It returns a pointer to a string of bytes |
| 3058 | that encode a breakpoint instruction, stores the length of the string |
| 3059 | to *@var{lenptr}, and adjusts pc (if necessary) to point to the actual |
| 3060 | memory location where the breakpoint should be inserted. |
| 3061 | |
| 3062 | Although it is common to use a trap instruction for a breakpoint, it's |
| 3063 | not required; for instance, the bit pattern could be an invalid |
| 3064 | instruction. The breakpoint must be no longer than the shortest |
| 3065 | instruction of the architecture. |
| 3066 | |
| 3067 | Replaces all the other @var{BREAKPOINT} macros. |
| 3068 | |
| 3069 | @item MEMORY_INSERT_BREAKPOINT (@var{addr}, @var{contents_cache}) |
| 3070 | @itemx MEMORY_REMOVE_BREAKPOINT (@var{addr}, @var{contents_cache}) |
| 3071 | @findex MEMORY_REMOVE_BREAKPOINT |
| 3072 | @findex MEMORY_INSERT_BREAKPOINT |
| 3073 | Insert or remove memory based breakpoints. Reasonable defaults |
| 3074 | (@code{default_memory_insert_breakpoint} and |
| 3075 | @code{default_memory_remove_breakpoint} respectively) have been |
| 3076 | provided so that it is not necessary to define these for most |
| 3077 | architectures. Architectures which may want to define |
| 3078 | @code{MEMORY_INSERT_BREAKPOINT} and @code{MEMORY_REMOVE_BREAKPOINT} will |
| 3079 | likely have instructions that are oddly sized or are not stored in a |
| 3080 | conventional manner. |
| 3081 | |
| 3082 | It may also be desirable (from an efficiency standpoint) to define |
| 3083 | custom breakpoint insertion and removal routines if |
| 3084 | @code{BREAKPOINT_FROM_PC} needs to read the target's memory for some |
| 3085 | reason. |
| 3086 | |
| 3087 | @item CALL_DUMMY_P |
| 3088 | @findex CALL_DUMMY_P |
| 3089 | A C expression that is non-zero when the target supports inferior function |
| 3090 | calls. |
| 3091 | |
| 3092 | @item CALL_DUMMY_WORDS |
| 3093 | @findex CALL_DUMMY_WORDS |
| 3094 | Pointer to an array of @code{LONGEST} words of data containing |
| 3095 | host-byte-ordered @code{REGISTER_BYTES} sized values that partially |
| 3096 | specify the sequence of instructions needed for an inferior function |
| 3097 | call. |
| 3098 | |
| 3099 | Should be deprecated in favor of a macro that uses target-byte-ordered |
| 3100 | data. |
| 3101 | |
| 3102 | @item SIZEOF_CALL_DUMMY_WORDS |
| 3103 | @findex SIZEOF_CALL_DUMMY_WORDS |
| 3104 | The size of @code{CALL_DUMMY_WORDS}. When @code{CALL_DUMMY_P} this must |
| 3105 | return a positive value. See also @code{CALL_DUMMY_LENGTH}. |
| 3106 | |
| 3107 | @item CALL_DUMMY |
| 3108 | @findex CALL_DUMMY |
| 3109 | A static initializer for @code{CALL_DUMMY_WORDS}. Deprecated. |
| 3110 | |
| 3111 | @item CALL_DUMMY_LOCATION |
| 3112 | @findex CALL_DUMMY_LOCATION |
| 3113 | See the file @file{inferior.h}. |
| 3114 | |
| 3115 | @item DEPRECATED_CALL_DUMMY_STACK_ADJUST |
| 3116 | @findex DEPRECATED_CALL_DUMMY_STACK_ADJUST |
| 3117 | Stack adjustment needed when performing an inferior function call. This |
| 3118 | function is no longer needed. @xref{push_dummy_call}, which can handle |
| 3119 | all alignment directly. |
| 3120 | |
| 3121 | @item CANNOT_FETCH_REGISTER (@var{regno}) |
| 3122 | @findex CANNOT_FETCH_REGISTER |
| 3123 | A C expression that should be nonzero if @var{regno} cannot be fetched |
| 3124 | from an inferior process. This is only relevant if |
| 3125 | @code{FETCH_INFERIOR_REGISTERS} is not defined. |
| 3126 | |
| 3127 | @item CANNOT_STORE_REGISTER (@var{regno}) |
| 3128 | @findex CANNOT_STORE_REGISTER |
| 3129 | A C expression that should be nonzero if @var{regno} should not be |
| 3130 | written to the target. This is often the case for program counters, |
| 3131 | status words, and other special registers. If this is not defined, |
| 3132 | @value{GDBN} will assume that all registers may be written. |
| 3133 | |
| 3134 | @item DO_DEFERRED_STORES |
| 3135 | @itemx CLEAR_DEFERRED_STORES |
| 3136 | @findex CLEAR_DEFERRED_STORES |
| 3137 | @findex DO_DEFERRED_STORES |
| 3138 | Define this to execute any deferred stores of registers into the inferior, |
| 3139 | and to cancel any deferred stores. |
| 3140 | |
| 3141 | Currently only implemented correctly for native Sparc configurations? |
| 3142 | |
| 3143 | @item int CONVERT_REGISTER_P(@var{regnum}) |
| 3144 | @findex CONVERT_REGISTER_P |
| 3145 | Return non-zero if register @var{regnum} can represent data values in a |
| 3146 | non-standard form. |
| 3147 | @xref{Target Architecture Definition, , Using Different Register and Memory Data Representations}. |
| 3148 | |
| 3149 | @item DECR_PC_AFTER_BREAK |
| 3150 | @findex DECR_PC_AFTER_BREAK |
| 3151 | Define this to be the amount by which to decrement the PC after the |
| 3152 | program encounters a breakpoint. This is often the number of bytes in |
| 3153 | @code{BREAKPOINT}, though not always. For most targets this value will be 0. |
| 3154 | |
| 3155 | @item DECR_PC_AFTER_HW_BREAK |
| 3156 | @findex DECR_PC_AFTER_HW_BREAK |
| 3157 | Similarly, for hardware breakpoints. |
| 3158 | |
| 3159 | @item DISABLE_UNSETTABLE_BREAK (@var{addr}) |
| 3160 | @findex DISABLE_UNSETTABLE_BREAK |
| 3161 | If defined, this should evaluate to 1 if @var{addr} is in a shared |
| 3162 | library in which breakpoints cannot be set and so should be disabled. |
| 3163 | |
| 3164 | @item PRINT_FLOAT_INFO() |
| 3165 | @findex PRINT_FLOAT_INFO |
| 3166 | If defined, then the @samp{info float} command will print information about |
| 3167 | the processor's floating point unit. |
| 3168 | |
| 3169 | @item print_registers_info (@var{gdbarch}, @var{frame}, @var{regnum}, @var{all}) |
| 3170 | @findex print_registers_info |
| 3171 | If defined, pretty print the value of the register @var{regnum} for the |
| 3172 | specified @var{frame}. If the value of @var{regnum} is -1, pretty print |
| 3173 | either all registers (@var{all} is non zero) or a select subset of |
| 3174 | registers (@var{all} is zero). |
| 3175 | |
| 3176 | The default method prints one register per line, and if @var{all} is |
| 3177 | zero omits floating-point registers. |
| 3178 | |
| 3179 | @item PRINT_VECTOR_INFO() |
| 3180 | @findex PRINT_VECTOR_INFO |
| 3181 | If defined, then the @samp{info vector} command will call this function |
| 3182 | to print information about the processor's vector unit. |
| 3183 | |
| 3184 | By default, the @samp{info vector} command will print all vector |
| 3185 | registers (the register's type having the vector attribute). |
| 3186 | |
| 3187 | @item DWARF_REG_TO_REGNUM |
| 3188 | @findex DWARF_REG_TO_REGNUM |
| 3189 | Convert DWARF register number into @value{GDBN} regnum. If not defined, |
| 3190 | no conversion will be performed. |
| 3191 | |
| 3192 | @item DWARF2_REG_TO_REGNUM |
| 3193 | @findex DWARF2_REG_TO_REGNUM |
| 3194 | Convert DWARF2 register number into @value{GDBN} regnum. If not |
| 3195 | defined, no conversion will be performed. |
| 3196 | |
| 3197 | @item ECOFF_REG_TO_REGNUM |
| 3198 | @findex ECOFF_REG_TO_REGNUM |
| 3199 | Convert ECOFF register number into @value{GDBN} regnum. If not defined, |
| 3200 | no conversion will be performed. |
| 3201 | |
| 3202 | @item END_OF_TEXT_DEFAULT |
| 3203 | @findex END_OF_TEXT_DEFAULT |
| 3204 | This is an expression that should designate the end of the text section. |
| 3205 | @c (? FIXME ?) |
| 3206 | |
| 3207 | @item EXTRACT_RETURN_VALUE(@var{type}, @var{regbuf}, @var{valbuf}) |
| 3208 | @findex EXTRACT_RETURN_VALUE |
| 3209 | Define this to extract a function's return value of type @var{type} from |
| 3210 | the raw register state @var{regbuf} and copy that, in virtual format, |
| 3211 | into @var{valbuf}. |
| 3212 | |
| 3213 | @item EXTRACT_STRUCT_VALUE_ADDRESS(@var{regbuf}) |
| 3214 | @findex EXTRACT_STRUCT_VALUE_ADDRESS |
| 3215 | When defined, extract from the array @var{regbuf} (containing the raw |
| 3216 | register state) the @code{CORE_ADDR} at which a function should return |
| 3217 | its structure value. |
| 3218 | |
| 3219 | If not defined, @code{EXTRACT_RETURN_VALUE} is used. |
| 3220 | |
| 3221 | @item EXTRACT_STRUCT_VALUE_ADDRESS_P() |
| 3222 | @findex EXTRACT_STRUCT_VALUE_ADDRESS_P |
| 3223 | Predicate for @code{EXTRACT_STRUCT_VALUE_ADDRESS}. |
| 3224 | |
| 3225 | @item FP_REGNUM |
| 3226 | @findex FP_REGNUM |
| 3227 | If the virtual frame pointer is kept in a register, then define this |
| 3228 | macro to be the number (greater than or equal to zero) of that register. |
| 3229 | |
| 3230 | This should only need to be defined if @code{TARGET_READ_FP} is not |
| 3231 | defined. |
| 3232 | |
| 3233 | @item FRAMELESS_FUNCTION_INVOCATION(@var{fi}) |
| 3234 | @findex FRAMELESS_FUNCTION_INVOCATION |
| 3235 | Define this to an expression that returns 1 if the function invocation |
| 3236 | represented by @var{fi} does not have a stack frame associated with it. |
| 3237 | Otherwise return 0. |
| 3238 | |
| 3239 | @item frame_align (@var{address}) |
| 3240 | @anchor{frame_align} |
| 3241 | @findex frame_align |
| 3242 | Define this to adjust @var{address} so that it meets the alignment |
| 3243 | requirements for the start of a new stack frame. A stack frame's |
| 3244 | alignment requirements are typically stronger than a target processors |
| 3245 | stack alignment requirements (@pxref{STACK_ALIGN}). |
| 3246 | |
| 3247 | This function is used to ensure that, when creating a dummy frame, both |
| 3248 | the initial stack pointer and (if needed) the address of the return |
| 3249 | value are correctly aligned. |
| 3250 | |
| 3251 | Unlike @code{STACK_ALIGN}, this function always adjusts the address in |
| 3252 | the direction of stack growth. |
| 3253 | |
| 3254 | By default, no frame based stack alignment is performed. |
| 3255 | |
| 3256 | @item FRAME_ARGS_ADDRESS_CORRECT |
| 3257 | @findex FRAME_ARGS_ADDRESS_CORRECT |
| 3258 | See @file{stack.c}. |
| 3259 | |
| 3260 | @item DEPRECATED_FRAME_CHAIN(@var{frame}) |
| 3261 | @findex DEPRECATED_FRAME_CHAIN |
| 3262 | Given @var{frame}, return a pointer to the calling frame. |
| 3263 | |
| 3264 | @item DEPRECATED_FRAME_CHAIN_VALID(@var{chain}, @var{thisframe}) |
| 3265 | @findex DEPRECATED_FRAME_CHAIN_VALID |
| 3266 | Define this to be an expression that returns zero if the given frame is an |
| 3267 | outermost frame, with no caller, and nonzero otherwise. Most normal |
| 3268 | situations can be handled without defining this macro, including @code{NULL} |
| 3269 | chain pointers, dummy frames, and frames whose PC values are inside the |
| 3270 | startup file (e.g.@: @file{crt0.o}), inside @code{main}, or inside |
| 3271 | @code{_start}. |
| 3272 | |
| 3273 | @item DEPRECATED_FRAME_INIT_SAVED_REGS(@var{frame}) |
| 3274 | @findex DEPRECATED_FRAME_INIT_SAVED_REGS |
| 3275 | See @file{frame.h}. Determines the address of all registers in the |
| 3276 | current stack frame storing each in @code{frame->saved_regs}. Space for |
| 3277 | @code{frame->saved_regs} shall be allocated by |
| 3278 | @code{DEPRECATED_FRAME_INIT_SAVED_REGS} using |
| 3279 | @code{frame_saved_regs_zalloc}. |
| 3280 | |
| 3281 | @code{FRAME_FIND_SAVED_REGS} and @code{EXTRA_FRAME_INFO} are deprecated. |
| 3282 | |
| 3283 | @item FRAME_NUM_ARGS (@var{fi}) |
| 3284 | @findex FRAME_NUM_ARGS |
| 3285 | For the frame described by @var{fi} return the number of arguments that |
| 3286 | are being passed. If the number of arguments is not known, return |
| 3287 | @code{-1}. |
| 3288 | |
| 3289 | @item DEPRECATED_FRAME_SAVED_PC(@var{frame}) |
| 3290 | @findex DEPRECATED_FRAME_SAVED_PC |
| 3291 | @anchor{DEPRECATED_FRAME_SAVED_PC} Given @var{frame}, return the pc |
| 3292 | saved there. This is the return address. |
| 3293 | |
| 3294 | This method is deprecated. @xref{unwind_pc}. |
| 3295 | |
| 3296 | @item CORE_ADDR unwind_pc (struct frame_info *@var{this_frame}) |
| 3297 | @findex unwind_pc |
| 3298 | @anchor{unwind_pc} Return the instruction address, in @var{this_frame}'s |
| 3299 | caller, at which execution will resume after @var{this_frame} returns. |
| 3300 | This is commonly refered to as the return address. |
| 3301 | |
| 3302 | The implementation, which must be frame agnostic (work with any frame), |
| 3303 | is typically no more than: |
| 3304 | |
| 3305 | @smallexample |
| 3306 | ULONGEST pc; |
| 3307 | frame_unwind_unsigned_register (this_frame, D10V_PC_REGNUM, &pc); |
| 3308 | return d10v_make_iaddr (pc); |
| 3309 | @end smallexample |
| 3310 | |
| 3311 | @noindent |
| 3312 | @xref{DEPRECATED_FRAME_SAVED_PC}, which this method replaces. |
| 3313 | |
| 3314 | @item FUNCTION_EPILOGUE_SIZE |
| 3315 | @findex FUNCTION_EPILOGUE_SIZE |
| 3316 | For some COFF targets, the @code{x_sym.x_misc.x_fsize} field of the |
| 3317 | function end symbol is 0. For such targets, you must define |
| 3318 | @code{FUNCTION_EPILOGUE_SIZE} to expand into the standard size of a |
| 3319 | function's epilogue. |
| 3320 | |
| 3321 | @item FUNCTION_START_OFFSET |
| 3322 | @findex FUNCTION_START_OFFSET |
| 3323 | An integer, giving the offset in bytes from a function's address (as |
| 3324 | used in the values of symbols, function pointers, etc.), and the |
| 3325 | function's first genuine instruction. |
| 3326 | |
| 3327 | This is zero on almost all machines: the function's address is usually |
| 3328 | the address of its first instruction. However, on the VAX, for example, |
| 3329 | each function starts with two bytes containing a bitmask indicating |
| 3330 | which registers to save upon entry to the function. The VAX @code{call} |
| 3331 | instructions check this value, and save the appropriate registers |
| 3332 | automatically. Thus, since the offset from the function's address to |
| 3333 | its first instruction is two bytes, @code{FUNCTION_START_OFFSET} would |
| 3334 | be 2 on the VAX. |
| 3335 | |
| 3336 | @item GCC_COMPILED_FLAG_SYMBOL |
| 3337 | @itemx GCC2_COMPILED_FLAG_SYMBOL |
| 3338 | @findex GCC2_COMPILED_FLAG_SYMBOL |
| 3339 | @findex GCC_COMPILED_FLAG_SYMBOL |
| 3340 | If defined, these are the names of the symbols that @value{GDBN} will |
| 3341 | look for to detect that GCC compiled the file. The default symbols |
| 3342 | are @code{gcc_compiled.} and @code{gcc2_compiled.}, |
| 3343 | respectively. (Currently only defined for the Delta 68.) |
| 3344 | |
| 3345 | @item @value{GDBN}_MULTI_ARCH |
| 3346 | @findex @value{GDBN}_MULTI_ARCH |
| 3347 | If defined and non-zero, enables support for multiple architectures |
| 3348 | within @value{GDBN}. |
| 3349 | |
| 3350 | This support can be enabled at two levels. At level one, only |
| 3351 | definitions for previously undefined macros are provided; at level two, |
| 3352 | a multi-arch definition of all architecture dependent macros will be |
| 3353 | defined. |
| 3354 | |
| 3355 | @item @value{GDBN}_TARGET_IS_HPPA |
| 3356 | @findex @value{GDBN}_TARGET_IS_HPPA |
| 3357 | This determines whether horrible kludge code in @file{dbxread.c} and |
| 3358 | @file{partial-stab.h} is used to mangle multiple-symbol-table files from |
| 3359 | HPPA's. This should all be ripped out, and a scheme like @file{elfread.c} |
| 3360 | used instead. |
| 3361 | |
| 3362 | @item GET_LONGJMP_TARGET |
| 3363 | @findex GET_LONGJMP_TARGET |
| 3364 | For most machines, this is a target-dependent parameter. On the |
| 3365 | DECstation and the Iris, this is a native-dependent parameter, since |
| 3366 | the header file @file{setjmp.h} is needed to define it. |
| 3367 | |
| 3368 | This macro determines the target PC address that @code{longjmp} will jump to, |
| 3369 | assuming that we have just stopped at a @code{longjmp} breakpoint. It takes a |
| 3370 | @code{CORE_ADDR *} as argument, and stores the target PC value through this |
| 3371 | pointer. It examines the current state of the machine as needed. |
| 3372 | |
| 3373 | @item DEPRECATED_GET_SAVED_REGISTER |
| 3374 | @findex DEPRECATED_GET_SAVED_REGISTER |
| 3375 | Define this if you need to supply your own definition for the function |
| 3376 | @code{DEPRECATED_GET_SAVED_REGISTER}. |
| 3377 | |
| 3378 | @item IBM6000_TARGET |
| 3379 | @findex IBM6000_TARGET |
| 3380 | Shows that we are configured for an IBM RS/6000 target. This |
| 3381 | conditional should be eliminated (FIXME) and replaced by |
| 3382 | feature-specific macros. It was introduced in a haste and we are |
| 3383 | repenting at leisure. |
| 3384 | |
| 3385 | @item I386_USE_GENERIC_WATCHPOINTS |
| 3386 | An x86-based target can define this to use the generic x86 watchpoint |
| 3387 | support; see @ref{Algorithms, I386_USE_GENERIC_WATCHPOINTS}. |
| 3388 | |
| 3389 | @item SYMBOLS_CAN_START_WITH_DOLLAR |
| 3390 | @findex SYMBOLS_CAN_START_WITH_DOLLAR |
| 3391 | Some systems have routines whose names start with @samp{$}. Giving this |
| 3392 | macro a non-zero value tells @value{GDBN}'s expression parser to check for such |
| 3393 | routines when parsing tokens that begin with @samp{$}. |
| 3394 | |
| 3395 | On HP-UX, certain system routines (millicode) have names beginning with |
| 3396 | @samp{$} or @samp{$$}. For example, @code{$$dyncall} is a millicode |
| 3397 | routine that handles inter-space procedure calls on PA-RISC. |
| 3398 | |
| 3399 | @item DEPRECATED_INIT_EXTRA_FRAME_INFO (@var{fromleaf}, @var{frame}) |
| 3400 | @findex DEPRECATED_INIT_EXTRA_FRAME_INFO |
| 3401 | If additional information about the frame is required this should be |
| 3402 | stored in @code{frame->extra_info}. Space for @code{frame->extra_info} |
| 3403 | is allocated using @code{frame_extra_info_zalloc}. |
| 3404 | |
| 3405 | @item DEPRECATED_INIT_FRAME_PC (@var{fromleaf}, @var{prev}) |
| 3406 | @findex DEPRECATED_INIT_FRAME_PC |
| 3407 | This is a C statement that sets the pc of the frame pointed to by |
| 3408 | @var{prev}. [By default...] |
| 3409 | |
| 3410 | @item INNER_THAN (@var{lhs}, @var{rhs}) |
| 3411 | @findex INNER_THAN |
| 3412 | Returns non-zero if stack address @var{lhs} is inner than (nearer to the |
| 3413 | stack top) stack address @var{rhs}. Define this as @code{lhs < rhs} if |
| 3414 | the target's stack grows downward in memory, or @code{lhs > rsh} if the |
| 3415 | stack grows upward. |
| 3416 | |
| 3417 | @item gdbarch_in_function_epilogue_p (@var{gdbarch}, @var{pc}) |
| 3418 | @findex gdbarch_in_function_epilogue_p |
| 3419 | Returns non-zero if the given @var{pc} is in the epilogue of a function. |
| 3420 | The epilogue of a function is defined as the part of a function where |
| 3421 | the stack frame of the function already has been destroyed up to the |
| 3422 | final `return from function call' instruction. |
| 3423 | |
| 3424 | @item SIGTRAMP_START (@var{pc}) |
| 3425 | @findex SIGTRAMP_START |
| 3426 | @itemx SIGTRAMP_END (@var{pc}) |
| 3427 | @findex SIGTRAMP_END |
| 3428 | Define these to be the start and end address of the @code{sigtramp} for the |
| 3429 | given @var{pc}. On machines where the address is just a compile time |
| 3430 | constant, the macro expansion will typically just ignore the supplied |
| 3431 | @var{pc}. |
| 3432 | |
| 3433 | @item IN_SOLIB_CALL_TRAMPOLINE (@var{pc}, @var{name}) |
| 3434 | @findex IN_SOLIB_CALL_TRAMPOLINE |
| 3435 | Define this to evaluate to nonzero if the program is stopped in the |
| 3436 | trampoline that connects to a shared library. |
| 3437 | |
| 3438 | @item IN_SOLIB_RETURN_TRAMPOLINE (@var{pc}, @var{name}) |
| 3439 | @findex IN_SOLIB_RETURN_TRAMPOLINE |
| 3440 | Define this to evaluate to nonzero if the program is stopped in the |
| 3441 | trampoline that returns from a shared library. |
| 3442 | |
| 3443 | @item IN_SOLIB_DYNSYM_RESOLVE_CODE (@var{pc}) |
| 3444 | @findex IN_SOLIB_DYNSYM_RESOLVE_CODE |
| 3445 | Define this to evaluate to nonzero if the program is stopped in the |
| 3446 | dynamic linker. |
| 3447 | |
| 3448 | @item SKIP_SOLIB_RESOLVER (@var{pc}) |
| 3449 | @findex SKIP_SOLIB_RESOLVER |
| 3450 | Define this to evaluate to the (nonzero) address at which execution |
| 3451 | should continue to get past the dynamic linker's symbol resolution |
| 3452 | function. A zero value indicates that it is not important or necessary |
| 3453 | to set a breakpoint to get through the dynamic linker and that single |
| 3454 | stepping will suffice. |
| 3455 | |
| 3456 | @item INTEGER_TO_ADDRESS (@var{type}, @var{buf}) |
| 3457 | @findex INTEGER_TO_ADDRESS |
| 3458 | @cindex converting integers to addresses |
| 3459 | Define this when the architecture needs to handle non-pointer to address |
| 3460 | conversions specially. Converts that value to an address according to |
| 3461 | the current architectures conventions. |
| 3462 | |
| 3463 | @emph{Pragmatics: When the user copies a well defined expression from |
| 3464 | their source code and passes it, as a parameter, to @value{GDBN}'s |
| 3465 | @code{print} command, they should get the same value as would have been |
| 3466 | computed by the target program. Any deviation from this rule can cause |
| 3467 | major confusion and annoyance, and needs to be justified carefully. In |
| 3468 | other words, @value{GDBN} doesn't really have the freedom to do these |
| 3469 | conversions in clever and useful ways. It has, however, been pointed |
| 3470 | out that users aren't complaining about how @value{GDBN} casts integers |
| 3471 | to pointers; they are complaining that they can't take an address from a |
| 3472 | disassembly listing and give it to @code{x/i}. Adding an architecture |
| 3473 | method like @code{INTEGER_TO_ADDRESS} certainly makes it possible for |
| 3474 | @value{GDBN} to ``get it right'' in all circumstances.} |
| 3475 | |
| 3476 | @xref{Target Architecture Definition, , Pointers Are Not Always |
| 3477 | Addresses}. |
| 3478 | |
| 3479 | @item NEED_TEXT_START_END |
| 3480 | @findex NEED_TEXT_START_END |
| 3481 | Define this if @value{GDBN} should determine the start and end addresses of the |
| 3482 | text section. (Seems dubious.) |
| 3483 | |
| 3484 | @item NO_HIF_SUPPORT |
| 3485 | @findex NO_HIF_SUPPORT |
| 3486 | (Specific to the a29k.) |
| 3487 | |
| 3488 | @item POINTER_TO_ADDRESS (@var{type}, @var{buf}) |
| 3489 | @findex POINTER_TO_ADDRESS |
| 3490 | Assume that @var{buf} holds a pointer of type @var{type}, in the |
| 3491 | appropriate format for the current architecture. Return the byte |
| 3492 | address the pointer refers to. |
| 3493 | @xref{Target Architecture Definition, , Pointers Are Not Always Addresses}. |
| 3494 | |
| 3495 | @item REGISTER_CONVERTIBLE (@var{reg}) |
| 3496 | @findex REGISTER_CONVERTIBLE |
| 3497 | Return non-zero if @var{reg} uses different raw and virtual formats. |
| 3498 | @xref{Target Architecture Definition, , Raw and Virtual Register Representations}. |
| 3499 | |
| 3500 | @item REGISTER_TO_VALUE(@var{regnum}, @var{type}, @var{from}, @var{to}) |
| 3501 | @findex REGISTER_TO_VALUE |
| 3502 | Convert the raw contents of register @var{regnum} into a value of type |
| 3503 | @var{type}. |
| 3504 | @xref{Target Architecture Definition, , Using Different Register and Memory Data Representations}. |
| 3505 | |
| 3506 | @item REGISTER_RAW_SIZE (@var{reg}) |
| 3507 | @findex REGISTER_RAW_SIZE |
| 3508 | Return the raw size of @var{reg}; defaults to the size of the register's |
| 3509 | virtual type. |
| 3510 | @xref{Target Architecture Definition, , Raw and Virtual Register Representations}. |
| 3511 | |
| 3512 | @item register_reggroup_p (@var{gdbarch}, @var{regnum}, @var{reggroup}) |
| 3513 | @findex register_reggroup_p |
| 3514 | @cindex register groups |
| 3515 | Return non-zero if register @var{regnum} is a member of the register |
| 3516 | group @var{reggroup}. |
| 3517 | |
| 3518 | By default, registers are grouped as follows: |
| 3519 | |
| 3520 | @table @code |
| 3521 | @item float_reggroup |
| 3522 | Any register with a valid name and a floating-point type. |
| 3523 | @item vector_reggroup |
| 3524 | Any register with a valid name and a vector type. |
| 3525 | @item general_reggroup |
| 3526 | Any register with a valid name and a type other than vector or |
| 3527 | floating-point. @samp{float_reggroup}. |
| 3528 | @item save_reggroup |
| 3529 | @itemx restore_reggroup |
| 3530 | @itemx all_reggroup |
| 3531 | Any register with a valid name. |
| 3532 | @end table |
| 3533 | |
| 3534 | @item REGISTER_VIRTUAL_SIZE (@var{reg}) |
| 3535 | @findex REGISTER_VIRTUAL_SIZE |
| 3536 | Return the virtual size of @var{reg}; defaults to the size of the |
| 3537 | register's virtual type. |
| 3538 | Return the virtual size of @var{reg}. |
| 3539 | @xref{Target Architecture Definition, , Raw and Virtual Register Representations}. |
| 3540 | |
| 3541 | @item REGISTER_VIRTUAL_TYPE (@var{reg}) |
| 3542 | @findex REGISTER_VIRTUAL_TYPE |
| 3543 | Return the virtual type of @var{reg}. |
| 3544 | @xref{Target Architecture Definition, , Raw and Virtual Register Representations}. |
| 3545 | |
| 3546 | @item struct type *register_type (@var{gdbarch}, @var{reg}) |
| 3547 | @findex register_type |
| 3548 | If defined, return the type of register @var{reg}. This function |
| 3549 | superseeds @code{REGISTER_VIRTUAL_TYPE}. @xref{Target Architecture |
| 3550 | Definition, , Raw and Virtual Register Representations}. |
| 3551 | |
| 3552 | @item REGISTER_CONVERT_TO_VIRTUAL(@var{reg}, @var{type}, @var{from}, @var{to}) |
| 3553 | @findex REGISTER_CONVERT_TO_VIRTUAL |
| 3554 | Convert the value of register @var{reg} from its raw form to its virtual |
| 3555 | form. |
| 3556 | @xref{Target Architecture Definition, , Raw and Virtual Register Representations}. |
| 3557 | |
| 3558 | @item REGISTER_CONVERT_TO_RAW(@var{type}, @var{reg}, @var{from}, @var{to}) |
| 3559 | @findex REGISTER_CONVERT_TO_RAW |
| 3560 | Convert the value of register @var{reg} from its virtual form to its raw |
| 3561 | form. |
| 3562 | @xref{Target Architecture Definition, , Raw and Virtual Register Representations}. |
| 3563 | |
| 3564 | @item RETURN_VALUE_ON_STACK(@var{type}) |
| 3565 | @findex RETURN_VALUE_ON_STACK |
| 3566 | @cindex returning structures by value |
| 3567 | @cindex structures, returning by value |
| 3568 | |
| 3569 | Return non-zero if values of type TYPE are returned on the stack, using |
| 3570 | the ``struct convention'' (i.e., the caller provides a pointer to a |
| 3571 | buffer in which the callee should store the return value). This |
| 3572 | controls how the @samp{finish} command finds a function's return value, |
| 3573 | and whether an inferior function call reserves space on the stack for |
| 3574 | the return value. |
| 3575 | |
| 3576 | The full logic @value{GDBN} uses here is kind of odd. |
| 3577 | |
| 3578 | @itemize @bullet |
| 3579 | @item |
| 3580 | If the type being returned by value is not a structure, union, or array, |
| 3581 | and @code{RETURN_VALUE_ON_STACK} returns zero, then @value{GDBN} |
| 3582 | concludes the value is not returned using the struct convention. |
| 3583 | |
| 3584 | @item |
| 3585 | Otherwise, @value{GDBN} calls @code{USE_STRUCT_CONVENTION} (see below). |
| 3586 | If that returns non-zero, @value{GDBN} assumes the struct convention is |
| 3587 | in use. |
| 3588 | @end itemize |
| 3589 | |
| 3590 | In other words, to indicate that a given type is returned by value using |
| 3591 | the struct convention, that type must be either a struct, union, array, |
| 3592 | or something @code{RETURN_VALUE_ON_STACK} likes, @emph{and} something |
| 3593 | that @code{USE_STRUCT_CONVENTION} likes. |
| 3594 | |
| 3595 | Note that, in C and C@t{++}, arrays are never returned by value. In those |
| 3596 | languages, these predicates will always see a pointer type, never an |
| 3597 | array type. All the references above to arrays being returned by value |
| 3598 | apply only to other languages. |
| 3599 | |
| 3600 | @item SOFTWARE_SINGLE_STEP_P() |
| 3601 | @findex SOFTWARE_SINGLE_STEP_P |
| 3602 | Define this as 1 if the target does not have a hardware single-step |
| 3603 | mechanism. The macro @code{SOFTWARE_SINGLE_STEP} must also be defined. |
| 3604 | |
| 3605 | @item SOFTWARE_SINGLE_STEP(@var{signal}, @var{insert_breapoints_p}) |
| 3606 | @findex SOFTWARE_SINGLE_STEP |
| 3607 | A function that inserts or removes (depending on |
| 3608 | @var{insert_breapoints_p}) breakpoints at each possible destinations of |
| 3609 | the next instruction. See @file{sparc-tdep.c} and @file{rs6000-tdep.c} |
| 3610 | for examples. |
| 3611 | |
| 3612 | @item SOFUN_ADDRESS_MAYBE_MISSING |
| 3613 | @findex SOFUN_ADDRESS_MAYBE_MISSING |
| 3614 | Somebody clever observed that, the more actual addresses you have in the |
| 3615 | debug information, the more time the linker has to spend relocating |
| 3616 | them. So whenever there's some other way the debugger could find the |
| 3617 | address it needs, you should omit it from the debug info, to make |
| 3618 | linking faster. |
| 3619 | |
| 3620 | @code{SOFUN_ADDRESS_MAYBE_MISSING} indicates that a particular set of |
| 3621 | hacks of this sort are in use, affecting @code{N_SO} and @code{N_FUN} |
| 3622 | entries in stabs-format debugging information. @code{N_SO} stabs mark |
| 3623 | the beginning and ending addresses of compilation units in the text |
| 3624 | segment. @code{N_FUN} stabs mark the starts and ends of functions. |
| 3625 | |
| 3626 | @code{SOFUN_ADDRESS_MAYBE_MISSING} means two things: |
| 3627 | |
| 3628 | @itemize @bullet |
| 3629 | @item |
| 3630 | @code{N_FUN} stabs have an address of zero. Instead, you should find the |
| 3631 | addresses where the function starts by taking the function name from |
| 3632 | the stab, and then looking that up in the minsyms (the |
| 3633 | linker/assembler symbol table). In other words, the stab has the |
| 3634 | name, and the linker/assembler symbol table is the only place that carries |
| 3635 | the address. |
| 3636 | |
| 3637 | @item |
| 3638 | @code{N_SO} stabs have an address of zero, too. You just look at the |
| 3639 | @code{N_FUN} stabs that appear before and after the @code{N_SO} stab, |
| 3640 | and guess the starting and ending addresses of the compilation unit from |
| 3641 | them. |
| 3642 | @end itemize |
| 3643 | |
| 3644 | @item PCC_SOL_BROKEN |
| 3645 | @findex PCC_SOL_BROKEN |
| 3646 | (Used only in the Convex target.) |
| 3647 | |
| 3648 | @item PC_IN_SIGTRAMP (@var{pc}, @var{name}) |
| 3649 | @findex PC_IN_SIGTRAMP |
| 3650 | @cindex sigtramp |
| 3651 | The @dfn{sigtramp} is a routine that the kernel calls (which then calls |
| 3652 | the signal handler). On most machines it is a library routine that is |
| 3653 | linked into the executable. |
| 3654 | |
| 3655 | This function, given a program counter value in @var{pc} and the |
| 3656 | (possibly NULL) name of the function in which that @var{pc} resides, |
| 3657 | returns nonzero if the @var{pc} and/or @var{name} show that we are in |
| 3658 | sigtramp. |
| 3659 | |
| 3660 | @item PC_LOAD_SEGMENT |
| 3661 | @findex PC_LOAD_SEGMENT |
| 3662 | If defined, print information about the load segment for the program |
| 3663 | counter. (Defined only for the RS/6000.) |
| 3664 | |
| 3665 | @item PC_REGNUM |
| 3666 | @findex PC_REGNUM |
| 3667 | If the program counter is kept in a register, then define this macro to |
| 3668 | be the number (greater than or equal to zero) of that register. |
| 3669 | |
| 3670 | This should only need to be defined if @code{TARGET_READ_PC} and |
| 3671 | @code{TARGET_WRITE_PC} are not defined. |
| 3672 | |
| 3673 | @item NPC_REGNUM |
| 3674 | @findex NPC_REGNUM |
| 3675 | The number of the ``next program counter'' register, if defined. |
| 3676 | |
| 3677 | @item PARM_BOUNDARY |
| 3678 | @findex PARM_BOUNDARY |
| 3679 | If non-zero, round arguments to a boundary of this many bits before |
| 3680 | pushing them on the stack. |
| 3681 | |
| 3682 | @item PRINT_TYPELESS_INTEGER |
| 3683 | @findex PRINT_TYPELESS_INTEGER |
| 3684 | This is an obscure substitute for @code{print_longest} that seems to |
| 3685 | have been defined for the Convex target. |
| 3686 | |
| 3687 | @item PROCESS_LINENUMBER_HOOK |
| 3688 | @findex PROCESS_LINENUMBER_HOOK |
| 3689 | A hook defined for XCOFF reading. |
| 3690 | |
| 3691 | @item PROLOGUE_FIRSTLINE_OVERLAP |
| 3692 | @findex PROLOGUE_FIRSTLINE_OVERLAP |
| 3693 | (Only used in unsupported Convex configuration.) |
| 3694 | |
| 3695 | @item PS_REGNUM |
| 3696 | @findex PS_REGNUM |
| 3697 | If defined, this is the number of the processor status register. (This |
| 3698 | definition is only used in generic code when parsing "$ps".) |
| 3699 | |
| 3700 | @item DEPRECATED_POP_FRAME |
| 3701 | @findex DEPRECATED_POP_FRAME |
| 3702 | @findex frame_pop |
| 3703 | If defined, used by @code{frame_pop} to remove a stack frame. This |
| 3704 | method has been superseeded by generic code. |
| 3705 | |
| 3706 | @item push_dummy_call (@var{gdbarch}, @var{regcache}, @var{dummy_addr}, @var{nargs}, @var{args}, @var{sp}, @var{struct_return}, @var{struct_addr}) |
| 3707 | @findex push_dummy_call |
| 3708 | @findex DEPRECATED_PUSH_ARGUMENTS. |
| 3709 | @anchor{push_dummy_call} |
| 3710 | Define this to push the dummy frame's call to the inferior function onto |
| 3711 | the stack. In addition to pushing @var{nargs}, the code should push |
| 3712 | @var{struct_addr} (when @var{struct_return}), and the return value (in |
| 3713 | the call dummy at @var{dummy_addr}). |
| 3714 | |
| 3715 | Returns the updated top-of-stack pointer. |
| 3716 | |
| 3717 | This method replaces @code{DEPRECATED_PUSH_ARGUMENTS}. |
| 3718 | |
| 3719 | @item DEPRECATED_PUSH_DUMMY_FRAME |
| 3720 | @findex DEPRECATED_PUSH_DUMMY_FRAME |
| 3721 | Used in @samp{call_function_by_hand} to create an artificial stack frame. |
| 3722 | |
| 3723 | @item REGISTER_BYTES |
| 3724 | @findex REGISTER_BYTES |
| 3725 | The total amount of space needed to store @value{GDBN}'s copy of the machine's |
| 3726 | register state. |
| 3727 | |
| 3728 | @item REGISTER_NAME(@var{i}) |
| 3729 | @findex REGISTER_NAME |
| 3730 | Return the name of register @var{i} as a string. May return @code{NULL} |
| 3731 | or @code{NUL} to indicate that register @var{i} is not valid. |
| 3732 | |
| 3733 | @item REGISTER_NAMES |
| 3734 | @findex REGISTER_NAMES |
| 3735 | Deprecated in favor of @code{REGISTER_NAME}. |
| 3736 | |
| 3737 | @item REG_STRUCT_HAS_ADDR (@var{gcc_p}, @var{type}) |
| 3738 | @findex REG_STRUCT_HAS_ADDR |
| 3739 | Define this to return 1 if the given type will be passed by pointer |
| 3740 | rather than directly. |
| 3741 | |
| 3742 | @item SAVE_DUMMY_FRAME_TOS (@var{sp}) |
| 3743 | @findex SAVE_DUMMY_FRAME_TOS |
| 3744 | @anchor{SAVE_DUMMY_FRAME_TOS} Used in @samp{call_function_by_hand} to |
| 3745 | notify the target dependent code of the top-of-stack value that will be |
| 3746 | passed to the the inferior code. This is the value of the @code{SP} |
| 3747 | after both the dummy frame and space for parameters/results have been |
| 3748 | allocated on the stack. @xref{unwind_dummy_id}. |
| 3749 | |
| 3750 | @item SDB_REG_TO_REGNUM |
| 3751 | @findex SDB_REG_TO_REGNUM |
| 3752 | Define this to convert sdb register numbers into @value{GDBN} regnums. If not |
| 3753 | defined, no conversion will be done. |
| 3754 | |
| 3755 | @item SKIP_PERMANENT_BREAKPOINT |
| 3756 | @findex SKIP_PERMANENT_BREAKPOINT |
| 3757 | Advance the inferior's PC past a permanent breakpoint. @value{GDBN} normally |
| 3758 | steps over a breakpoint by removing it, stepping one instruction, and |
| 3759 | re-inserting the breakpoint. However, permanent breakpoints are |
| 3760 | hardwired into the inferior, and can't be removed, so this strategy |
| 3761 | doesn't work. Calling @code{SKIP_PERMANENT_BREAKPOINT} adjusts the processor's |
| 3762 | state so that execution will resume just after the breakpoint. This |
| 3763 | macro does the right thing even when the breakpoint is in the delay slot |
| 3764 | of a branch or jump. |
| 3765 | |
| 3766 | @item SKIP_PROLOGUE (@var{pc}) |
| 3767 | @findex SKIP_PROLOGUE |
| 3768 | A C expression that returns the address of the ``real'' code beyond the |
| 3769 | function entry prologue found at @var{pc}. |
| 3770 | |
| 3771 | @item SKIP_TRAMPOLINE_CODE (@var{pc}) |
| 3772 | @findex SKIP_TRAMPOLINE_CODE |
| 3773 | If the target machine has trampoline code that sits between callers and |
| 3774 | the functions being called, then define this macro to return a new PC |
| 3775 | that is at the start of the real function. |
| 3776 | |
| 3777 | @item SP_REGNUM |
| 3778 | @findex SP_REGNUM |
| 3779 | If the stack-pointer is kept in a register, then define this macro to be |
| 3780 | the number (greater than or equal to zero) of that register. |
| 3781 | |
| 3782 | This should only need to be defined if @code{TARGET_WRITE_SP} and |
| 3783 | @code{TARGET_WRITE_SP} are not defined. |
| 3784 | |
| 3785 | @item STAB_REG_TO_REGNUM |
| 3786 | @findex STAB_REG_TO_REGNUM |
| 3787 | Define this to convert stab register numbers (as gotten from `r' |
| 3788 | declarations) into @value{GDBN} regnums. If not defined, no conversion will be |
| 3789 | done. |
| 3790 | |
| 3791 | @item STACK_ALIGN (@var{addr}) |
| 3792 | @anchor{STACK_ALIGN} |
| 3793 | @findex STACK_ALIGN |
| 3794 | Define this to increase @var{addr} so that it meets the alignment |
| 3795 | requirements for the processor's stack. |
| 3796 | |
| 3797 | Unlike @ref{frame_align}, this function always adjusts @var{addr} |
| 3798 | upwards. |
| 3799 | |
| 3800 | By default, no stack alignment is performed. |
| 3801 | |
| 3802 | @item STEP_SKIPS_DELAY (@var{addr}) |
| 3803 | @findex STEP_SKIPS_DELAY |
| 3804 | Define this to return true if the address is of an instruction with a |
| 3805 | delay slot. If a breakpoint has been placed in the instruction's delay |
| 3806 | slot, @value{GDBN} will single-step over that instruction before resuming |
| 3807 | normally. Currently only defined for the Mips. |
| 3808 | |
| 3809 | @item STORE_RETURN_VALUE (@var{type}, @var{regcache}, @var{valbuf}) |
| 3810 | @findex STORE_RETURN_VALUE |
| 3811 | A C expression that writes the function return value, found in |
| 3812 | @var{valbuf}, into the @var{regcache}. @var{type} is the type of the |
| 3813 | value that is to be returned. |
| 3814 | |
| 3815 | @item SUN_FIXED_LBRAC_BUG |
| 3816 | @findex SUN_FIXED_LBRAC_BUG |
| 3817 | (Used only for Sun-3 and Sun-4 targets.) |
| 3818 | |
| 3819 | @item SYMBOL_RELOADING_DEFAULT |
| 3820 | @findex SYMBOL_RELOADING_DEFAULT |
| 3821 | The default value of the ``symbol-reloading'' variable. (Never defined in |
| 3822 | current sources.) |
| 3823 | |
| 3824 | @item TARGET_CHAR_BIT |
| 3825 | @findex TARGET_CHAR_BIT |
| 3826 | Number of bits in a char; defaults to 8. |
| 3827 | |
| 3828 | @item TARGET_CHAR_SIGNED |
| 3829 | @findex TARGET_CHAR_SIGNED |
| 3830 | Non-zero if @code{char} is normally signed on this architecture; zero if |
| 3831 | it should be unsigned. |
| 3832 | |
| 3833 | The ISO C standard requires the compiler to treat @code{char} as |
| 3834 | equivalent to either @code{signed char} or @code{unsigned char}; any |
| 3835 | character in the standard execution set is supposed to be positive. |
| 3836 | Most compilers treat @code{char} as signed, but @code{char} is unsigned |
| 3837 | on the IBM S/390, RS6000, and PowerPC targets. |
| 3838 | |
| 3839 | @item TARGET_COMPLEX_BIT |
| 3840 | @findex TARGET_COMPLEX_BIT |
| 3841 | Number of bits in a complex number; defaults to @code{2 * TARGET_FLOAT_BIT}. |
| 3842 | |
| 3843 | At present this macro is not used. |
| 3844 | |
| 3845 | @item TARGET_DOUBLE_BIT |
| 3846 | @findex TARGET_DOUBLE_BIT |
| 3847 | Number of bits in a double float; defaults to @code{8 * TARGET_CHAR_BIT}. |
| 3848 | |
| 3849 | @item TARGET_DOUBLE_COMPLEX_BIT |
| 3850 | @findex TARGET_DOUBLE_COMPLEX_BIT |
| 3851 | Number of bits in a double complex; defaults to @code{2 * TARGET_DOUBLE_BIT}. |
| 3852 | |
| 3853 | At present this macro is not used. |
| 3854 | |
| 3855 | @item TARGET_FLOAT_BIT |
| 3856 | @findex TARGET_FLOAT_BIT |
| 3857 | Number of bits in a float; defaults to @code{4 * TARGET_CHAR_BIT}. |
| 3858 | |
| 3859 | @item TARGET_INT_BIT |
| 3860 | @findex TARGET_INT_BIT |
| 3861 | Number of bits in an integer; defaults to @code{4 * TARGET_CHAR_BIT}. |
| 3862 | |
| 3863 | @item TARGET_LONG_BIT |
| 3864 | @findex TARGET_LONG_BIT |
| 3865 | Number of bits in a long integer; defaults to @code{4 * TARGET_CHAR_BIT}. |
| 3866 | |
| 3867 | @item TARGET_LONG_DOUBLE_BIT |
| 3868 | @findex TARGET_LONG_DOUBLE_BIT |
| 3869 | Number of bits in a long double float; |
| 3870 | defaults to @code{2 * TARGET_DOUBLE_BIT}. |
| 3871 | |
| 3872 | @item TARGET_LONG_LONG_BIT |
| 3873 | @findex TARGET_LONG_LONG_BIT |
| 3874 | Number of bits in a long long integer; defaults to @code{2 * TARGET_LONG_BIT}. |
| 3875 | |
| 3876 | @item TARGET_PTR_BIT |
| 3877 | @findex TARGET_PTR_BIT |
| 3878 | Number of bits in a pointer; defaults to @code{TARGET_INT_BIT}. |
| 3879 | |
| 3880 | @item TARGET_SHORT_BIT |
| 3881 | @findex TARGET_SHORT_BIT |
| 3882 | Number of bits in a short integer; defaults to @code{2 * TARGET_CHAR_BIT}. |
| 3883 | |
| 3884 | @item TARGET_READ_PC |
| 3885 | @findex TARGET_READ_PC |
| 3886 | @itemx TARGET_WRITE_PC (@var{val}, @var{pid}) |
| 3887 | @findex TARGET_WRITE_PC |
| 3888 | @itemx TARGET_READ_SP |
| 3889 | @findex TARGET_READ_SP |
| 3890 | @itemx TARGET_WRITE_SP |
| 3891 | @findex TARGET_WRITE_SP |
| 3892 | @itemx TARGET_READ_FP |
| 3893 | @findex TARGET_READ_FP |
| 3894 | @findex read_pc |
| 3895 | @findex write_pc |
| 3896 | @findex read_sp |
| 3897 | @findex read_fp |
| 3898 | These change the behavior of @code{read_pc}, @code{write_pc}, |
| 3899 | @code{read_sp} and @code{read_fp}. For most targets, these may be left |
| 3900 | undefined. @value{GDBN} will call the read and write register functions |
| 3901 | with the relevant @code{_REGNUM} argument. |
| 3902 | |
| 3903 | These macros are useful when a target keeps one of these registers in a |
| 3904 | hard to get at place; for example, part in a segment register and part |
| 3905 | in an ordinary register. |
| 3906 | |
| 3907 | @item TARGET_VIRTUAL_FRAME_POINTER(@var{pc}, @var{regp}, @var{offsetp}) |
| 3908 | @findex TARGET_VIRTUAL_FRAME_POINTER |
| 3909 | Returns a @code{(register, offset)} pair representing the virtual |
| 3910 | frame pointer in use at the code address @var{pc}. If virtual |
| 3911 | frame pointers are not used, a default definition simply returns |
| 3912 | @code{FP_REGNUM}, with an offset of zero. |
| 3913 | |
| 3914 | @item TARGET_HAS_HARDWARE_WATCHPOINTS |
| 3915 | If non-zero, the target has support for hardware-assisted |
| 3916 | watchpoints. @xref{Algorithms, watchpoints}, for more details and |
| 3917 | other related macros. |
| 3918 | |
| 3919 | @item TARGET_PRINT_INSN (@var{addr}, @var{info}) |
| 3920 | @findex TARGET_PRINT_INSN |
| 3921 | This is the function used by @value{GDBN} to print an assembly |
| 3922 | instruction. It prints the instruction at address @var{addr} in |
| 3923 | debugged memory and returns the length of the instruction, in bytes. If |
| 3924 | a target doesn't define its own printing routine, it defaults to an |
| 3925 | accessor function for the global pointer @code{tm_print_insn}. This |
| 3926 | usually points to a function in the @code{opcodes} library (@pxref{Support |
| 3927 | Libraries, ,Opcodes}). @var{info} is a structure (of type |
| 3928 | @code{disassemble_info}) defined in @file{include/dis-asm.h} used to |
| 3929 | pass information to the instruction decoding routine. |
| 3930 | |
| 3931 | @item struct frame_id unwind_dummy_id (struct frame_info *@var{frame}) |
| 3932 | @findex unwind_dummy_id |
| 3933 | @anchor{unwind_dummy_id} Given @var{frame} return a @code{struct |
| 3934 | frame_id} that uniquely identifies an inferior function call's dummy |
| 3935 | frame. The value returned must match the dummy frame stack value |
| 3936 | previously saved using @code{SAVE_DUMMY_FRAME_TOS}. |
| 3937 | @xref{SAVE_DUMMY_FRAME_TOS}. |
| 3938 | |
| 3939 | @item USE_STRUCT_CONVENTION (@var{gcc_p}, @var{type}) |
| 3940 | @findex USE_STRUCT_CONVENTION |
| 3941 | If defined, this must be an expression that is nonzero if a value of the |
| 3942 | given @var{type} being returned from a function must have space |
| 3943 | allocated for it on the stack. @var{gcc_p} is true if the function |
| 3944 | being considered is known to have been compiled by GCC; this is helpful |
| 3945 | for systems where GCC is known to use different calling convention than |
| 3946 | other compilers. |
| 3947 | |
| 3948 | @item VALUE_TO_REGISTER(@var{type}, @var{regnum}, @var{from}, @var{to}) |
| 3949 | @findex VALUE_TO_REGISTER |
| 3950 | Convert a value of type @var{type} into the raw contents of register |
| 3951 | @var{regnum}'s. |
| 3952 | @xref{Target Architecture Definition, , Using Different Register and Memory Data Representations}. |
| 3953 | |
| 3954 | @item VARIABLES_INSIDE_BLOCK (@var{desc}, @var{gcc_p}) |
| 3955 | @findex VARIABLES_INSIDE_BLOCK |
| 3956 | For dbx-style debugging information, if the compiler puts variable |
| 3957 | declarations inside LBRAC/RBRAC blocks, this should be defined to be |
| 3958 | nonzero. @var{desc} is the value of @code{n_desc} from the |
| 3959 | @code{N_RBRAC} symbol, and @var{gcc_p} is true if @value{GDBN} has noticed the |
| 3960 | presence of either the @code{GCC_COMPILED_SYMBOL} or the |
| 3961 | @code{GCC2_COMPILED_SYMBOL}. By default, this is 0. |
| 3962 | |
| 3963 | @item OS9K_VARIABLES_INSIDE_BLOCK (@var{desc}, @var{gcc_p}) |
| 3964 | @findex OS9K_VARIABLES_INSIDE_BLOCK |
| 3965 | Similarly, for OS/9000. Defaults to 1. |
| 3966 | @end table |
| 3967 | |
| 3968 | Motorola M68K target conditionals. |
| 3969 | |
| 3970 | @ftable @code |
| 3971 | @item BPT_VECTOR |
| 3972 | Define this to be the 4-bit location of the breakpoint trap vector. If |
| 3973 | not defined, it will default to @code{0xf}. |
| 3974 | |
| 3975 | @item REMOTE_BPT_VECTOR |
| 3976 | Defaults to @code{1}. |
| 3977 | |
| 3978 | @item NAME_OF_MALLOC |
| 3979 | @findex NAME_OF_MALLOC |
| 3980 | A string containing the name of the function to call in order to |
| 3981 | allocate some memory in the inferior. The default value is "malloc". |
| 3982 | |
| 3983 | @end ftable |
| 3984 | |
| 3985 | @section Adding a New Target |
| 3986 | |
| 3987 | @cindex adding a target |
| 3988 | The following files add a target to @value{GDBN}: |
| 3989 | |
| 3990 | @table @file |
| 3991 | @vindex TDEPFILES |
| 3992 | @item gdb/config/@var{arch}/@var{ttt}.mt |
| 3993 | Contains a Makefile fragment specific to this target. Specifies what |
| 3994 | object files are needed for target @var{ttt}, by defining |
| 3995 | @samp{TDEPFILES=@dots{}} and @samp{TDEPLIBS=@dots{}}. Also specifies |
| 3996 | the header file which describes @var{ttt}, by defining @samp{TM_FILE= |
| 3997 | tm-@var{ttt}.h}. |
| 3998 | |
| 3999 | You can also define @samp{TM_CFLAGS}, @samp{TM_CLIBS}, @samp{TM_CDEPS}, |
| 4000 | but these are now deprecated, replaced by autoconf, and may go away in |
| 4001 | future versions of @value{GDBN}. |
| 4002 | |
| 4003 | @item gdb/@var{ttt}-tdep.c |
| 4004 | Contains any miscellaneous code required for this target machine. On |
| 4005 | some machines it doesn't exist at all. Sometimes the macros in |
| 4006 | @file{tm-@var{ttt}.h} become very complicated, so they are implemented |
| 4007 | as functions here instead, and the macro is simply defined to call the |
| 4008 | function. This is vastly preferable, since it is easier to understand |
| 4009 | and debug. |
| 4010 | |
| 4011 | @item gdb/@var{arch}-tdep.c |
| 4012 | @itemx gdb/@var{arch}-tdep.h |
| 4013 | This often exists to describe the basic layout of the target machine's |
| 4014 | processor chip (registers, stack, etc.). If used, it is included by |
| 4015 | @file{@var{ttt}-tdep.h}. It can be shared among many targets that use |
| 4016 | the same processor. |
| 4017 | |
| 4018 | @item gdb/config/@var{arch}/tm-@var{ttt}.h |
| 4019 | (@file{tm.h} is a link to this file, created by @code{configure}). Contains |
| 4020 | macro definitions about the target machine's registers, stack frame |
| 4021 | format and instructions. |
| 4022 | |
| 4023 | New targets do not need this file and should not create it. |
| 4024 | |
| 4025 | @item gdb/config/@var{arch}/tm-@var{arch}.h |
| 4026 | This often exists to describe the basic layout of the target machine's |
| 4027 | processor chip (registers, stack, etc.). If used, it is included by |
| 4028 | @file{tm-@var{ttt}.h}. It can be shared among many targets that use the |
| 4029 | same processor. |
| 4030 | |
| 4031 | New targets do not need this file and should not create it. |
| 4032 | |
| 4033 | @end table |
| 4034 | |
| 4035 | If you are adding a new operating system for an existing CPU chip, add a |
| 4036 | @file{config/tm-@var{os}.h} file that describes the operating system |
| 4037 | facilities that are unusual (extra symbol table info; the breakpoint |
| 4038 | instruction needed; etc.). Then write a @file{@var{arch}/tm-@var{os}.h} |
| 4039 | that just @code{#include}s @file{tm-@var{arch}.h} and |
| 4040 | @file{config/tm-@var{os}.h}. |
| 4041 | |
| 4042 | |
| 4043 | @section Converting an existing Target Architecture to Multi-arch |
| 4044 | @cindex converting targets to multi-arch |
| 4045 | |
| 4046 | This section describes the current accepted best practice for converting |
| 4047 | an existing target architecture to the multi-arch framework. |
| 4048 | |
| 4049 | The process consists of generating, testing, posting and committing a |
| 4050 | sequence of patches. Each patch must contain a single change, for |
| 4051 | instance: |
| 4052 | |
| 4053 | @itemize @bullet |
| 4054 | |
| 4055 | @item |
| 4056 | Directly convert a group of functions into macros (the conversion does |
| 4057 | not change the behavior of any of the functions). |
| 4058 | |
| 4059 | @item |
| 4060 | Replace a non-multi-arch with a multi-arch mechanism (e.g., |
| 4061 | @code{FRAME_INFO}). |
| 4062 | |
| 4063 | @item |
| 4064 | Enable multi-arch level one. |
| 4065 | |
| 4066 | @item |
| 4067 | Delete one or more files. |
| 4068 | |
| 4069 | @end itemize |
| 4070 | |
| 4071 | @noindent |
| 4072 | There isn't a size limit on a patch, however, a developer is strongly |
| 4073 | encouraged to keep the patch size down. |
| 4074 | |
| 4075 | Since each patch is well defined, and since each change has been tested |
| 4076 | and shows no regressions, the patches are considered @emph{fairly} |
| 4077 | obvious. Such patches, when submitted by developers listed in the |
| 4078 | @file{MAINTAINERS} file, do not need approval. Occasional steps in the |
| 4079 | process may be more complicated and less clear. The developer is |
| 4080 | expected to use their judgment and is encouraged to seek advice as |
| 4081 | needed. |
| 4082 | |
| 4083 | @subsection Preparation |
| 4084 | |
| 4085 | The first step is to establish control. Build (with @option{-Werror} |
| 4086 | enabled) and test the target so that there is a baseline against which |
| 4087 | the debugger can be compared. |
| 4088 | |
| 4089 | At no stage can the test results regress or @value{GDBN} stop compiling |
| 4090 | with @option{-Werror}. |
| 4091 | |
| 4092 | @subsection Add the multi-arch initialization code |
| 4093 | |
| 4094 | The objective of this step is to establish the basic multi-arch |
| 4095 | framework. It involves |
| 4096 | |
| 4097 | @itemize @bullet |
| 4098 | |
| 4099 | @item |
| 4100 | The addition of a @code{@var{arch}_gdbarch_init} function@footnote{The |
| 4101 | above is from the original example and uses K&R C. @value{GDBN} |
| 4102 | has since converted to ISO C but lets ignore that.} that creates |
| 4103 | the architecture: |
| 4104 | @smallexample |
| 4105 | static struct gdbarch * |
| 4106 | d10v_gdbarch_init (info, arches) |
| 4107 | struct gdbarch_info info; |
| 4108 | struct gdbarch_list *arches; |
| 4109 | @{ |
| 4110 | struct gdbarch *gdbarch; |
| 4111 | /* there is only one d10v architecture */ |
| 4112 | if (arches != NULL) |
| 4113 | return arches->gdbarch; |
| 4114 | gdbarch = gdbarch_alloc (&info, NULL); |
| 4115 | return gdbarch; |
| 4116 | @} |
| 4117 | @end smallexample |
| 4118 | @noindent |
| 4119 | @emph{} |
| 4120 | |
| 4121 | @item |
| 4122 | A per-architecture dump function to print any architecture specific |
| 4123 | information: |
| 4124 | @smallexample |
| 4125 | static void |
| 4126 | mips_dump_tdep (struct gdbarch *current_gdbarch, |
| 4127 | struct ui_file *file) |
| 4128 | @{ |
| 4129 | @dots{} code to print architecture specific info @dots{} |
| 4130 | @} |
| 4131 | @end smallexample |
| 4132 | |
| 4133 | @item |
| 4134 | A change to @code{_initialize_@var{arch}_tdep} to register this new |
| 4135 | architecture: |
| 4136 | @smallexample |
| 4137 | void |
| 4138 | _initialize_mips_tdep (void) |
| 4139 | @{ |
| 4140 | gdbarch_register (bfd_arch_mips, mips_gdbarch_init, |
| 4141 | mips_dump_tdep); |
| 4142 | @end smallexample |
| 4143 | |
| 4144 | @item |
| 4145 | Add the macro @code{GDB_MULTI_ARCH}, defined as 0 (zero), to the file@* |
| 4146 | @file{config/@var{arch}/tm-@var{arch}.h}. |
| 4147 | |
| 4148 | @end itemize |
| 4149 | |
| 4150 | @subsection Update multi-arch incompatible mechanisms |
| 4151 | |
| 4152 | Some mechanisms do not work with multi-arch. They include: |
| 4153 | |
| 4154 | @table @code |
| 4155 | @item EXTRA_FRAME_INFO |
| 4156 | Delete. |
| 4157 | @item FRAME_FIND_SAVED_REGS |
| 4158 | Replaced with @code{DEPRECATED_FRAME_INIT_SAVED_REGS} |
| 4159 | @end table |
| 4160 | |
| 4161 | @noindent |
| 4162 | At this stage you could also consider converting the macros into |
| 4163 | functions. |
| 4164 | |
| 4165 | @subsection Prepare for multi-arch level to one |
| 4166 | |
| 4167 | Temporally set @code{GDB_MULTI_ARCH} to @code{GDB_MULTI_ARCH_PARTIAL} |
| 4168 | and then build and start @value{GDBN} (the change should not be |
| 4169 | committed). @value{GDBN} may not build, and once built, it may die with |
| 4170 | an internal error listing the architecture methods that must be |
| 4171 | provided. |
| 4172 | |
| 4173 | Fix any build problems (patch(es)). |
| 4174 | |
| 4175 | Convert all the architecture methods listed, which are only macros, into |
| 4176 | functions (patch(es)). |
| 4177 | |
| 4178 | Update @code{@var{arch}_gdbarch_init} to set all the missing |
| 4179 | architecture methods and wrap the corresponding macros in @code{#if |
| 4180 | !GDB_MULTI_ARCH} (patch(es)). |
| 4181 | |
| 4182 | @subsection Set multi-arch level one |
| 4183 | |
| 4184 | Change the value of @code{GDB_MULTI_ARCH} to GDB_MULTI_ARCH_PARTIAL (a |
| 4185 | single patch). |
| 4186 | |
| 4187 | Any problems with throwing ``the switch'' should have been fixed |
| 4188 | already. |
| 4189 | |
| 4190 | @subsection Convert remaining macros |
| 4191 | |
| 4192 | Suggest converting macros into functions (and setting the corresponding |
| 4193 | architecture method) in small batches. |
| 4194 | |
| 4195 | @subsection Set multi-arch level to two |
| 4196 | |
| 4197 | This should go smoothly. |
| 4198 | |
| 4199 | @subsection Delete the TM file |
| 4200 | |
| 4201 | The @file{tm-@var{arch}.h} can be deleted. @file{@var{arch}.mt} and |
| 4202 | @file{configure.in} updated. |
| 4203 | |
| 4204 | |
| 4205 | @node Target Vector Definition |
| 4206 | |
| 4207 | @chapter Target Vector Definition |
| 4208 | @cindex target vector |
| 4209 | |
| 4210 | The target vector defines the interface between @value{GDBN}'s |
| 4211 | abstract handling of target systems, and the nitty-gritty code that |
| 4212 | actually exercises control over a process or a serial port. |
| 4213 | @value{GDBN} includes some 30-40 different target vectors; however, |
| 4214 | each configuration of @value{GDBN} includes only a few of them. |
| 4215 | |
| 4216 | @section File Targets |
| 4217 | |
| 4218 | Both executables and core files have target vectors. |
| 4219 | |
| 4220 | @section Standard Protocol and Remote Stubs |
| 4221 | |
| 4222 | @value{GDBN}'s file @file{remote.c} talks a serial protocol to code |
| 4223 | that runs in the target system. @value{GDBN} provides several sample |
| 4224 | @dfn{stubs} that can be integrated into target programs or operating |
| 4225 | systems for this purpose; they are named @file{*-stub.c}. |
| 4226 | |
| 4227 | The @value{GDBN} user's manual describes how to put such a stub into |
| 4228 | your target code. What follows is a discussion of integrating the |
| 4229 | SPARC stub into a complicated operating system (rather than a simple |
| 4230 | program), by Stu Grossman, the author of this stub. |
| 4231 | |
| 4232 | The trap handling code in the stub assumes the following upon entry to |
| 4233 | @code{trap_low}: |
| 4234 | |
| 4235 | @enumerate |
| 4236 | @item |
| 4237 | %l1 and %l2 contain pc and npc respectively at the time of the trap; |
| 4238 | |
| 4239 | @item |
| 4240 | traps are disabled; |
| 4241 | |
| 4242 | @item |
| 4243 | you are in the correct trap window. |
| 4244 | @end enumerate |
| 4245 | |
| 4246 | As long as your trap handler can guarantee those conditions, then there |
| 4247 | is no reason why you shouldn't be able to ``share'' traps with the stub. |
| 4248 | The stub has no requirement that it be jumped to directly from the |
| 4249 | hardware trap vector. That is why it calls @code{exceptionHandler()}, |
| 4250 | which is provided by the external environment. For instance, this could |
| 4251 | set up the hardware traps to actually execute code which calls the stub |
| 4252 | first, and then transfers to its own trap handler. |
| 4253 | |
| 4254 | For the most point, there probably won't be much of an issue with |
| 4255 | ``sharing'' traps, as the traps we use are usually not used by the kernel, |
| 4256 | and often indicate unrecoverable error conditions. Anyway, this is all |
| 4257 | controlled by a table, and is trivial to modify. The most important |
| 4258 | trap for us is for @code{ta 1}. Without that, we can't single step or |
| 4259 | do breakpoints. Everything else is unnecessary for the proper operation |
| 4260 | of the debugger/stub. |
| 4261 | |
| 4262 | From reading the stub, it's probably not obvious how breakpoints work. |
| 4263 | They are simply done by deposit/examine operations from @value{GDBN}. |
| 4264 | |
| 4265 | @section ROM Monitor Interface |
| 4266 | |
| 4267 | @section Custom Protocols |
| 4268 | |
| 4269 | @section Transport Layer |
| 4270 | |
| 4271 | @section Builtin Simulator |
| 4272 | |
| 4273 | |
| 4274 | @node Native Debugging |
| 4275 | |
| 4276 | @chapter Native Debugging |
| 4277 | @cindex native debugging |
| 4278 | |
| 4279 | Several files control @value{GDBN}'s configuration for native support: |
| 4280 | |
| 4281 | @table @file |
| 4282 | @vindex NATDEPFILES |
| 4283 | @item gdb/config/@var{arch}/@var{xyz}.mh |
| 4284 | Specifies Makefile fragments needed by a @emph{native} configuration on |
| 4285 | machine @var{xyz}. In particular, this lists the required |
| 4286 | native-dependent object files, by defining @samp{NATDEPFILES=@dots{}}. |
| 4287 | Also specifies the header file which describes native support on |
| 4288 | @var{xyz}, by defining @samp{NAT_FILE= nm-@var{xyz}.h}. You can also |
| 4289 | define @samp{NAT_CFLAGS}, @samp{NAT_ADD_FILES}, @samp{NAT_CLIBS}, |
| 4290 | @samp{NAT_CDEPS}, etc.; see @file{Makefile.in}. |
| 4291 | |
| 4292 | @emph{Maintainer's note: The @file{.mh} suffix is because this file |
| 4293 | originally contained @file{Makefile} fragments for hosting @value{GDBN} |
| 4294 | on machine @var{xyz}. While the file is no longer used for this |
| 4295 | purpose, the @file{.mh} suffix remains. Perhaps someone will |
| 4296 | eventually rename these fragments so that they have a @file{.mn} |
| 4297 | suffix.} |
| 4298 | |
| 4299 | @item gdb/config/@var{arch}/nm-@var{xyz}.h |
| 4300 | (@file{nm.h} is a link to this file, created by @code{configure}). Contains C |
| 4301 | macro definitions describing the native system environment, such as |
| 4302 | child process control and core file support. |
| 4303 | |
| 4304 | @item gdb/@var{xyz}-nat.c |
| 4305 | Contains any miscellaneous C code required for this native support of |
| 4306 | this machine. On some machines it doesn't exist at all. |
| 4307 | @end table |
| 4308 | |
| 4309 | There are some ``generic'' versions of routines that can be used by |
| 4310 | various systems. These can be customized in various ways by macros |
| 4311 | defined in your @file{nm-@var{xyz}.h} file. If these routines work for |
| 4312 | the @var{xyz} host, you can just include the generic file's name (with |
| 4313 | @samp{.o}, not @samp{.c}) in @code{NATDEPFILES}. |
| 4314 | |
| 4315 | Otherwise, if your machine needs custom support routines, you will need |
| 4316 | to write routines that perform the same functions as the generic file. |
| 4317 | Put them into @file{@var{xyz}-nat.c}, and put @file{@var{xyz}-nat.o} |
| 4318 | into @code{NATDEPFILES}. |
| 4319 | |
| 4320 | @table @file |
| 4321 | @item inftarg.c |
| 4322 | This contains the @emph{target_ops vector} that supports Unix child |
| 4323 | processes on systems which use ptrace and wait to control the child. |
| 4324 | |
| 4325 | @item procfs.c |
| 4326 | This contains the @emph{target_ops vector} that supports Unix child |
| 4327 | processes on systems which use /proc to control the child. |
| 4328 | |
| 4329 | @item fork-child.c |
| 4330 | This does the low-level grunge that uses Unix system calls to do a ``fork |
| 4331 | and exec'' to start up a child process. |
| 4332 | |
| 4333 | @item infptrace.c |
| 4334 | This is the low level interface to inferior processes for systems using |
| 4335 | the Unix @code{ptrace} call in a vanilla way. |
| 4336 | @end table |
| 4337 | |
| 4338 | @section Native core file Support |
| 4339 | @cindex native core files |
| 4340 | |
| 4341 | @table @file |
| 4342 | @findex fetch_core_registers |
| 4343 | @item core-aout.c::fetch_core_registers() |
| 4344 | Support for reading registers out of a core file. This routine calls |
| 4345 | @code{register_addr()}, see below. Now that BFD is used to read core |
| 4346 | files, virtually all machines should use @code{core-aout.c}, and should |
| 4347 | just provide @code{fetch_core_registers} in @code{@var{xyz}-nat.c} (or |
| 4348 | @code{REGISTER_U_ADDR} in @code{nm-@var{xyz}.h}). |
| 4349 | |
| 4350 | @item core-aout.c::register_addr() |
| 4351 | If your @code{nm-@var{xyz}.h} file defines the macro |
| 4352 | @code{REGISTER_U_ADDR(addr, blockend, regno)}, it should be defined to |
| 4353 | set @code{addr} to the offset within the @samp{user} struct of @value{GDBN} |
| 4354 | register number @code{regno}. @code{blockend} is the offset within the |
| 4355 | ``upage'' of @code{u.u_ar0}. If @code{REGISTER_U_ADDR} is defined, |
| 4356 | @file{core-aout.c} will define the @code{register_addr()} function and |
| 4357 | use the macro in it. If you do not define @code{REGISTER_U_ADDR}, but |
| 4358 | you are using the standard @code{fetch_core_registers()}, you will need |
| 4359 | to define your own version of @code{register_addr()}, put it into your |
| 4360 | @code{@var{xyz}-nat.c} file, and be sure @code{@var{xyz}-nat.o} is in |
| 4361 | the @code{NATDEPFILES} list. If you have your own |
| 4362 | @code{fetch_core_registers()}, you may not need a separate |
| 4363 | @code{register_addr()}. Many custom @code{fetch_core_registers()} |
| 4364 | implementations simply locate the registers themselves.@refill |
| 4365 | @end table |
| 4366 | |
| 4367 | When making @value{GDBN} run native on a new operating system, to make it |
| 4368 | possible to debug core files, you will need to either write specific |
| 4369 | code for parsing your OS's core files, or customize |
| 4370 | @file{bfd/trad-core.c}. First, use whatever @code{#include} files your |
| 4371 | machine uses to define the struct of registers that is accessible |
| 4372 | (possibly in the u-area) in a core file (rather than |
| 4373 | @file{machine/reg.h}), and an include file that defines whatever header |
| 4374 | exists on a core file (e.g. the u-area or a @code{struct core}). Then |
| 4375 | modify @code{trad_unix_core_file_p} to use these values to set up the |
| 4376 | section information for the data segment, stack segment, any other |
| 4377 | segments in the core file (perhaps shared library contents or control |
| 4378 | information), ``registers'' segment, and if there are two discontiguous |
| 4379 | sets of registers (e.g. integer and float), the ``reg2'' segment. This |
| 4380 | section information basically delimits areas in the core file in a |
| 4381 | standard way, which the section-reading routines in BFD know how to seek |
| 4382 | around in. |
| 4383 | |
| 4384 | Then back in @value{GDBN}, you need a matching routine called |
| 4385 | @code{fetch_core_registers}. If you can use the generic one, it's in |
| 4386 | @file{core-aout.c}; if not, it's in your @file{@var{xyz}-nat.c} file. |
| 4387 | It will be passed a char pointer to the entire ``registers'' segment, |
| 4388 | its length, and a zero; or a char pointer to the entire ``regs2'' |
| 4389 | segment, its length, and a 2. The routine should suck out the supplied |
| 4390 | register values and install them into @value{GDBN}'s ``registers'' array. |
| 4391 | |
| 4392 | If your system uses @file{/proc} to control processes, and uses ELF |
| 4393 | format core files, then you may be able to use the same routines for |
| 4394 | reading the registers out of processes and out of core files. |
| 4395 | |
| 4396 | @section ptrace |
| 4397 | |
| 4398 | @section /proc |
| 4399 | |
| 4400 | @section win32 |
| 4401 | |
| 4402 | @section shared libraries |
| 4403 | |
| 4404 | @section Native Conditionals |
| 4405 | @cindex native conditionals |
| 4406 | |
| 4407 | When @value{GDBN} is configured and compiled, various macros are |
| 4408 | defined or left undefined, to control compilation when the host and |
| 4409 | target systems are the same. These macros should be defined (or left |
| 4410 | undefined) in @file{nm-@var{system}.h}. |
| 4411 | |
| 4412 | @table @code |
| 4413 | @item ATTACH_DETACH |
| 4414 | @findex ATTACH_DETACH |
| 4415 | If defined, then @value{GDBN} will include support for the @code{attach} and |
| 4416 | @code{detach} commands. |
| 4417 | |
| 4418 | @item CHILD_PREPARE_TO_STORE |
| 4419 | @findex CHILD_PREPARE_TO_STORE |
| 4420 | If the machine stores all registers at once in the child process, then |
| 4421 | define this to ensure that all values are correct. This usually entails |
| 4422 | a read from the child. |
| 4423 | |
| 4424 | [Note that this is incorrectly defined in @file{xm-@var{system}.h} files |
| 4425 | currently.] |
| 4426 | |
| 4427 | @item FETCH_INFERIOR_REGISTERS |
| 4428 | @findex FETCH_INFERIOR_REGISTERS |
| 4429 | Define this if the native-dependent code will provide its own routines |
| 4430 | @code{fetch_inferior_registers} and @code{store_inferior_registers} in |
| 4431 | @file{@var{host}-nat.c}. If this symbol is @emph{not} defined, and |
| 4432 | @file{infptrace.c} is included in this configuration, the default |
| 4433 | routines in @file{infptrace.c} are used for these functions. |
| 4434 | |
| 4435 | @item FILES_INFO_HOOK |
| 4436 | @findex FILES_INFO_HOOK |
| 4437 | (Only defined for Convex.) |
| 4438 | |
| 4439 | @item FP0_REGNUM |
| 4440 | @findex FP0_REGNUM |
| 4441 | This macro is normally defined to be the number of the first floating |
| 4442 | point register, if the machine has such registers. As such, it would |
| 4443 | appear only in target-specific code. However, @file{/proc} support uses this |
| 4444 | to decide whether floats are in use on this target. |
| 4445 | |
| 4446 | @item GET_LONGJMP_TARGET |
| 4447 | @findex GET_LONGJMP_TARGET |
| 4448 | For most machines, this is a target-dependent parameter. On the |
| 4449 | DECstation and the Iris, this is a native-dependent parameter, since |
| 4450 | @file{setjmp.h} is needed to define it. |
| 4451 | |
| 4452 | This macro determines the target PC address that @code{longjmp} will jump to, |
| 4453 | assuming that we have just stopped at a longjmp breakpoint. It takes a |
| 4454 | @code{CORE_ADDR *} as argument, and stores the target PC value through this |
| 4455 | pointer. It examines the current state of the machine as needed. |
| 4456 | |
| 4457 | @item I386_USE_GENERIC_WATCHPOINTS |
| 4458 | An x86-based machine can define this to use the generic x86 watchpoint |
| 4459 | support; see @ref{Algorithms, I386_USE_GENERIC_WATCHPOINTS}. |
| 4460 | |
| 4461 | @item KERNEL_U_ADDR |
| 4462 | @findex KERNEL_U_ADDR |
| 4463 | Define this to the address of the @code{u} structure (the ``user |
| 4464 | struct'', also known as the ``u-page'') in kernel virtual memory. @value{GDBN} |
| 4465 | needs to know this so that it can subtract this address from absolute |
| 4466 | addresses in the upage, that are obtained via ptrace or from core files. |
| 4467 | On systems that don't need this value, set it to zero. |
| 4468 | |
| 4469 | @item KERNEL_U_ADDR_BSD |
| 4470 | @findex KERNEL_U_ADDR_BSD |
| 4471 | Define this to cause @value{GDBN} to determine the address of @code{u} at |
| 4472 | runtime, by using Berkeley-style @code{nlist} on the kernel's image in |
| 4473 | the root directory. |
| 4474 | |
| 4475 | @item KERNEL_U_ADDR_HPUX |
| 4476 | @findex KERNEL_U_ADDR_HPUX |
| 4477 | Define this to cause @value{GDBN} to determine the address of @code{u} at |
| 4478 | runtime, by using HP-style @code{nlist} on the kernel's image in the |
| 4479 | root directory. |
| 4480 | |
| 4481 | @item ONE_PROCESS_WRITETEXT |
| 4482 | @findex ONE_PROCESS_WRITETEXT |
| 4483 | Define this to be able to, when a breakpoint insertion fails, warn the |
| 4484 | user that another process may be running with the same executable. |
| 4485 | |
| 4486 | @item PREPARE_TO_PROCEED (@var{select_it}) |
| 4487 | @findex PREPARE_TO_PROCEED |
| 4488 | This (ugly) macro allows a native configuration to customize the way the |
| 4489 | @code{proceed} function in @file{infrun.c} deals with switching between |
| 4490 | threads. |
| 4491 | |
| 4492 | In a multi-threaded task we may select another thread and then continue |
| 4493 | or step. But if the old thread was stopped at a breakpoint, it will |
| 4494 | immediately cause another breakpoint stop without any execution (i.e. it |
| 4495 | will report a breakpoint hit incorrectly). So @value{GDBN} must step over it |
| 4496 | first. |
| 4497 | |
| 4498 | If defined, @code{PREPARE_TO_PROCEED} should check the current thread |
| 4499 | against the thread that reported the most recent event. If a step-over |
| 4500 | is required, it returns TRUE. If @var{select_it} is non-zero, it should |
| 4501 | reselect the old thread. |
| 4502 | |
| 4503 | @item PROC_NAME_FMT |
| 4504 | @findex PROC_NAME_FMT |
| 4505 | Defines the format for the name of a @file{/proc} device. Should be |
| 4506 | defined in @file{nm.h} @emph{only} in order to override the default |
| 4507 | definition in @file{procfs.c}. |
| 4508 | |
| 4509 | @item PTRACE_FP_BUG |
| 4510 | @findex PTRACE_FP_BUG |
| 4511 | See @file{mach386-xdep.c}. |
| 4512 | |
| 4513 | @item PTRACE_ARG3_TYPE |
| 4514 | @findex PTRACE_ARG3_TYPE |
| 4515 | The type of the third argument to the @code{ptrace} system call, if it |
| 4516 | exists and is different from @code{int}. |
| 4517 | |
| 4518 | @item REGISTER_U_ADDR |
| 4519 | @findex REGISTER_U_ADDR |
| 4520 | Defines the offset of the registers in the ``u area''. |
| 4521 | |
| 4522 | @item SHELL_COMMAND_CONCAT |
| 4523 | @findex SHELL_COMMAND_CONCAT |
| 4524 | If defined, is a string to prefix on the shell command used to start the |
| 4525 | inferior. |
| 4526 | |
| 4527 | @item SHELL_FILE |
| 4528 | @findex SHELL_FILE |
| 4529 | If defined, this is the name of the shell to use to run the inferior. |
| 4530 | Defaults to @code{"/bin/sh"}. |
| 4531 | |
| 4532 | @item SOLIB_ADD (@var{filename}, @var{from_tty}, @var{targ}, @var{readsyms}) |
| 4533 | @findex SOLIB_ADD |
| 4534 | Define this to expand into an expression that will cause the symbols in |
| 4535 | @var{filename} to be added to @value{GDBN}'s symbol table. If |
| 4536 | @var{readsyms} is zero symbols are not read but any necessary low level |
| 4537 | processing for @var{filename} is still done. |
| 4538 | |
| 4539 | @item SOLIB_CREATE_INFERIOR_HOOK |
| 4540 | @findex SOLIB_CREATE_INFERIOR_HOOK |
| 4541 | Define this to expand into any shared-library-relocation code that you |
| 4542 | want to be run just after the child process has been forked. |
| 4543 | |
| 4544 | @item START_INFERIOR_TRAPS_EXPECTED |
| 4545 | @findex START_INFERIOR_TRAPS_EXPECTED |
| 4546 | When starting an inferior, @value{GDBN} normally expects to trap |
| 4547 | twice; once when |
| 4548 | the shell execs, and once when the program itself execs. If the actual |
| 4549 | number of traps is something other than 2, then define this macro to |
| 4550 | expand into the number expected. |
| 4551 | |
| 4552 | @item SVR4_SHARED_LIBS |
| 4553 | @findex SVR4_SHARED_LIBS |
| 4554 | Define this to indicate that SVR4-style shared libraries are in use. |
| 4555 | |
| 4556 | @item USE_PROC_FS |
| 4557 | @findex USE_PROC_FS |
| 4558 | This determines whether small routines in @file{*-tdep.c}, which |
| 4559 | translate register values between @value{GDBN}'s internal |
| 4560 | representation and the @file{/proc} representation, are compiled. |
| 4561 | |
| 4562 | @item U_REGS_OFFSET |
| 4563 | @findex U_REGS_OFFSET |
| 4564 | This is the offset of the registers in the upage. It need only be |
| 4565 | defined if the generic ptrace register access routines in |
| 4566 | @file{infptrace.c} are being used (that is, @file{infptrace.c} is |
| 4567 | configured in, and @code{FETCH_INFERIOR_REGISTERS} is not defined). If |
| 4568 | the default value from @file{infptrace.c} is good enough, leave it |
| 4569 | undefined. |
| 4570 | |
| 4571 | The default value means that u.u_ar0 @emph{points to} the location of |
| 4572 | the registers. I'm guessing that @code{#define U_REGS_OFFSET 0} means |
| 4573 | that @code{u.u_ar0} @emph{is} the location of the registers. |
| 4574 | |
| 4575 | @item CLEAR_SOLIB |
| 4576 | @findex CLEAR_SOLIB |
| 4577 | See @file{objfiles.c}. |
| 4578 | |
| 4579 | @item DEBUG_PTRACE |
| 4580 | @findex DEBUG_PTRACE |
| 4581 | Define this to debug @code{ptrace} calls. |
| 4582 | @end table |
| 4583 | |
| 4584 | |
| 4585 | @node Support Libraries |
| 4586 | |
| 4587 | @chapter Support Libraries |
| 4588 | |
| 4589 | @section BFD |
| 4590 | @cindex BFD library |
| 4591 | |
| 4592 | BFD provides support for @value{GDBN} in several ways: |
| 4593 | |
| 4594 | @table @emph |
| 4595 | @item identifying executable and core files |
| 4596 | BFD will identify a variety of file types, including a.out, coff, and |
| 4597 | several variants thereof, as well as several kinds of core files. |
| 4598 | |
| 4599 | @item access to sections of files |
| 4600 | BFD parses the file headers to determine the names, virtual addresses, |
| 4601 | sizes, and file locations of all the various named sections in files |
| 4602 | (such as the text section or the data section). @value{GDBN} simply |
| 4603 | calls BFD to read or write section @var{x} at byte offset @var{y} for |
| 4604 | length @var{z}. |
| 4605 | |
| 4606 | @item specialized core file support |
| 4607 | BFD provides routines to determine the failing command name stored in a |
| 4608 | core file, the signal with which the program failed, and whether a core |
| 4609 | file matches (i.e.@: could be a core dump of) a particular executable |
| 4610 | file. |
| 4611 | |
| 4612 | @item locating the symbol information |
| 4613 | @value{GDBN} uses an internal interface of BFD to determine where to find the |
| 4614 | symbol information in an executable file or symbol-file. @value{GDBN} itself |
| 4615 | handles the reading of symbols, since BFD does not ``understand'' debug |
| 4616 | symbols, but @value{GDBN} uses BFD's cached information to find the symbols, |
| 4617 | string table, etc. |
| 4618 | @end table |
| 4619 | |
| 4620 | @section opcodes |
| 4621 | @cindex opcodes library |
| 4622 | |
| 4623 | The opcodes library provides @value{GDBN}'s disassembler. (It's a separate |
| 4624 | library because it's also used in binutils, for @file{objdump}). |
| 4625 | |
| 4626 | @section readline |
| 4627 | |
| 4628 | @section mmalloc |
| 4629 | |
| 4630 | @section libiberty |
| 4631 | |
| 4632 | @section gnu-regex |
| 4633 | @cindex regular expressions library |
| 4634 | |
| 4635 | Regex conditionals. |
| 4636 | |
| 4637 | @table @code |
| 4638 | @item C_ALLOCA |
| 4639 | |
| 4640 | @item NFAILURES |
| 4641 | |
| 4642 | @item RE_NREGS |
| 4643 | |
| 4644 | @item SIGN_EXTEND_CHAR |
| 4645 | |
| 4646 | @item SWITCH_ENUM_BUG |
| 4647 | |
| 4648 | @item SYNTAX_TABLE |
| 4649 | |
| 4650 | @item Sword |
| 4651 | |
| 4652 | @item sparc |
| 4653 | @end table |
| 4654 | |
| 4655 | @section include |
| 4656 | |
| 4657 | @node Coding |
| 4658 | |
| 4659 | @chapter Coding |
| 4660 | |
| 4661 | This chapter covers topics that are lower-level than the major |
| 4662 | algorithms of @value{GDBN}. |
| 4663 | |
| 4664 | @section Cleanups |
| 4665 | @cindex cleanups |
| 4666 | |
| 4667 | Cleanups are a structured way to deal with things that need to be done |
| 4668 | later. |
| 4669 | |
| 4670 | When your code does something (e.g., @code{xmalloc} some memory, or |
| 4671 | @code{open} a file) that needs to be undone later (e.g., @code{xfree} |
| 4672 | the memory or @code{close} the file), it can make a cleanup. The |
| 4673 | cleanup will be done at some future point: when the command is finished |
| 4674 | and control returns to the top level; when an error occurs and the stack |
| 4675 | is unwound; or when your code decides it's time to explicitly perform |
| 4676 | cleanups. Alternatively you can elect to discard the cleanups you |
| 4677 | created. |
| 4678 | |
| 4679 | Syntax: |
| 4680 | |
| 4681 | @table @code |
| 4682 | @item struct cleanup *@var{old_chain}; |
| 4683 | Declare a variable which will hold a cleanup chain handle. |
| 4684 | |
| 4685 | @findex make_cleanup |
| 4686 | @item @var{old_chain} = make_cleanup (@var{function}, @var{arg}); |
| 4687 | Make a cleanup which will cause @var{function} to be called with |
| 4688 | @var{arg} (a @code{char *}) later. The result, @var{old_chain}, is a |
| 4689 | handle that can later be passed to @code{do_cleanups} or |
| 4690 | @code{discard_cleanups}. Unless you are going to call |
| 4691 | @code{do_cleanups} or @code{discard_cleanups}, you can ignore the result |
| 4692 | from @code{make_cleanup}. |
| 4693 | |
| 4694 | @findex do_cleanups |
| 4695 | @item do_cleanups (@var{old_chain}); |
| 4696 | Do all cleanups added to the chain since the corresponding |
| 4697 | @code{make_cleanup} call was made. |
| 4698 | |
| 4699 | @findex discard_cleanups |
| 4700 | @item discard_cleanups (@var{old_chain}); |
| 4701 | Same as @code{do_cleanups} except that it just removes the cleanups from |
| 4702 | the chain and does not call the specified functions. |
| 4703 | @end table |
| 4704 | |
| 4705 | Cleanups are implemented as a chain. The handle returned by |
| 4706 | @code{make_cleanups} includes the cleanup passed to the call and any |
| 4707 | later cleanups appended to the chain (but not yet discarded or |
| 4708 | performed). E.g.: |
| 4709 | |
| 4710 | @smallexample |
| 4711 | make_cleanup (a, 0); |
| 4712 | @{ |
| 4713 | struct cleanup *old = make_cleanup (b, 0); |
| 4714 | make_cleanup (c, 0) |
| 4715 | ... |
| 4716 | do_cleanups (old); |
| 4717 | @} |
| 4718 | @end smallexample |
| 4719 | |
| 4720 | @noindent |
| 4721 | will call @code{c()} and @code{b()} but will not call @code{a()}. The |
| 4722 | cleanup that calls @code{a()} will remain in the cleanup chain, and will |
| 4723 | be done later unless otherwise discarded.@refill |
| 4724 | |
| 4725 | Your function should explicitly do or discard the cleanups it creates. |
| 4726 | Failing to do this leads to non-deterministic behavior since the caller |
| 4727 | will arbitrarily do or discard your functions cleanups. This need leads |
| 4728 | to two common cleanup styles. |
| 4729 | |
| 4730 | The first style is try/finally. Before it exits, your code-block calls |
| 4731 | @code{do_cleanups} with the old cleanup chain and thus ensures that your |
| 4732 | code-block's cleanups are always performed. For instance, the following |
| 4733 | code-segment avoids a memory leak problem (even when @code{error} is |
| 4734 | called and a forced stack unwind occurs) by ensuring that the |
| 4735 | @code{xfree} will always be called: |
| 4736 | |
| 4737 | @smallexample |
| 4738 | struct cleanup *old = make_cleanup (null_cleanup, 0); |
| 4739 | data = xmalloc (sizeof blah); |
| 4740 | make_cleanup (xfree, data); |
| 4741 | ... blah blah ... |
| 4742 | do_cleanups (old); |
| 4743 | @end smallexample |
| 4744 | |
| 4745 | The second style is try/except. Before it exits, your code-block calls |
| 4746 | @code{discard_cleanups} with the old cleanup chain and thus ensures that |
| 4747 | any created cleanups are not performed. For instance, the following |
| 4748 | code segment, ensures that the file will be closed but only if there is |
| 4749 | an error: |
| 4750 | |
| 4751 | @smallexample |
| 4752 | FILE *file = fopen ("afile", "r"); |
| 4753 | struct cleanup *old = make_cleanup (close_file, file); |
| 4754 | ... blah blah ... |
| 4755 | discard_cleanups (old); |
| 4756 | return file; |
| 4757 | @end smallexample |
| 4758 | |
| 4759 | Some functions, e.g. @code{fputs_filtered()} or @code{error()}, specify |
| 4760 | that they ``should not be called when cleanups are not in place''. This |
| 4761 | means that any actions you need to reverse in the case of an error or |
| 4762 | interruption must be on the cleanup chain before you call these |
| 4763 | functions, since they might never return to your code (they |
| 4764 | @samp{longjmp} instead). |
| 4765 | |
| 4766 | @section Per-architecture module data |
| 4767 | @cindex per-architecture module data |
| 4768 | @cindex multi-arch data |
| 4769 | @cindex data-pointer, per-architecture/per-module |
| 4770 | |
| 4771 | The multi-arch framework includes a mechanism for adding module specific |
| 4772 | per-architecture data-pointers to the @code{struct gdbarch} architecture |
| 4773 | object. |
| 4774 | |
| 4775 | A module registers one or more per-architecture data-pointers using the |
| 4776 | function @code{register_gdbarch_data}: |
| 4777 | |
| 4778 | @deftypefun struct gdbarch_data *register_gdbarch_data (gdbarch_data_init_ftype *@var{init}, gdbarch_data_free_ftype *@var{free}) |
| 4779 | |
| 4780 | The @var{init} function is used to obtain an initial value for a |
| 4781 | per-architecture data-pointer. The function is called, after the |
| 4782 | architecture has been created, when the data-pointer is still |
| 4783 | uninitialized (@code{NULL}) and its value has been requested via a call |
| 4784 | to @code{gdbarch_data}. A data-pointer can also be initialize |
| 4785 | explicitly using @code{set_gdbarch_data}. |
| 4786 | |
| 4787 | The @var{free} function is called when a data-pointer needs to be |
| 4788 | destroyed. This occurs when either the corresponding @code{struct |
| 4789 | gdbarch} object is being destroyed or when @code{set_gdbarch_data} is |
| 4790 | overriding a non-@code{NULL} data-pointer value. |
| 4791 | |
| 4792 | The function @code{register_gdbarch_data} returns a @code{struct |
| 4793 | gdbarch_data} that is used to identify the data-pointer that was added |
| 4794 | to the module. |
| 4795 | |
| 4796 | @end deftypefun |
| 4797 | |
| 4798 | A typical module has @code{init} and @code{free} functions of the form: |
| 4799 | |
| 4800 | @smallexample |
| 4801 | static struct gdbarch_data *nozel_handle; |
| 4802 | static void * |
| 4803 | nozel_init (struct gdbarch *gdbarch) |
| 4804 | @{ |
| 4805 | struct nozel *data = XMALLOC (struct nozel); |
| 4806 | @dots{} |
| 4807 | return data; |
| 4808 | @} |
| 4809 | @dots{} |
| 4810 | static void |
| 4811 | nozel_free (struct gdbarch *gdbarch, void *data) |
| 4812 | @{ |
| 4813 | xfree (data); |
| 4814 | @} |
| 4815 | @end smallexample |
| 4816 | |
| 4817 | Since uninitialized (@code{NULL}) data-pointers are initialized |
| 4818 | on-demand, an @code{init} function is free to call other modules that |
| 4819 | use data-pointers. Those modules data-pointers will be initialized as |
| 4820 | needed. Care should be taken to ensure that the @code{init} call graph |
| 4821 | does not contain cycles. |
| 4822 | |
| 4823 | The data-pointer is registered with the call: |
| 4824 | |
| 4825 | @smallexample |
| 4826 | void |
| 4827 | _initialize_nozel (void) |
| 4828 | @{ |
| 4829 | nozel_handle = register_gdbarch_data (nozel_init, nozel_free); |
| 4830 | @dots{} |
| 4831 | @end smallexample |
| 4832 | |
| 4833 | The per-architecture data-pointer is accessed using the function: |
| 4834 | |
| 4835 | @deftypefun void *gdbarch_data (struct gdbarch *@var{gdbarch}, struct gdbarch_data *@var{data_handle}) |
| 4836 | Given the architecture @var{arch} and module data handle |
| 4837 | @var{data_handle} (returned by @code{register_gdbarch_data}, this |
| 4838 | function returns the current value of the per-architecture data-pointer. |
| 4839 | @end deftypefun |
| 4840 | |
| 4841 | The non-@code{NULL} data-pointer returned by @code{gdbarch_data} should |
| 4842 | be saved in a local variable and then used directly: |
| 4843 | |
| 4844 | @smallexample |
| 4845 | int |
| 4846 | nozel_total (struct gdbarch *gdbarch) |
| 4847 | @{ |
| 4848 | int total; |
| 4849 | struct nozel *data = gdbarch_data (gdbarch, nozel_handle); |
| 4850 | @dots{} |
| 4851 | return total; |
| 4852 | @} |
| 4853 | @end smallexample |
| 4854 | |
| 4855 | It is also possible to directly initialize the data-pointer using: |
| 4856 | |
| 4857 | @deftypefun void set_gdbarch_data (struct gdbarch *@var{gdbarch}, struct gdbarch_data *handle, void *@var{pointer}) |
| 4858 | Update the data-pointer corresponding to @var{handle} with the value of |
| 4859 | @var{pointer}. If the previous data-pointer value is non-NULL, then it |
| 4860 | is freed using data-pointers @var{free} function. |
| 4861 | @end deftypefun |
| 4862 | |
| 4863 | This function is used by modules that require a mechanism for explicitly |
| 4864 | setting the per-architecture data-pointer during architecture creation: |
| 4865 | |
| 4866 | @smallexample |
| 4867 | /* Called during architecture creation. */ |
| 4868 | extern void |
| 4869 | set_gdbarch_nozel (struct gdbarch *gdbarch, |
| 4870 | int total) |
| 4871 | @{ |
| 4872 | struct nozel *data = XMALLOC (struct nozel); |
| 4873 | @dots{} |
| 4874 | set_gdbarch_data (gdbarch, nozel_handle, nozel); |
| 4875 | @} |
| 4876 | @end smallexample |
| 4877 | |
| 4878 | @smallexample |
| 4879 | /* Default, called when nozel not set by set_gdbarch_nozel(). */ |
| 4880 | static void * |
| 4881 | nozel_init (struct gdbarch *gdbarch) |
| 4882 | @{ |
| 4883 | struct nozel *default_nozel = XMALLOC (struc nozel); |
| 4884 | @dots{} |
| 4885 | return default_nozel; |
| 4886 | @} |
| 4887 | @end smallexample |
| 4888 | |
| 4889 | @smallexample |
| 4890 | void |
| 4891 | _initialize_nozel (void) |
| 4892 | @{ |
| 4893 | nozel_handle = register_gdbarch_data (nozel_init, NULL); |
| 4894 | @dots{} |
| 4895 | @end smallexample |
| 4896 | |
| 4897 | @noindent |
| 4898 | Note that an @code{init} function still needs to be registered. It is |
| 4899 | used to initialize the data-pointer when the architecture creation phase |
| 4900 | fail to set an initial value. |
| 4901 | |
| 4902 | |
| 4903 | @section Wrapping Output Lines |
| 4904 | @cindex line wrap in output |
| 4905 | |
| 4906 | @findex wrap_here |
| 4907 | Output that goes through @code{printf_filtered} or @code{fputs_filtered} |
| 4908 | or @code{fputs_demangled} needs only to have calls to @code{wrap_here} |
| 4909 | added in places that would be good breaking points. The utility |
| 4910 | routines will take care of actually wrapping if the line width is |
| 4911 | exceeded. |
| 4912 | |
| 4913 | The argument to @code{wrap_here} is an indentation string which is |
| 4914 | printed @emph{only} if the line breaks there. This argument is saved |
| 4915 | away and used later. It must remain valid until the next call to |
| 4916 | @code{wrap_here} or until a newline has been printed through the |
| 4917 | @code{*_filtered} functions. Don't pass in a local variable and then |
| 4918 | return! |
| 4919 | |
| 4920 | It is usually best to call @code{wrap_here} after printing a comma or |
| 4921 | space. If you call it before printing a space, make sure that your |
| 4922 | indentation properly accounts for the leading space that will print if |
| 4923 | the line wraps there. |
| 4924 | |
| 4925 | Any function or set of functions that produce filtered output must |
| 4926 | finish by printing a newline, to flush the wrap buffer, before switching |
| 4927 | to unfiltered (@code{printf}) output. Symbol reading routines that |
| 4928 | print warnings are a good example. |
| 4929 | |
| 4930 | @section @value{GDBN} Coding Standards |
| 4931 | @cindex coding standards |
| 4932 | |
| 4933 | @value{GDBN} follows the GNU coding standards, as described in |
| 4934 | @file{etc/standards.texi}. This file is also available for anonymous |
| 4935 | FTP from GNU archive sites. @value{GDBN} takes a strict interpretation |
| 4936 | of the standard; in general, when the GNU standard recommends a practice |
| 4937 | but does not require it, @value{GDBN} requires it. |
| 4938 | |
| 4939 | @value{GDBN} follows an additional set of coding standards specific to |
| 4940 | @value{GDBN}, as described in the following sections. |
| 4941 | |
| 4942 | |
| 4943 | @subsection ISO C |
| 4944 | |
| 4945 | @value{GDBN} assumes an ISO/IEC 9899:1990 (a.k.a.@: ISO C90) compliant |
| 4946 | compiler. |
| 4947 | |
| 4948 | @value{GDBN} does not assume an ISO C or POSIX compliant C library. |
| 4949 | |
| 4950 | |
| 4951 | @subsection Memory Management |
| 4952 | |
| 4953 | @value{GDBN} does not use the functions @code{malloc}, @code{realloc}, |
| 4954 | @code{calloc}, @code{free} and @code{asprintf}. |
| 4955 | |
| 4956 | @value{GDBN} uses the functions @code{xmalloc}, @code{xrealloc} and |
| 4957 | @code{xcalloc} when allocating memory. Unlike @code{malloc} et.al.@: |
| 4958 | these functions do not return when the memory pool is empty. Instead, |
| 4959 | they unwind the stack using cleanups. These functions return |
| 4960 | @code{NULL} when requested to allocate a chunk of memory of size zero. |
| 4961 | |
| 4962 | @emph{Pragmatics: By using these functions, the need to check every |
| 4963 | memory allocation is removed. These functions provide portable |
| 4964 | behavior.} |
| 4965 | |
| 4966 | @value{GDBN} does not use the function @code{free}. |
| 4967 | |
| 4968 | @value{GDBN} uses the function @code{xfree} to return memory to the |
| 4969 | memory pool. Consistent with ISO-C, this function ignores a request to |
| 4970 | free a @code{NULL} pointer. |
| 4971 | |
| 4972 | @emph{Pragmatics: On some systems @code{free} fails when passed a |
| 4973 | @code{NULL} pointer.} |
| 4974 | |
| 4975 | @value{GDBN} can use the non-portable function @code{alloca} for the |
| 4976 | allocation of small temporary values (such as strings). |
| 4977 | |
| 4978 | @emph{Pragmatics: This function is very non-portable. Some systems |
| 4979 | restrict the memory being allocated to no more than a few kilobytes.} |
| 4980 | |
| 4981 | @value{GDBN} uses the string function @code{xstrdup} and the print |
| 4982 | function @code{xasprintf}. |
| 4983 | |
| 4984 | @emph{Pragmatics: @code{asprintf} and @code{strdup} can fail. Print |
| 4985 | functions such as @code{sprintf} are very prone to buffer overflow |
| 4986 | errors.} |
| 4987 | |
| 4988 | |
| 4989 | @subsection Compiler Warnings |
| 4990 | @cindex compiler warnings |
| 4991 | |
| 4992 | With few exceptions, developers should include the configuration option |
| 4993 | @samp{--enable-gdb-build-warnings=,-Werror} when building @value{GDBN}. |
| 4994 | The exceptions are listed in the file @file{gdb/MAINTAINERS}. |
| 4995 | |
| 4996 | This option causes @value{GDBN} (when built using GCC) to be compiled |
| 4997 | with a carefully selected list of compiler warning flags. Any warnings |
| 4998 | from those flags being treated as errors. |
| 4999 | |
| 5000 | The current list of warning flags includes: |
| 5001 | |
| 5002 | @table @samp |
| 5003 | @item -Wimplicit |
| 5004 | Since @value{GDBN} coding standard requires all functions to be declared |
| 5005 | using a prototype, the flag has the side effect of ensuring that |
| 5006 | prototyped functions are always visible with out resorting to |
| 5007 | @samp{-Wstrict-prototypes}. |
| 5008 | |
| 5009 | @item -Wreturn-type |
| 5010 | Such code often appears to work except on instruction set architectures |
| 5011 | that use register windows. |
| 5012 | |
| 5013 | @item -Wcomment |
| 5014 | |
| 5015 | @item -Wtrigraphs |
| 5016 | |
| 5017 | @item -Wformat |
| 5018 | Since @value{GDBN} uses the @code{format printf} attribute on all |
| 5019 | @code{printf} like functions this checks not just @code{printf} calls |
| 5020 | but also calls to functions such as @code{fprintf_unfiltered}. |
| 5021 | |
| 5022 | @item -Wparentheses |
| 5023 | This warning includes uses of the assignment operator within an |
| 5024 | @code{if} statement. |
| 5025 | |
| 5026 | @item -Wpointer-arith |
| 5027 | |
| 5028 | @item -Wuninitialized |
| 5029 | @end table |
| 5030 | |
| 5031 | @emph{Pragmatics: Due to the way that @value{GDBN} is implemented most |
| 5032 | functions have unused parameters. Consequently the warning |
| 5033 | @samp{-Wunused-parameter} is precluded from the list. The macro |
| 5034 | @code{ATTRIBUTE_UNUSED} is not used as it leads to false negatives --- |
| 5035 | it is not an error to have @code{ATTRIBUTE_UNUSED} on a parameter that |
| 5036 | is being used. The options @samp{-Wall} and @samp{-Wunused} are also |
| 5037 | precluded because they both include @samp{-Wunused-parameter}.} |
| 5038 | |
| 5039 | @emph{Pragmatics: @value{GDBN} has not simply accepted the warnings |
| 5040 | enabled by @samp{-Wall -Werror -W...}. Instead it is selecting warnings |
| 5041 | when and where their benefits can be demonstrated.} |
| 5042 | |
| 5043 | @subsection Formatting |
| 5044 | |
| 5045 | @cindex source code formatting |
| 5046 | The standard GNU recommendations for formatting must be followed |
| 5047 | strictly. |
| 5048 | |
| 5049 | A function declaration should not have its name in column zero. A |
| 5050 | function definition should have its name in column zero. |
| 5051 | |
| 5052 | @smallexample |
| 5053 | /* Declaration */ |
| 5054 | static void foo (void); |
| 5055 | /* Definition */ |
| 5056 | void |
| 5057 | foo (void) |
| 5058 | @{ |
| 5059 | @} |
| 5060 | @end smallexample |
| 5061 | |
| 5062 | @emph{Pragmatics: This simplifies scripting. Function definitions can |
| 5063 | be found using @samp{^function-name}.} |
| 5064 | |
| 5065 | There must be a space between a function or macro name and the opening |
| 5066 | parenthesis of its argument list (except for macro definitions, as |
| 5067 | required by C). There must not be a space after an open paren/bracket |
| 5068 | or before a close paren/bracket. |
| 5069 | |
| 5070 | While additional whitespace is generally helpful for reading, do not use |
| 5071 | more than one blank line to separate blocks, and avoid adding whitespace |
| 5072 | after the end of a program line (as of 1/99, some 600 lines had |
| 5073 | whitespace after the semicolon). Excess whitespace causes difficulties |
| 5074 | for @code{diff} and @code{patch} utilities. |
| 5075 | |
| 5076 | Pointers are declared using the traditional K&R C style: |
| 5077 | |
| 5078 | @smallexample |
| 5079 | void *foo; |
| 5080 | @end smallexample |
| 5081 | |
| 5082 | @noindent |
| 5083 | and not: |
| 5084 | |
| 5085 | @smallexample |
| 5086 | void * foo; |
| 5087 | void* foo; |
| 5088 | @end smallexample |
| 5089 | |
| 5090 | @subsection Comments |
| 5091 | |
| 5092 | @cindex comment formatting |
| 5093 | The standard GNU requirements on comments must be followed strictly. |
| 5094 | |
| 5095 | Block comments must appear in the following form, with no @code{/*}- or |
| 5096 | @code{*/}-only lines, and no leading @code{*}: |
| 5097 | |
| 5098 | @smallexample |
| 5099 | /* Wait for control to return from inferior to debugger. If inferior |
| 5100 | gets a signal, we may decide to start it up again instead of |
| 5101 | returning. That is why there is a loop in this function. When |
| 5102 | this function actually returns it means the inferior should be left |
| 5103 | stopped and @value{GDBN} should read more commands. */ |
| 5104 | @end smallexample |
| 5105 | |
| 5106 | (Note that this format is encouraged by Emacs; tabbing for a multi-line |
| 5107 | comment works correctly, and @kbd{M-q} fills the block consistently.) |
| 5108 | |
| 5109 | Put a blank line between the block comments preceding function or |
| 5110 | variable definitions, and the definition itself. |
| 5111 | |
| 5112 | In general, put function-body comments on lines by themselves, rather |
| 5113 | than trying to fit them into the 20 characters left at the end of a |
| 5114 | line, since either the comment or the code will inevitably get longer |
| 5115 | than will fit, and then somebody will have to move it anyhow. |
| 5116 | |
| 5117 | @subsection C Usage |
| 5118 | |
| 5119 | @cindex C data types |
| 5120 | Code must not depend on the sizes of C data types, the format of the |
| 5121 | host's floating point numbers, the alignment of anything, or the order |
| 5122 | of evaluation of expressions. |
| 5123 | |
| 5124 | @cindex function usage |
| 5125 | Use functions freely. There are only a handful of compute-bound areas |
| 5126 | in @value{GDBN} that might be affected by the overhead of a function |
| 5127 | call, mainly in symbol reading. Most of @value{GDBN}'s performance is |
| 5128 | limited by the target interface (whether serial line or system call). |
| 5129 | |
| 5130 | However, use functions with moderation. A thousand one-line functions |
| 5131 | are just as hard to understand as a single thousand-line function. |
| 5132 | |
| 5133 | @emph{Macros are bad, M'kay.} |
| 5134 | (But if you have to use a macro, make sure that the macro arguments are |
| 5135 | protected with parentheses.) |
| 5136 | |
| 5137 | @cindex types |
| 5138 | |
| 5139 | Declarations like @samp{struct foo *} should be used in preference to |
| 5140 | declarations like @samp{typedef struct foo @{ @dots{} @} *foo_ptr}. |
| 5141 | |
| 5142 | |
| 5143 | @subsection Function Prototypes |
| 5144 | @cindex function prototypes |
| 5145 | |
| 5146 | Prototypes must be used when both @emph{declaring} and @emph{defining} |
| 5147 | a function. Prototypes for @value{GDBN} functions must include both the |
| 5148 | argument type and name, with the name matching that used in the actual |
| 5149 | function definition. |
| 5150 | |
| 5151 | All external functions should have a declaration in a header file that |
| 5152 | callers include, except for @code{_initialize_*} functions, which must |
| 5153 | be external so that @file{init.c} construction works, but shouldn't be |
| 5154 | visible to random source files. |
| 5155 | |
| 5156 | Where a source file needs a forward declaration of a static function, |
| 5157 | that declaration must appear in a block near the top of the source file. |
| 5158 | |
| 5159 | |
| 5160 | @subsection Internal Error Recovery |
| 5161 | |
| 5162 | During its execution, @value{GDBN} can encounter two types of errors. |
| 5163 | User errors and internal errors. User errors include not only a user |
| 5164 | entering an incorrect command but also problems arising from corrupt |
| 5165 | object files and system errors when interacting with the target. |
| 5166 | Internal errors include situations where @value{GDBN} has detected, at |
| 5167 | run time, a corrupt or erroneous situation. |
| 5168 | |
| 5169 | When reporting an internal error, @value{GDBN} uses |
| 5170 | @code{internal_error} and @code{gdb_assert}. |
| 5171 | |
| 5172 | @value{GDBN} must not call @code{abort} or @code{assert}. |
| 5173 | |
| 5174 | @emph{Pragmatics: There is no @code{internal_warning} function. Either |
| 5175 | the code detected a user error, recovered from it and issued a |
| 5176 | @code{warning} or the code failed to correctly recover from the user |
| 5177 | error and issued an @code{internal_error}.} |
| 5178 | |
| 5179 | @subsection File Names |
| 5180 | |
| 5181 | Any file used when building the core of @value{GDBN} must be in lower |
| 5182 | case. Any file used when building the core of @value{GDBN} must be 8.3 |
| 5183 | unique. These requirements apply to both source and generated files. |
| 5184 | |
| 5185 | @emph{Pragmatics: The core of @value{GDBN} must be buildable on many |
| 5186 | platforms including DJGPP and MacOS/HFS. Every time an unfriendly file |
| 5187 | is introduced to the build process both @file{Makefile.in} and |
| 5188 | @file{configure.in} need to be modified accordingly. Compare the |
| 5189 | convoluted conversion process needed to transform @file{COPYING} into |
| 5190 | @file{copying.c} with the conversion needed to transform |
| 5191 | @file{version.in} into @file{version.c}.} |
| 5192 | |
| 5193 | Any file non 8.3 compliant file (that is not used when building the core |
| 5194 | of @value{GDBN}) must be added to @file{gdb/config/djgpp/fnchange.lst}. |
| 5195 | |
| 5196 | @emph{Pragmatics: This is clearly a compromise.} |
| 5197 | |
| 5198 | When @value{GDBN} has a local version of a system header file (ex |
| 5199 | @file{string.h}) the file name based on the POSIX header prefixed with |
| 5200 | @file{gdb_} (@file{gdb_string.h}). |
| 5201 | |
| 5202 | For other files @samp{-} is used as the separator. |
| 5203 | |
| 5204 | |
| 5205 | @subsection Include Files |
| 5206 | |
| 5207 | A @file{.c} file should include @file{defs.h} first. |
| 5208 | |
| 5209 | A @file{.c} file should directly include the @code{.h} file of every |
| 5210 | declaration and/or definition it directly refers to. It cannot rely on |
| 5211 | indirect inclusion. |
| 5212 | |
| 5213 | A @file{.h} file should directly include the @code{.h} file of every |
| 5214 | declaration and/or definition it directly refers to. It cannot rely on |
| 5215 | indirect inclusion. Exception: The file @file{defs.h} does not need to |
| 5216 | be directly included. |
| 5217 | |
| 5218 | An external declaration should only appear in one include file. |
| 5219 | |
| 5220 | An external declaration should never appear in a @code{.c} file. |
| 5221 | Exception: a declaration for the @code{_initialize} function that |
| 5222 | pacifies @option{-Wmissing-declaration}. |
| 5223 | |
| 5224 | A @code{typedef} definition should only appear in one include file. |
| 5225 | |
| 5226 | An opaque @code{struct} declaration can appear in multiple @file{.h} |
| 5227 | files. Where possible, a @file{.h} file should use an opaque |
| 5228 | @code{struct} declaration instead of an include. |
| 5229 | |
| 5230 | All @file{.h} files should be wrapped in: |
| 5231 | |
| 5232 | @smallexample |
| 5233 | #ifndef INCLUDE_FILE_NAME_H |
| 5234 | #define INCLUDE_FILE_NAME_H |
| 5235 | header body |
| 5236 | #endif |
| 5237 | @end smallexample |
| 5238 | |
| 5239 | |
| 5240 | @subsection Clean Design and Portable Implementation |
| 5241 | |
| 5242 | @cindex design |
| 5243 | In addition to getting the syntax right, there's the little question of |
| 5244 | semantics. Some things are done in certain ways in @value{GDBN} because long |
| 5245 | experience has shown that the more obvious ways caused various kinds of |
| 5246 | trouble. |
| 5247 | |
| 5248 | @cindex assumptions about targets |
| 5249 | You can't assume the byte order of anything that comes from a target |
| 5250 | (including @var{value}s, object files, and instructions). Such things |
| 5251 | must be byte-swapped using @code{SWAP_TARGET_AND_HOST} in |
| 5252 | @value{GDBN}, or one of the swap routines defined in @file{bfd.h}, |
| 5253 | such as @code{bfd_get_32}. |
| 5254 | |
| 5255 | You can't assume that you know what interface is being used to talk to |
| 5256 | the target system. All references to the target must go through the |
| 5257 | current @code{target_ops} vector. |
| 5258 | |
| 5259 | You can't assume that the host and target machines are the same machine |
| 5260 | (except in the ``native'' support modules). In particular, you can't |
| 5261 | assume that the target machine's header files will be available on the |
| 5262 | host machine. Target code must bring along its own header files -- |
| 5263 | written from scratch or explicitly donated by their owner, to avoid |
| 5264 | copyright problems. |
| 5265 | |
| 5266 | @cindex portability |
| 5267 | Insertion of new @code{#ifdef}'s will be frowned upon. It's much better |
| 5268 | to write the code portably than to conditionalize it for various |
| 5269 | systems. |
| 5270 | |
| 5271 | @cindex system dependencies |
| 5272 | New @code{#ifdef}'s which test for specific compilers or manufacturers |
| 5273 | or operating systems are unacceptable. All @code{#ifdef}'s should test |
| 5274 | for features. The information about which configurations contain which |
| 5275 | features should be segregated into the configuration files. Experience |
| 5276 | has proven far too often that a feature unique to one particular system |
| 5277 | often creeps into other systems; and that a conditional based on some |
| 5278 | predefined macro for your current system will become worthless over |
| 5279 | time, as new versions of your system come out that behave differently |
| 5280 | with regard to this feature. |
| 5281 | |
| 5282 | Adding code that handles specific architectures, operating systems, |
| 5283 | target interfaces, or hosts, is not acceptable in generic code. |
| 5284 | |
| 5285 | @cindex portable file name handling |
| 5286 | @cindex file names, portability |
| 5287 | One particularly notorious area where system dependencies tend to |
| 5288 | creep in is handling of file names. The mainline @value{GDBN} code |
| 5289 | assumes Posix semantics of file names: absolute file names begin with |
| 5290 | a forward slash @file{/}, slashes are used to separate leading |
| 5291 | directories, case-sensitive file names. These assumptions are not |
| 5292 | necessarily true on non-Posix systems such as MS-Windows. To avoid |
| 5293 | system-dependent code where you need to take apart or construct a file |
| 5294 | name, use the following portable macros: |
| 5295 | |
| 5296 | @table @code |
| 5297 | @findex HAVE_DOS_BASED_FILE_SYSTEM |
| 5298 | @item HAVE_DOS_BASED_FILE_SYSTEM |
| 5299 | This preprocessing symbol is defined to a non-zero value on hosts |
| 5300 | whose filesystems belong to the MS-DOS/MS-Windows family. Use this |
| 5301 | symbol to write conditional code which should only be compiled for |
| 5302 | such hosts. |
| 5303 | |
| 5304 | @findex IS_DIR_SEPARATOR |
| 5305 | @item IS_DIR_SEPARATOR (@var{c}) |
| 5306 | Evaluates to a non-zero value if @var{c} is a directory separator |
| 5307 | character. On Unix and GNU/Linux systems, only a slash @file{/} is |
| 5308 | such a character, but on Windows, both @file{/} and @file{\} will |
| 5309 | pass. |
| 5310 | |
| 5311 | @findex IS_ABSOLUTE_PATH |
| 5312 | @item IS_ABSOLUTE_PATH (@var{file}) |
| 5313 | Evaluates to a non-zero value if @var{file} is an absolute file name. |
| 5314 | For Unix and GNU/Linux hosts, a name which begins with a slash |
| 5315 | @file{/} is absolute. On DOS and Windows, @file{d:/foo} and |
| 5316 | @file{x:\bar} are also absolute file names. |
| 5317 | |
| 5318 | @findex FILENAME_CMP |
| 5319 | @item FILENAME_CMP (@var{f1}, @var{f2}) |
| 5320 | Calls a function which compares file names @var{f1} and @var{f2} as |
| 5321 | appropriate for the underlying host filesystem. For Posix systems, |
| 5322 | this simply calls @code{strcmp}; on case-insensitive filesystems it |
| 5323 | will call @code{strcasecmp} instead. |
| 5324 | |
| 5325 | @findex DIRNAME_SEPARATOR |
| 5326 | @item DIRNAME_SEPARATOR |
| 5327 | Evaluates to a character which separates directories in |
| 5328 | @code{PATH}-style lists, typically held in environment variables. |
| 5329 | This character is @samp{:} on Unix, @samp{;} on DOS and Windows. |
| 5330 | |
| 5331 | @findex SLASH_STRING |
| 5332 | @item SLASH_STRING |
| 5333 | This evaluates to a constant string you should use to produce an |
| 5334 | absolute filename from leading directories and the file's basename. |
| 5335 | @code{SLASH_STRING} is @code{"/"} on most systems, but might be |
| 5336 | @code{"\\"} for some Windows-based ports. |
| 5337 | @end table |
| 5338 | |
| 5339 | In addition to using these macros, be sure to use portable library |
| 5340 | functions whenever possible. For example, to extract a directory or a |
| 5341 | basename part from a file name, use the @code{dirname} and |
| 5342 | @code{basename} library functions (available in @code{libiberty} for |
| 5343 | platforms which don't provide them), instead of searching for a slash |
| 5344 | with @code{strrchr}. |
| 5345 | |
| 5346 | Another way to generalize @value{GDBN} along a particular interface is with an |
| 5347 | attribute struct. For example, @value{GDBN} has been generalized to handle |
| 5348 | multiple kinds of remote interfaces---not by @code{#ifdef}s everywhere, but |
| 5349 | by defining the @code{target_ops} structure and having a current target (as |
| 5350 | well as a stack of targets below it, for memory references). Whenever |
| 5351 | something needs to be done that depends on which remote interface we are |
| 5352 | using, a flag in the current target_ops structure is tested (e.g., |
| 5353 | @code{target_has_stack}), or a function is called through a pointer in the |
| 5354 | current target_ops structure. In this way, when a new remote interface |
| 5355 | is added, only one module needs to be touched---the one that actually |
| 5356 | implements the new remote interface. Other examples of |
| 5357 | attribute-structs are BFD access to multiple kinds of object file |
| 5358 | formats, or @value{GDBN}'s access to multiple source languages. |
| 5359 | |
| 5360 | Please avoid duplicating code. For example, in @value{GDBN} 3.x all |
| 5361 | the code interfacing between @code{ptrace} and the rest of |
| 5362 | @value{GDBN} was duplicated in @file{*-dep.c}, and so changing |
| 5363 | something was very painful. In @value{GDBN} 4.x, these have all been |
| 5364 | consolidated into @file{infptrace.c}. @file{infptrace.c} can deal |
| 5365 | with variations between systems the same way any system-independent |
| 5366 | file would (hooks, @code{#if defined}, etc.), and machines which are |
| 5367 | radically different don't need to use @file{infptrace.c} at all. |
| 5368 | |
| 5369 | All debugging code must be controllable using the @samp{set debug |
| 5370 | @var{module}} command. Do not use @code{printf} to print trace |
| 5371 | messages. Use @code{fprintf_unfiltered(gdb_stdlog, ...}. Do not use |
| 5372 | @code{#ifdef DEBUG}. |
| 5373 | |
| 5374 | |
| 5375 | @node Porting GDB |
| 5376 | |
| 5377 | @chapter Porting @value{GDBN} |
| 5378 | @cindex porting to new machines |
| 5379 | |
| 5380 | Most of the work in making @value{GDBN} compile on a new machine is in |
| 5381 | specifying the configuration of the machine. This is done in a |
| 5382 | dizzying variety of header files and configuration scripts, which we |
| 5383 | hope to make more sensible soon. Let's say your new host is called an |
| 5384 | @var{xyz} (e.g., @samp{sun4}), and its full three-part configuration |
| 5385 | name is @code{@var{arch}-@var{xvend}-@var{xos}} (e.g., |
| 5386 | @samp{sparc-sun-sunos4}). In particular: |
| 5387 | |
| 5388 | @itemize @bullet |
| 5389 | @item |
| 5390 | In the top level directory, edit @file{config.sub} and add @var{arch}, |
| 5391 | @var{xvend}, and @var{xos} to the lists of supported architectures, |
| 5392 | vendors, and operating systems near the bottom of the file. Also, add |
| 5393 | @var{xyz} as an alias that maps to |
| 5394 | @code{@var{arch}-@var{xvend}-@var{xos}}. You can test your changes by |
| 5395 | running |
| 5396 | |
| 5397 | @smallexample |
| 5398 | ./config.sub @var{xyz} |
| 5399 | @end smallexample |
| 5400 | |
| 5401 | @noindent |
| 5402 | and |
| 5403 | |
| 5404 | @smallexample |
| 5405 | ./config.sub @code{@var{arch}-@var{xvend}-@var{xos}} |
| 5406 | @end smallexample |
| 5407 | |
| 5408 | @noindent |
| 5409 | which should both respond with @code{@var{arch}-@var{xvend}-@var{xos}} |
| 5410 | and no error messages. |
| 5411 | |
| 5412 | @noindent |
| 5413 | You need to port BFD, if that hasn't been done already. Porting BFD is |
| 5414 | beyond the scope of this manual. |
| 5415 | |
| 5416 | @item |
| 5417 | To configure @value{GDBN} itself, edit @file{gdb/configure.host} to recognize |
| 5418 | your system and set @code{gdb_host} to @var{xyz}, and (unless your |
| 5419 | desired target is already available) also edit @file{gdb/configure.tgt}, |
| 5420 | setting @code{gdb_target} to something appropriate (for instance, |
| 5421 | @var{xyz}). |
| 5422 | |
| 5423 | @emph{Maintainer's note: Work in progress. The file |
| 5424 | @file{gdb/configure.host} originally needed to be modified when either a |
| 5425 | new native target or a new host machine was being added to @value{GDBN}. |
| 5426 | Recent changes have removed this requirement. The file now only needs |
| 5427 | to be modified when adding a new native configuration. This will likely |
| 5428 | changed again in the future.} |
| 5429 | |
| 5430 | @item |
| 5431 | Finally, you'll need to specify and define @value{GDBN}'s host-, native-, and |
| 5432 | target-dependent @file{.h} and @file{.c} files used for your |
| 5433 | configuration. |
| 5434 | @end itemize |
| 5435 | |
| 5436 | @node Releasing GDB |
| 5437 | |
| 5438 | @chapter Releasing @value{GDBN} |
| 5439 | @cindex making a new release of gdb |
| 5440 | |
| 5441 | @section Versions and Branches |
| 5442 | |
| 5443 | @subsection Version Identifiers |
| 5444 | |
| 5445 | @value{GDBN}'s version is determined by the file @file{gdb/version.in}. |
| 5446 | |
| 5447 | @value{GDBN}'s mainline uses ISO dates to differentiate between |
| 5448 | versions. The CVS repository uses @var{YYYY}-@var{MM}-@var{DD}-cvs |
| 5449 | while the corresponding snapshot uses @var{YYYYMMDD}. |
| 5450 | |
| 5451 | @value{GDBN}'s release branch uses a slightly more complicated scheme. |
| 5452 | When the branch is first cut, the mainline version identifier is |
| 5453 | prefixed with the @var{major}.@var{minor} from of the previous release |
| 5454 | series but with .90 appended. As draft releases are drawn from the |
| 5455 | branch, the minor minor number (.90) is incremented. Once the first |
| 5456 | release (@var{M}.@var{N}) has been made, the version prefix is updated |
| 5457 | to @var{M}.@var{N}.0.90 (dot zero, dot ninety). Follow on releases have |
| 5458 | an incremented minor minor version number (.0). |
| 5459 | |
| 5460 | Using 5.1 (previous) and 5.2 (current), the example below illustrates a |
| 5461 | typical sequence of version identifiers: |
| 5462 | |
| 5463 | @table @asis |
| 5464 | @item 5.1.1 |
| 5465 | final release from previous branch |
| 5466 | @item 2002-03-03-cvs |
| 5467 | main-line the day the branch is cut |
| 5468 | @item 5.1.90-2002-03-03-cvs |
| 5469 | corresponding branch version |
| 5470 | @item 5.1.91 |
| 5471 | first draft release candidate |
| 5472 | @item 5.1.91-2002-03-17-cvs |
| 5473 | updated branch version |
| 5474 | @item 5.1.92 |
| 5475 | second draft release candidate |
| 5476 | @item 5.1.92-2002-03-31-cvs |
| 5477 | updated branch version |
| 5478 | @item 5.1.93 |
| 5479 | final release candidate (see below) |
| 5480 | @item 5.2 |
| 5481 | official release |
| 5482 | @item 5.2.0.90-2002-04-07-cvs |
| 5483 | updated CVS branch version |
| 5484 | @item 5.2.1 |
| 5485 | second official release |
| 5486 | @end table |
| 5487 | |
| 5488 | Notes: |
| 5489 | |
| 5490 | @itemize @bullet |
| 5491 | @item |
| 5492 | Minor minor minor draft release candidates such as 5.2.0.91 have been |
| 5493 | omitted from the example. Such release candidates are, typically, never |
| 5494 | made. |
| 5495 | @item |
| 5496 | For 5.1.93 the bziped tar ball @file{gdb-5.1.93.tar.bz2} is just the |
| 5497 | official @file{gdb-5.2.tar} renamed and compressed. |
| 5498 | @end itemize |
| 5499 | |
| 5500 | To avoid version conflicts, vendors are expected to modify the file |
| 5501 | @file{gdb/version.in} to include a vendor unique alphabetic identifier |
| 5502 | (an official @value{GDBN} release never uses alphabetic characters in |
| 5503 | its version identifer). |
| 5504 | |
| 5505 | Since @value{GDBN} does not make minor minor minor releases (e.g., |
| 5506 | 5.1.0.1) the conflict between that and a minor minor draft release |
| 5507 | identifier (e.g., 5.1.0.90) is avoided. |
| 5508 | |
| 5509 | |
| 5510 | @subsection Branches |
| 5511 | |
| 5512 | @value{GDBN} draws a release series (5.2, 5.2.1, @dots{}) from a single |
| 5513 | release branch (gdb_5_2-branch). Since minor minor minor releases |
| 5514 | (5.1.0.1) are not made, the need to branch the release branch is avoided |
| 5515 | (it also turns out that the effort required for such a a branch and |
| 5516 | release is significantly greater than the effort needed to create a new |
| 5517 | release from the head of the release branch). |
| 5518 | |
| 5519 | Releases 5.0 and 5.1 used branch and release tags of the form: |
| 5520 | |
| 5521 | @smallexample |
| 5522 | gdb_N_M-YYYY-MM-DD-branchpoint |
| 5523 | gdb_N_M-YYYY-MM-DD-branch |
| 5524 | gdb_M_N-YYYY-MM-DD-release |
| 5525 | @end smallexample |
| 5526 | |
| 5527 | Release 5.2 is trialing the branch and release tags: |
| 5528 | |
| 5529 | @smallexample |
| 5530 | gdb_N_M-YYYY-MM-DD-branchpoint |
| 5531 | gdb_N_M-branch |
| 5532 | gdb_M_N-YYYY-MM-DD-release |
| 5533 | @end smallexample |
| 5534 | |
| 5535 | @emph{Pragmatics: The branchpoint and release tags need to identify when |
| 5536 | a branch and release are made. The branch tag, denoting the head of the |
| 5537 | branch, does not have this criteria.} |
| 5538 | |
| 5539 | |
| 5540 | @section Branch Commit Policy |
| 5541 | |
| 5542 | The branch commit policy is pretty slack. @value{GDBN} releases 5.0, |
| 5543 | 5.1 and 5.2 all used the below: |
| 5544 | |
| 5545 | @itemize @bullet |
| 5546 | @item |
| 5547 | The @file{gdb/MAINTAINERS} file still holds. |
| 5548 | @item |
| 5549 | Don't fix something on the branch unless/until it is also fixed in the |
| 5550 | trunk. If this isn't possible, mentioning it in the @file{gdb/PROBLEMS} |
| 5551 | file is better than committing a hack. |
| 5552 | @item |
| 5553 | When considering a patch for the branch, suggested criteria include: |
| 5554 | Does it fix a build? Does it fix the sequence @kbd{break main; run} |
| 5555 | when debugging a static binary? |
| 5556 | @item |
| 5557 | The further a change is from the core of @value{GDBN}, the less likely |
| 5558 | the change will worry anyone (e.g., target specific code). |
| 5559 | @item |
| 5560 | Only post a proposal to change the core of @value{GDBN} after you've |
| 5561 | sent individual bribes to all the people listed in the |
| 5562 | @file{MAINTAINERS} file @t{;-)} |
| 5563 | @end itemize |
| 5564 | |
| 5565 | @emph{Pragmatics: Provided updates are restricted to non-core |
| 5566 | functionality there is little chance that a broken change will be fatal. |
| 5567 | This means that changes such as adding a new architectures or (within |
| 5568 | reason) support for a new host are considered acceptable.} |
| 5569 | |
| 5570 | |
| 5571 | @section Obsoleting code |
| 5572 | |
| 5573 | Before anything else, poke the other developers (and around the source |
| 5574 | code) to see if there is anything that can be removed from @value{GDBN} |
| 5575 | (an old target, an unused file). |
| 5576 | |
| 5577 | Obsolete code is identified by adding an @code{OBSOLETE} prefix to every |
| 5578 | line. Doing this means that it is easy to identify something that has |
| 5579 | been obsoleted when greping through the sources. |
| 5580 | |
| 5581 | The process is done in stages --- this is mainly to ensure that the |
| 5582 | wider @value{GDBN} community has a reasonable opportunity to respond. |
| 5583 | Remember, everything on the Internet takes a week. |
| 5584 | |
| 5585 | @enumerate |
| 5586 | @item |
| 5587 | Post the proposal on @email{gdb@@sources.redhat.com, the GDB mailing |
| 5588 | list} Creating a bug report to track the task's state, is also highly |
| 5589 | recommended. |
| 5590 | @item |
| 5591 | Wait a week or so. |
| 5592 | @item |
| 5593 | Post the proposal on @email{gdb-announce@@sources.redhat.com, the GDB |
| 5594 | Announcement mailing list}. |
| 5595 | @item |
| 5596 | Wait a week or so. |
| 5597 | @item |
| 5598 | Go through and edit all relevant files and lines so that they are |
| 5599 | prefixed with the word @code{OBSOLETE}. |
| 5600 | @item |
| 5601 | Wait until the next GDB version, containing this obsolete code, has been |
| 5602 | released. |
| 5603 | @item |
| 5604 | Remove the obsolete code. |
| 5605 | @end enumerate |
| 5606 | |
| 5607 | @noindent |
| 5608 | @emph{Maintainer note: While removing old code is regrettable it is |
| 5609 | hopefully better for @value{GDBN}'s long term development. Firstly it |
| 5610 | helps the developers by removing code that is either no longer relevant |
| 5611 | or simply wrong. Secondly since it removes any history associated with |
| 5612 | the file (effectively clearing the slate) the developer has a much freer |
| 5613 | hand when it comes to fixing broken files.} |
| 5614 | |
| 5615 | |
| 5616 | |
| 5617 | @section Before the Branch |
| 5618 | |
| 5619 | The most important objective at this stage is to find and fix simple |
| 5620 | changes that become a pain to track once the branch is created. For |
| 5621 | instance, configuration problems that stop @value{GDBN} from even |
| 5622 | building. If you can't get the problem fixed, document it in the |
| 5623 | @file{gdb/PROBLEMS} file. |
| 5624 | |
| 5625 | @subheading Prompt for @file{gdb/NEWS} |
| 5626 | |
| 5627 | People always forget. Send a post reminding them but also if you know |
| 5628 | something interesting happened add it yourself. The @code{schedule} |
| 5629 | script will mention this in its e-mail. |
| 5630 | |
| 5631 | @subheading Review @file{gdb/README} |
| 5632 | |
| 5633 | Grab one of the nightly snapshots and then walk through the |
| 5634 | @file{gdb/README} looking for anything that can be improved. The |
| 5635 | @code{schedule} script will mention this in its e-mail. |
| 5636 | |
| 5637 | @subheading Refresh any imported files. |
| 5638 | |
| 5639 | A number of files are taken from external repositories. They include: |
| 5640 | |
| 5641 | @itemize @bullet |
| 5642 | @item |
| 5643 | @file{texinfo/texinfo.tex} |
| 5644 | @item |
| 5645 | @file{config.guess} et.@: al.@: (see the top-level @file{MAINTAINERS} |
| 5646 | file) |
| 5647 | @item |
| 5648 | @file{etc/standards.texi}, @file{etc/make-stds.texi} |
| 5649 | @end itemize |
| 5650 | |
| 5651 | @subheading Check the ARI |
| 5652 | |
| 5653 | @uref{http://sources.redhat.com/gdb/ari,,A.R.I.} is an @code{awk} script |
| 5654 | (Awk Regression Index ;-) that checks for a number of errors and coding |
| 5655 | conventions. The checks include things like using @code{malloc} instead |
| 5656 | of @code{xmalloc} and file naming problems. There shouldn't be any |
| 5657 | regressions. |
| 5658 | |
| 5659 | @subsection Review the bug data base |
| 5660 | |
| 5661 | Close anything obviously fixed. |
| 5662 | |
| 5663 | @subsection Check all cross targets build |
| 5664 | |
| 5665 | The targets are listed in @file{gdb/MAINTAINERS}. |
| 5666 | |
| 5667 | |
| 5668 | @section Cut the Branch |
| 5669 | |
| 5670 | @subheading Create the branch |
| 5671 | |
| 5672 | @smallexample |
| 5673 | $ u=5.1 |
| 5674 | $ v=5.2 |
| 5675 | $ V=`echo $v | sed 's/\./_/g'` |
| 5676 | $ D=`date -u +%Y-%m-%d` |
| 5677 | $ echo $u $V $D |
| 5678 | 5.1 5_2 2002-03-03 |
| 5679 | $ echo cvs -f -d :ext:sources.redhat.com:/cvs/src rtag \ |
| 5680 | -D $D-gmt gdb_$V-$D-branchpoint insight+dejagnu |
| 5681 | cvs -f -d :ext:sources.redhat.com:/cvs/src rtag |
| 5682 | -D 2002-03-03-gmt gdb_5_2-2002-03-03-branchpoint insight+dejagnu |
| 5683 | $ ^echo ^^ |
| 5684 | ... |
| 5685 | $ echo cvs -f -d :ext:sources.redhat.com:/cvs/src rtag \ |
| 5686 | -b -r gdb_$V-$D-branchpoint gdb_$V-branch insight+dejagnu |
| 5687 | cvs -f -d :ext:sources.redhat.com:/cvs/src rtag \ |
| 5688 | -b -r gdb_5_2-2002-03-03-branchpoint gdb_5_2-branch insight+dejagnu |
| 5689 | $ ^echo ^^ |
| 5690 | ... |
| 5691 | $ |
| 5692 | @end smallexample |
| 5693 | |
| 5694 | @itemize @bullet |
| 5695 | @item |
| 5696 | by using @kbd{-D YYYY-MM-DD-gmt} the branch is forced to an exact |
| 5697 | date/time. |
| 5698 | @item |
| 5699 | the trunk is first taged so that the branch point can easily be found |
| 5700 | @item |
| 5701 | Insight (which includes GDB) and dejagnu are all tagged at the same time |
| 5702 | @item |
| 5703 | @file{version.in} gets bumped to avoid version number conflicts |
| 5704 | @item |
| 5705 | the reading of @file{.cvsrc} is disabled using @file{-f} |
| 5706 | @end itemize |
| 5707 | |
| 5708 | @subheading Update @file{version.in} |
| 5709 | |
| 5710 | @smallexample |
| 5711 | $ u=5.1 |
| 5712 | $ v=5.2 |
| 5713 | $ V=`echo $v | sed 's/\./_/g'` |
| 5714 | $ echo $u $v$V |
| 5715 | 5.1 5_2 |
| 5716 | $ cd /tmp |
| 5717 | $ echo cvs -f -d :ext:sources.redhat.com:/cvs/src co \ |
| 5718 | -r gdb_$V-branch src/gdb/version.in |
| 5719 | cvs -f -d :ext:sources.redhat.com:/cvs/src co |
| 5720 | -r gdb_5_2-branch src/gdb/version.in |
| 5721 | $ ^echo ^^ |
| 5722 | U src/gdb/version.in |
| 5723 | $ cd src/gdb |
| 5724 | $ echo $u.90-0000-00-00-cvs > version.in |
| 5725 | $ cat version.in |
| 5726 | 5.1.90-0000-00-00-cvs |
| 5727 | $ cvs -f commit version.in |
| 5728 | @end smallexample |
| 5729 | |
| 5730 | @itemize @bullet |
| 5731 | @item |
| 5732 | @file{0000-00-00} is used as a date to pump prime the version.in update |
| 5733 | mechanism |
| 5734 | @item |
| 5735 | @file{.90} and the previous branch version are used as fairly arbitrary |
| 5736 | initial branch version number |
| 5737 | @end itemize |
| 5738 | |
| 5739 | |
| 5740 | @subheading Update the web and news pages |
| 5741 | |
| 5742 | Something? |
| 5743 | |
| 5744 | @subheading Tweak cron to track the new branch |
| 5745 | |
| 5746 | The file @file{gdbadmin/cron/crontab} contains gdbadmin's cron table. |
| 5747 | This file needs to be updated so that: |
| 5748 | |
| 5749 | @itemize @bullet |
| 5750 | @item |
| 5751 | a daily timestamp is added to the file @file{version.in} |
| 5752 | @item |
| 5753 | the new branch is included in the snapshot process |
| 5754 | @end itemize |
| 5755 | |
| 5756 | @noindent |
| 5757 | See the file @file{gdbadmin/cron/README} for how to install the updated |
| 5758 | cron table. |
| 5759 | |
| 5760 | The file @file{gdbadmin/ss/README} should also be reviewed to reflect |
| 5761 | any changes. That file is copied to both the branch/ and current/ |
| 5762 | snapshot directories. |
| 5763 | |
| 5764 | |
| 5765 | @subheading Update the NEWS and README files |
| 5766 | |
| 5767 | The @file{NEWS} file needs to be updated so that on the branch it refers |
| 5768 | to @emph{changes in the current release} while on the trunk it also |
| 5769 | refers to @emph{changes since the current release}. |
| 5770 | |
| 5771 | The @file{README} file needs to be updated so that it refers to the |
| 5772 | current release. |
| 5773 | |
| 5774 | @subheading Post the branch info |
| 5775 | |
| 5776 | Send an announcement to the mailing lists: |
| 5777 | |
| 5778 | @itemize @bullet |
| 5779 | @item |
| 5780 | @email{gdb-announce@@sources.redhat.com, GDB Announcement mailing list} |
| 5781 | @item |
| 5782 | @email{gdb@@sources.redhat.com, GDB Discsussion mailing list} and |
| 5783 | @email{gdb-testers@@sources.redhat.com, GDB Discsussion mailing list} |
| 5784 | @end itemize |
| 5785 | |
| 5786 | @emph{Pragmatics: The branch creation is sent to the announce list to |
| 5787 | ensure that people people not subscribed to the higher volume discussion |
| 5788 | list are alerted.} |
| 5789 | |
| 5790 | The announcement should include: |
| 5791 | |
| 5792 | @itemize @bullet |
| 5793 | @item |
| 5794 | the branch tag |
| 5795 | @item |
| 5796 | how to check out the branch using CVS |
| 5797 | @item |
| 5798 | the date/number of weeks until the release |
| 5799 | @item |
| 5800 | the branch commit policy |
| 5801 | still holds. |
| 5802 | @end itemize |
| 5803 | |
| 5804 | @section Stabilize the branch |
| 5805 | |
| 5806 | Something goes here. |
| 5807 | |
| 5808 | @section Create a Release |
| 5809 | |
| 5810 | The process of creating and then making available a release is broken |
| 5811 | down into a number of stages. The first part addresses the technical |
| 5812 | process of creating a releasable tar ball. The later stages address the |
| 5813 | process of releasing that tar ball. |
| 5814 | |
| 5815 | When making a release candidate just the first section is needed. |
| 5816 | |
| 5817 | @subsection Create a release candidate |
| 5818 | |
| 5819 | The objective at this stage is to create a set of tar balls that can be |
| 5820 | made available as a formal release (or as a less formal release |
| 5821 | candidate). |
| 5822 | |
| 5823 | @subsubheading Freeze the branch |
| 5824 | |
| 5825 | Send out an e-mail notifying everyone that the branch is frozen to |
| 5826 | @email{gdb-patches@@sources.redhat.com}. |
| 5827 | |
| 5828 | @subsubheading Establish a few defaults. |
| 5829 | |
| 5830 | @smallexample |
| 5831 | $ b=gdb_5_2-branch |
| 5832 | $ v=5.2 |
| 5833 | $ t=/sourceware/snapshot-tmp/gdbadmin-tmp |
| 5834 | $ echo $t/$b/$v |
| 5835 | /sourceware/snapshot-tmp/gdbadmin-tmp/gdb_5_2-branch/5.2 |
| 5836 | $ mkdir -p $t/$b/$v |
| 5837 | $ cd $t/$b/$v |
| 5838 | $ pwd |
| 5839 | /sourceware/snapshot-tmp/gdbadmin-tmp/gdb_5_2-branch/5.2 |
| 5840 | $ which autoconf |
| 5841 | /home/gdbadmin/bin/autoconf |
| 5842 | $ |
| 5843 | @end smallexample |
| 5844 | |
| 5845 | @noindent |
| 5846 | Notes: |
| 5847 | |
| 5848 | @itemize @bullet |
| 5849 | @item |
| 5850 | Check the @code{autoconf} version carefully. You want to be using the |
| 5851 | version taken from the @file{binutils} snapshot directory, which can be |
| 5852 | found at @uref{ftp://sources.redhat.com/pub/binutils/}. It is very |
| 5853 | unlikely that a system installed version of @code{autoconf} (e.g., |
| 5854 | @file{/usr/bin/autoconf}) is correct. |
| 5855 | @end itemize |
| 5856 | |
| 5857 | @subsubheading Check out the relevant modules: |
| 5858 | |
| 5859 | @smallexample |
| 5860 | $ for m in gdb insight dejagnu |
| 5861 | do |
| 5862 | ( mkdir -p $m && cd $m && cvs -q -f -d /cvs/src co -P -r $b $m ) |
| 5863 | done |
| 5864 | $ |
| 5865 | @end smallexample |
| 5866 | |
| 5867 | @noindent |
| 5868 | Note: |
| 5869 | |
| 5870 | @itemize @bullet |
| 5871 | @item |
| 5872 | The reading of @file{.cvsrc} is disabled (@file{-f}) so that there isn't |
| 5873 | any confusion between what is written here and what your local |
| 5874 | @code{cvs} really does. |
| 5875 | @end itemize |
| 5876 | |
| 5877 | @subsubheading Update relevant files. |
| 5878 | |
| 5879 | @table @file |
| 5880 | |
| 5881 | @item gdb/NEWS |
| 5882 | |
| 5883 | Major releases get their comments added as part of the mainline. Minor |
| 5884 | releases should probably mention any significant bugs that were fixed. |
| 5885 | |
| 5886 | Don't forget to include the @file{ChangeLog} entry. |
| 5887 | |
| 5888 | @smallexample |
| 5889 | $ emacs gdb/src/gdb/NEWS |
| 5890 | ... |
| 5891 | c-x 4 a |
| 5892 | ... |
| 5893 | c-x c-s c-x c-c |
| 5894 | $ cp gdb/src/gdb/NEWS insight/src/gdb/NEWS |
| 5895 | $ cp gdb/src/gdb/ChangeLog insight/src/gdb/ChangeLog |
| 5896 | @end smallexample |
| 5897 | |
| 5898 | @item gdb/README |
| 5899 | |
| 5900 | You'll need to update: |
| 5901 | |
| 5902 | @itemize @bullet |
| 5903 | @item |
| 5904 | the version |
| 5905 | @item |
| 5906 | the update date |
| 5907 | @item |
| 5908 | who did it |
| 5909 | @end itemize |
| 5910 | |
| 5911 | @smallexample |
| 5912 | $ emacs gdb/src/gdb/README |
| 5913 | ... |
| 5914 | c-x 4 a |
| 5915 | ... |
| 5916 | c-x c-s c-x c-c |
| 5917 | $ cp gdb/src/gdb/README insight/src/gdb/README |
| 5918 | $ cp gdb/src/gdb/ChangeLog insight/src/gdb/ChangeLog |
| 5919 | @end smallexample |
| 5920 | |
| 5921 | @emph{Maintainer note: Hopefully the @file{README} file was reviewed |
| 5922 | before the initial branch was cut so just a simple substitute is needed |
| 5923 | to get it updated.} |
| 5924 | |
| 5925 | @emph{Maintainer note: Other projects generate @file{README} and |
| 5926 | @file{INSTALL} from the core documentation. This might be worth |
| 5927 | pursuing.} |
| 5928 | |
| 5929 | @item gdb/version.in |
| 5930 | |
| 5931 | @smallexample |
| 5932 | $ echo $v > gdb/src/gdb/version.in |
| 5933 | $ cat gdb/src/gdb/version.in |
| 5934 | 5.2 |
| 5935 | $ emacs gdb/src/gdb/version.in |
| 5936 | ... |
| 5937 | c-x 4 a |
| 5938 | ... Bump to version ... |
| 5939 | c-x c-s c-x c-c |
| 5940 | $ cp gdb/src/gdb/version.in insight/src/gdb/version.in |
| 5941 | $ cp gdb/src/gdb/ChangeLog insight/src/gdb/ChangeLog |
| 5942 | @end smallexample |
| 5943 | |
| 5944 | @item dejagnu/src/dejagnu/configure.in |
| 5945 | |
| 5946 | Dejagnu is more complicated. The version number is a parameter to |
| 5947 | @code{AM_INIT_AUTOMAKE}. Tweak it to read something like gdb-5.1.91. |
| 5948 | |
| 5949 | Don't forget to re-generate @file{configure}. |
| 5950 | |
| 5951 | Don't forget to include a @file{ChangeLog} entry. |
| 5952 | |
| 5953 | @smallexample |
| 5954 | $ emacs dejagnu/src/dejagnu/configure.in |
| 5955 | ... |
| 5956 | c-x 4 a |
| 5957 | ... |
| 5958 | c-x c-s c-x c-c |
| 5959 | $ ( cd dejagnu/src/dejagnu && autoconf ) |
| 5960 | @end smallexample |
| 5961 | |
| 5962 | @end table |
| 5963 | |
| 5964 | @subsubheading Do the dirty work |
| 5965 | |
| 5966 | This is identical to the process used to create the daily snapshot. |
| 5967 | |
| 5968 | @smallexample |
| 5969 | $ for m in gdb insight |
| 5970 | do |
| 5971 | ( cd $m/src && gmake -f src-release $m.tar ) |
| 5972 | done |
| 5973 | $ ( m=dejagnu; cd $m/src && gmake -f src-release $m.tar.bz2 ) |
| 5974 | @end smallexample |
| 5975 | |
| 5976 | If the top level source directory does not have @file{src-release} |
| 5977 | (@value{GDBN} version 5.3.1 or earlier), try these commands instead: |
| 5978 | |
| 5979 | @smallexample |
| 5980 | $ for m in gdb insight |
| 5981 | do |
| 5982 | ( cd $m/src && gmake -f Makefile.in $m.tar ) |
| 5983 | done |
| 5984 | $ ( m=dejagnu; cd $m/src && gmake -f Makefile.in $m.tar.bz2 ) |
| 5985 | @end smallexample |
| 5986 | |
| 5987 | @subsubheading Check the source files |
| 5988 | |
| 5989 | You're looking for files that have mysteriously disappeared. |
| 5990 | @kbd{distclean} has the habit of deleting files it shouldn't. Watch out |
| 5991 | for the @file{version.in} update @kbd{cronjob}. |
| 5992 | |
| 5993 | @smallexample |
| 5994 | $ ( cd gdb/src && cvs -f -q -n update ) |
| 5995 | M djunpack.bat |
| 5996 | ? gdb-5.1.91.tar |
| 5997 | ? proto-toplev |
| 5998 | @dots{} lots of generated files @dots{} |
| 5999 | M gdb/ChangeLog |
| 6000 | M gdb/NEWS |
| 6001 | M gdb/README |
| 6002 | M gdb/version.in |
| 6003 | @dots{} lots of generated files @dots{} |
| 6004 | $ |
| 6005 | @end smallexample |
| 6006 | |
| 6007 | @noindent |
| 6008 | @emph{Don't worry about the @file{gdb.info-??} or |
| 6009 | @file{gdb/p-exp.tab.c}. They were generated (and yes @file{gdb.info-1} |
| 6010 | was also generated only something strange with CVS means that they |
| 6011 | didn't get supressed). Fixing it would be nice though.} |
| 6012 | |
| 6013 | @subsubheading Create compressed versions of the release |
| 6014 | |
| 6015 | @smallexample |
| 6016 | $ cp */src/*.tar . |
| 6017 | $ cp */src/*.bz2 . |
| 6018 | $ ls -F |
| 6019 | dejagnu/ dejagnu-gdb-5.2.tar.bz2 gdb/ gdb-5.2.tar insight/ insight-5.2.tar |
| 6020 | $ for m in gdb insight |
| 6021 | do |
| 6022 | bzip2 -v -9 -c $m-$v.tar > $m-$v.tar.bz2 |
| 6023 | gzip -v -9 -c $m-$v.tar > $m-$v.tar.gz |
| 6024 | done |
| 6025 | $ |
| 6026 | @end smallexample |
| 6027 | |
| 6028 | @noindent |
| 6029 | Note: |
| 6030 | |
| 6031 | @itemize @bullet |
| 6032 | @item |
| 6033 | A pipe such as @kbd{bunzip2 < xxx.bz2 | gzip -9 > xxx.gz} is not since, |
| 6034 | in that mode, @code{gzip} does not know the name of the file and, hence, |
| 6035 | can not include it in the compressed file. This is also why the release |
| 6036 | process runs @code{tar} and @code{bzip2} as separate passes. |
| 6037 | @end itemize |
| 6038 | |
| 6039 | @subsection Sanity check the tar ball |
| 6040 | |
| 6041 | Pick a popular machine (Solaris/PPC?) and try the build on that. |
| 6042 | |
| 6043 | @smallexample |
| 6044 | $ bunzip2 < gdb-5.2.tar.bz2 | tar xpf - |
| 6045 | $ cd gdb-5.2 |
| 6046 | $ ./configure |
| 6047 | $ make |
| 6048 | @dots{} |
| 6049 | $ ./gdb/gdb ./gdb/gdb |
| 6050 | GNU gdb 5.2 |
| 6051 | @dots{} |
| 6052 | (gdb) b main |
| 6053 | Breakpoint 1 at 0x80732bc: file main.c, line 734. |
| 6054 | (gdb) run |
| 6055 | Starting program: /tmp/gdb-5.2/gdb/gdb |
| 6056 | |
| 6057 | Breakpoint 1, main (argc=1, argv=0xbffff8b4) at main.c:734 |
| 6058 | 734 catch_errors (captured_main, &args, "", RETURN_MASK_ALL); |
| 6059 | (gdb) print args |
| 6060 | $1 = @{argc = 136426532, argv = 0x821b7f0@} |
| 6061 | (gdb) |
| 6062 | @end smallexample |
| 6063 | |
| 6064 | @subsection Make a release candidate available |
| 6065 | |
| 6066 | If this is a release candidate then the only remaining steps are: |
| 6067 | |
| 6068 | @enumerate |
| 6069 | @item |
| 6070 | Commit @file{version.in} and @file{ChangeLog} |
| 6071 | @item |
| 6072 | Tweak @file{version.in} (and @file{ChangeLog} to read |
| 6073 | @var{L}.@var{M}.@var{N}-0000-00-00-cvs so that the version update |
| 6074 | process can restart. |
| 6075 | @item |
| 6076 | Make the release candidate available in |
| 6077 | @uref{ftp://sources.redhat.com/pub/gdb/snapshots/branch} |
| 6078 | @item |
| 6079 | Notify the relevant mailing lists ( @email{gdb@@sources.redhat.com} and |
| 6080 | @email{gdb-testers@@sources.redhat.com} that the candidate is available. |
| 6081 | @end enumerate |
| 6082 | |
| 6083 | @subsection Make a formal release available |
| 6084 | |
| 6085 | (And you thought all that was required was to post an e-mail.) |
| 6086 | |
| 6087 | @subsubheading Install on sware |
| 6088 | |
| 6089 | Copy the new files to both the release and the old release directory: |
| 6090 | |
| 6091 | @smallexample |
| 6092 | $ cp *.bz2 *.gz ~ftp/pub/gdb/old-releases/ |
| 6093 | $ cp *.bz2 *.gz ~ftp/pub/gdb/releases |
| 6094 | @end smallexample |
| 6095 | |
| 6096 | @noindent |
| 6097 | Clean up the releases directory so that only the most recent releases |
| 6098 | are available (e.g. keep 5.2 and 5.2.1 but remove 5.1): |
| 6099 | |
| 6100 | @smallexample |
| 6101 | $ cd ~ftp/pub/gdb/releases |
| 6102 | $ rm @dots{} |
| 6103 | @end smallexample |
| 6104 | |
| 6105 | @noindent |
| 6106 | Update the file @file{README} and @file{.message} in the releases |
| 6107 | directory: |
| 6108 | |
| 6109 | @smallexample |
| 6110 | $ vi README |
| 6111 | @dots{} |
| 6112 | $ rm -f .message |
| 6113 | $ ln README .message |
| 6114 | @end smallexample |
| 6115 | |
| 6116 | @subsubheading Update the web pages. |
| 6117 | |
| 6118 | @table @file |
| 6119 | |
| 6120 | @item htdocs/download/ANNOUNCEMENT |
| 6121 | This file, which is posted as the official announcement, includes: |
| 6122 | @itemize @bullet |
| 6123 | @item |
| 6124 | General announcement |
| 6125 | @item |
| 6126 | News. If making an @var{M}.@var{N}.1 release, retain the news from |
| 6127 | earlier @var{M}.@var{N} release. |
| 6128 | @item |
| 6129 | Errata |
| 6130 | @end itemize |
| 6131 | |
| 6132 | @item htdocs/index.html |
| 6133 | @itemx htdocs/news/index.html |
| 6134 | @itemx htdocs/download/index.html |
| 6135 | These files include: |
| 6136 | @itemize @bullet |
| 6137 | @item |
| 6138 | announcement of the most recent release |
| 6139 | @item |
| 6140 | news entry (remember to update both the top level and the news directory). |
| 6141 | @end itemize |
| 6142 | These pages also need to be regenerate using @code{index.sh}. |
| 6143 | |
| 6144 | @item download/onlinedocs/ |
| 6145 | You need to find the magic command that is used to generate the online |
| 6146 | docs from the @file{.tar.bz2}. The best way is to look in the output |
| 6147 | from one of the nightly @code{cron} jobs and then just edit accordingly. |
| 6148 | Something like: |
| 6149 | |
| 6150 | @smallexample |
| 6151 | $ ~/ss/update-web-docs \ |
| 6152 | ~ftp/pub/gdb/releases/gdb-5.2.tar.bz2 \ |
| 6153 | $PWD/www \ |
| 6154 | /www/sourceware/htdocs/gdb/download/onlinedocs \ |
| 6155 | gdb |
| 6156 | @end smallexample |
| 6157 | |
| 6158 | @item download/ari/ |
| 6159 | Just like the online documentation. Something like: |
| 6160 | |
| 6161 | @smallexample |
| 6162 | $ /bin/sh ~/ss/update-web-ari \ |
| 6163 | ~ftp/pub/gdb/releases/gdb-5.2.tar.bz2 \ |
| 6164 | $PWD/www \ |
| 6165 | /www/sourceware/htdocs/gdb/download/ari \ |
| 6166 | gdb |
| 6167 | @end smallexample |
| 6168 | |
| 6169 | @end table |
| 6170 | |
| 6171 | @subsubheading Shadow the pages onto gnu |
| 6172 | |
| 6173 | Something goes here. |
| 6174 | |
| 6175 | |
| 6176 | @subsubheading Install the @value{GDBN} tar ball on GNU |
| 6177 | |
| 6178 | At the time of writing, the GNU machine was @kbd{gnudist.gnu.org} in |
| 6179 | @file{~ftp/gnu/gdb}. |
| 6180 | |
| 6181 | @subsubheading Make the @file{ANNOUNCEMENT} |
| 6182 | |
| 6183 | Post the @file{ANNOUNCEMENT} file you created above to: |
| 6184 | |
| 6185 | @itemize @bullet |
| 6186 | @item |
| 6187 | @email{gdb-announce@@sources.redhat.com, GDB Announcement mailing list} |
| 6188 | @item |
| 6189 | @email{info-gnu@@gnu.org, General GNU Announcement list} (but delay it a |
| 6190 | day or so to let things get out) |
| 6191 | @item |
| 6192 | @email{bug-gdb@@gnu.org, GDB Bug Report mailing list} |
| 6193 | @end itemize |
| 6194 | |
| 6195 | @subsection Cleanup |
| 6196 | |
| 6197 | The release is out but you're still not finished. |
| 6198 | |
| 6199 | @subsubheading Commit outstanding changes |
| 6200 | |
| 6201 | In particular you'll need to commit any changes to: |
| 6202 | |
| 6203 | @itemize @bullet |
| 6204 | @item |
| 6205 | @file{gdb/ChangeLog} |
| 6206 | @item |
| 6207 | @file{gdb/version.in} |
| 6208 | @item |
| 6209 | @file{gdb/NEWS} |
| 6210 | @item |
| 6211 | @file{gdb/README} |
| 6212 | @end itemize |
| 6213 | |
| 6214 | @subsubheading Tag the release |
| 6215 | |
| 6216 | Something like: |
| 6217 | |
| 6218 | @smallexample |
| 6219 | $ d=`date -u +%Y-%m-%d` |
| 6220 | $ echo $d |
| 6221 | 2002-01-24 |
| 6222 | $ ( cd insight/src/gdb && cvs -f -q update ) |
| 6223 | $ ( cd insight/src && cvs -f -q tag gdb_5_2-$d-release ) |
| 6224 | @end smallexample |
| 6225 | |
| 6226 | Insight is used since that contains more of the release than |
| 6227 | @value{GDBN} (@code{dejagnu} doesn't get tagged but I think we can live |
| 6228 | with that). |
| 6229 | |
| 6230 | @subsubheading Mention the release on the trunk |
| 6231 | |
| 6232 | Just put something in the @file{ChangeLog} so that the trunk also |
| 6233 | indicates when the release was made. |
| 6234 | |
| 6235 | @subsubheading Restart @file{gdb/version.in} |
| 6236 | |
| 6237 | If @file{gdb/version.in} does not contain an ISO date such as |
| 6238 | @kbd{2002-01-24} then the daily @code{cronjob} won't update it. Having |
| 6239 | committed all the release changes it can be set to |
| 6240 | @file{5.2.0_0000-00-00-cvs} which will restart things (yes the @kbd{_} |
| 6241 | is important - it affects the snapshot process). |
| 6242 | |
| 6243 | Don't forget the @file{ChangeLog}. |
| 6244 | |
| 6245 | @subsubheading Merge into trunk |
| 6246 | |
| 6247 | The files committed to the branch may also need changes merged into the |
| 6248 | trunk. |
| 6249 | |
| 6250 | @subsubheading Revise the release schedule |
| 6251 | |
| 6252 | Post a revised release schedule to @email{gdb@@sources.redhat.com, GDB |
| 6253 | Discussion List} with an updated announcement. The schedule can be |
| 6254 | generated by running: |
| 6255 | |
| 6256 | @smallexample |
| 6257 | $ ~/ss/schedule `date +%s` schedule |
| 6258 | @end smallexample |
| 6259 | |
| 6260 | @noindent |
| 6261 | The first parameter is approximate date/time in seconds (from the epoch) |
| 6262 | of the most recent release. |
| 6263 | |
| 6264 | Also update the schedule @code{cronjob}. |
| 6265 | |
| 6266 | @section Post release |
| 6267 | |
| 6268 | Remove any @code{OBSOLETE} code. |
| 6269 | |
| 6270 | @node Testsuite |
| 6271 | |
| 6272 | @chapter Testsuite |
| 6273 | @cindex test suite |
| 6274 | |
| 6275 | The testsuite is an important component of the @value{GDBN} package. |
| 6276 | While it is always worthwhile to encourage user testing, in practice |
| 6277 | this is rarely sufficient; users typically use only a small subset of |
| 6278 | the available commands, and it has proven all too common for a change |
| 6279 | to cause a significant regression that went unnoticed for some time. |
| 6280 | |
| 6281 | The @value{GDBN} testsuite uses the DejaGNU testing framework. |
| 6282 | DejaGNU is built using @code{Tcl} and @code{expect}. The tests |
| 6283 | themselves are calls to various @code{Tcl} procs; the framework runs all the |
| 6284 | procs and summarizes the passes and fails. |
| 6285 | |
| 6286 | @section Using the Testsuite |
| 6287 | |
| 6288 | @cindex running the test suite |
| 6289 | To run the testsuite, simply go to the @value{GDBN} object directory (or to the |
| 6290 | testsuite's objdir) and type @code{make check}. This just sets up some |
| 6291 | environment variables and invokes DejaGNU's @code{runtest} script. While |
| 6292 | the testsuite is running, you'll get mentions of which test file is in use, |
| 6293 | and a mention of any unexpected passes or fails. When the testsuite is |
| 6294 | finished, you'll get a summary that looks like this: |
| 6295 | |
| 6296 | @smallexample |
| 6297 | === gdb Summary === |
| 6298 | |
| 6299 | # of expected passes 6016 |
| 6300 | # of unexpected failures 58 |
| 6301 | # of unexpected successes 5 |
| 6302 | # of expected failures 183 |
| 6303 | # of unresolved testcases 3 |
| 6304 | # of untested testcases 5 |
| 6305 | @end smallexample |
| 6306 | |
| 6307 | The ideal test run consists of expected passes only; however, reality |
| 6308 | conspires to keep us from this ideal. Unexpected failures indicate |
| 6309 | real problems, whether in @value{GDBN} or in the testsuite. Expected |
| 6310 | failures are still failures, but ones which have been decided are too |
| 6311 | hard to deal with at the time; for instance, a test case might work |
| 6312 | everywhere except on AIX, and there is no prospect of the AIX case |
| 6313 | being fixed in the near future. Expected failures should not be added |
| 6314 | lightly, since you may be masking serious bugs in @value{GDBN}. |
| 6315 | Unexpected successes are expected fails that are passing for some |
| 6316 | reason, while unresolved and untested cases often indicate some minor |
| 6317 | catastrophe, such as the compiler being unable to deal with a test |
| 6318 | program. |
| 6319 | |
| 6320 | When making any significant change to @value{GDBN}, you should run the |
| 6321 | testsuite before and after the change, to confirm that there are no |
| 6322 | regressions. Note that truly complete testing would require that you |
| 6323 | run the testsuite with all supported configurations and a variety of |
| 6324 | compilers; however this is more than really necessary. In many cases |
| 6325 | testing with a single configuration is sufficient. Other useful |
| 6326 | options are to test one big-endian (Sparc) and one little-endian (x86) |
| 6327 | host, a cross config with a builtin simulator (powerpc-eabi, |
| 6328 | mips-elf), or a 64-bit host (Alpha). |
| 6329 | |
| 6330 | If you add new functionality to @value{GDBN}, please consider adding |
| 6331 | tests for it as well; this way future @value{GDBN} hackers can detect |
| 6332 | and fix their changes that break the functionality you added. |
| 6333 | Similarly, if you fix a bug that was not previously reported as a test |
| 6334 | failure, please add a test case for it. Some cases are extremely |
| 6335 | difficult to test, such as code that handles host OS failures or bugs |
| 6336 | in particular versions of compilers, and it's OK not to try to write |
| 6337 | tests for all of those. |
| 6338 | |
| 6339 | @section Testsuite Organization |
| 6340 | |
| 6341 | @cindex test suite organization |
| 6342 | The testsuite is entirely contained in @file{gdb/testsuite}. While the |
| 6343 | testsuite includes some makefiles and configury, these are very minimal, |
| 6344 | and used for little besides cleaning up, since the tests themselves |
| 6345 | handle the compilation of the programs that @value{GDBN} will run. The file |
| 6346 | @file{testsuite/lib/gdb.exp} contains common utility procs useful for |
| 6347 | all @value{GDBN} tests, while the directory @file{testsuite/config} contains |
| 6348 | configuration-specific files, typically used for special-purpose |
| 6349 | definitions of procs like @code{gdb_load} and @code{gdb_start}. |
| 6350 | |
| 6351 | The tests themselves are to be found in @file{testsuite/gdb.*} and |
| 6352 | subdirectories of those. The names of the test files must always end |
| 6353 | with @file{.exp}. DejaGNU collects the test files by wildcarding |
| 6354 | in the test directories, so both subdirectories and individual files |
| 6355 | get chosen and run in alphabetical order. |
| 6356 | |
| 6357 | The following table lists the main types of subdirectories and what they |
| 6358 | are for. Since DejaGNU finds test files no matter where they are |
| 6359 | located, and since each test file sets up its own compilation and |
| 6360 | execution environment, this organization is simply for convenience and |
| 6361 | intelligibility. |
| 6362 | |
| 6363 | @table @file |
| 6364 | @item gdb.base |
| 6365 | This is the base testsuite. The tests in it should apply to all |
| 6366 | configurations of @value{GDBN} (but generic native-only tests may live here). |
| 6367 | The test programs should be in the subset of C that is valid K&R, |
| 6368 | ANSI/ISO, and C++ (@code{#ifdef}s are allowed if necessary, for instance |
| 6369 | for prototypes). |
| 6370 | |
| 6371 | @item gdb.@var{lang} |
| 6372 | Language-specific tests for any language @var{lang} besides C. Examples are |
| 6373 | @file{gdb.c++} and @file{gdb.java}. |
| 6374 | |
| 6375 | @item gdb.@var{platform} |
| 6376 | Non-portable tests. The tests are specific to a specific configuration |
| 6377 | (host or target), such as HP-UX or eCos. Example is @file{gdb.hp}, for |
| 6378 | HP-UX. |
| 6379 | |
| 6380 | @item gdb.@var{compiler} |
| 6381 | Tests specific to a particular compiler. As of this writing (June |
| 6382 | 1999), there aren't currently any groups of tests in this category that |
| 6383 | couldn't just as sensibly be made platform-specific, but one could |
| 6384 | imagine a @file{gdb.gcc}, for tests of @value{GDBN}'s handling of GCC |
| 6385 | extensions. |
| 6386 | |
| 6387 | @item gdb.@var{subsystem} |
| 6388 | Tests that exercise a specific @value{GDBN} subsystem in more depth. For |
| 6389 | instance, @file{gdb.disasm} exercises various disassemblers, while |
| 6390 | @file{gdb.stabs} tests pathways through the stabs symbol reader. |
| 6391 | @end table |
| 6392 | |
| 6393 | @section Writing Tests |
| 6394 | @cindex writing tests |
| 6395 | |
| 6396 | In many areas, the @value{GDBN} tests are already quite comprehensive; you |
| 6397 | should be able to copy existing tests to handle new cases. |
| 6398 | |
| 6399 | You should try to use @code{gdb_test} whenever possible, since it |
| 6400 | includes cases to handle all the unexpected errors that might happen. |
| 6401 | However, it doesn't cost anything to add new test procedures; for |
| 6402 | instance, @file{gdb.base/exprs.exp} defines a @code{test_expr} that |
| 6403 | calls @code{gdb_test} multiple times. |
| 6404 | |
| 6405 | Only use @code{send_gdb} and @code{gdb_expect} when absolutely |
| 6406 | necessary, such as when @value{GDBN} has several valid responses to a command. |
| 6407 | |
| 6408 | The source language programs do @emph{not} need to be in a consistent |
| 6409 | style. Since @value{GDBN} is used to debug programs written in many different |
| 6410 | styles, it's worth having a mix of styles in the testsuite; for |
| 6411 | instance, some @value{GDBN} bugs involving the display of source lines would |
| 6412 | never manifest themselves if the programs used GNU coding style |
| 6413 | uniformly. |
| 6414 | |
| 6415 | @node Hints |
| 6416 | |
| 6417 | @chapter Hints |
| 6418 | |
| 6419 | Check the @file{README} file, it often has useful information that does not |
| 6420 | appear anywhere else in the directory. |
| 6421 | |
| 6422 | @menu |
| 6423 | * Getting Started:: Getting started working on @value{GDBN} |
| 6424 | * Debugging GDB:: Debugging @value{GDBN} with itself |
| 6425 | @end menu |
| 6426 | |
| 6427 | @node Getting Started,,, Hints |
| 6428 | |
| 6429 | @section Getting Started |
| 6430 | |
| 6431 | @value{GDBN} is a large and complicated program, and if you first starting to |
| 6432 | work on it, it can be hard to know where to start. Fortunately, if you |
| 6433 | know how to go about it, there are ways to figure out what is going on. |
| 6434 | |
| 6435 | This manual, the @value{GDBN} Internals manual, has information which applies |
| 6436 | generally to many parts of @value{GDBN}. |
| 6437 | |
| 6438 | Information about particular functions or data structures are located in |
| 6439 | comments with those functions or data structures. If you run across a |
| 6440 | function or a global variable which does not have a comment correctly |
| 6441 | explaining what is does, this can be thought of as a bug in @value{GDBN}; feel |
| 6442 | free to submit a bug report, with a suggested comment if you can figure |
| 6443 | out what the comment should say. If you find a comment which is |
| 6444 | actually wrong, be especially sure to report that. |
| 6445 | |
| 6446 | Comments explaining the function of macros defined in host, target, or |
| 6447 | native dependent files can be in several places. Sometimes they are |
| 6448 | repeated every place the macro is defined. Sometimes they are where the |
| 6449 | macro is used. Sometimes there is a header file which supplies a |
| 6450 | default definition of the macro, and the comment is there. This manual |
| 6451 | also documents all the available macros. |
| 6452 | @c (@pxref{Host Conditionals}, @pxref{Target |
| 6453 | @c Conditionals}, @pxref{Native Conditionals}, and @pxref{Obsolete |
| 6454 | @c Conditionals}) |
| 6455 | |
| 6456 | Start with the header files. Once you have some idea of how |
| 6457 | @value{GDBN}'s internal symbol tables are stored (see @file{symtab.h}, |
| 6458 | @file{gdbtypes.h}), you will find it much easier to understand the |
| 6459 | code which uses and creates those symbol tables. |
| 6460 | |
| 6461 | You may wish to process the information you are getting somehow, to |
| 6462 | enhance your understanding of it. Summarize it, translate it to another |
| 6463 | language, add some (perhaps trivial or non-useful) feature to @value{GDBN}, use |
| 6464 | the code to predict what a test case would do and write the test case |
| 6465 | and verify your prediction, etc. If you are reading code and your eyes |
| 6466 | are starting to glaze over, this is a sign you need to use a more active |
| 6467 | approach. |
| 6468 | |
| 6469 | Once you have a part of @value{GDBN} to start with, you can find more |
| 6470 | specifically the part you are looking for by stepping through each |
| 6471 | function with the @code{next} command. Do not use @code{step} or you |
| 6472 | will quickly get distracted; when the function you are stepping through |
| 6473 | calls another function try only to get a big-picture understanding |
| 6474 | (perhaps using the comment at the beginning of the function being |
| 6475 | called) of what it does. This way you can identify which of the |
| 6476 | functions being called by the function you are stepping through is the |
| 6477 | one which you are interested in. You may need to examine the data |
| 6478 | structures generated at each stage, with reference to the comments in |
| 6479 | the header files explaining what the data structures are supposed to |
| 6480 | look like. |
| 6481 | |
| 6482 | Of course, this same technique can be used if you are just reading the |
| 6483 | code, rather than actually stepping through it. The same general |
| 6484 | principle applies---when the code you are looking at calls something |
| 6485 | else, just try to understand generally what the code being called does, |
| 6486 | rather than worrying about all its details. |
| 6487 | |
| 6488 | @cindex command implementation |
| 6489 | A good place to start when tracking down some particular area is with |
| 6490 | a command which invokes that feature. Suppose you want to know how |
| 6491 | single-stepping works. As a @value{GDBN} user, you know that the |
| 6492 | @code{step} command invokes single-stepping. The command is invoked |
| 6493 | via command tables (see @file{command.h}); by convention the function |
| 6494 | which actually performs the command is formed by taking the name of |
| 6495 | the command and adding @samp{_command}, or in the case of an |
| 6496 | @code{info} subcommand, @samp{_info}. For example, the @code{step} |
| 6497 | command invokes the @code{step_command} function and the @code{info |
| 6498 | display} command invokes @code{display_info}. When this convention is |
| 6499 | not followed, you might have to use @code{grep} or @kbd{M-x |
| 6500 | tags-search} in emacs, or run @value{GDBN} on itself and set a |
| 6501 | breakpoint in @code{execute_command}. |
| 6502 | |
| 6503 | @cindex @code{bug-gdb} mailing list |
| 6504 | If all of the above fail, it may be appropriate to ask for information |
| 6505 | on @code{bug-gdb}. But @emph{never} post a generic question like ``I was |
| 6506 | wondering if anyone could give me some tips about understanding |
| 6507 | @value{GDBN}''---if we had some magic secret we would put it in this manual. |
| 6508 | Suggestions for improving the manual are always welcome, of course. |
| 6509 | |
| 6510 | @node Debugging GDB,,,Hints |
| 6511 | |
| 6512 | @section Debugging @value{GDBN} with itself |
| 6513 | @cindex debugging @value{GDBN} |
| 6514 | |
| 6515 | If @value{GDBN} is limping on your machine, this is the preferred way to get it |
| 6516 | fully functional. Be warned that in some ancient Unix systems, like |
| 6517 | Ultrix 4.2, a program can't be running in one process while it is being |
| 6518 | debugged in another. Rather than typing the command @kbd{@w{./gdb |
| 6519 | ./gdb}}, which works on Suns and such, you can copy @file{gdb} to |
| 6520 | @file{gdb2} and then type @kbd{@w{./gdb ./gdb2}}. |
| 6521 | |
| 6522 | When you run @value{GDBN} in the @value{GDBN} source directory, it will read a |
| 6523 | @file{.gdbinit} file that sets up some simple things to make debugging |
| 6524 | gdb easier. The @code{info} command, when executed without a subcommand |
| 6525 | in a @value{GDBN} being debugged by gdb, will pop you back up to the top level |
| 6526 | gdb. See @file{.gdbinit} for details. |
| 6527 | |
| 6528 | If you use emacs, you will probably want to do a @code{make TAGS} after |
| 6529 | you configure your distribution; this will put the machine dependent |
| 6530 | routines for your local machine where they will be accessed first by |
| 6531 | @kbd{M-.} |
| 6532 | |
| 6533 | Also, make sure that you've either compiled @value{GDBN} with your local cc, or |
| 6534 | have run @code{fixincludes} if you are compiling with gcc. |
| 6535 | |
| 6536 | @section Submitting Patches |
| 6537 | |
| 6538 | @cindex submitting patches |
| 6539 | Thanks for thinking of offering your changes back to the community of |
| 6540 | @value{GDBN} users. In general we like to get well designed enhancements. |
| 6541 | Thanks also for checking in advance about the best way to transfer the |
| 6542 | changes. |
| 6543 | |
| 6544 | The @value{GDBN} maintainers will only install ``cleanly designed'' patches. |
| 6545 | This manual summarizes what we believe to be clean design for @value{GDBN}. |
| 6546 | |
| 6547 | If the maintainers don't have time to put the patch in when it arrives, |
| 6548 | or if there is any question about a patch, it goes into a large queue |
| 6549 | with everyone else's patches and bug reports. |
| 6550 | |
| 6551 | @cindex legal papers for code contributions |
| 6552 | The legal issue is that to incorporate substantial changes requires a |
| 6553 | copyright assignment from you and/or your employer, granting ownership |
| 6554 | of the changes to the Free Software Foundation. You can get the |
| 6555 | standard documents for doing this by sending mail to @code{gnu@@gnu.org} |
| 6556 | and asking for it. We recommend that people write in "All programs |
| 6557 | owned by the Free Software Foundation" as "NAME OF PROGRAM", so that |
| 6558 | changes in many programs (not just @value{GDBN}, but GAS, Emacs, GCC, |
| 6559 | etc) can be |
| 6560 | contributed with only one piece of legalese pushed through the |
| 6561 | bureaucracy and filed with the FSF. We can't start merging changes until |
| 6562 | this paperwork is received by the FSF (their rules, which we follow |
| 6563 | since we maintain it for them). |
| 6564 | |
| 6565 | Technically, the easiest way to receive changes is to receive each |
| 6566 | feature as a small context diff or unidiff, suitable for @code{patch}. |
| 6567 | Each message sent to me should include the changes to C code and |
| 6568 | header files for a single feature, plus @file{ChangeLog} entries for |
| 6569 | each directory where files were modified, and diffs for any changes |
| 6570 | needed to the manuals (@file{gdb/doc/gdb.texinfo} or |
| 6571 | @file{gdb/doc/gdbint.texinfo}). If there are a lot of changes for a |
| 6572 | single feature, they can be split down into multiple messages. |
| 6573 | |
| 6574 | In this way, if we read and like the feature, we can add it to the |
| 6575 | sources with a single patch command, do some testing, and check it in. |
| 6576 | If you leave out the @file{ChangeLog}, we have to write one. If you leave |
| 6577 | out the doc, we have to puzzle out what needs documenting. Etc., etc. |
| 6578 | |
| 6579 | The reason to send each change in a separate message is that we will not |
| 6580 | install some of the changes. They'll be returned to you with questions |
| 6581 | or comments. If we're doing our job correctly, the message back to you |
| 6582 | will say what you have to fix in order to make the change acceptable. |
| 6583 | The reason to have separate messages for separate features is so that |
| 6584 | the acceptable changes can be installed while one or more changes are |
| 6585 | being reworked. If multiple features are sent in a single message, we |
| 6586 | tend to not put in the effort to sort out the acceptable changes from |
| 6587 | the unacceptable, so none of the features get installed until all are |
| 6588 | acceptable. |
| 6589 | |
| 6590 | If this sounds painful or authoritarian, well, it is. But we get a lot |
| 6591 | of bug reports and a lot of patches, and many of them don't get |
| 6592 | installed because we don't have the time to finish the job that the bug |
| 6593 | reporter or the contributor could have done. Patches that arrive |
| 6594 | complete, working, and well designed, tend to get installed on the day |
| 6595 | they arrive. The others go into a queue and get installed as time |
| 6596 | permits, which, since the maintainers have many demands to meet, may not |
| 6597 | be for quite some time. |
| 6598 | |
| 6599 | Please send patches directly to |
| 6600 | @email{gdb-patches@@sources.redhat.com, the @value{GDBN} maintainers}. |
| 6601 | |
| 6602 | @section Obsolete Conditionals |
| 6603 | @cindex obsolete code |
| 6604 | |
| 6605 | Fragments of old code in @value{GDBN} sometimes reference or set the following |
| 6606 | configuration macros. They should not be used by new code, and old uses |
| 6607 | should be removed as those parts of the debugger are otherwise touched. |
| 6608 | |
| 6609 | @table @code |
| 6610 | @item STACK_END_ADDR |
| 6611 | This macro used to define where the end of the stack appeared, for use |
| 6612 | in interpreting core file formats that don't record this address in the |
| 6613 | core file itself. This information is now configured in BFD, and @value{GDBN} |
| 6614 | gets the info portably from there. The values in @value{GDBN}'s configuration |
| 6615 | files should be moved into BFD configuration files (if needed there), |
| 6616 | and deleted from all of @value{GDBN}'s config files. |
| 6617 | |
| 6618 | Any @file{@var{foo}-xdep.c} file that references STACK_END_ADDR |
| 6619 | is so old that it has never been converted to use BFD. Now that's old! |
| 6620 | |
| 6621 | @end table |
| 6622 | |
| 6623 | @include observer.texi |
| 6624 | @include fdl.texi |
| 6625 | |
| 6626 | @node Index |
| 6627 | @unnumbered Index |
| 6628 | |
| 6629 | @printindex cp |
| 6630 | |
| 6631 | @bye |