| 1 | What has changed in GDB? |
| 2 | (Organized release by release) |
| 3 | |
| 4 | *** Changes since GDB 7.2 |
| 5 | |
| 6 | * The -data-disassemble MI command now supports modes 2 and 3 for |
| 7 | dumping the instruction opcodes. |
| 8 | |
| 9 | * New command line options |
| 10 | |
| 11 | -data-directory DIR Specify DIR as the "data-directory". |
| 12 | This is mostly for testing purposes. |
| 13 | |
| 14 | * The "maint set python auto-load on|off" command has been renamed to |
| 15 | "set auto-load-scripts on|off". |
| 16 | |
| 17 | * GDB has a new command: "set directories". |
| 18 | It is like the "dir" command except that it replaces the |
| 19 | source path list instead of augmenting it. |
| 20 | |
| 21 | * GDB now understands thread names. |
| 22 | |
| 23 | On GNU/Linux, "info threads" will display the thread name as set by |
| 24 | prctl or pthread_setname_np. |
| 25 | |
| 26 | There is also a new command, "thread name", which can be used to |
| 27 | assign a name internally for GDB to display. |
| 28 | |
| 29 | * OpenCL C |
| 30 | Initial support for the OpenCL C language (http://www.khronos.org/opencl) |
| 31 | has been integrated into GDB. |
| 32 | |
| 33 | * Python scripting |
| 34 | |
| 35 | ** GDB values in Python are now callable if the value represents a |
| 36 | function. For example, if 'some_value' represents a function that |
| 37 | takes two integer parameters and returns a value, you can call |
| 38 | that function like so: |
| 39 | |
| 40 | result = some_value (10,20) |
| 41 | |
| 42 | ** Module gdb.types has been added. |
| 43 | It contains a collection of utilities for working with gdb.Types objects: |
| 44 | get_basic_type, has_field, make_enum_dict. |
| 45 | |
| 46 | ** Module gdb.printing has been added. |
| 47 | It contains utilities for writing and registering pretty-printers. |
| 48 | New classes: PrettyPrinter, SubPrettyPrinter, |
| 49 | RegexpCollectionPrettyPrinter. |
| 50 | New function: register_pretty_printer. |
| 51 | |
| 52 | ** New commands "info pretty-printers", "enable pretty-printer" and |
| 53 | "disable pretty-printer" have been added. |
| 54 | |
| 55 | ** gdb.parameter("directories") is now available. |
| 56 | |
| 57 | ** New function gdb.newest_frame returns the newest frame in the |
| 58 | selected thread. |
| 59 | |
| 60 | ** The gdb.InferiorThread class has a new "name" attribute. This |
| 61 | holds the thread's name. |
| 62 | |
| 63 | * C++ Improvements: |
| 64 | |
| 65 | ** GDB now puts template parameters in scope when debugging in an |
| 66 | instantiation. For example, if you have: |
| 67 | |
| 68 | template<int X> int func (void) { return X; } |
| 69 | |
| 70 | then if you step into func<5>, "print X" will show "5". This |
| 71 | feature requires proper debuginfo support from the compiler; it |
| 72 | was added to GCC 4.5. |
| 73 | |
| 74 | ** The motion commands "next", "finish", "until", and "advance" now |
| 75 | work better when exceptions are thrown. In particular, GDB will |
| 76 | no longer lose control of the inferior; instead, the GDB will |
| 77 | stop the inferior at the point at which the exception is caught. |
| 78 | This functionality requires a change in the exception handling |
| 79 | code that was introduced in GCC 4.5. |
| 80 | |
| 81 | * GDB now follows GCC's rules on accessing volatile objects when |
| 82 | reading or writing target state during expression evaluation. |
| 83 | One notable difference to prior behavior is that "print x = 0" |
| 84 | no longer generates a read of x; the value of the assignment is |
| 85 | now always taken directly from the value being assigned. |
| 86 | |
| 87 | * GDB now has some support for using labels in the program's source in |
| 88 | linespecs. For instance, you can use "advance label" to continue |
| 89 | execution to a label. |
| 90 | |
| 91 | * GDB now has support for reading and writing a new .gdb_index |
| 92 | section. This section holds a fast index of DWARF debugging |
| 93 | information and can be used to greatly speed up GDB startup and |
| 94 | operation. See the documentation for `save gdb-index' for details. |
| 95 | |
| 96 | * The "watch" command now accepts an optional "-location" argument. |
| 97 | When used, this causes GDB to watch the memory referred to by the |
| 98 | expression. Such a watchpoint is never deleted due to it going out |
| 99 | of scope. |
| 100 | |
| 101 | * GDB now supports thread debugging of core dumps on GNU/Linux. |
| 102 | |
| 103 | GDB now activates thread debugging using the libthread_db library |
| 104 | when debugging GNU/Linux core dumps, similarly to when debugging |
| 105 | live processes. As a result, when debugging a core dump file, GDB |
| 106 | is now able to display pthread_t ids of threads. For example, "info |
| 107 | threads" shows the same output as when debugging the process when it |
| 108 | was live. In earlier releases, you'd see something like this: |
| 109 | |
| 110 | (gdb) info threads |
| 111 | * 1 LWP 6780 main () at main.c:10 |
| 112 | |
| 113 | While now you see this: |
| 114 | |
| 115 | (gdb) info threads |
| 116 | * 1 Thread 0x7f0f5712a700 (LWP 6780) main () at main.c:10 |
| 117 | |
| 118 | It is also now possible to inspect TLS variables when debugging core |
| 119 | dumps. |
| 120 | |
| 121 | When debugging a core dump generated on a machine other than the one |
| 122 | used to run GDB, you may need to point GDB at the correct |
| 123 | libthread_db library with the "set libthread-db-search-path" |
| 124 | command. See the user manual for more details on this command. |
| 125 | |
| 126 | * New features in the GDB remote stub, GDBserver |
| 127 | |
| 128 | ** GDBserver is now supported on PowerPC LynxOS (versions 4.x and 5.x), |
| 129 | and i686 LynxOS (version 5.x). |
| 130 | |
| 131 | ** GDBserver is now supported on Blackfin Linux. |
| 132 | |
| 133 | * New native configurations |
| 134 | |
| 135 | ia64 HP-UX ia64-*-hpux* |
| 136 | |
| 137 | * New targets: |
| 138 | |
| 139 | Analog Devices, Inc. Blackfin Processor bfin-* |
| 140 | |
| 141 | * Ada task switching is now supported on sparc-elf targets when |
| 142 | debugging a program using the Ravenscar Profile. For more information, |
| 143 | see the "Tasking Support when using the Ravenscar Profile" section |
| 144 | in the GDB user manual. |
| 145 | |
| 146 | * Guile support was removed. |
| 147 | |
| 148 | * New features in the GNU simulator |
| 149 | |
| 150 | ** The --map-info flag lists all known core mappings. |
| 151 | |
| 152 | *** Changes in GDB 7.2 |
| 153 | |
| 154 | * Shared library support for remote targets by default |
| 155 | |
| 156 | When GDB is configured for a generic, non-OS specific target, like |
| 157 | for example, --target=arm-eabi or one of the many *-*-elf targets, |
| 158 | GDB now queries remote stubs for loaded shared libraries using the |
| 159 | `qXfer:libraries:read' packet. Previously, shared library support |
| 160 | was always disabled for such configurations. |
| 161 | |
| 162 | * C++ Improvements: |
| 163 | |
| 164 | ** Argument Dependent Lookup (ADL) |
| 165 | |
| 166 | In C++ ADL lookup directs function search to the namespaces of its |
| 167 | arguments even if the namespace has not been imported. |
| 168 | For example: |
| 169 | namespace A |
| 170 | { |
| 171 | class B { }; |
| 172 | void foo (B) { } |
| 173 | } |
| 174 | ... |
| 175 | A::B b |
| 176 | foo(b) |
| 177 | Here the compiler will search for `foo' in the namespace of 'b' |
| 178 | and find A::foo. GDB now supports this. This construct is commonly |
| 179 | used in the Standard Template Library for operators. |
| 180 | |
| 181 | ** Improved User Defined Operator Support |
| 182 | |
| 183 | In addition to member operators, GDB now supports lookup of operators |
| 184 | defined in a namespace and imported with a `using' directive, operators |
| 185 | defined in the global scope, operators imported implicitly from an |
| 186 | anonymous namespace, and the ADL operators mentioned in the previous |
| 187 | entry. |
| 188 | GDB now also supports proper overload resolution for all the previously |
| 189 | mentioned flavors of operators. |
| 190 | |
| 191 | ** static const class members |
| 192 | |
| 193 | Printing of static const class members that are initialized in the |
| 194 | class definition has been fixed. |
| 195 | |
| 196 | * Windows Thread Information Block access. |
| 197 | |
| 198 | On Windows targets, GDB now supports displaying the Windows Thread |
| 199 | Information Block (TIB) structure. This structure is visible either |
| 200 | by using the new command `info w32 thread-information-block' or, by |
| 201 | dereferencing the new convenience variable named `$_tlb', a |
| 202 | thread-specific pointer to the TIB. This feature is also supported |
| 203 | when remote debugging using GDBserver. |
| 204 | |
| 205 | * Static tracepoints |
| 206 | |
| 207 | Static tracepoints are calls in the user program into a tracing |
| 208 | library. One such library is a port of the LTTng kernel tracer to |
| 209 | userspace --- UST (LTTng Userspace Tracer, http://lttng.org/ust). |
| 210 | When debugging with GDBserver, GDB now supports combining the GDB |
| 211 | tracepoint machinery with such libraries. For example: the user can |
| 212 | use GDB to probe a static tracepoint marker (a call from the user |
| 213 | program into the tracing library) with the new "strace" command (see |
| 214 | "New commands" below). This creates a "static tracepoint" in the |
| 215 | breakpoint list, that can be manipulated with the same feature set |
| 216 | as fast and regular tracepoints. E.g., collect registers, local and |
| 217 | global variables, collect trace state variables, and define |
| 218 | tracepoint conditions. In addition, the user can collect extra |
| 219 | static tracepoint marker specific data, by collecting the new |
| 220 | $_sdata internal variable. When analyzing the trace buffer, you can |
| 221 | inspect $_sdata like any other variable available to GDB. For more |
| 222 | information, see the "Tracepoints" chapter in GDB user manual. New |
| 223 | remote packets have been defined to support static tracepoints, see |
| 224 | the "New remote packets" section below. |
| 225 | |
| 226 | * Better reconstruction of tracepoints after disconnected tracing |
| 227 | |
| 228 | GDB will attempt to download the original source form of tracepoint |
| 229 | definitions when starting a trace run, and then will upload these |
| 230 | upon reconnection to the target, resulting in a more accurate |
| 231 | reconstruction of the tracepoints that are in use on the target. |
| 232 | |
| 233 | * Observer mode |
| 234 | |
| 235 | You can now exercise direct control over the ways that GDB can |
| 236 | affect your program. For instance, you can disallow the setting of |
| 237 | breakpoints, so that the program can run continuously (assuming |
| 238 | non-stop mode). In addition, the "observer" variable is available |
| 239 | to switch all of the different controls; in observer mode, GDB |
| 240 | cannot affect the target's behavior at all, which is useful for |
| 241 | tasks like diagnosing live systems in the field. |
| 242 | |
| 243 | * The new convenience variable $_thread holds the number of the |
| 244 | current thread. |
| 245 | |
| 246 | * New remote packets |
| 247 | |
| 248 | qGetTIBAddr |
| 249 | |
| 250 | Return the address of the Windows Thread Information Block of a given thread. |
| 251 | |
| 252 | qRelocInsn |
| 253 | |
| 254 | In response to several of the tracepoint packets, the target may now |
| 255 | also respond with a number of intermediate `qRelocInsn' request |
| 256 | packets before the final result packet, to have GDB handle |
| 257 | relocating an instruction to execute at a different address. This |
| 258 | is particularly useful for stubs that support fast tracepoints. GDB |
| 259 | reports support for this feature in the qSupported packet. |
| 260 | |
| 261 | qTfSTM, qTsSTM |
| 262 | |
| 263 | List static tracepoint markers in the target program. |
| 264 | |
| 265 | qTSTMat |
| 266 | |
| 267 | List static tracepoint markers at a given address in the target |
| 268 | program. |
| 269 | |
| 270 | qXfer:statictrace:read |
| 271 | |
| 272 | Read the static trace data collected (by a `collect $_sdata' |
| 273 | tracepoint action). The remote stub reports support for this packet |
| 274 | to gdb's qSupported query. |
| 275 | |
| 276 | QAllow |
| 277 | |
| 278 | Send the current settings of GDB's permission flags. |
| 279 | |
| 280 | QTDPsrc |
| 281 | |
| 282 | Send part of the source (textual) form of a tracepoint definition, |
| 283 | which includes location, conditional, and action list. |
| 284 | |
| 285 | * The source command now accepts a -s option to force searching for the |
| 286 | script in the source search path even if the script name specifies |
| 287 | a directory. |
| 288 | |
| 289 | * New features in the GDB remote stub, GDBserver |
| 290 | |
| 291 | - GDBserver now support tracepoints (including fast tracepoints, and |
| 292 | static tracepoints). The feature is currently supported by the |
| 293 | i386-linux and amd64-linux builds. See the "Tracepoints support |
| 294 | in gdbserver" section in the manual for more information. |
| 295 | |
| 296 | GDBserver JIT compiles the tracepoint's conditional agent |
| 297 | expression bytecode into native code whenever possible for low |
| 298 | overhead dynamic tracepoints conditionals. For such tracepoints, |
| 299 | an expression that examines program state is evaluated when the |
| 300 | tracepoint is reached, in order to determine whether to capture |
| 301 | trace data. If the condition is simple and false, processing the |
| 302 | tracepoint finishes very quickly and no data is gathered. |
| 303 | |
| 304 | GDBserver interfaces with the UST (LTTng Userspace Tracer) library |
| 305 | for static tracepoints support. |
| 306 | |
| 307 | - GDBserver now supports x86_64 Windows 64-bit debugging. |
| 308 | |
| 309 | * GDB now sends xmlRegisters= in qSupported packet to indicate that |
| 310 | it understands register description. |
| 311 | |
| 312 | * The --batch flag now disables pagination and queries. |
| 313 | |
| 314 | * X86 general purpose registers |
| 315 | |
| 316 | GDB now supports reading/writing byte, word and double-word x86 |
| 317 | general purpose registers directly. This means you can use, say, |
| 318 | $ah or $ax to refer, respectively, to the byte register AH and |
| 319 | 16-bit word register AX that are actually portions of the 32-bit |
| 320 | register EAX or 64-bit register RAX. |
| 321 | |
| 322 | * The `commands' command now accepts a range of breakpoints to modify. |
| 323 | A plain `commands' following a command that creates multiple |
| 324 | breakpoints affects all the breakpoints set by that command. This |
| 325 | applies to breakpoints set by `rbreak', and also applies when a |
| 326 | single `break' command creates multiple breakpoints (e.g., |
| 327 | breakpoints on overloaded c++ functions). |
| 328 | |
| 329 | * The `rbreak' command now accepts a filename specification as part of |
| 330 | its argument, limiting the functions selected by the regex to those |
| 331 | in the specified file. |
| 332 | |
| 333 | * Support for remote debugging Windows and SymbianOS shared libraries |
| 334 | from Unix hosts has been improved. Non Windows GDB builds now can |
| 335 | understand target reported file names that follow MS-DOS based file |
| 336 | system semantics, such as file names that include drive letters and |
| 337 | use the backslash character as directory separator. This makes it |
| 338 | possible to transparently use the "set sysroot" and "set |
| 339 | solib-search-path" on Unix hosts to point as host copies of the |
| 340 | target's shared libraries. See the new command "set |
| 341 | target-file-system-kind" described below, and the "Commands to |
| 342 | specify files" section in the user manual for more information. |
| 343 | |
| 344 | * New commands |
| 345 | |
| 346 | eval template, expressions... |
| 347 | Convert the values of one or more expressions under the control |
| 348 | of the string template to a command line, and call it. |
| 349 | |
| 350 | set target-file-system-kind unix|dos-based|auto |
| 351 | show target-file-system-kind |
| 352 | Set or show the assumed file system kind for target reported file |
| 353 | names. |
| 354 | |
| 355 | save breakpoints <filename> |
| 356 | Save all current breakpoint definitions to a file suitable for use |
| 357 | in a later debugging session. To read the saved breakpoint |
| 358 | definitions, use the `source' command. |
| 359 | |
| 360 | `save tracepoints' is a new alias for `save-tracepoints'. The latter |
| 361 | is now deprecated. |
| 362 | |
| 363 | info static-tracepoint-markers |
| 364 | Display information about static tracepoint markers in the target. |
| 365 | |
| 366 | strace FN | FILE:LINE | *ADDR | -m MARKER_ID |
| 367 | Define a static tracepoint by probing a marker at the given |
| 368 | function, line, address, or marker ID. |
| 369 | |
| 370 | set observer on|off |
| 371 | show observer |
| 372 | Enable and disable observer mode. |
| 373 | |
| 374 | set may-write-registers on|off |
| 375 | set may-write-memory on|off |
| 376 | set may-insert-breakpoints on|off |
| 377 | set may-insert-tracepoints on|off |
| 378 | set may-insert-fast-tracepoints on|off |
| 379 | set may-interrupt on|off |
| 380 | Set individual permissions for GDB effects on the target. Note that |
| 381 | some of these settings can have undesirable or surprising |
| 382 | consequences, particularly when changed in the middle of a session. |
| 383 | For instance, disabling the writing of memory can prevent |
| 384 | breakpoints from being inserted, cause single-stepping to fail, or |
| 385 | even crash your program, if you disable after breakpoints have been |
| 386 | inserted. However, GDB should not crash. |
| 387 | |
| 388 | set record memory-query on|off |
| 389 | show record memory-query |
| 390 | Control whether to stop the inferior if memory changes caused |
| 391 | by an instruction cannot be recorded. |
| 392 | |
| 393 | * Changed commands |
| 394 | |
| 395 | disassemble |
| 396 | The disassemble command now supports "start,+length" form of two arguments. |
| 397 | |
| 398 | * Python scripting |
| 399 | |
| 400 | ** GDB now provides a new directory location, called the python directory, |
| 401 | where Python scripts written for GDB can be installed. The location |
| 402 | of that directory is <data-directory>/python, where <data-directory> |
| 403 | is the GDB data directory. For more details, see section `Scripting |
| 404 | GDB using Python' in the manual. |
| 405 | |
| 406 | ** The GDB Python API now has access to breakpoints, symbols, symbol |
| 407 | tables, program spaces, inferiors, threads and frame's code blocks. |
| 408 | Additionally, GDB Parameters can now be created from the API, and |
| 409 | manipulated via set/show in the CLI. |
| 410 | |
| 411 | ** New functions gdb.target_charset, gdb.target_wide_charset, |
| 412 | gdb.progspaces, gdb.current_progspace, and gdb.string_to_argv. |
| 413 | |
| 414 | ** New exception gdb.GdbError. |
| 415 | |
| 416 | ** Pretty-printers are now also looked up in the current program space. |
| 417 | |
| 418 | ** Pretty-printers can now be individually enabled and disabled. |
| 419 | |
| 420 | ** GDB now looks for names of Python scripts to auto-load in a |
| 421 | special section named `.debug_gdb_scripts', in addition to looking |
| 422 | for a OBJFILE-gdb.py script when OBJFILE is read by the debugger. |
| 423 | |
| 424 | * Tracepoint actions were unified with breakpoint commands. In particular, |
| 425 | there are no longer differences in "info break" output for breakpoints and |
| 426 | tracepoints and the "commands" command can be used for both tracepoints and |
| 427 | regular breakpoints. |
| 428 | |
| 429 | * New targets |
| 430 | |
| 431 | ARM Symbian arm*-*-symbianelf* |
| 432 | |
| 433 | * D language support. |
| 434 | GDB now supports debugging programs written in the D programming |
| 435 | language. |
| 436 | |
| 437 | * GDB now supports the extended ptrace interface for PowerPC which is |
| 438 | available since Linux kernel version 2.6.34. This automatically enables |
| 439 | any hardware breakpoints and additional hardware watchpoints available in |
| 440 | the processor. The old ptrace interface exposes just one hardware |
| 441 | watchpoint and no hardware breakpoints. |
| 442 | |
| 443 | * GDB is now able to use the Data Value Compare (DVC) register available on |
| 444 | embedded PowerPC processors to implement in hardware simple watchpoint |
| 445 | conditions of the form: |
| 446 | |
| 447 | watch ADDRESS|VARIABLE if ADDRESS|VARIABLE == CONSTANT EXPRESSION |
| 448 | |
| 449 | This works in native GDB running on Linux kernels with the extended ptrace |
| 450 | interface mentioned above. |
| 451 | |
| 452 | *** Changes in GDB 7.1 |
| 453 | |
| 454 | * C++ Improvements |
| 455 | |
| 456 | ** Namespace Support |
| 457 | |
| 458 | GDB now supports importing of namespaces in C++. This enables the |
| 459 | user to inspect variables from imported namespaces. Support for |
| 460 | namepace aliasing has also been added. So, if a namespace is |
| 461 | aliased in the current scope (e.g. namepace C=A; ) the user can |
| 462 | print variables using the alias (e.g. (gdb) print C::x). |
| 463 | |
| 464 | ** Bug Fixes |
| 465 | |
| 466 | All known bugs relating to the printing of virtual base class were |
| 467 | fixed. It is now possible to call overloaded static methods using a |
| 468 | qualified name. |
| 469 | |
| 470 | ** Cast Operators |
| 471 | |
| 472 | The C++ cast operators static_cast<>, dynamic_cast<>, const_cast<>, |
| 473 | and reinterpret_cast<> are now handled by the C++ expression parser. |
| 474 | |
| 475 | * New targets |
| 476 | |
| 477 | Xilinx MicroBlaze microblaze-*-* |
| 478 | Renesas RX rx-*-elf |
| 479 | |
| 480 | * New Simulators |
| 481 | |
| 482 | Xilinx MicroBlaze microblaze |
| 483 | Renesas RX rx |
| 484 | |
| 485 | * Multi-program debugging. |
| 486 | |
| 487 | GDB now has support for multi-program (a.k.a. multi-executable or |
| 488 | multi-exec) debugging. This allows for debugging multiple inferiors |
| 489 | simultaneously each running a different program under the same GDB |
| 490 | session. See "Debugging Multiple Inferiors and Programs" in the |
| 491 | manual for more information. This implied some user visible changes |
| 492 | in the multi-inferior support. For example, "info inferiors" now |
| 493 | lists inferiors that are not running yet or that have exited |
| 494 | already. See also "New commands" and "New options" below. |
| 495 | |
| 496 | * New tracing features |
| 497 | |
| 498 | GDB's tracepoint facility now includes several new features: |
| 499 | |
| 500 | ** Trace state variables |
| 501 | |
| 502 | GDB tracepoints now include support for trace state variables, which |
| 503 | are variables managed by the target agent during a tracing |
| 504 | experiment. They are useful for tracepoints that trigger each |
| 505 | other, so for instance one tracepoint can count hits in a variable, |
| 506 | and then a second tracepoint has a condition that is true when the |
| 507 | count reaches a particular value. Trace state variables share the |
| 508 | $-syntax of GDB convenience variables, and can appear in both |
| 509 | tracepoint actions and condition expressions. Use the "tvariable" |
| 510 | command to create, and "info tvariables" to view; see "Trace State |
| 511 | Variables" in the manual for more detail. |
| 512 | |
| 513 | ** Fast tracepoints |
| 514 | |
| 515 | GDB now includes an option for defining fast tracepoints, which |
| 516 | targets may implement more efficiently, such as by installing a jump |
| 517 | into the target agent rather than a trap instruction. The resulting |
| 518 | speedup can be by two orders of magnitude or more, although the |
| 519 | tradeoff is that some program locations on some target architectures |
| 520 | might not allow fast tracepoint installation, for instance if the |
| 521 | instruction to be replaced is shorter than the jump. To request a |
| 522 | fast tracepoint, use the "ftrace" command, with syntax identical to |
| 523 | the regular trace command. |
| 524 | |
| 525 | ** Disconnected tracing |
| 526 | |
| 527 | It is now possible to detach GDB from the target while it is running |
| 528 | a trace experiment, then reconnect later to see how the experiment |
| 529 | is going. In addition, a new variable disconnected-tracing lets you |
| 530 | tell the target agent whether to continue running a trace if the |
| 531 | connection is lost unexpectedly. |
| 532 | |
| 533 | ** Trace files |
| 534 | |
| 535 | GDB now has the ability to save the trace buffer into a file, and |
| 536 | then use that file as a target, similarly to you can do with |
| 537 | corefiles. You can select trace frames, print data that was |
| 538 | collected in them, and use tstatus to display the state of the |
| 539 | tracing run at the moment that it was saved. To create a trace |
| 540 | file, use "tsave <filename>", and to use it, do "target tfile |
| 541 | <name>". |
| 542 | |
| 543 | ** Circular trace buffer |
| 544 | |
| 545 | You can ask the target agent to handle the trace buffer as a |
| 546 | circular buffer, discarding the oldest trace frames to make room for |
| 547 | newer ones, by setting circular-trace-buffer to on. This feature may |
| 548 | not be available for all target agents. |
| 549 | |
| 550 | * Changed commands |
| 551 | |
| 552 | disassemble |
| 553 | The disassemble command, when invoked with two arguments, now requires |
| 554 | the arguments to be comma-separated. |
| 555 | |
| 556 | info variables |
| 557 | The info variables command now displays variable definitions. Files |
| 558 | which only declare a variable are not shown. |
| 559 | |
| 560 | source |
| 561 | The source command is now capable of sourcing Python scripts. |
| 562 | This feature is dependent on the debugger being build with Python |
| 563 | support. |
| 564 | |
| 565 | Related to this enhancement is also the introduction of a new command |
| 566 | "set script-extension" (see below). |
| 567 | |
| 568 | * New commands (for set/show, see "New options" below) |
| 569 | |
| 570 | record save [<FILENAME>] |
| 571 | Save a file (in core file format) containing the process record |
| 572 | execution log for replay debugging at a later time. |
| 573 | |
| 574 | record restore <FILENAME> |
| 575 | Restore the process record execution log that was saved at an |
| 576 | earlier time, for replay debugging. |
| 577 | |
| 578 | add-inferior [-copies <N>] [-exec <FILENAME>] |
| 579 | Add a new inferior. |
| 580 | |
| 581 | clone-inferior [-copies <N>] [ID] |
| 582 | Make a new inferior ready to execute the same program another |
| 583 | inferior has loaded. |
| 584 | |
| 585 | remove-inferior ID |
| 586 | Remove an inferior. |
| 587 | |
| 588 | maint info program-spaces |
| 589 | List the program spaces loaded into GDB. |
| 590 | |
| 591 | set remote interrupt-sequence [Ctrl-C | BREAK | BREAK-g] |
| 592 | show remote interrupt-sequence |
| 593 | Allow the user to select one of ^C, a BREAK signal or BREAK-g |
| 594 | as the sequence to the remote target in order to interrupt the execution. |
| 595 | Ctrl-C is a default. Some system prefers BREAK which is high level of |
| 596 | serial line for some certain time. Linux kernel prefers BREAK-g, a.k.a |
| 597 | Magic SysRq g. It is BREAK signal and character 'g'. |
| 598 | |
| 599 | set remote interrupt-on-connect [on | off] |
| 600 | show remote interrupt-on-connect |
| 601 | When interrupt-on-connect is ON, gdb sends interrupt-sequence to |
| 602 | remote target when gdb connects to it. This is needed when you debug |
| 603 | Linux kernel. |
| 604 | |
| 605 | set remotebreak [on | off] |
| 606 | show remotebreak |
| 607 | Deprecated. Use "set/show remote interrupt-sequence" instead. |
| 608 | |
| 609 | tvariable $NAME [ = EXP ] |
| 610 | Create or modify a trace state variable. |
| 611 | |
| 612 | info tvariables |
| 613 | List trace state variables and their values. |
| 614 | |
| 615 | delete tvariable $NAME ... |
| 616 | Delete one or more trace state variables. |
| 617 | |
| 618 | teval EXPR, ... |
| 619 | Evaluate the given expressions without collecting anything into the |
| 620 | trace buffer. (Valid in tracepoint actions only.) |
| 621 | |
| 622 | ftrace FN / FILE:LINE / *ADDR |
| 623 | Define a fast tracepoint at the given function, line, or address. |
| 624 | |
| 625 | * New expression syntax |
| 626 | |
| 627 | GDB now parses the 0b prefix of binary numbers the same way as GCC does. |
| 628 | GDB now parses 0b101010 identically with 42. |
| 629 | |
| 630 | * New options |
| 631 | |
| 632 | set follow-exec-mode new|same |
| 633 | show follow-exec-mode |
| 634 | Control whether GDB reuses the same inferior across an exec call or |
| 635 | creates a new one. This is useful to be able to restart the old |
| 636 | executable after the inferior having done an exec call. |
| 637 | |
| 638 | set default-collect EXPR, ... |
| 639 | show default-collect |
| 640 | Define a list of expressions to be collected at each tracepoint. |
| 641 | This is a useful way to ensure essential items are not overlooked, |
| 642 | such as registers or a critical global variable. |
| 643 | |
| 644 | set disconnected-tracing |
| 645 | show disconnected-tracing |
| 646 | If set to 1, the target is instructed to continue tracing if it |
| 647 | loses its connection to GDB. If 0, the target is to stop tracing |
| 648 | upon disconnection. |
| 649 | |
| 650 | set circular-trace-buffer |
| 651 | show circular-trace-buffer |
| 652 | If set to on, the target is instructed to use a circular trace buffer |
| 653 | and discard the oldest trace frames instead of stopping the trace due |
| 654 | to a full trace buffer. If set to off, the trace stops when the buffer |
| 655 | fills up. Some targets may not support this. |
| 656 | |
| 657 | set script-extension off|soft|strict |
| 658 | show script-extension |
| 659 | If set to "off", the debugger does not perform any script language |
| 660 | recognition, and all sourced files are assumed to be GDB scripts. |
| 661 | If set to "soft" (the default), files are sourced according to |
| 662 | filename extension, falling back to GDB scripts if the first |
| 663 | evaluation failed. |
| 664 | If set to "strict", files are sourced according to filename extension. |
| 665 | |
| 666 | set ada trust-PAD-over-XVS on|off |
| 667 | show ada trust-PAD-over-XVS |
| 668 | If off, activate a workaround against a bug in the debugging information |
| 669 | generated by the compiler for PAD types (see gcc/exp_dbug.ads in |
| 670 | the GCC sources for more information about the GNAT encoding and |
| 671 | PAD types in particular). It is always safe to set this option to |
| 672 | off, but this introduces a slight performance penalty. The default |
| 673 | is on. |
| 674 | |
| 675 | * Python API Improvements |
| 676 | |
| 677 | ** GDB provides the new class gdb.LazyString. This is useful in |
| 678 | some pretty-printing cases. The new method gdb.Value.lazy_string |
| 679 | provides a simple way to create objects of this type. |
| 680 | |
| 681 | ** The fields returned by gdb.Type.fields now have an |
| 682 | `is_base_class' attribute. |
| 683 | |
| 684 | ** The new method gdb.Type.range returns the range of an array type. |
| 685 | |
| 686 | ** The new method gdb.parse_and_eval can be used to parse and |
| 687 | evaluate an expression. |
| 688 | |
| 689 | * New remote packets |
| 690 | |
| 691 | QTDV |
| 692 | Define a trace state variable. |
| 693 | |
| 694 | qTV |
| 695 | Get the current value of a trace state variable. |
| 696 | |
| 697 | QTDisconnected |
| 698 | Set desired tracing behavior upon disconnection. |
| 699 | |
| 700 | QTBuffer:circular |
| 701 | Set the trace buffer to be linear or circular. |
| 702 | |
| 703 | qTfP, qTsP |
| 704 | Get data about the tracepoints currently in use. |
| 705 | |
| 706 | * Bug fixes |
| 707 | |
| 708 | Process record now works correctly with hardware watchpoints. |
| 709 | |
| 710 | Multiple bug fixes have been made to the mips-irix port, making it |
| 711 | much more reliable. In particular: |
| 712 | - Debugging threaded applications is now possible again. Previously, |
| 713 | GDB would hang while starting the program, or while waiting for |
| 714 | the program to stop at a breakpoint. |
| 715 | - Attaching to a running process no longer hangs. |
| 716 | - An error occurring while loading a core file has been fixed. |
| 717 | - Changing the value of the PC register now works again. This fixes |
| 718 | problems observed when using the "jump" command, or when calling |
| 719 | a function from GDB, or even when assigning a new value to $pc. |
| 720 | - With the "finish" and "return" commands, the return value for functions |
| 721 | returning a small array is now correctly printed. |
| 722 | - It is now possible to break on shared library code which gets executed |
| 723 | during a shared library init phase (code executed while executing |
| 724 | their .init section). Previously, the breakpoint would have no effect. |
| 725 | - GDB is now able to backtrace through the signal handler for |
| 726 | non-threaded programs. |
| 727 | |
| 728 | PIE (Position Independent Executable) programs debugging is now supported. |
| 729 | This includes debugging execution of PIC (Position Independent Code) shared |
| 730 | libraries although for that, it should be possible to run such libraries as an |
| 731 | executable program. |
| 732 | |
| 733 | *** Changes in GDB 7.0 |
| 734 | |
| 735 | * GDB now has an interface for JIT compilation. Applications that |
| 736 | dynamically generate code can create symbol files in memory and register |
| 737 | them with GDB. For users, the feature should work transparently, and |
| 738 | for JIT developers, the interface is documented in the GDB manual in the |
| 739 | "JIT Compilation Interface" chapter. |
| 740 | |
| 741 | * Tracepoints may now be conditional. The syntax is as for |
| 742 | breakpoints; either an "if" clause appended to the "trace" command, |
| 743 | or the "condition" command is available. GDB sends the condition to |
| 744 | the target for evaluation using the same bytecode format as is used |
| 745 | for tracepoint actions. |
| 746 | |
| 747 | * The disassemble command now supports: an optional /r modifier, print the |
| 748 | raw instructions in hex as well as in symbolic form, and an optional /m |
| 749 | modifier to print mixed source+assembly. |
| 750 | |
| 751 | * Process record and replay |
| 752 | |
| 753 | In a architecture environment that supports ``process record and |
| 754 | replay'', ``process record and replay'' target can record a log of |
| 755 | the process execution, and replay it with both forward and reverse |
| 756 | execute commands. |
| 757 | |
| 758 | * Reverse debugging: GDB now has new commands reverse-continue, reverse- |
| 759 | step, reverse-next, reverse-finish, reverse-stepi, reverse-nexti, and |
| 760 | set execution-direction {forward|reverse}, for targets that support |
| 761 | reverse execution. |
| 762 | |
| 763 | * GDB now supports hardware watchpoints on MIPS/Linux systems. This |
| 764 | feature is available with a native GDB running on kernel version |
| 765 | 2.6.28 or later. |
| 766 | |
| 767 | * GDB now has support for multi-byte and wide character sets on the |
| 768 | target. Strings whose character type is wchar_t, char16_t, or |
| 769 | char32_t are now correctly printed. GDB supports wide- and unicode- |
| 770 | literals in C, that is, L'x', L"string", u'x', u"string", U'x', and |
| 771 | U"string" syntax. And, GDB allows the "%ls" and "%lc" formats in |
| 772 | `printf'. This feature requires iconv to work properly; if your |
| 773 | system does not have a working iconv, GDB can use GNU libiconv. See |
| 774 | the installation instructions for more information. |
| 775 | |
| 776 | * GDB now supports automatic retrieval of shared library files from |
| 777 | remote targets. To use this feature, specify a system root that begins |
| 778 | with the `remote:' prefix, either via the `set sysroot' command or via |
| 779 | the `--with-sysroot' configure-time option. |
| 780 | |
| 781 | * "info sharedlibrary" now takes an optional regex of libraries to show, |
| 782 | and it now reports if a shared library has no debugging information. |
| 783 | |
| 784 | * Commands `set debug-file-directory', `set solib-search-path' and `set args' |
| 785 | now complete on file names. |
| 786 | |
| 787 | * When completing in expressions, gdb will attempt to limit |
| 788 | completions to allowable structure or union fields, where appropriate. |
| 789 | For instance, consider: |
| 790 | |
| 791 | # struct example { int f1; double f2; }; |
| 792 | # struct example variable; |
| 793 | (gdb) p variable. |
| 794 | |
| 795 | If the user types TAB at the end of this command line, the available |
| 796 | completions will be "f1" and "f2". |
| 797 | |
| 798 | * Inlined functions are now supported. They show up in backtraces, and |
| 799 | the "step", "next", and "finish" commands handle them automatically. |
| 800 | |
| 801 | * GDB now supports the token-splicing (##) and stringification (#) |
| 802 | operators when expanding macros. It also supports variable-arity |
| 803 | macros. |
| 804 | |
| 805 | * GDB now supports inspecting extra signal information, exported by |
| 806 | the new $_siginfo convenience variable. The feature is currently |
| 807 | implemented on linux ARM, i386 and amd64. |
| 808 | |
| 809 | * GDB can now display the VFP floating point registers and NEON vector |
| 810 | registers on ARM targets. Both ARM GNU/Linux native GDB and gdbserver |
| 811 | can provide these registers (requires Linux 2.6.30 or later). Remote |
| 812 | and simulator targets may also provide them. |
| 813 | |
| 814 | * New remote packets |
| 815 | |
| 816 | qSearch:memory: |
| 817 | Search memory for a sequence of bytes. |
| 818 | |
| 819 | QStartNoAckMode |
| 820 | Turn off `+'/`-' protocol acknowledgments to permit more efficient |
| 821 | operation over reliable transport links. Use of this packet is |
| 822 | controlled by the `set remote noack-packet' command. |
| 823 | |
| 824 | vKill |
| 825 | Kill the process with the specified process ID. Use this in preference |
| 826 | to `k' when multiprocess protocol extensions are supported. |
| 827 | |
| 828 | qXfer:osdata:read |
| 829 | Obtains additional operating system information |
| 830 | |
| 831 | qXfer:siginfo:read |
| 832 | qXfer:siginfo:write |
| 833 | Read or write additional signal information. |
| 834 | |
| 835 | * Removed remote protocol undocumented extension |
| 836 | |
| 837 | An undocumented extension to the remote protocol's `S' stop reply |
| 838 | packet that permited the stub to pass a process id was removed. |
| 839 | Remote servers should use the `T' stop reply packet instead. |
| 840 | |
| 841 | * GDB now supports multiple function calling conventions according to the |
| 842 | DWARF-2 DW_AT_calling_convention function attribute. |
| 843 | |
| 844 | * The SH target utilizes the aforementioned change to distinguish between gcc |
| 845 | and Renesas calling convention. It also adds the new CLI commands |
| 846 | `set/show sh calling-convention'. |
| 847 | |
| 848 | * GDB can now read compressed debug sections, as produced by GNU gold |
| 849 | with the --compress-debug-sections=zlib flag. |
| 850 | |
| 851 | * 64-bit core files are now supported on AIX. |
| 852 | |
| 853 | * Thread switching is now supported on Tru64. |
| 854 | |
| 855 | * Watchpoints can now be set on unreadable memory locations, e.g. addresses |
| 856 | which will be allocated using malloc later in program execution. |
| 857 | |
| 858 | * The qXfer:libraries:read remote procotol packet now allows passing a |
| 859 | list of section offsets. |
| 860 | |
| 861 | * On GNU/Linux, GDB can now attach to stopped processes. Several race |
| 862 | conditions handling signals delivered during attach or thread creation |
| 863 | have also been fixed. |
| 864 | |
| 865 | * GDB now supports the use of DWARF boolean types for Ada's type Boolean. |
| 866 | From the user's standpoint, all unqualified instances of True and False |
| 867 | are treated as the standard definitions, regardless of context. |
| 868 | |
| 869 | * GDB now parses C++ symbol and type names more flexibly. For |
| 870 | example, given: |
| 871 | |
| 872 | template<typename T> class C { }; |
| 873 | C<char const *> c; |
| 874 | |
| 875 | GDB will now correctly handle all of: |
| 876 | |
| 877 | ptype C<char const *> |
| 878 | ptype C<char const*> |
| 879 | ptype C<const char *> |
| 880 | ptype C<const char*> |
| 881 | |
| 882 | * New features in the GDB remote stub, gdbserver |
| 883 | |
| 884 | - The "--wrapper" command-line argument tells gdbserver to use a |
| 885 | wrapper program to launch programs for debugging. |
| 886 | |
| 887 | - On PowerPC and S/390 targets, it is now possible to use a single |
| 888 | gdbserver executable to debug both 32-bit and 64-bit programs. |
| 889 | (This requires gdbserver itself to be built as a 64-bit executable.) |
| 890 | |
| 891 | - gdbserver uses the new noack protocol mode for TCP connections to |
| 892 | reduce communications latency, if also supported and enabled in GDB. |
| 893 | |
| 894 | - Support for the sparc64-linux-gnu target is now included in |
| 895 | gdbserver. |
| 896 | |
| 897 | - The amd64-linux build of gdbserver now supports debugging both |
| 898 | 32-bit and 64-bit programs. |
| 899 | |
| 900 | - The i386-linux, amd64-linux, and i386-win32 builds of gdbserver |
| 901 | now support hardware watchpoints, and will use them automatically |
| 902 | as appropriate. |
| 903 | |
| 904 | * Python scripting |
| 905 | |
| 906 | GDB now has support for scripting using Python. Whether this is |
| 907 | available is determined at configure time. |
| 908 | |
| 909 | New GDB commands can now be written in Python. |
| 910 | |
| 911 | * Ada tasking support |
| 912 | |
| 913 | Ada tasks can now be inspected in GDB. The following commands have |
| 914 | been introduced: |
| 915 | |
| 916 | info tasks |
| 917 | Print the list of Ada tasks. |
| 918 | info task N |
| 919 | Print detailed information about task number N. |
| 920 | task |
| 921 | Print the task number of the current task. |
| 922 | task N |
| 923 | Switch the context of debugging to task number N. |
| 924 | |
| 925 | * Support for user-defined prefixed commands. The "define" command can |
| 926 | add new commands to existing prefixes, e.g. "target". |
| 927 | |
| 928 | * Multi-inferior, multi-process debugging. |
| 929 | |
| 930 | GDB now has generalized support for multi-inferior debugging. See |
| 931 | "Debugging Multiple Inferiors" in the manual for more information. |
| 932 | Although availability still depends on target support, the command |
| 933 | set is more uniform now. The GNU/Linux specific multi-forks support |
| 934 | has been migrated to this new framework. This implied some user |
| 935 | visible changes; see "New commands" and also "Removed commands" |
| 936 | below. |
| 937 | |
| 938 | * Target descriptions can now describe the target OS ABI. See the |
| 939 | "Target Description Format" section in the user manual for more |
| 940 | information. |
| 941 | |
| 942 | * Target descriptions can now describe "compatible" architectures |
| 943 | to indicate that the target can execute applications for a different |
| 944 | architecture in addition to those for the main target architecture. |
| 945 | See the "Target Description Format" section in the user manual for |
| 946 | more information. |
| 947 | |
| 948 | * Multi-architecture debugging. |
| 949 | |
| 950 | GDB now includes general supports for debugging applications on |
| 951 | hybrid systems that use more than one single processor architecture |
| 952 | at the same time. Each such hybrid architecture still requires |
| 953 | specific support to be added. The only hybrid architecture supported |
| 954 | in this version of GDB is the Cell Broadband Engine. |
| 955 | |
| 956 | * GDB now supports integrated debugging of Cell/B.E. applications that |
| 957 | use both the PPU and SPU architectures. To enable support for hybrid |
| 958 | Cell/B.E. debugging, you need to configure GDB to support both the |
| 959 | powerpc-linux or powerpc64-linux and the spu-elf targets, using the |
| 960 | --enable-targets configure option. |
| 961 | |
| 962 | * Non-stop mode debugging. |
| 963 | |
| 964 | For some targets, GDB now supports an optional mode of operation in |
| 965 | which you can examine stopped threads while other threads continue |
| 966 | to execute freely. This is referred to as non-stop mode, with the |
| 967 | old mode referred to as all-stop mode. See the "Non-Stop Mode" |
| 968 | section in the user manual for more information. |
| 969 | |
| 970 | To be able to support remote non-stop debugging, a remote stub needs |
| 971 | to implement the non-stop mode remote protocol extensions, as |
| 972 | described in the "Remote Non-Stop" section of the user manual. The |
| 973 | GDB remote stub, gdbserver, has been adjusted to support these |
| 974 | extensions on linux targets. |
| 975 | |
| 976 | * New commands (for set/show, see "New options" below) |
| 977 | |
| 978 | catch syscall [NAME(S) | NUMBER(S)] |
| 979 | Catch system calls. Arguments, which should be names of system |
| 980 | calls or their numbers, mean catch only those syscalls. Without |
| 981 | arguments, every syscall will be caught. When the inferior issues |
| 982 | any of the specified syscalls, GDB will stop and announce the system |
| 983 | call, both when it is called and when its call returns. This |
| 984 | feature is currently available with a native GDB running on the |
| 985 | Linux Kernel, under the following architectures: x86, x86_64, |
| 986 | PowerPC and PowerPC64. |
| 987 | |
| 988 | find [/size-char] [/max-count] start-address, end-address|+search-space-size, |
| 989 | val1 [, val2, ...] |
| 990 | Search memory for a sequence of bytes. |
| 991 | |
| 992 | maint set python print-stack |
| 993 | maint show python print-stack |
| 994 | Show a stack trace when an error is encountered in a Python script. |
| 995 | |
| 996 | python [CODE] |
| 997 | Invoke CODE by passing it to the Python interpreter. |
| 998 | |
| 999 | macro define |
| 1000 | macro list |
| 1001 | macro undef |
| 1002 | These allow macros to be defined, undefined, and listed |
| 1003 | interactively. |
| 1004 | |
| 1005 | info os processes |
| 1006 | Show operating system information about processes. |
| 1007 | |
| 1008 | info inferiors |
| 1009 | List the inferiors currently under GDB's control. |
| 1010 | |
| 1011 | inferior NUM |
| 1012 | Switch focus to inferior number NUM. |
| 1013 | |
| 1014 | detach inferior NUM |
| 1015 | Detach from inferior number NUM. |
| 1016 | |
| 1017 | kill inferior NUM |
| 1018 | Kill inferior number NUM. |
| 1019 | |
| 1020 | * New options |
| 1021 | |
| 1022 | set spu stop-on-load |
| 1023 | show spu stop-on-load |
| 1024 | Control whether to stop for new SPE threads during Cell/B.E. debugging. |
| 1025 | |
| 1026 | set spu auto-flush-cache |
| 1027 | show spu auto-flush-cache |
| 1028 | Control whether to automatically flush the software-managed cache |
| 1029 | during Cell/B.E. debugging. |
| 1030 | |
| 1031 | set sh calling-convention |
| 1032 | show sh calling-convention |
| 1033 | Control the calling convention used when calling SH target functions. |
| 1034 | |
| 1035 | set debug timestamp |
| 1036 | show debug timestamp |
| 1037 | Control display of timestamps with GDB debugging output. |
| 1038 | |
| 1039 | set disassemble-next-line |
| 1040 | show disassemble-next-line |
| 1041 | Control display of disassembled source lines or instructions when |
| 1042 | the debuggee stops. |
| 1043 | |
| 1044 | set remote noack-packet |
| 1045 | show remote noack-packet |
| 1046 | Set/show the use of remote protocol QStartNoAckMode packet. See above |
| 1047 | under "New remote packets." |
| 1048 | |
| 1049 | set remote query-attached-packet |
| 1050 | show remote query-attached-packet |
| 1051 | Control use of remote protocol `qAttached' (query-attached) packet. |
| 1052 | |
| 1053 | set remote read-siginfo-object |
| 1054 | show remote read-siginfo-object |
| 1055 | Control use of remote protocol `qXfer:siginfo:read' (read-siginfo-object) |
| 1056 | packet. |
| 1057 | |
| 1058 | set remote write-siginfo-object |
| 1059 | show remote write-siginfo-object |
| 1060 | Control use of remote protocol `qXfer:siginfo:write' (write-siginfo-object) |
| 1061 | packet. |
| 1062 | |
| 1063 | set remote reverse-continue |
| 1064 | show remote reverse-continue |
| 1065 | Control use of remote protocol 'bc' (reverse-continue) packet. |
| 1066 | |
| 1067 | set remote reverse-step |
| 1068 | show remote reverse-step |
| 1069 | Control use of remote protocol 'bs' (reverse-step) packet. |
| 1070 | |
| 1071 | set displaced-stepping |
| 1072 | show displaced-stepping |
| 1073 | Control displaced stepping mode. Displaced stepping is a way to |
| 1074 | single-step over breakpoints without removing them from the debuggee. |
| 1075 | Also known as "out-of-line single-stepping". |
| 1076 | |
| 1077 | set debug displaced |
| 1078 | show debug displaced |
| 1079 | Control display of debugging info for displaced stepping. |
| 1080 | |
| 1081 | maint set internal-error |
| 1082 | maint show internal-error |
| 1083 | Control what GDB does when an internal error is detected. |
| 1084 | |
| 1085 | maint set internal-warning |
| 1086 | maint show internal-warning |
| 1087 | Control what GDB does when an internal warning is detected. |
| 1088 | |
| 1089 | set exec-wrapper |
| 1090 | show exec-wrapper |
| 1091 | unset exec-wrapper |
| 1092 | Use a wrapper program to launch programs for debugging. |
| 1093 | |
| 1094 | set multiple-symbols (all|ask|cancel) |
| 1095 | show multiple-symbols |
| 1096 | The value of this variable can be changed to adjust the debugger behavior |
| 1097 | when an expression or a breakpoint location contains an ambiguous symbol |
| 1098 | name (an overloaded function name, for instance). |
| 1099 | |
| 1100 | set breakpoint always-inserted |
| 1101 | show breakpoint always-inserted |
| 1102 | Keep breakpoints always inserted in the target, as opposed to inserting |
| 1103 | them when resuming the target, and removing them when the target stops. |
| 1104 | This option can improve debugger performance on slow remote targets. |
| 1105 | |
| 1106 | set arm fallback-mode (arm|thumb|auto) |
| 1107 | show arm fallback-mode |
| 1108 | set arm force-mode (arm|thumb|auto) |
| 1109 | show arm force-mode |
| 1110 | These commands control how ARM GDB determines whether instructions |
| 1111 | are ARM or Thumb. The default for both settings is auto, which uses |
| 1112 | the current CPSR value for instructions without symbols; previous |
| 1113 | versions of GDB behaved as if "set arm fallback-mode arm". |
| 1114 | |
| 1115 | set disable-randomization |
| 1116 | show disable-randomization |
| 1117 | Standalone programs run with the virtual address space randomization enabled |
| 1118 | by default on some platforms. This option keeps the addresses stable across |
| 1119 | multiple debugging sessions. |
| 1120 | |
| 1121 | set non-stop |
| 1122 | show non-stop |
| 1123 | Control whether other threads are stopped or not when some thread hits |
| 1124 | a breakpoint. |
| 1125 | |
| 1126 | set target-async |
| 1127 | show target-async |
| 1128 | Requests that asynchronous execution is enabled in the target, if available. |
| 1129 | In this case, it's possible to resume target in the background, and interact |
| 1130 | with GDB while the target is running. "show target-async" displays the |
| 1131 | current state of asynchronous execution of the target. |
| 1132 | |
| 1133 | set target-wide-charset |
| 1134 | show target-wide-charset |
| 1135 | The target-wide-charset is the name of the character set that GDB |
| 1136 | uses when printing characters whose type is wchar_t. |
| 1137 | |
| 1138 | set tcp auto-retry (on|off) |
| 1139 | show tcp auto-retry |
| 1140 | set tcp connect-timeout |
| 1141 | show tcp connect-timeout |
| 1142 | These commands allow GDB to retry failed TCP connections to a remote stub |
| 1143 | with a specified timeout period; this is useful if the stub is launched |
| 1144 | in parallel with GDB but may not be ready to accept connections immediately. |
| 1145 | |
| 1146 | set libthread-db-search-path |
| 1147 | show libthread-db-search-path |
| 1148 | Control list of directories which GDB will search for appropriate |
| 1149 | libthread_db. |
| 1150 | |
| 1151 | set schedule-multiple (on|off) |
| 1152 | show schedule-multiple |
| 1153 | Allow GDB to resume all threads of all processes or only threads of |
| 1154 | the current process. |
| 1155 | |
| 1156 | set stack-cache |
| 1157 | show stack-cache |
| 1158 | Use more aggressive caching for accesses to the stack. This improves |
| 1159 | performance of remote debugging (particularly backtraces) without |
| 1160 | affecting correctness. |
| 1161 | |
| 1162 | set interactive-mode (on|off|auto) |
| 1163 | show interactive-mode |
| 1164 | Control whether GDB runs in interactive mode (on) or not (off). |
| 1165 | When in interactive mode, GDB waits for the user to answer all |
| 1166 | queries. Otherwise, GDB does not wait and assumes the default |
| 1167 | answer. When set to auto (the default), GDB determines which |
| 1168 | mode to use based on the stdin settings. |
| 1169 | |
| 1170 | * Removed commands |
| 1171 | |
| 1172 | info forks |
| 1173 | For program forks, this is replaced by the new more generic `info |
| 1174 | inferiors' command. To list checkpoints, you can still use the |
| 1175 | `info checkpoints' command, which was an alias for the `info forks' |
| 1176 | command. |
| 1177 | |
| 1178 | fork NUM |
| 1179 | Replaced by the new `inferior' command. To switch between |
| 1180 | checkpoints, you can still use the `restart' command, which was an |
| 1181 | alias for the `fork' command. |
| 1182 | |
| 1183 | process PID |
| 1184 | This is removed, since some targets don't have a notion of |
| 1185 | processes. To switch between processes, you can still use the |
| 1186 | `inferior' command using GDB's own inferior number. |
| 1187 | |
| 1188 | delete fork NUM |
| 1189 | For program forks, this is replaced by the new more generic `kill |
| 1190 | inferior' command. To delete a checkpoint, you can still use the |
| 1191 | `delete checkpoint' command, which was an alias for the `delete |
| 1192 | fork' command. |
| 1193 | |
| 1194 | detach fork NUM |
| 1195 | For program forks, this is replaced by the new more generic `detach |
| 1196 | inferior' command. To detach a checkpoint, you can still use the |
| 1197 | `detach checkpoint' command, which was an alias for the `detach |
| 1198 | fork' command. |
| 1199 | |
| 1200 | * New native configurations |
| 1201 | |
| 1202 | x86/x86_64 Darwin i[34567]86-*-darwin* |
| 1203 | |
| 1204 | x86_64 MinGW x86_64-*-mingw* |
| 1205 | |
| 1206 | * New targets |
| 1207 | |
| 1208 | Lattice Mico32 lm32-* |
| 1209 | x86 DICOS i[34567]86-*-dicos* |
| 1210 | x86_64 DICOS x86_64-*-dicos* |
| 1211 | S+core 3 score-*-* |
| 1212 | |
| 1213 | * The GDB remote stub, gdbserver, now supports x86 Windows CE |
| 1214 | (mingw32ce) debugging. |
| 1215 | |
| 1216 | * Removed commands |
| 1217 | |
| 1218 | catch load |
| 1219 | catch unload |
| 1220 | These commands were actually not implemented on any target. |
| 1221 | |
| 1222 | *** Changes in GDB 6.8 |
| 1223 | |
| 1224 | * New native configurations |
| 1225 | |
| 1226 | NetBSD/hppa hppa*-*netbsd* |
| 1227 | Xtensa GNU/Linux xtensa*-*-linux* |
| 1228 | |
| 1229 | * New targets |
| 1230 | |
| 1231 | NetBSD/hppa hppa*-*-netbsd* |
| 1232 | Xtensa GNU/Lunux xtensa*-*-linux* |
| 1233 | |
| 1234 | * Change in command line behavior -- corefiles vs. process ids. |
| 1235 | |
| 1236 | When the '-p NUMBER' or '--pid NUMBER' options are used, and |
| 1237 | attaching to process NUMBER fails, GDB no longer attempts to open a |
| 1238 | core file named NUMBER. Attaching to a program using the -c option |
| 1239 | is no longer supported. Instead, use the '-p' or '--pid' options. |
| 1240 | |
| 1241 | * GDB can now be built as a native debugger for debugging Windows x86 |
| 1242 | (mingw32) Portable Executable (PE) programs. |
| 1243 | |
| 1244 | * Pending breakpoints no longer change their number when their address |
| 1245 | is resolved. |
| 1246 | |
| 1247 | * GDB now supports breakpoints with multiple locations, |
| 1248 | including breakpoints on C++ constructors, inside C++ templates, |
| 1249 | and in inlined functions. |
| 1250 | |
| 1251 | * GDB's ability to debug optimized code has been improved. GDB more |
| 1252 | accurately identifies function bodies and lexical blocks that occupy |
| 1253 | more than one contiguous range of addresses. |
| 1254 | |
| 1255 | * Target descriptions can now describe registers for PowerPC. |
| 1256 | |
| 1257 | * The GDB remote stub, gdbserver, now supports the AltiVec and SPE |
| 1258 | registers on PowerPC targets. |
| 1259 | |
| 1260 | * The GDB remote stub, gdbserver, now supports thread debugging on GNU/Linux |
| 1261 | targets even when the libthread_db library is not available. |
| 1262 | |
| 1263 | * The GDB remote stub, gdbserver, now supports the new file transfer |
| 1264 | commands (remote put, remote get, and remote delete). |
| 1265 | |
| 1266 | * The GDB remote stub, gdbserver, now supports run and attach in |
| 1267 | extended-remote mode. |
| 1268 | |
| 1269 | * hppa*64*-*-hpux11* target broken |
| 1270 | The debugger is unable to start a program and fails with the following |
| 1271 | error: "Error trying to get information about dynamic linker". |
| 1272 | The gdb-6.7 release is also affected. |
| 1273 | |
| 1274 | * GDB now supports the --enable-targets= configure option to allow |
| 1275 | building a single GDB executable that supports multiple remote |
| 1276 | target architectures. |
| 1277 | |
| 1278 | * GDB now supports debugging C and C++ programs which use the |
| 1279 | Decimal Floating Point extension. In addition, the PowerPC target |
| 1280 | now has a set of pseudo-registers to inspect decimal float values |
| 1281 | stored in two consecutive float registers. |
| 1282 | |
| 1283 | * The -break-insert MI command can optionally create pending |
| 1284 | breakpoints now. |
| 1285 | |
| 1286 | * Improved support for debugging Ada |
| 1287 | Many improvements to the Ada language support have been made. These |
| 1288 | include: |
| 1289 | - Better support for Ada2005 interface types |
| 1290 | - Improved handling of arrays and slices in general |
| 1291 | - Better support for Taft-amendment types |
| 1292 | - The '{type} ADDRESS' expression is now allowed on the left hand-side |
| 1293 | of an assignment |
| 1294 | - Improved command completion in Ada |
| 1295 | - Several bug fixes |
| 1296 | |
| 1297 | * GDB on GNU/Linux and HP/UX can now debug through "exec" of a new |
| 1298 | process. |
| 1299 | |
| 1300 | * New commands |
| 1301 | |
| 1302 | set print frame-arguments (all|scalars|none) |
| 1303 | show print frame-arguments |
| 1304 | The value of this variable can be changed to control which argument |
| 1305 | values should be printed by the debugger when displaying a frame. |
| 1306 | |
| 1307 | remote put |
| 1308 | remote get |
| 1309 | remote delete |
| 1310 | Transfer files to and from a remote target, and delete remote files. |
| 1311 | |
| 1312 | * New MI commands |
| 1313 | |
| 1314 | -target-file-put |
| 1315 | -target-file-get |
| 1316 | -target-file-delete |
| 1317 | Transfer files to and from a remote target, and delete remote files. |
| 1318 | |
| 1319 | * New remote packets |
| 1320 | |
| 1321 | vFile:open: |
| 1322 | vFile:close: |
| 1323 | vFile:pread: |
| 1324 | vFile:pwrite: |
| 1325 | vFile:unlink: |
| 1326 | Open, close, read, write, and delete files on the remote system. |
| 1327 | |
| 1328 | vAttach |
| 1329 | Attach to an existing process on the remote system, in extended-remote |
| 1330 | mode. |
| 1331 | |
| 1332 | vRun |
| 1333 | Run a new process on the remote system, in extended-remote mode. |
| 1334 | |
| 1335 | *** Changes in GDB 6.7 |
| 1336 | |
| 1337 | * Resolved 101 resource leaks, null pointer dereferences, etc. in gdb, |
| 1338 | bfd, libiberty and opcodes, as revealed by static analysis donated by |
| 1339 | Coverity, Inc. (http://scan.coverity.com). |
| 1340 | |
| 1341 | * When looking up multiply-defined global symbols, GDB will now prefer the |
| 1342 | symbol definition in the current shared library if it was built using the |
| 1343 | -Bsymbolic linker option. |
| 1344 | |
| 1345 | * When the Text User Interface (TUI) is not configured, GDB will now |
| 1346 | recognize the -tui command-line option and print a message that the TUI |
| 1347 | is not supported. |
| 1348 | |
| 1349 | * The GDB remote stub, gdbserver, now has lower overhead for high |
| 1350 | frequency signals (e.g. SIGALRM) via the QPassSignals packet. |
| 1351 | |
| 1352 | * GDB for MIPS targets now autodetects whether a remote target provides |
| 1353 | 32-bit or 64-bit register values. |
| 1354 | |
| 1355 | * Support for C++ member pointers has been improved. |
| 1356 | |
| 1357 | * GDB now understands XML target descriptions, which specify the |
| 1358 | target's overall architecture. GDB can read a description from |
| 1359 | a local file or over the remote serial protocol. |
| 1360 | |
| 1361 | * Vectors of single-byte data use a new integer type which is not |
| 1362 | automatically displayed as character or string data. |
| 1363 | |
| 1364 | * The /s format now works with the print command. It displays |
| 1365 | arrays of single-byte integers and pointers to single-byte integers |
| 1366 | as strings. |
| 1367 | |
| 1368 | * Target descriptions can now describe target-specific registers, |
| 1369 | for architectures which have implemented the support (currently |
| 1370 | only ARM, M68K, and MIPS). |
| 1371 | |
| 1372 | * GDB and the GDB remote stub, gdbserver, now support the XScale |
| 1373 | iWMMXt coprocessor. |
| 1374 | |
| 1375 | * The GDB remote stub, gdbserver, has been updated to support |
| 1376 | ARM Windows CE (mingw32ce) debugging, and GDB Windows CE support |
| 1377 | has been rewritten to use the standard GDB remote protocol. |
| 1378 | |
| 1379 | * GDB can now step into C++ functions which are called through thunks. |
| 1380 | |
| 1381 | * GDB for the Cell/B.E. SPU now supports overlay debugging. |
| 1382 | |
| 1383 | * The GDB remote protocol "qOffsets" packet can now honor ELF segment |
| 1384 | layout. It also supports a TextSeg= and DataSeg= response when only |
| 1385 | segment base addresses (rather than offsets) are available. |
| 1386 | |
| 1387 | * The /i format now outputs any trailing branch delay slot instructions |
| 1388 | immediately following the last instruction within the count specified. |
| 1389 | |
| 1390 | * The GDB remote protocol "T" stop reply packet now supports a |
| 1391 | "library" response. Combined with the new "qXfer:libraries:read" |
| 1392 | packet, this response allows GDB to debug shared libraries on targets |
| 1393 | where the operating system manages the list of loaded libraries (e.g. |
| 1394 | Windows and SymbianOS). |
| 1395 | |
| 1396 | * The GDB remote stub, gdbserver, now supports dynamic link libraries |
| 1397 | (DLLs) on Windows and Windows CE targets. |
| 1398 | |
| 1399 | * GDB now supports a faster verification that a .debug file matches its binary |
| 1400 | according to its build-id signature, if the signature is present. |
| 1401 | |
| 1402 | * New commands |
| 1403 | |
| 1404 | set remoteflow |
| 1405 | show remoteflow |
| 1406 | Enable or disable hardware flow control (RTS/CTS) on the serial port |
| 1407 | when debugging using remote targets. |
| 1408 | |
| 1409 | set mem inaccessible-by-default |
| 1410 | show mem inaccessible-by-default |
| 1411 | If the target supplies a memory map, for instance via the remote |
| 1412 | protocol's "qXfer:memory-map:read" packet, setting this variable |
| 1413 | prevents GDB from accessing memory outside the memory map. This |
| 1414 | is useful for targets with memory mapped registers or which react |
| 1415 | badly to accesses of unmapped address space. |
| 1416 | |
| 1417 | set breakpoint auto-hw |
| 1418 | show breakpoint auto-hw |
| 1419 | If the target supplies a memory map, for instance via the remote |
| 1420 | protocol's "qXfer:memory-map:read" packet, setting this variable |
| 1421 | lets GDB use hardware breakpoints automatically for memory regions |
| 1422 | where it can not use software breakpoints. This covers both the |
| 1423 | "break" command and internal breakpoints used for other commands |
| 1424 | including "next" and "finish". |
| 1425 | |
| 1426 | catch exception |
| 1427 | catch exception unhandled |
| 1428 | Stop the program execution when Ada exceptions are raised. |
| 1429 | |
| 1430 | catch assert |
| 1431 | Stop the program execution when an Ada assertion failed. |
| 1432 | |
| 1433 | set sysroot |
| 1434 | show sysroot |
| 1435 | Set an alternate system root for target files. This is a more |
| 1436 | general version of "set solib-absolute-prefix", which is now |
| 1437 | an alias to "set sysroot". |
| 1438 | |
| 1439 | info spu |
| 1440 | Provide extended SPU facility status information. This set of |
| 1441 | commands is available only when debugging the Cell/B.E. SPU |
| 1442 | architecture. |
| 1443 | |
| 1444 | * New native configurations |
| 1445 | |
| 1446 | OpenBSD/sh sh*-*openbsd* |
| 1447 | |
| 1448 | set tdesc filename |
| 1449 | unset tdesc filename |
| 1450 | show tdesc filename |
| 1451 | Use the specified local file as an XML target description, and do |
| 1452 | not query the target for its built-in description. |
| 1453 | |
| 1454 | * New targets |
| 1455 | |
| 1456 | OpenBSD/sh sh*-*-openbsd* |
| 1457 | MIPS64 GNU/Linux (gdbserver) mips64-linux-gnu |
| 1458 | Toshiba Media Processor mep-elf |
| 1459 | |
| 1460 | * New remote packets |
| 1461 | |
| 1462 | QPassSignals: |
| 1463 | Ignore the specified signals; pass them directly to the debugged program |
| 1464 | without stopping other threads or reporting them to GDB. |
| 1465 | |
| 1466 | qXfer:features:read: |
| 1467 | Read an XML target description from the target, which describes its |
| 1468 | features. |
| 1469 | |
| 1470 | qXfer:spu:read: |
| 1471 | qXfer:spu:write: |
| 1472 | Read or write contents of an spufs file on the target system. These |
| 1473 | packets are available only on the Cell/B.E. SPU architecture. |
| 1474 | |
| 1475 | qXfer:libraries:read: |
| 1476 | Report the loaded shared libraries. Combined with new "T" packet |
| 1477 | response, this packet allows GDB to debug shared libraries on |
| 1478 | targets where the operating system manages the list of loaded |
| 1479 | libraries (e.g. Windows and SymbianOS). |
| 1480 | |
| 1481 | * Removed targets |
| 1482 | |
| 1483 | Support for these obsolete configurations has been removed. |
| 1484 | |
| 1485 | alpha*-*-osf1* |
| 1486 | alpha*-*-osf2* |
| 1487 | d10v-*-* |
| 1488 | hppa*-*-hiux* |
| 1489 | i[34567]86-ncr-* |
| 1490 | i[34567]86-*-dgux* |
| 1491 | i[34567]86-*-lynxos* |
| 1492 | i[34567]86-*-netware* |
| 1493 | i[34567]86-*-sco3.2v5* |
| 1494 | i[34567]86-*-sco3.2v4* |
| 1495 | i[34567]86-*-sco* |
| 1496 | i[34567]86-*-sysv4.2* |
| 1497 | i[34567]86-*-sysv4* |
| 1498 | i[34567]86-*-sysv5* |
| 1499 | i[34567]86-*-unixware2* |
| 1500 | i[34567]86-*-unixware* |
| 1501 | i[34567]86-*-sysv* |
| 1502 | i[34567]86-*-isc* |
| 1503 | m68*-cisco*-* |
| 1504 | m68*-tandem-* |
| 1505 | mips*-*-pe |
| 1506 | rs6000-*-lynxos* |
| 1507 | sh*-*-pe |
| 1508 | |
| 1509 | * Other removed features |
| 1510 | |
| 1511 | target abug |
| 1512 | target cpu32bug |
| 1513 | target est |
| 1514 | target rom68k |
| 1515 | |
| 1516 | Various m68k-only ROM monitors. |
| 1517 | |
| 1518 | target hms |
| 1519 | target e7000 |
| 1520 | target sh3 |
| 1521 | target sh3e |
| 1522 | |
| 1523 | Various Renesas ROM monitors and debugging interfaces for SH and |
| 1524 | H8/300. |
| 1525 | |
| 1526 | target ocd |
| 1527 | |
| 1528 | Support for a Macraigor serial interface to on-chip debugging. |
| 1529 | GDB does not directly support the newer parallel or USB |
| 1530 | interfaces. |
| 1531 | |
| 1532 | DWARF 1 support |
| 1533 | |
| 1534 | A debug information format. The predecessor to DWARF 2 and |
| 1535 | DWARF 3, which are still supported. |
| 1536 | |
| 1537 | Support for the HP aCC compiler on HP-UX/PA-RISC |
| 1538 | |
| 1539 | SOM-encapsulated symbolic debugging information, automatic |
| 1540 | invocation of pxdb, and the aCC custom C++ ABI. This does not |
| 1541 | affect HP-UX for Itanium or GCC for HP-UX/PA-RISC. Code compiled |
| 1542 | with aCC can still be debugged on an assembly level. |
| 1543 | |
| 1544 | MIPS ".pdr" sections |
| 1545 | |
| 1546 | A MIPS-specific format used to describe stack frame layout |
| 1547 | in debugging information. |
| 1548 | |
| 1549 | Scheme support |
| 1550 | |
| 1551 | GDB could work with an older version of Guile to debug |
| 1552 | the interpreter and Scheme programs running in it. |
| 1553 | |
| 1554 | set mips stack-arg-size |
| 1555 | set mips saved-gpreg-size |
| 1556 | |
| 1557 | Use "set mips abi" to control parameter passing for MIPS. |
| 1558 | |
| 1559 | *** Changes in GDB 6.6 |
| 1560 | |
| 1561 | * New targets |
| 1562 | |
| 1563 | Xtensa xtensa-elf |
| 1564 | Cell Broadband Engine SPU spu-elf |
| 1565 | |
| 1566 | * GDB can now be configured as a cross-debugger targeting native Windows |
| 1567 | (mingw32) or Cygwin. It can communicate with a remote debugging stub |
| 1568 | running on a Windows system over TCP/IP to debug Windows programs. |
| 1569 | |
| 1570 | * The GDB remote stub, gdbserver, has been updated to support Windows and |
| 1571 | Cygwin debugging. Both single-threaded and multi-threaded programs are |
| 1572 | supported. |
| 1573 | |
| 1574 | * The "set trust-readonly-sections" command works again. This command was |
| 1575 | broken in GDB 6.3, 6.4, and 6.5. |
| 1576 | |
| 1577 | * The "load" command now supports writing to flash memory, if the remote |
| 1578 | stub provides the required support. |
| 1579 | |
| 1580 | * Support for GNU/Linux Thread Local Storage (TLS, per-thread variables) no |
| 1581 | longer requires symbolic debug information (e.g. DWARF-2). |
| 1582 | |
| 1583 | * New commands |
| 1584 | |
| 1585 | set substitute-path |
| 1586 | unset substitute-path |
| 1587 | show substitute-path |
| 1588 | Manage a list of substitution rules that GDB uses to rewrite the name |
| 1589 | of the directories where the sources are located. This can be useful |
| 1590 | for instance when the sources were moved to a different location |
| 1591 | between compilation and debugging. |
| 1592 | |
| 1593 | set trace-commands |
| 1594 | show trace-commands |
| 1595 | Print each CLI command as it is executed. Each command is prefixed with |
| 1596 | a number of `+' symbols representing the nesting depth. |
| 1597 | The source command now has a `-v' option to enable the same feature. |
| 1598 | |
| 1599 | * REMOVED features |
| 1600 | |
| 1601 | The ARM Demon monitor support (RDP protocol, "target rdp"). |
| 1602 | |
| 1603 | Kernel Object Display, an embedded debugging feature which only worked with |
| 1604 | an obsolete version of Cisco IOS. |
| 1605 | |
| 1606 | The 'set download-write-size' and 'show download-write-size' commands. |
| 1607 | |
| 1608 | * New remote packets |
| 1609 | |
| 1610 | qSupported: |
| 1611 | Tell a stub about GDB client features, and request remote target features. |
| 1612 | The first feature implemented is PacketSize, which allows the target to |
| 1613 | specify the size of packets it can handle - to minimize the number of |
| 1614 | packets required and improve performance when connected to a remote |
| 1615 | target. |
| 1616 | |
| 1617 | qXfer:auxv:read: |
| 1618 | Fetch an OS auxilliary vector from the remote stub. This packet is a |
| 1619 | more efficient replacement for qPart:auxv:read. |
| 1620 | |
| 1621 | qXfer:memory-map:read: |
| 1622 | Fetch a memory map from the remote stub, including information about |
| 1623 | RAM, ROM, and flash memory devices. |
| 1624 | |
| 1625 | vFlashErase: |
| 1626 | vFlashWrite: |
| 1627 | vFlashDone: |
| 1628 | Erase and program a flash memory device. |
| 1629 | |
| 1630 | * Removed remote packets |
| 1631 | |
| 1632 | qPart:auxv:read: |
| 1633 | This packet has been replaced by qXfer:auxv:read. Only GDB 6.4 and 6.5 |
| 1634 | used it, and only gdbserver implemented it. |
| 1635 | |
| 1636 | *** Changes in GDB 6.5 |
| 1637 | |
| 1638 | * New targets |
| 1639 | |
| 1640 | Renesas M32C/M16C m32c-elf |
| 1641 | |
| 1642 | Morpho Technologies ms1 ms1-elf |
| 1643 | |
| 1644 | * New commands |
| 1645 | |
| 1646 | init-if-undefined Initialize a convenience variable, but |
| 1647 | only if it doesn't already have a value. |
| 1648 | |
| 1649 | The following commands are presently only implemented for native GNU/Linux: |
| 1650 | |
| 1651 | checkpoint Save a snapshot of the program state. |
| 1652 | |
| 1653 | restart <n> Return the program state to a |
| 1654 | previously saved state. |
| 1655 | |
| 1656 | info checkpoints List currently saved checkpoints. |
| 1657 | |
| 1658 | delete-checkpoint <n> Delete a previously saved checkpoint. |
| 1659 | |
| 1660 | set|show detach-on-fork Tell gdb whether to detach from a newly |
| 1661 | forked process, or to keep debugging it. |
| 1662 | |
| 1663 | info forks List forks of the user program that |
| 1664 | are available to be debugged. |
| 1665 | |
| 1666 | fork <n> Switch to debugging one of several |
| 1667 | forks of the user program that are |
| 1668 | available to be debugged. |
| 1669 | |
| 1670 | delete-fork <n> Delete a fork from the list of forks |
| 1671 | that are available to be debugged (and |
| 1672 | kill the forked process). |
| 1673 | |
| 1674 | detach-fork <n> Delete a fork from the list of forks |
| 1675 | that are available to be debugged (and |
| 1676 | allow the process to continue). |
| 1677 | |
| 1678 | * New architecture |
| 1679 | |
| 1680 | Morpho Technologies ms2 ms1-elf |
| 1681 | |
| 1682 | * Improved Windows host support |
| 1683 | |
| 1684 | GDB now builds as a cross debugger hosted on i686-mingw32, including |
| 1685 | native console support, and remote communications using either |
| 1686 | network sockets or serial ports. |
| 1687 | |
| 1688 | * Improved Modula-2 language support |
| 1689 | |
| 1690 | GDB can now print most types in the Modula-2 syntax. This includes: |
| 1691 | basic types, set types, record types, enumerated types, range types, |
| 1692 | pointer types and ARRAY types. Procedure var parameters are correctly |
| 1693 | printed and hexadecimal addresses and character constants are also |
| 1694 | written in the Modula-2 syntax. Best results can be obtained by using |
| 1695 | GNU Modula-2 together with the -gdwarf-2 command line option. |
| 1696 | |
| 1697 | * REMOVED features |
| 1698 | |
| 1699 | The ARM rdi-share module. |
| 1700 | |
| 1701 | The Netware NLM debug server. |
| 1702 | |
| 1703 | *** Changes in GDB 6.4 |
| 1704 | |
| 1705 | * New native configurations |
| 1706 | |
| 1707 | OpenBSD/arm arm*-*-openbsd* |
| 1708 | OpenBSD/mips64 mips64-*-openbsd* |
| 1709 | |
| 1710 | * New targets |
| 1711 | |
| 1712 | Morpho Technologies ms1 ms1-elf |
| 1713 | |
| 1714 | * New command line options |
| 1715 | |
| 1716 | --batch-silent As for --batch, but totally silent. |
| 1717 | --return-child-result The debugger will exist with the same value |
| 1718 | the child (debugged) program exited with. |
| 1719 | --eval-command COMMAND, -ex COMMAND |
| 1720 | Execute a single GDB CLI command. This may be |
| 1721 | specified multiple times and in conjunction |
| 1722 | with the --command (-x) option. |
| 1723 | |
| 1724 | * Deprecated commands removed |
| 1725 | |
| 1726 | The following commands, that were deprecated in 2000, have been |
| 1727 | removed: |
| 1728 | |
| 1729 | Command Replacement |
| 1730 | set|show arm disassembly-flavor set|show arm disassembler |
| 1731 | othernames set arm disassembler |
| 1732 | set|show remotedebug set|show debug remote |
| 1733 | set|show archdebug set|show debug arch |
| 1734 | set|show eventdebug set|show debug event |
| 1735 | regs info registers |
| 1736 | |
| 1737 | * New BSD user-level threads support |
| 1738 | |
| 1739 | It is now possible to debug programs using the user-level threads |
| 1740 | library on OpenBSD and FreeBSD. Currently supported (target) |
| 1741 | configurations are: |
| 1742 | |
| 1743 | FreeBSD/amd64 x86_64-*-freebsd* |
| 1744 | FreeBSD/i386 i386-*-freebsd* |
| 1745 | OpenBSD/i386 i386-*-openbsd* |
| 1746 | |
| 1747 | Note that the new kernel threads libraries introduced in FreeBSD 5.x |
| 1748 | are not yet supported. |
| 1749 | |
| 1750 | * New support for Matsushita MN10300 w/sim added |
| 1751 | (Work in progress). mn10300-elf. |
| 1752 | |
| 1753 | * REMOVED configurations and files |
| 1754 | |
| 1755 | VxWorks and the XDR protocol *-*-vxworks |
| 1756 | Motorola MCORE mcore-*-* |
| 1757 | National Semiconductor NS32000 ns32k-*-* |
| 1758 | |
| 1759 | * New "set print array-indexes" command |
| 1760 | |
| 1761 | After turning this setting "on", GDB prints the index of each element |
| 1762 | when displaying arrays. The default is "off" to preserve the previous |
| 1763 | behavior. |
| 1764 | |
| 1765 | * VAX floating point support |
| 1766 | |
| 1767 | GDB now supports the not-quite-ieee VAX F and D floating point formats. |
| 1768 | |
| 1769 | * User-defined command support |
| 1770 | |
| 1771 | In addition to using $arg0..$arg9 for argument passing, it is now possible |
| 1772 | to use $argc to determine now many arguments have been passed. See the |
| 1773 | section on user-defined commands in the user manual for more information. |
| 1774 | |
| 1775 | *** Changes in GDB 6.3: |
| 1776 | |
| 1777 | * New command line option |
| 1778 | |
| 1779 | GDB now accepts -l followed by a number to set the timeout for remote |
| 1780 | debugging. |
| 1781 | |
| 1782 | * GDB works with GCC -feliminate-dwarf2-dups |
| 1783 | |
| 1784 | GDB now supports a more compact representation of DWARF-2 debug |
| 1785 | information using DW_FORM_ref_addr references. These are produced |
| 1786 | by GCC with the option -feliminate-dwarf2-dups and also by some |
| 1787 | proprietary compilers. With GCC, you must use GCC 3.3.4 or later |
| 1788 | to use -feliminate-dwarf2-dups. |
| 1789 | |
| 1790 | * Internationalization |
| 1791 | |
| 1792 | When supported by the host system, GDB will be built with |
| 1793 | internationalization (libintl). The task of marking up the sources is |
| 1794 | continued, we're looking forward to our first translation. |
| 1795 | |
| 1796 | * Ada |
| 1797 | |
| 1798 | Initial support for debugging programs compiled with the GNAT |
| 1799 | implementation of the Ada programming language has been integrated |
| 1800 | into GDB. In this release, support is limited to expression evaluation. |
| 1801 | |
| 1802 | * New native configurations |
| 1803 | |
| 1804 | GNU/Linux/m32r m32r-*-linux-gnu |
| 1805 | |
| 1806 | * Remote 'p' packet |
| 1807 | |
| 1808 | GDB's remote protocol now includes support for the 'p' packet. This |
| 1809 | packet is used to fetch individual registers from a remote inferior. |
| 1810 | |
| 1811 | * END-OF-LIFE registers[] compatibility module |
| 1812 | |
| 1813 | GDB's internal register infrastructure has been completely rewritten. |
| 1814 | The new infrastructure making possible the implementation of key new |
| 1815 | features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit |
| 1816 | i386 application). |
| 1817 | |
| 1818 | GDB 6.3 will be the last release to include the the registers[] |
| 1819 | compatibility module that allowed out-of-date configurations to |
| 1820 | continue to work. This change directly impacts the following |
| 1821 | configurations: |
| 1822 | |
| 1823 | hppa-*-hpux |
| 1824 | ia64-*-aix |
| 1825 | mips-*-irix* |
| 1826 | *-*-lynx |
| 1827 | mips-*-linux-gnu |
| 1828 | sds protocol |
| 1829 | xdr protocol |
| 1830 | powerpc bdm protocol |
| 1831 | |
| 1832 | Unless there is activity to revive these configurations, they will be |
| 1833 | made OBSOLETE in GDB 6.4, and REMOVED from GDB 6.5. |
| 1834 | |
| 1835 | * OBSOLETE configurations and files |
| 1836 | |
| 1837 | Configurations that have been declared obsolete in this release have |
| 1838 | been commented out. Unless there is activity to revive these |
| 1839 | configurations, the next release of GDB will have their sources |
| 1840 | permanently REMOVED. |
| 1841 | |
| 1842 | h8300-*-* |
| 1843 | mcore-*-* |
| 1844 | mn10300-*-* |
| 1845 | ns32k-*-* |
| 1846 | sh64-*-* |
| 1847 | v850-*-* |
| 1848 | |
| 1849 | *** Changes in GDB 6.2.1: |
| 1850 | |
| 1851 | * MIPS `break main; run' gave an heuristic-fence-post warning |
| 1852 | |
| 1853 | When attempting to run even a simple program, a warning about |
| 1854 | heuristic-fence-post being hit would be reported. This problem has |
| 1855 | been fixed. |
| 1856 | |
| 1857 | * MIPS IRIX 'long double' crashed GDB |
| 1858 | |
| 1859 | When examining a long double variable, GDB would get a segmentation |
| 1860 | fault. The crash has been fixed (but GDB 6.2 cannot correctly examine |
| 1861 | IRIX long double values). |
| 1862 | |
| 1863 | * VAX and "next" |
| 1864 | |
| 1865 | A bug in the VAX stack code was causing problems with the "next" |
| 1866 | command. This problem has been fixed. |
| 1867 | |
| 1868 | *** Changes in GDB 6.2: |
| 1869 | |
| 1870 | * Fix for ``many threads'' |
| 1871 | |
| 1872 | On GNU/Linux systems that use the NPTL threads library, a program |
| 1873 | rapidly creating and deleting threads would confuse GDB leading to the |
| 1874 | error message: |
| 1875 | |
| 1876 | ptrace: No such process. |
| 1877 | thread_db_get_info: cannot get thread info: generic error |
| 1878 | |
| 1879 | This problem has been fixed. |
| 1880 | |
| 1881 | * "-async" and "-noasync" options removed. |
| 1882 | |
| 1883 | Support for the broken "-noasync" option has been removed (it caused |
| 1884 | GDB to dump core). |
| 1885 | |
| 1886 | * New ``start'' command. |
| 1887 | |
| 1888 | This command runs the program until the begining of the main procedure. |
| 1889 | |
| 1890 | * New BSD Kernel Data Access Library (libkvm) interface |
| 1891 | |
| 1892 | Using ``target kvm'' it is now possible to debug kernel core dumps and |
| 1893 | live kernel memory images on various FreeBSD, NetBSD and OpenBSD |
| 1894 | platforms. Currently supported (native-only) configurations are: |
| 1895 | |
| 1896 | FreeBSD/amd64 x86_64-*-freebsd* |
| 1897 | FreeBSD/i386 i?86-*-freebsd* |
| 1898 | NetBSD/i386 i?86-*-netbsd* |
| 1899 | NetBSD/m68k m68*-*-netbsd* |
| 1900 | NetBSD/sparc sparc-*-netbsd* |
| 1901 | OpenBSD/amd64 x86_64-*-openbsd* |
| 1902 | OpenBSD/i386 i?86-*-openbsd* |
| 1903 | OpenBSD/m68k m68*-openbsd* |
| 1904 | OpenBSD/sparc sparc-*-openbsd* |
| 1905 | |
| 1906 | * Signal trampoline code overhauled |
| 1907 | |
| 1908 | Many generic problems with GDB's signal handling code have been fixed. |
| 1909 | These include: backtraces through non-contiguous stacks; recognition |
| 1910 | of sa_sigaction signal trampolines; backtrace from a NULL pointer |
| 1911 | call; backtrace through a signal trampoline; step into and out of |
| 1912 | signal handlers; and single-stepping in the signal trampoline. |
| 1913 | |
| 1914 | Please note that kernel bugs are a limiting factor here. These |
| 1915 | features have been shown to work on an s390 GNU/Linux system that |
| 1916 | include a 2.6.8-rc1 kernel. Ref PR breakpoints/1702. |
| 1917 | |
| 1918 | * Cygwin support for DWARF 2 added. |
| 1919 | |
| 1920 | * New native configurations |
| 1921 | |
| 1922 | GNU/Linux/hppa hppa*-*-linux* |
| 1923 | OpenBSD/hppa hppa*-*-openbsd* |
| 1924 | OpenBSD/m68k m68*-*-openbsd* |
| 1925 | OpenBSD/m88k m88*-*-openbsd* |
| 1926 | OpenBSD/powerpc powerpc-*-openbsd* |
| 1927 | NetBSD/vax vax-*-netbsd* |
| 1928 | OpenBSD/vax vax-*-openbsd* |
| 1929 | |
| 1930 | * END-OF-LIFE frame compatibility module |
| 1931 | |
| 1932 | GDB's internal frame infrastructure has been completely rewritten. |
| 1933 | The new infrastructure making it possible to support key new features |
| 1934 | including DWARF 2 Call Frame Information. To aid in the task of |
| 1935 | migrating old configurations to this new infrastructure, a |
| 1936 | compatibility module, that allowed old configurations to continue to |
| 1937 | work, was also included. |
| 1938 | |
| 1939 | GDB 6.2 will be the last release to include this frame compatibility |
| 1940 | module. This change directly impacts the following configurations: |
| 1941 | |
| 1942 | h8300-*-* |
| 1943 | mcore-*-* |
| 1944 | mn10300-*-* |
| 1945 | ns32k-*-* |
| 1946 | sh64-*-* |
| 1947 | v850-*-* |
| 1948 | xstormy16-*-* |
| 1949 | |
| 1950 | Unless there is activity to revive these configurations, they will be |
| 1951 | made OBSOLETE in GDB 6.3, and REMOVED from GDB 6.4. |
| 1952 | |
| 1953 | * REMOVED configurations and files |
| 1954 | |
| 1955 | Sun 3, running SunOS 3 m68*-*-sunos3* |
| 1956 | Sun 3, running SunOS 4 m68*-*-sunos4* |
| 1957 | Sun 2, running SunOS 3 m68000-*-sunos3* |
| 1958 | Sun 2, running SunOS 4 m68000-*-sunos4* |
| 1959 | Motorola 680x0 running LynxOS m68*-*-lynxos* |
| 1960 | AT&T 3b1/Unix pc m68*-att-* |
| 1961 | Bull DPX2 (68k, System V release 3) m68*-bull-sysv* |
| 1962 | decstation mips-dec-* mips-little-* |
| 1963 | riscos mips-*-riscos* mips-*-sysv* |
| 1964 | sonymips mips-sony-* |
| 1965 | sysv mips*-*-sysv4* (IRIX 5/6 not included) |
| 1966 | |
| 1967 | *** Changes in GDB 6.1.1: |
| 1968 | |
| 1969 | * TUI (Text-mode User Interface) built-in (also included in GDB 6.1) |
| 1970 | |
| 1971 | The TUI (Text-mode User Interface) is now built as part of a default |
| 1972 | GDB configuration. It is enabled by either selecting the TUI with the |
| 1973 | command line option "-i=tui" or by running the separate "gdbtui" |
| 1974 | program. For more information on the TUI, see the manual "Debugging |
| 1975 | with GDB". |
| 1976 | |
| 1977 | * Pending breakpoint support (also included in GDB 6.1) |
| 1978 | |
| 1979 | Support has been added to allow you to specify breakpoints in shared |
| 1980 | libraries that have not yet been loaded. If a breakpoint location |
| 1981 | cannot be found, and the "breakpoint pending" option is set to auto, |
| 1982 | GDB queries you if you wish to make the breakpoint pending on a future |
| 1983 | shared-library load. If and when GDB resolves the breakpoint symbol, |
| 1984 | the pending breakpoint is removed as one or more regular breakpoints |
| 1985 | are created. |
| 1986 | |
| 1987 | Pending breakpoints are very useful for GCJ Java debugging. |
| 1988 | |
| 1989 | * Fixed ISO-C build problems |
| 1990 | |
| 1991 | The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained |
| 1992 | non ISO-C code that stopped them being built using a more strict ISO-C |
| 1993 | compiler (e.g., IBM's C compiler). |
| 1994 | |
| 1995 | * Fixed build problem on IRIX 5 |
| 1996 | |
| 1997 | Due to header problems with <sys/proc.h>, the file gdb/proc-api.c |
| 1998 | wasn't able to compile compile on an IRIX 5 system. |
| 1999 | |
| 2000 | * Added execute permission to gdb/gdbserver/configure |
| 2001 | |
| 2002 | The shell script gdb/testsuite/gdb.stabs/configure lacked execute |
| 2003 | permission. This bug would cause configure to fail on a number of |
| 2004 | systems (Solaris, IRIX). Ref: server/519. |
| 2005 | |
| 2006 | * Fixed build problem on hpux2.0w-hp-hpux11.00 using the HP ANSI C compiler |
| 2007 | |
| 2008 | Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c |
| 2009 | has been updated to use constant array sizes. |
| 2010 | |
| 2011 | * Fixed a panic in the DWARF Call Frame Info code on Solaris 2.7 |
| 2012 | |
| 2013 | GCC 3.3.2, on Solaris 2.7, includes the DW_EH_PE_funcrel encoding in |
| 2014 | its generated DWARF Call Frame Info. This encoding was causing GDB to |
| 2015 | panic, that panic has been fixed. Ref: gdb/1628. |
| 2016 | |
| 2017 | * Fixed a problem when examining parameters in shared library code. |
| 2018 | |
| 2019 | When examining parameters in optimized shared library code generated |
| 2020 | by a mainline GCC, GDB would incorrectly report ``Variable "..." is |
| 2021 | not available''. GDB now correctly displays the variable's value. |
| 2022 | |
| 2023 | *** Changes in GDB 6.1: |
| 2024 | |
| 2025 | * Removed --with-mmalloc |
| 2026 | |
| 2027 | Support for the mmalloc memory manager has been removed, as it |
| 2028 | conflicted with the internal gdb byte cache. |
| 2029 | |
| 2030 | * Changes in AMD64 configurations |
| 2031 | |
| 2032 | The AMD64 target now includes the %cs and %ss registers. As a result |
| 2033 | the AMD64 remote protocol has changed; this affects the floating-point |
| 2034 | and SSE registers. If you rely on those registers for your debugging, |
| 2035 | you should upgrade gdbserver on the remote side. |
| 2036 | |
| 2037 | * Revised SPARC target |
| 2038 | |
| 2039 | The SPARC target has been completely revised, incorporating the |
| 2040 | FreeBSD/sparc64 support that was added for GDB 6.0. As a result |
| 2041 | support for LynxOS and SunOS 4 has been dropped. Calling functions |
| 2042 | from within GDB on operating systems with a non-executable stack |
| 2043 | (Solaris, OpenBSD) now works. |
| 2044 | |
| 2045 | * New C++ demangler |
| 2046 | |
| 2047 | GDB has a new C++ demangler which does a better job on the mangled |
| 2048 | names generated by current versions of g++. It also runs faster, so |
| 2049 | with this and other changes gdb should now start faster on large C++ |
| 2050 | programs. |
| 2051 | |
| 2052 | * DWARF 2 Location Expressions |
| 2053 | |
| 2054 | GDB support for location expressions has been extended to support function |
| 2055 | arguments and frame bases. Older versions of GDB could crash when they |
| 2056 | encountered these. |
| 2057 | |
| 2058 | * C++ nested types and namespaces |
| 2059 | |
| 2060 | GDB's support for nested types and namespaces in C++ has been |
| 2061 | improved, especially if you use the DWARF 2 debugging format. (This |
| 2062 | is the default for recent versions of GCC on most platforms.) |
| 2063 | Specifically, if you have a class "Inner" defined within a class or |
| 2064 | namespace "Outer", then GDB realizes that the class's name is |
| 2065 | "Outer::Inner", not simply "Inner". This should greatly reduce the |
| 2066 | frequency of complaints about not finding RTTI symbols. In addition, |
| 2067 | if you are stopped at inside of a function defined within a namespace, |
| 2068 | GDB modifies its name lookup accordingly. |
| 2069 | |
| 2070 | * New native configurations |
| 2071 | |
| 2072 | NetBSD/amd64 x86_64-*-netbsd* |
| 2073 | OpenBSD/amd64 x86_64-*-openbsd* |
| 2074 | OpenBSD/alpha alpha*-*-openbsd* |
| 2075 | OpenBSD/sparc sparc-*-openbsd* |
| 2076 | OpenBSD/sparc64 sparc64-*-openbsd* |
| 2077 | |
| 2078 | * New debugging protocols |
| 2079 | |
| 2080 | M32R with SDI protocol m32r-*-elf* |
| 2081 | |
| 2082 | * "set prompt-escape-char" command deleted. |
| 2083 | |
| 2084 | The command "set prompt-escape-char" has been deleted. This command, |
| 2085 | and its very obscure effet on GDB's prompt, was never documented, |
| 2086 | tested, nor mentioned in the NEWS file. |
| 2087 | |
| 2088 | * OBSOLETE configurations and files |
| 2089 | |
| 2090 | Configurations that have been declared obsolete in this release have |
| 2091 | been commented out. Unless there is activity to revive these |
| 2092 | configurations, the next release of GDB will have their sources |
| 2093 | permanently REMOVED. |
| 2094 | |
| 2095 | Sun 3, running SunOS 3 m68*-*-sunos3* |
| 2096 | Sun 3, running SunOS 4 m68*-*-sunos4* |
| 2097 | Sun 2, running SunOS 3 m68000-*-sunos3* |
| 2098 | Sun 2, running SunOS 4 m68000-*-sunos4* |
| 2099 | Motorola 680x0 running LynxOS m68*-*-lynxos* |
| 2100 | AT&T 3b1/Unix pc m68*-att-* |
| 2101 | Bull DPX2 (68k, System V release 3) m68*-bull-sysv* |
| 2102 | decstation mips-dec-* mips-little-* |
| 2103 | riscos mips-*-riscos* mips-*-sysv* |
| 2104 | sonymips mips-sony-* |
| 2105 | sysv mips*-*-sysv4* (IRIX 5/6 not included) |
| 2106 | |
| 2107 | * REMOVED configurations and files |
| 2108 | |
| 2109 | SGI Irix-4.x mips-sgi-irix4 or iris4 |
| 2110 | SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris |
| 2111 | Z8000 simulator z8k-zilog-none or z8ksim |
| 2112 | Matsushita MN10200 w/simulator mn10200-*-* |
| 2113 | H8/500 simulator h8500-hitachi-hms or h8500hms |
| 2114 | HP/PA running BSD hppa*-*-bsd* |
| 2115 | HP/PA running OSF/1 hppa*-*-osf* |
| 2116 | HP/PA Pro target hppa*-*-pro* |
| 2117 | PMAX (MIPS) running Mach 3.0 mips*-*-mach3* |
| 2118 | 386BSD i[3456]86-*-bsd* |
| 2119 | Sequent family i[3456]86-sequent-sysv4* |
| 2120 | i[3456]86-sequent-sysv* |
| 2121 | i[3456]86-sequent-bsd* |
| 2122 | SPARC running LynxOS sparc-*-lynxos* |
| 2123 | SPARC running SunOS 4 sparc-*-sunos4* |
| 2124 | Tsqware Sparclet sparclet-*-* |
| 2125 | Fujitsu SPARClite sparclite-fujitsu-none or sparclite |
| 2126 | |
| 2127 | *** Changes in GDB 6.0: |
| 2128 | |
| 2129 | * Objective-C |
| 2130 | |
| 2131 | Support for debugging the Objective-C programming language has been |
| 2132 | integrated into GDB. |
| 2133 | |
| 2134 | * New backtrace mechanism (includes DWARF 2 Call Frame Information). |
| 2135 | |
| 2136 | DWARF 2's Call Frame Information makes available compiler generated |
| 2137 | information that more exactly describes the program's run-time stack. |
| 2138 | By using this information, GDB is able to provide more robust stack |
| 2139 | backtraces. |
| 2140 | |
| 2141 | The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets |
| 2142 | have been updated to use a new backtrace mechanism which includes |
| 2143 | DWARF 2 CFI support. |
| 2144 | |
| 2145 | * Hosted file I/O. |
| 2146 | |
| 2147 | GDB's remote protocol has been extended to include support for hosted |
| 2148 | file I/O (where the remote target uses GDB's file system). See GDB's |
| 2149 | remote protocol documentation for details. |
| 2150 | |
| 2151 | * All targets using the new architecture framework. |
| 2152 | |
| 2153 | All of GDB's targets have been updated to use the new internal |
| 2154 | architecture framework. The way is now open for future GDB releases |
| 2155 | to include cross-architecture native debugging support (i386 on amd64, |
| 2156 | ppc32 on ppc64). |
| 2157 | |
| 2158 | * GNU/Linux's Thread Local Storage (TLS) |
| 2159 | |
| 2160 | GDB now includes support for for the GNU/Linux implementation of |
| 2161 | per-thread variables. |
| 2162 | |
| 2163 | * GNU/Linux's Native POSIX Thread Library (NPTL) |
| 2164 | |
| 2165 | GDB's thread code has been updated to work with either the new |
| 2166 | GNU/Linux NPTL thread library or the older "LinuxThreads" library. |
| 2167 | |
| 2168 | * Separate debug info. |
| 2169 | |
| 2170 | GDB, in conjunction with BINUTILS, now supports a mechanism for |
| 2171 | automatically loading debug information from a separate file. Instead |
| 2172 | of shipping full debug and non-debug versions of system libraries, |
| 2173 | system integrators can now instead ship just the stripped libraries |
| 2174 | and optional debug files. |
| 2175 | |
| 2176 | * DWARF 2 Location Expressions |
| 2177 | |
| 2178 | DWARF 2 Location Expressions allow the compiler to more completely |
| 2179 | describe the location of variables (even in optimized code) to the |
| 2180 | debugger. |
| 2181 | |
| 2182 | GDB now includes preliminary support for location expressions (support |
| 2183 | for DW_OP_piece is still missing). |
| 2184 | |
| 2185 | * Java |
| 2186 | |
| 2187 | A number of long standing bugs that caused GDB to die while starting a |
| 2188 | Java application have been fixed. GDB's Java support is now |
| 2189 | considered "useable". |
| 2190 | |
| 2191 | * GNU/Linux support for fork, vfork, and exec. |
| 2192 | |
| 2193 | The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode" |
| 2194 | commands are now implemented for GNU/Linux. They require a 2.5.x or later |
| 2195 | kernel. |
| 2196 | |
| 2197 | * GDB supports logging output to a file |
| 2198 | |
| 2199 | There are two new commands, "set logging" and "show logging", which can be |
| 2200 | used to capture GDB's output to a file. |
| 2201 | |
| 2202 | * The meaning of "detach" has changed for gdbserver |
| 2203 | |
| 2204 | The "detach" command will now resume the application, as documented. To |
| 2205 | disconnect from gdbserver and leave it stopped, use the new "disconnect" |
| 2206 | command. |
| 2207 | |
| 2208 | * d10v, m68hc11 `regs' command deprecated |
| 2209 | |
| 2210 | The `info registers' command has been updated so that it displays the |
| 2211 | registers using a format identical to the old `regs' command. |
| 2212 | |
| 2213 | * Profiling support |
| 2214 | |
| 2215 | A new command, "maint set profile on/off", has been added. This command can |
| 2216 | be used to enable or disable profiling while running GDB, to profile a |
| 2217 | session or a set of commands. In addition there is a new configure switch, |
| 2218 | "--enable-profiling", which will cause GDB to be compiled with profiling |
| 2219 | data, for more informative profiling results. |
| 2220 | |
| 2221 | * Default MI syntax changed to "mi2". |
| 2222 | |
| 2223 | The default MI (machine interface) syntax, enabled by the command line |
| 2224 | option "-i=mi", has been changed to "mi2". The previous MI syntax, |
| 2225 | "mi1", can be enabled by specifying the option "-i=mi1". |
| 2226 | |
| 2227 | Support for the original "mi0" syntax (included in GDB 5.0) has been |
| 2228 | removed. |
| 2229 | |
| 2230 | Fix for gdb/192: removed extraneous space when displaying frame level. |
| 2231 | Fix for gdb/672: update changelist is now output in mi list format. |
| 2232 | Fix for gdb/702: a -var-assign that updates the value now shows up |
| 2233 | in a subsequent -var-update. |
| 2234 | |
| 2235 | * New native configurations. |
| 2236 | |
| 2237 | FreeBSD/amd64 x86_64-*-freebsd* |
| 2238 | |
| 2239 | * Multi-arched targets. |
| 2240 | |
| 2241 | HP/PA HPUX11 hppa*-*-hpux* |
| 2242 | Renesas M32R/D w/simulator m32r-*-elf* |
| 2243 | |
| 2244 | * OBSOLETE configurations and files |
| 2245 | |
| 2246 | Configurations that have been declared obsolete in this release have |
| 2247 | been commented out. Unless there is activity to revive these |
| 2248 | configurations, the next release of GDB will have their sources |
| 2249 | permanently REMOVED. |
| 2250 | |
| 2251 | Z8000 simulator z8k-zilog-none or z8ksim |
| 2252 | Matsushita MN10200 w/simulator mn10200-*-* |
| 2253 | H8/500 simulator h8500-hitachi-hms or h8500hms |
| 2254 | HP/PA running BSD hppa*-*-bsd* |
| 2255 | HP/PA running OSF/1 hppa*-*-osf* |
| 2256 | HP/PA Pro target hppa*-*-pro* |
| 2257 | PMAX (MIPS) running Mach 3.0 mips*-*-mach3* |
| 2258 | Sequent family i[3456]86-sequent-sysv4* |
| 2259 | i[3456]86-sequent-sysv* |
| 2260 | i[3456]86-sequent-bsd* |
| 2261 | Tsqware Sparclet sparclet-*-* |
| 2262 | Fujitsu SPARClite sparclite-fujitsu-none or sparclite |
| 2263 | |
| 2264 | * REMOVED configurations and files |
| 2265 | |
| 2266 | V850EA ISA |
| 2267 | Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88 |
| 2268 | IBM AIX PS/2 i[3456]86-*-aix |
| 2269 | i386 running Mach 3.0 i[3456]86-*-mach3* |
| 2270 | i386 running Mach i[3456]86-*-mach* |
| 2271 | i386 running OSF/1 i[3456]86-*osf1mk* |
| 2272 | HP/Apollo 68k Family m68*-apollo*-sysv*, |
| 2273 | m68*-apollo*-bsd*, |
| 2274 | m68*-hp-bsd*, m68*-hp-hpux* |
| 2275 | Argonaut Risc Chip (ARC) arc-*-* |
| 2276 | Mitsubishi D30V d30v-*-* |
| 2277 | Fujitsu FR30 fr30-*-elf* |
| 2278 | OS/9000 i[34]86-*-os9k |
| 2279 | I960 with MON960 i960-*-coff |
| 2280 | |
| 2281 | * MIPS $fp behavior changed |
| 2282 | |
| 2283 | The convenience variable $fp, for the MIPS, now consistently returns |
| 2284 | the address of the current frame's base. Previously, depending on the |
| 2285 | context, $fp could refer to either $sp or the current frame's base |
| 2286 | address. See ``8.10 Registers'' in the manual ``Debugging with GDB: |
| 2287 | The GNU Source-Level Debugger''. |
| 2288 | |
| 2289 | *** Changes in GDB 5.3: |
| 2290 | |
| 2291 | * GNU/Linux shared library multi-threaded performance improved. |
| 2292 | |
| 2293 | When debugging a multi-threaded application on GNU/Linux, GDB now uses |
| 2294 | `/proc', in preference to `ptrace' for memory reads. This may result |
| 2295 | in an improvement in the start-up time of multi-threaded, shared |
| 2296 | library applications when run under GDB. One GDB user writes: ``loads |
| 2297 | shared libs like mad''. |
| 2298 | |
| 2299 | * ``gdbserver'' now supports multi-threaded applications on some targets |
| 2300 | |
| 2301 | Support for debugging multi-threaded applications which use |
| 2302 | the GNU/Linux LinuxThreads package has been added for |
| 2303 | arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*, |
| 2304 | powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*. |
| 2305 | |
| 2306 | * GDB now supports C/C++ preprocessor macros. |
| 2307 | |
| 2308 | GDB now expands preprocessor macro invocations in C/C++ expressions, |
| 2309 | and provides various commands for showing macro definitions and how |
| 2310 | they expand. |
| 2311 | |
| 2312 | The new command `macro expand EXPRESSION' expands any macro |
| 2313 | invocations in expression, and shows the result. |
| 2314 | |
| 2315 | The new command `show macro MACRO-NAME' shows the definition of the |
| 2316 | macro named MACRO-NAME, and where it was defined. |
| 2317 | |
| 2318 | Most compilers don't include information about macros in the debugging |
| 2319 | information by default. In GCC 3.1, for example, you need to compile |
| 2320 | your program with the options `-gdwarf-2 -g3'. If the macro |
| 2321 | information is present in the executable, GDB will read it. |
| 2322 | |
| 2323 | * Multi-arched targets. |
| 2324 | |
| 2325 | DEC Alpha (partial) alpha*-*-* |
| 2326 | DEC VAX (partial) vax-*-* |
| 2327 | NEC V850 v850-*-* |
| 2328 | National Semiconductor NS32000 (partial) ns32k-*-* |
| 2329 | Motorola 68000 (partial) m68k-*-* |
| 2330 | Motorola MCORE mcore-*-* |
| 2331 | |
| 2332 | * New targets. |
| 2333 | |
| 2334 | Fujitsu FRV architecture added by Red Hat frv*-*-* |
| 2335 | |
| 2336 | |
| 2337 | * New native configurations |
| 2338 | |
| 2339 | Alpha NetBSD alpha*-*-netbsd* |
| 2340 | SH NetBSD sh*-*-netbsdelf* |
| 2341 | MIPS NetBSD mips*-*-netbsd* |
| 2342 | UltraSPARC NetBSD sparc64-*-netbsd* |
| 2343 | |
| 2344 | * OBSOLETE configurations and files |
| 2345 | |
| 2346 | Configurations that have been declared obsolete in this release have |
| 2347 | been commented out. Unless there is activity to revive these |
| 2348 | configurations, the next release of GDB will have their sources |
| 2349 | permanently REMOVED. |
| 2350 | |
| 2351 | Mitsubishi D30V d30v-*-* |
| 2352 | OS/9000 i[34]86-*-os9k |
| 2353 | IBM AIX PS/2 i[3456]86-*-aix |
| 2354 | Fujitsu FR30 fr30-*-elf* |
| 2355 | Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88 |
| 2356 | Argonaut Risc Chip (ARC) arc-*-* |
| 2357 | i386 running Mach 3.0 i[3456]86-*-mach3* |
| 2358 | i386 running Mach i[3456]86-*-mach* |
| 2359 | i386 running OSF/1 i[3456]86-*osf1mk* |
| 2360 | HP/Apollo 68k Family m68*-apollo*-sysv*, |
| 2361 | m68*-apollo*-bsd*, |
| 2362 | m68*-hp-bsd*, m68*-hp-hpux* |
| 2363 | I960 with MON960 i960-*-coff |
| 2364 | |
| 2365 | * OBSOLETE languages |
| 2366 | |
| 2367 | CHILL, a Pascal like language used by telecommunications companies. |
| 2368 | |
| 2369 | * REMOVED configurations and files |
| 2370 | |
| 2371 | AMD 29k family via UDI a29k-amd-udi, udi29k |
| 2372 | A29K VxWorks a29k-*-vxworks |
| 2373 | AMD 29000 embedded, using EBMON a29k-none-none |
| 2374 | AMD 29000 embedded with COFF a29k-none-coff |
| 2375 | AMD 29000 embedded with a.out a29k-none-aout |
| 2376 | |
| 2377 | testsuite/gdb.hp/gdb.threads-hp/ directory |
| 2378 | |
| 2379 | * New command "set max-user-call-depth <nnn>" |
| 2380 | |
| 2381 | This command allows the user to limit the call depth of user-defined |
| 2382 | commands. The default is 1024. |
| 2383 | |
| 2384 | * Changes in FreeBSD/i386 native debugging. |
| 2385 | |
| 2386 | Support for the "generate-core-file" has been added. |
| 2387 | |
| 2388 | * New commands "dump", "append", and "restore". |
| 2389 | |
| 2390 | These commands allow data to be copied from target memory |
| 2391 | to a bfd-format or binary file (dump and append), and back |
| 2392 | from a file into memory (restore). |
| 2393 | |
| 2394 | * Improved "next/step" support on multi-processor Alpha Tru64. |
| 2395 | |
| 2396 | The previous single-step mechanism could cause unpredictable problems, |
| 2397 | including the random appearance of SIGSEGV or SIGTRAP signals. The use |
| 2398 | of a software single-step mechanism prevents this. |
| 2399 | |
| 2400 | *** Changes in GDB 5.2.1: |
| 2401 | |
| 2402 | * New targets. |
| 2403 | |
| 2404 | Atmel AVR avr*-*-* |
| 2405 | |
| 2406 | * Bug fixes |
| 2407 | |
| 2408 | gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting: |
| 2409 | mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized |
| 2410 | Fix, by Joel Brobecker imported from mainline. |
| 2411 | |
| 2412 | gdb/439: gdb/291: On some ELF object files, gdb was reporting: |
| 2413 | dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize |
| 2414 | Fix, by Fred Fish, imported from mainline. |
| 2415 | |
| 2416 | Dwarf2 .debug_frame & .eh_frame handler improved in many ways. |
| 2417 | Surprisingly enough, it works now. |
| 2418 | By Michal Ludvig, imported from mainline. |
| 2419 | |
| 2420 | i386 hardware watchpoint support: |
| 2421 | avoid misses on second run for some targets. |
| 2422 | By Pierre Muller, imported from mainline. |
| 2423 | |
| 2424 | *** Changes in GDB 5.2: |
| 2425 | |
| 2426 | * New command "set trust-readonly-sections on[off]". |
| 2427 | |
| 2428 | This command is a hint that tells gdb that read-only sections |
| 2429 | really are read-only (ie. that their contents will not change). |
| 2430 | In this mode, gdb will go to the object file rather than the |
| 2431 | target to read memory from read-only sections (such as ".text"). |
| 2432 | This can be a significant performance improvement on some |
| 2433 | (notably embedded) targets. |
| 2434 | |
| 2435 | * New command "generate-core-file" (or "gcore"). |
| 2436 | |
| 2437 | This new gdb command allows the user to drop a core file of the child |
| 2438 | process state at any time. So far it's been implemented only for |
| 2439 | GNU/Linux and Solaris, but should be relatively easily ported to other |
| 2440 | hosts. Argument is core file name (defaults to core.<pid>). |
| 2441 | |
| 2442 | * New command line option |
| 2443 | |
| 2444 | GDB now accepts --pid or -p followed by a process id. |
| 2445 | |
| 2446 | * Change in command line behavior -- corefiles vs. process ids. |
| 2447 | |
| 2448 | There is a subtle behavior in the way in which GDB handles |
| 2449 | command line arguments. The first non-flag argument is always |
| 2450 | a program to debug, but the second non-flag argument may either |
| 2451 | be a corefile or a process id. Previously, GDB would attempt to |
| 2452 | open the second argument as a corefile, and if that failed, would |
| 2453 | issue a superfluous error message and then attempt to attach it as |
| 2454 | a process. Now, if the second argument begins with a non-digit, |
| 2455 | it will be treated as a corefile. If it begins with a digit, |
| 2456 | GDB will attempt to attach it as a process, and if no such process |
| 2457 | is found, will then attempt to open it as a corefile. |
| 2458 | |
| 2459 | * Changes in ARM configurations. |
| 2460 | |
| 2461 | Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD |
| 2462 | configuration is fully multi-arch. |
| 2463 | |
| 2464 | * New native configurations |
| 2465 | |
| 2466 | ARM NetBSD arm*-*-netbsd* |
| 2467 | x86 OpenBSD i[3456]86-*-openbsd* |
| 2468 | AMD x86-64 running GNU/Linux x86_64-*-linux-* |
| 2469 | Sparc64 running FreeBSD sparc64-*-freebsd* |
| 2470 | |
| 2471 | * New targets |
| 2472 | |
| 2473 | Sanyo XStormy16 xstormy16-elf |
| 2474 | |
| 2475 | * OBSOLETE configurations and files |
| 2476 | |
| 2477 | Configurations that have been declared obsolete in this release have |
| 2478 | been commented out. Unless there is activity to revive these |
| 2479 | configurations, the next release of GDB will have their sources |
| 2480 | permanently REMOVED. |
| 2481 | |
| 2482 | AMD 29k family via UDI a29k-amd-udi, udi29k |
| 2483 | A29K VxWorks a29k-*-vxworks |
| 2484 | AMD 29000 embedded, using EBMON a29k-none-none |
| 2485 | AMD 29000 embedded with COFF a29k-none-coff |
| 2486 | AMD 29000 embedded with a.out a29k-none-aout |
| 2487 | |
| 2488 | testsuite/gdb.hp/gdb.threads-hp/ directory |
| 2489 | |
| 2490 | * REMOVED configurations and files |
| 2491 | |
| 2492 | TI TMS320C80 tic80-*-* |
| 2493 | WDC 65816 w65-*-* |
| 2494 | PowerPC Solaris powerpcle-*-solaris* |
| 2495 | PowerPC Windows NT powerpcle-*-cygwin32 |
| 2496 | PowerPC Netware powerpc-*-netware* |
| 2497 | Harris/CXUX m88k m88*-harris-cxux* |
| 2498 | Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-* |
| 2499 | ns32k-utek-sysv* ns32k-utek-* |
| 2500 | SunOS 4.0.Xi on i386 i[3456]86-*-sunos* |
| 2501 | Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern* |
| 2502 | Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news |
| 2503 | ISI Optimum V (3.05) under 4.3bsd. m68*-isi-* |
| 2504 | Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos* |
| 2505 | |
| 2506 | * Changes to command line processing |
| 2507 | |
| 2508 | The new `--args' feature can be used to specify command-line arguments |
| 2509 | for the inferior from gdb's command line. |
| 2510 | |
| 2511 | * Changes to key bindings |
| 2512 | |
| 2513 | There is a new `operate-and-get-next' function bound to `C-o'. |
| 2514 | |
| 2515 | *** Changes in GDB 5.1.1 |
| 2516 | |
| 2517 | Fix compile problem on DJGPP. |
| 2518 | |
| 2519 | Fix a problem with floating-point registers on the i386 being |
| 2520 | corrupted. |
| 2521 | |
| 2522 | Fix to stop GDB crashing on .debug_str debug info. |
| 2523 | |
| 2524 | Numerous documentation fixes. |
| 2525 | |
| 2526 | Numerous testsuite fixes. |
| 2527 | |
| 2528 | *** Changes in GDB 5.1: |
| 2529 | |
| 2530 | * New native configurations |
| 2531 | |
| 2532 | Alpha FreeBSD alpha*-*-freebsd* |
| 2533 | x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]* |
| 2534 | MIPS GNU/Linux mips*-*-linux* |
| 2535 | MIPS SGI Irix 6.x mips*-sgi-irix6* |
| 2536 | ia64 AIX ia64-*-aix* |
| 2537 | s390 and s390x GNU/Linux {s390,s390x}-*-linux* |
| 2538 | |
| 2539 | * New targets |
| 2540 | |
| 2541 | Motorola 68HC11 and 68HC12 m68hc11-elf |
| 2542 | CRIS cris-axis |
| 2543 | UltraSparc running GNU/Linux sparc64-*-linux* |
| 2544 | |
| 2545 | * OBSOLETE configurations and files |
| 2546 | |
| 2547 | x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*, |
| 2548 | Harris/CXUX m88k m88*-harris-cxux* |
| 2549 | Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-* |
| 2550 | ns32k-utek-sysv* ns32k-utek-* |
| 2551 | TI TMS320C80 tic80-*-* |
| 2552 | WDC 65816 w65-*-* |
| 2553 | Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern* |
| 2554 | PowerPC Solaris powerpcle-*-solaris* |
| 2555 | PowerPC Windows NT powerpcle-*-cygwin32 |
| 2556 | PowerPC Netware powerpc-*-netware* |
| 2557 | SunOS 4.0.Xi on i386 i[3456]86-*-sunos* |
| 2558 | Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news |
| 2559 | ISI Optimum V (3.05) under 4.3bsd. m68*-isi-* |
| 2560 | Apple Macintosh (MPW) host N/A |
| 2561 | |
| 2562 | stuff.c (Program to stuff files into a specially prepared space in kdb) |
| 2563 | kdb-start.c (Main loop for the standalone kernel debugger) |
| 2564 | |
| 2565 | Configurations that have been declared obsolete in this release have |
| 2566 | been commented out. Unless there is activity to revive these |
| 2567 | configurations, the next release of GDB will have their sources |
| 2568 | permanently REMOVED. |
| 2569 | |
| 2570 | * REMOVED configurations and files |
| 2571 | |
| 2572 | Altos 3068 m68*-altos-* |
| 2573 | Convex c1-*-*, c2-*-* |
| 2574 | Pyramid pyramid-*-* |
| 2575 | ARM RISCix arm-*-* (as host) |
| 2576 | Tahoe tahoe-*-* |
| 2577 | ser-ocd.c *-*-* |
| 2578 | |
| 2579 | * GDB has been converted to ISO C. |
| 2580 | |
| 2581 | GDB's source code has been converted to ISO C. In particular, the |
| 2582 | sources are fully protoized, and rely on standard headers being |
| 2583 | present. |
| 2584 | |
| 2585 | * Other news: |
| 2586 | |
| 2587 | * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM. |
| 2588 | |
| 2589 | * The MI enabled by default. |
| 2590 | |
| 2591 | The new machine oriented interface (MI) introduced in GDB 5.0 has been |
| 2592 | revised and enabled by default. Packages which use GDB as a debugging |
| 2593 | engine behind a UI or another front end are encouraged to switch to |
| 2594 | using the GDB/MI interface, instead of the old annotations interface |
| 2595 | which is now deprecated. |
| 2596 | |
| 2597 | * Support for debugging Pascal programs. |
| 2598 | |
| 2599 | GDB now includes support for debugging Pascal programs. The following |
| 2600 | main features are supported: |
| 2601 | |
| 2602 | - Pascal-specific data types such as sets; |
| 2603 | |
| 2604 | - automatic recognition of Pascal sources based on file-name |
| 2605 | extension; |
| 2606 | |
| 2607 | - Pascal-style display of data types, variables, and functions; |
| 2608 | |
| 2609 | - a Pascal expression parser. |
| 2610 | |
| 2611 | However, some important features are not yet supported. |
| 2612 | |
| 2613 | - Pascal string operations are not supported at all; |
| 2614 | |
| 2615 | - there are some problems with boolean types; |
| 2616 | |
| 2617 | - Pascal type hexadecimal constants are not supported |
| 2618 | because they conflict with the internal variables format; |
| 2619 | |
| 2620 | - support for Pascal objects and classes is not full yet; |
| 2621 | |
| 2622 | - unlike Pascal, GDB is case-sensitive for symbol names. |
| 2623 | |
| 2624 | * Changes in completion. |
| 2625 | |
| 2626 | Commands such as `shell', `run' and `set args', which pass arguments |
| 2627 | to inferior programs, now complete on file names, similar to what |
| 2628 | users expect at the shell prompt. |
| 2629 | |
| 2630 | Commands which accept locations, such as `disassemble', `print', |
| 2631 | `breakpoint', `until', etc. now complete on filenames as well as |
| 2632 | program symbols. Thus, if you type "break foob TAB", and the source |
| 2633 | files linked into the programs include `foobar.c', that file name will |
| 2634 | be one of the candidates for completion. However, file names are not |
| 2635 | considered for completion after you typed a colon that delimits a file |
| 2636 | name from a name of a function in that file, as in "break foo.c:bar". |
| 2637 | |
| 2638 | `set demangle-style' completes on available demangling styles. |
| 2639 | |
| 2640 | * New platform-independent commands: |
| 2641 | |
| 2642 | It is now possible to define a post-hook for a command as well as a |
| 2643 | hook that runs before the command. For more details, see the |
| 2644 | documentation of `hookpost' in the GDB manual. |
| 2645 | |
| 2646 | * Changes in GNU/Linux native debugging. |
| 2647 | |
| 2648 | Support for debugging multi-threaded programs has been completely |
| 2649 | revised for all platforms except m68k and sparc. You can now debug as |
| 2650 | many threads as your system allows you to have. |
| 2651 | |
| 2652 | Attach/detach is supported for multi-threaded programs. |
| 2653 | |
| 2654 | Support for SSE registers was added for x86. This doesn't work for |
| 2655 | multi-threaded programs though. |
| 2656 | |
| 2657 | * Changes in MIPS configurations. |
| 2658 | |
| 2659 | Multi-arch support is enabled for all MIPS configurations. |
| 2660 | |
| 2661 | GDB can now be built as native debugger on SGI Irix 6.x systems for |
| 2662 | debugging n32 executables. (Debugging 64-bit executables is not yet |
| 2663 | supported.) |
| 2664 | |
| 2665 | * Unified support for hardware watchpoints in all x86 configurations. |
| 2666 | |
| 2667 | Most (if not all) native x86 configurations support hardware-assisted |
| 2668 | breakpoints and watchpoints in a unified manner. This support |
| 2669 | implements debug register sharing between watchpoints, which allows to |
| 2670 | put a virtually infinite number of watchpoints on the same address, |
| 2671 | and also supports watching regions up to 16 bytes with several debug |
| 2672 | registers. |
| 2673 | |
| 2674 | The new maintenance command `maintenance show-debug-regs' toggles |
| 2675 | debugging print-outs in functions that insert, remove, and test |
| 2676 | watchpoints and hardware breakpoints. |
| 2677 | |
| 2678 | * Changes in the DJGPP native configuration. |
| 2679 | |
| 2680 | New command ``info dos sysinfo'' displays assorted information about |
| 2681 | the CPU, OS, memory, and DPMI server. |
| 2682 | |
| 2683 | New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt'' |
| 2684 | display information about segment descriptors stored in GDT, LDT, and |
| 2685 | IDT. |
| 2686 | |
| 2687 | New commands ``info dos pde'' and ``info dos pte'' display entries |
| 2688 | from Page Directory and Page Tables (for now works with CWSDPMI only). |
| 2689 | New command ``info dos address-pte'' displays the Page Table entry for |
| 2690 | a given linear address. |
| 2691 | |
| 2692 | GDB can now pass command lines longer than 126 characters to the |
| 2693 | program being debugged (requires an update to the libdbg.a library |
| 2694 | which is part of the DJGPP development kit). |
| 2695 | |
| 2696 | DWARF2 debug info is now supported. |
| 2697 | |
| 2698 | It is now possible to `step' and `next' through calls to `longjmp'. |
| 2699 | |
| 2700 | * Changes in documentation. |
| 2701 | |
| 2702 | All GDB documentation was converted to GFDL, the GNU Free |
| 2703 | Documentation License. |
| 2704 | |
| 2705 | Tracepoints-related commands are now fully documented in the GDB |
| 2706 | manual. |
| 2707 | |
| 2708 | TUI, the Text-mode User Interface, is now documented in the manual. |
| 2709 | |
| 2710 | Tracepoints-related commands are now fully documented in the GDB |
| 2711 | manual. |
| 2712 | |
| 2713 | The "GDB Internals" manual now has an index. It also includes |
| 2714 | documentation of `ui_out' functions, GDB coding standards, x86 |
| 2715 | hardware watchpoints, and memory region attributes. |
| 2716 | |
| 2717 | * GDB's version number moved to ``version.in'' |
| 2718 | |
| 2719 | The Makefile variable VERSION has been replaced by the file |
| 2720 | ``version.in''. People creating GDB distributions should update the |
| 2721 | contents of this file. |
| 2722 | |
| 2723 | * gdba.el deleted |
| 2724 | |
| 2725 | GUD support is now a standard part of the EMACS distribution. |
| 2726 | |
| 2727 | *** Changes in GDB 5.0: |
| 2728 | |
| 2729 | * Improved support for debugging FP programs on x86 targets |
| 2730 | |
| 2731 | Unified and much-improved support for debugging floating-point |
| 2732 | programs on all x86 targets. In particular, ``info float'' now |
| 2733 | displays the FP registers in the same format on all x86 targets, with |
| 2734 | greater level of detail. |
| 2735 | |
| 2736 | * Improvements and bugfixes in hardware-assisted watchpoints |
| 2737 | |
| 2738 | It is now possible to watch array elements, struct members, and |
| 2739 | bitfields with hardware-assisted watchpoints. Data-read watchpoints |
| 2740 | on x86 targets no longer erroneously trigger when the address is |
| 2741 | written. |
| 2742 | |
| 2743 | * Improvements in the native DJGPP version of GDB |
| 2744 | |
| 2745 | The distribution now includes all the scripts and auxiliary files |
| 2746 | necessary to build the native DJGPP version on MS-DOS/MS-Windows |
| 2747 | machines ``out of the box''. |
| 2748 | |
| 2749 | The DJGPP version can now debug programs that use signals. It is |
| 2750 | possible to catch signals that happened in the debuggee, deliver |
| 2751 | signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal |
| 2752 | would kill the program being debugged.) Programs that hook hardware |
| 2753 | interrupts (keyboard, timer, etc.) can also be debugged. |
| 2754 | |
| 2755 | It is now possible to debug DJGPP programs that redirect their |
| 2756 | standard handles or switch them to raw (as opposed to cooked) mode, or |
| 2757 | even close them. The command ``run < foo > bar'' works as expected, |
| 2758 | and ``info terminal'' reports useful information about the debuggee's |
| 2759 | terminal, including raw/cooked mode, redirection, etc. |
| 2760 | |
| 2761 | The DJGPP version now uses termios functions for console I/O, which |
| 2762 | enables debugging graphics programs. Interrupting GDB with Ctrl-C |
| 2763 | also works. |
| 2764 | |
| 2765 | DOS-style file names with drive letters are now fully supported by |
| 2766 | GDB. |
| 2767 | |
| 2768 | It is now possible to debug DJGPP programs that switch their working |
| 2769 | directory. It is also possible to rerun the debuggee any number of |
| 2770 | times without restarting GDB; thus, you can use the same setup, |
| 2771 | breakpoints, etc. for many debugging sessions. |
| 2772 | |
| 2773 | * New native configurations |
| 2774 | |
| 2775 | ARM GNU/Linux arm*-*-linux* |
| 2776 | PowerPC GNU/Linux powerpc-*-linux* |
| 2777 | |
| 2778 | * New targets |
| 2779 | |
| 2780 | Motorola MCore mcore-*-* |
| 2781 | x86 VxWorks i[3456]86-*-vxworks* |
| 2782 | PowerPC VxWorks powerpc-*-vxworks* |
| 2783 | TI TMS320C80 tic80-*-* |
| 2784 | |
| 2785 | * OBSOLETE configurations |
| 2786 | |
| 2787 | Altos 3068 m68*-altos-* |
| 2788 | Convex c1-*-*, c2-*-* |
| 2789 | Pyramid pyramid-*-* |
| 2790 | ARM RISCix arm-*-* (as host) |
| 2791 | Tahoe tahoe-*-* |
| 2792 | |
| 2793 | Configurations that have been declared obsolete will be commented out, |
| 2794 | but the code will be left in place. If there is no activity to revive |
| 2795 | these configurations before the next release of GDB, the sources will |
| 2796 | be permanently REMOVED. |
| 2797 | |
| 2798 | * Gould support removed |
| 2799 | |
| 2800 | Support for the Gould PowerNode and NP1 has been removed. |
| 2801 | |
| 2802 | * New features for SVR4 |
| 2803 | |
| 2804 | On SVR4 native platforms (such as Solaris), if you attach to a process |
| 2805 | without first loading a symbol file, GDB will now attempt to locate and |
| 2806 | load symbols from the running process's executable file. |
| 2807 | |
| 2808 | * Many C++ enhancements |
| 2809 | |
| 2810 | C++ support has been greatly improved. Overload resolution now works properly |
| 2811 | in almost all cases. RTTI support is on the way. |
| 2812 | |
| 2813 | * Remote targets can connect to a sub-program |
| 2814 | |
| 2815 | A popen(3) style serial-device has been added. This device starts a |
| 2816 | sub-process (such as a stand-alone simulator) and then communicates |
| 2817 | with that. The sub-program to run is specified using the syntax |
| 2818 | ``|<program> <args>'' vis: |
| 2819 | |
| 2820 | (gdb) set remotedebug 1 |
| 2821 | (gdb) target extended-remote |mn10300-elf-sim program-args |
| 2822 | |
| 2823 | * MIPS 64 remote protocol |
| 2824 | |
| 2825 | A long standing bug in the mips64 remote protocol where by GDB |
| 2826 | expected certain 32 bit registers (ex SR) to be transfered as 32 |
| 2827 | instead of 64 bits has been fixed. |
| 2828 | |
| 2829 | The command ``set remote-mips64-transfers-32bit-regs on'' has been |
| 2830 | added to provide backward compatibility with older versions of GDB. |
| 2831 | |
| 2832 | * ``set remotebinarydownload'' replaced by ``set remote X-packet'' |
| 2833 | |
| 2834 | The command ``set remotebinarydownload'' command has been replaced by |
| 2835 | ``set remote X-packet''. Other commands in ``set remote'' family |
| 2836 | include ``set remote P-packet''. |
| 2837 | |
| 2838 | * Breakpoint commands accept ranges. |
| 2839 | |
| 2840 | The breakpoint commands ``enable'', ``disable'', and ``delete'' now |
| 2841 | accept a range of breakpoints, e.g. ``5-7''. The tracepoint command |
| 2842 | ``tracepoint passcount'' also accepts a range of tracepoints. |
| 2843 | |
| 2844 | * ``apropos'' command added. |
| 2845 | |
| 2846 | The ``apropos'' command searches through command names and |
| 2847 | documentation strings, printing out matches, making it much easier to |
| 2848 | try to find a command that does what you are looking for. |
| 2849 | |
| 2850 | * New MI interface |
| 2851 | |
| 2852 | A new machine oriented interface (MI) has been added to GDB. This |
| 2853 | interface is designed for debug environments running GDB as a separate |
| 2854 | process. This is part of the long term libGDB project. See the |
| 2855 | "GDB/MI" chapter of the GDB manual for further information. It can be |
| 2856 | enabled by configuring with: |
| 2857 | |
| 2858 | .../configure --enable-gdbmi |
| 2859 | |
| 2860 | *** Changes in GDB-4.18: |
| 2861 | |
| 2862 | * New native configurations |
| 2863 | |
| 2864 | HP-UX 10.20 hppa*-*-hpux10.20 |
| 2865 | HP-UX 11.x hppa*-*-hpux11.0* |
| 2866 | M68K GNU/Linux m68*-*-linux* |
| 2867 | |
| 2868 | * New targets |
| 2869 | |
| 2870 | Fujitsu FR30 fr30-*-elf* |
| 2871 | Intel StrongARM strongarm-*-* |
| 2872 | Mitsubishi D30V d30v-*-* |
| 2873 | |
| 2874 | * OBSOLETE configurations |
| 2875 | |
| 2876 | Gould PowerNode, NP1 np1-*-*, pn-*-* |
| 2877 | |
| 2878 | Configurations that have been declared obsolete will be commented out, |
| 2879 | but the code will be left in place. If there is no activity to revive |
| 2880 | these configurations before the next release of GDB, the sources will |
| 2881 | be permanently REMOVED. |
| 2882 | |
| 2883 | * ANSI/ISO C |
| 2884 | |
| 2885 | As a compatibility experiment, GDB's source files buildsym.h and |
| 2886 | buildsym.c have been converted to pure standard C, no longer |
| 2887 | containing any K&R compatibility code. We believe that all systems in |
| 2888 | use today either come with a standard C compiler, or have a GCC port |
| 2889 | available. If this is not true, please report the affected |
| 2890 | configuration to bug-gdb@gnu.org immediately. See the README file for |
| 2891 | information about getting a standard C compiler if you don't have one |
| 2892 | already. |
| 2893 | |
| 2894 | * Readline 2.2 |
| 2895 | |
| 2896 | GDB now uses readline 2.2. |
| 2897 | |
| 2898 | * set extension-language |
| 2899 | |
| 2900 | You can now control the mapping between filename extensions and source |
| 2901 | languages by using the `set extension-language' command. For instance, |
| 2902 | you can ask GDB to treat .c files as C++ by saying |
| 2903 | set extension-language .c c++ |
| 2904 | The command `info extensions' lists all of the recognized extensions |
| 2905 | and their associated languages. |
| 2906 | |
| 2907 | * Setting processor type for PowerPC and RS/6000 |
| 2908 | |
| 2909 | When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target, |
| 2910 | you can use the `set processor' command to specify what variant of the |
| 2911 | PowerPC family you are debugging. The command |
| 2912 | |
| 2913 | set processor NAME |
| 2914 | |
| 2915 | sets the PowerPC/RS6000 variant to NAME. GDB knows about the |
| 2916 | following PowerPC and RS6000 variants: |
| 2917 | |
| 2918 | ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code |
| 2919 | rs6000 IBM RS6000 ("POWER") architecture, user-level view |
| 2920 | 403 IBM PowerPC 403 |
| 2921 | 403GC IBM PowerPC 403GC |
| 2922 | 505 Motorola PowerPC 505 |
| 2923 | 860 Motorola PowerPC 860 or 850 |
| 2924 | 601 Motorola PowerPC 601 |
| 2925 | 602 Motorola PowerPC 602 |
| 2926 | 603 Motorola/IBM PowerPC 603 or 603e |
| 2927 | 604 Motorola PowerPC 604 or 604e |
| 2928 | 750 Motorola/IBM PowerPC 750 or 750 |
| 2929 | |
| 2930 | At the moment, this command just tells GDB what to name the |
| 2931 | special-purpose processor registers. Since almost all the affected |
| 2932 | registers are inaccessible to user-level programs, this command is |
| 2933 | only useful for remote debugging in its present form. |
| 2934 | |
| 2935 | * HP-UX support |
| 2936 | |
| 2937 | Thanks to a major code donation from Hewlett-Packard, GDB now has much |
| 2938 | more extensive support for HP-UX. Added features include shared |
| 2939 | library support, kernel threads and hardware watchpoints for 11.00, |
| 2940 | support for HP's ANSI C and C++ compilers, and a compatibility mode |
| 2941 | for xdb and dbx commands. |
| 2942 | |
| 2943 | * Catchpoints |
| 2944 | |
| 2945 | HP's donation includes the new concept of catchpoints, which is a |
| 2946 | generalization of the old catch command. On HP-UX, it is now possible |
| 2947 | to catch exec, fork, and vfork, as well as library loading. |
| 2948 | |
| 2949 | This means that the existing catch command has changed; its first |
| 2950 | argument now specifies the type of catch to be set up. See the |
| 2951 | output of "help catch" for a list of catchpoint types. |
| 2952 | |
| 2953 | * Debugging across forks |
| 2954 | |
| 2955 | On HP-UX, you can choose which process to debug when a fork() happens |
| 2956 | in the inferior. |
| 2957 | |
| 2958 | * TUI |
| 2959 | |
| 2960 | HP has donated a curses-based terminal user interface (TUI). To get |
| 2961 | it, build with --enable-tui. Although this can be enabled for any |
| 2962 | configuration, at present it only works for native HP debugging. |
| 2963 | |
| 2964 | * GDB remote protocol additions |
| 2965 | |
| 2966 | A new protocol packet 'X' that writes binary data is now available. |
| 2967 | Default behavior is to try 'X', then drop back to 'M' if the stub |
| 2968 | fails to respond. The settable variable `remotebinarydownload' |
| 2969 | allows explicit control over the use of 'X'. |
| 2970 | |
| 2971 | For 64-bit targets, the memory packets ('M' and 'm') can now contain a |
| 2972 | full 64-bit address. The command |
| 2973 | |
| 2974 | set remoteaddresssize 32 |
| 2975 | |
| 2976 | can be used to revert to the old behaviour. For existing remote stubs |
| 2977 | the change should not be noticed, as the additional address information |
| 2978 | will be discarded. |
| 2979 | |
| 2980 | In order to assist in debugging stubs, you may use the maintenance |
| 2981 | command `packet' to send any text string to the stub. For instance, |
| 2982 | |
| 2983 | maint packet heythere |
| 2984 | |
| 2985 | sends the packet "$heythere#<checksum>". Note that it is very easy to |
| 2986 | disrupt a debugging session by sending the wrong packet at the wrong |
| 2987 | time. |
| 2988 | |
| 2989 | The compare-sections command allows you to compare section data on the |
| 2990 | target to what is in the executable file without uploading or |
| 2991 | downloading, by comparing CRC checksums. |
| 2992 | |
| 2993 | * Tracing can collect general expressions |
| 2994 | |
| 2995 | You may now collect general expressions at tracepoints. This requires |
| 2996 | further additions to the target-side stub; see tracepoint.c and |
| 2997 | doc/agentexpr.texi for further details. |
| 2998 | |
| 2999 | * mask-address variable for Mips |
| 3000 | |
| 3001 | For Mips targets, you may control the zeroing of the upper 32 bits of |
| 3002 | a 64-bit address by entering `set mask-address on'. This is mainly |
| 3003 | of interest to users of embedded R4xxx and R5xxx processors. |
| 3004 | |
| 3005 | * Higher serial baud rates |
| 3006 | |
| 3007 | GDB's serial code now allows you to specify baud rates 57600, 115200, |
| 3008 | 230400, and 460800 baud. (Note that your host system may not be able |
| 3009 | to achieve all of these rates.) |
| 3010 | |
| 3011 | * i960 simulator |
| 3012 | |
| 3013 | The i960 configuration now includes an initial implementation of a |
| 3014 | builtin simulator, contributed by Jim Wilson. |
| 3015 | |
| 3016 | |
| 3017 | *** Changes in GDB-4.17: |
| 3018 | |
| 3019 | * New native configurations |
| 3020 | |
| 3021 | Alpha GNU/Linux alpha*-*-linux* |
| 3022 | Unixware 2.x i[3456]86-unixware2* |
| 3023 | Irix 6.x mips*-sgi-irix6* |
| 3024 | PowerPC GNU/Linux powerpc-*-linux* |
| 3025 | PowerPC Solaris powerpcle-*-solaris* |
| 3026 | Sparc GNU/Linux sparc-*-linux* |
| 3027 | Motorola sysV68 R3V7.1 m68k-motorola-sysv |
| 3028 | |
| 3029 | * New targets |
| 3030 | |
| 3031 | Argonaut Risc Chip (ARC) arc-*-* |
| 3032 | Hitachi H8/300S h8300*-*-* |
| 3033 | Matsushita MN10200 w/simulator mn10200-*-* |
| 3034 | Matsushita MN10300 w/simulator mn10300-*-* |
| 3035 | MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf* |
| 3036 | MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf* |
| 3037 | MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf* |
| 3038 | Mitsubishi D10V w/simulator d10v-*-* |
| 3039 | Mitsubishi M32R/D w/simulator m32r-*-elf* |
| 3040 | Tsqware Sparclet sparclet-*-* |
| 3041 | NEC V850 w/simulator v850-*-* |
| 3042 | |
| 3043 | * New debugging protocols |
| 3044 | |
| 3045 | ARM with RDI protocol arm*-*-* |
| 3046 | M68K with dBUG monitor m68*-*-{aout,coff,elf} |
| 3047 | DDB and LSI variants of PMON protocol mips*-*-* |
| 3048 | PowerPC with DINK32 monitor powerpc{,le}-*-eabi |
| 3049 | PowerPC with SDS protocol powerpc{,le}-*-eabi |
| 3050 | Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi |
| 3051 | |
| 3052 | * DWARF 2 |
| 3053 | |
| 3054 | All configurations can now understand and use the DWARF 2 debugging |
| 3055 | format. The choice is automatic, if the symbol file contains DWARF 2 |
| 3056 | information. |
| 3057 | |
| 3058 | * Java frontend |
| 3059 | |
| 3060 | GDB now includes basic Java language support. This support is |
| 3061 | only useful with Java compilers that produce native machine code. |
| 3062 | |
| 3063 | * solib-absolute-prefix and solib-search-path |
| 3064 | |
| 3065 | For SunOS and SVR4 shared libraries, you may now set the prefix for |
| 3066 | loading absolute shared library symbol files, and the search path for |
| 3067 | locating non-absolute shared library symbol files. |
| 3068 | |
| 3069 | * Live range splitting |
| 3070 | |
| 3071 | GDB can now effectively debug code for which GCC has performed live |
| 3072 | range splitting as part of its optimization. See gdb/doc/LRS for |
| 3073 | more details on the expected format of the stabs information. |
| 3074 | |
| 3075 | * Hurd support |
| 3076 | |
| 3077 | GDB's support for the GNU Hurd, including thread debugging, has been |
| 3078 | updated to work with current versions of the Hurd. |
| 3079 | |
| 3080 | * ARM Thumb support |
| 3081 | |
| 3082 | GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit |
| 3083 | instruction set. ARM GDB automatically detects when Thumb |
| 3084 | instructions are in use, and adjusts disassembly and backtracing |
| 3085 | accordingly. |
| 3086 | |
| 3087 | * MIPS16 support |
| 3088 | |
| 3089 | GDB's MIPS target configurations now handle the MIP16 16-bit |
| 3090 | instruction set. |
| 3091 | |
| 3092 | * Overlay support |
| 3093 | |
| 3094 | GDB now includes support for overlays; if an executable has been |
| 3095 | linked such that multiple sections are based at the same address, GDB |
| 3096 | will decide which section to use for symbolic info. You can choose to |
| 3097 | control the decision manually, using overlay commands, or implement |
| 3098 | additional target-side support and use "overlay load-target" to bring |
| 3099 | in the overlay mapping. Do "help overlay" for more detail. |
| 3100 | |
| 3101 | * info symbol |
| 3102 | |
| 3103 | The command "info symbol <address>" displays information about |
| 3104 | the symbol at the specified address. |
| 3105 | |
| 3106 | * Trace support |
| 3107 | |
| 3108 | The standard remote protocol now includes an extension that allows |
| 3109 | asynchronous collection and display of trace data. This requires |
| 3110 | extensive support in the target-side debugging stub. Tracing mode |
| 3111 | includes a new interaction mode in GDB and new commands: see the |
| 3112 | file tracepoint.c for more details. |
| 3113 | |
| 3114 | * MIPS simulator |
| 3115 | |
| 3116 | Configurations for embedded MIPS now include a simulator contributed |
| 3117 | by Cygnus Solutions. The simulator supports the instruction sets |
| 3118 | of most MIPS variants. |
| 3119 | |
| 3120 | * Sparc simulator |
| 3121 | |
| 3122 | Sparc configurations may now include the ERC32 simulator contributed |
| 3123 | by the European Space Agency. The simulator is not built into |
| 3124 | Sparc targets by default; configure with --enable-sim to include it. |
| 3125 | |
| 3126 | * set architecture |
| 3127 | |
| 3128 | For target configurations that may include multiple variants of a |
| 3129 | basic architecture (such as MIPS and SH), you may now set the |
| 3130 | architecture explicitly. "set arch" sets, "info arch" lists |
| 3131 | the possible architectures. |
| 3132 | |
| 3133 | *** Changes in GDB-4.16: |
| 3134 | |
| 3135 | * New native configurations |
| 3136 | |
| 3137 | Windows 95, x86 Windows NT i[345]86-*-cygwin32 |
| 3138 | M68K NetBSD m68k-*-netbsd* |
| 3139 | PowerPC AIX 4.x powerpc-*-aix* |
| 3140 | PowerPC MacOS powerpc-*-macos* |
| 3141 | PowerPC Windows NT powerpcle-*-cygwin32 |
| 3142 | RS/6000 AIX 4.x rs6000-*-aix4* |
| 3143 | |
| 3144 | * New targets |
| 3145 | |
| 3146 | ARM with RDP protocol arm-*-* |
| 3147 | I960 with MON960 i960-*-coff |
| 3148 | MIPS VxWorks mips*-*-vxworks* |
| 3149 | MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf* |
| 3150 | PowerPC with PPCBUG monitor powerpc{,le}-*-eabi* |
| 3151 | Hitachi SH3 sh-*-* |
| 3152 | Matra Sparclet sparclet-*-* |
| 3153 | |
| 3154 | * PowerPC simulator |
| 3155 | |
| 3156 | The powerpc-eabi configuration now includes the PSIM simulator, |
| 3157 | contributed by Andrew Cagney, with assistance from Mike Meissner. |
| 3158 | PSIM is a very elaborate model of the PowerPC, including not only |
| 3159 | basic instruction set execution, but also details of execution unit |
| 3160 | performance and I/O hardware. See sim/ppc/README for more details. |
| 3161 | |
| 3162 | * Solaris 2.5 |
| 3163 | |
| 3164 | GDB now works with Solaris 2.5. |
| 3165 | |
| 3166 | * Windows 95/NT native |
| 3167 | |
| 3168 | GDB will now work as a native debugger on Windows 95 and Windows NT. |
| 3169 | To build it from source, you must use the "gnu-win32" environment, |
| 3170 | which uses a DLL to emulate enough of Unix to run the GNU tools. |
| 3171 | Further information, binaries, and sources are available at |
| 3172 | ftp.cygnus.com, under pub/gnu-win32. |
| 3173 | |
| 3174 | * dont-repeat command |
| 3175 | |
| 3176 | If a user-defined command includes the command `dont-repeat', then the |
| 3177 | command will not be repeated if the user just types return. This is |
| 3178 | useful if the command is time-consuming to run, so that accidental |
| 3179 | extra keystrokes don't run the same command many times. |
| 3180 | |
| 3181 | * Send break instead of ^C |
| 3182 | |
| 3183 | The standard remote protocol now includes an option to send a break |
| 3184 | rather than a ^C to the target in order to interrupt it. By default, |
| 3185 | GDB will send ^C; to send a break, set the variable `remotebreak' to 1. |
| 3186 | |
| 3187 | * Remote protocol timeout |
| 3188 | |
| 3189 | The standard remote protocol includes a new variable `remotetimeout' |
| 3190 | that allows you to set the number of seconds before GDB gives up trying |
| 3191 | to read from the target. The default value is 2. |
| 3192 | |
| 3193 | * Automatic tracking of dynamic object loading (HPUX and Solaris only) |
| 3194 | |
| 3195 | By default GDB will automatically keep track of objects as they are |
| 3196 | loaded and unloaded by the dynamic linker. By using the command `set |
| 3197 | stop-on-solib-events 1' you can arrange for GDB to stop the inferior |
| 3198 | when shared library events occur, thus allowing you to set breakpoints |
| 3199 | in shared libraries which are explicitly loaded by the inferior. |
| 3200 | |
| 3201 | Note this feature does not work on hpux8. On hpux9 you must link |
| 3202 | /usr/lib/end.o into your program. This feature should work |
| 3203 | automatically on hpux10. |
| 3204 | |
| 3205 | * Irix 5.x hardware watchpoint support |
| 3206 | |
| 3207 | Irix 5 configurations now support the use of hardware watchpoints. |
| 3208 | |
| 3209 | * Mips protocol "SYN garbage limit" |
| 3210 | |
| 3211 | When debugging a Mips target using the `target mips' protocol, you |
| 3212 | may set the number of characters that GDB will ignore by setting |
| 3213 | the `syn-garbage-limit'. A value of -1 means that GDB will ignore |
| 3214 | every character. The default value is 1050. |
| 3215 | |
| 3216 | * Recording and replaying remote debug sessions |
| 3217 | |
| 3218 | If you set `remotelogfile' to the name of a file, gdb will write to it |
| 3219 | a recording of a remote debug session. This recording may then be |
| 3220 | replayed back to gdb using "gdbreplay". See gdbserver/README for |
| 3221 | details. This is useful when you have a problem with GDB while doing |
| 3222 | remote debugging; you can make a recording of the session and send it |
| 3223 | to someone else, who can then recreate the problem. |
| 3224 | |
| 3225 | * Speedups for remote debugging |
| 3226 | |
| 3227 | GDB includes speedups for downloading and stepping MIPS systems using |
| 3228 | the IDT monitor, fast downloads to the Hitachi SH E7000 emulator, |
| 3229 | and more efficient S-record downloading. |
| 3230 | |
| 3231 | * Memory use reductions and statistics collection |
| 3232 | |
| 3233 | GDB now uses less memory and reports statistics about memory usage. |
| 3234 | Try the `maint print statistics' command, for example. |
| 3235 | |
| 3236 | *** Changes in GDB-4.15: |
| 3237 | |
| 3238 | * Psymtabs for XCOFF |
| 3239 | |
| 3240 | The symbol reader for AIX GDB now uses partial symbol tables. This |
| 3241 | can greatly improve startup time, especially for large executables. |
| 3242 | |
| 3243 | * Remote targets use caching |
| 3244 | |
| 3245 | Remote targets now use a data cache to speed up communication with the |
| 3246 | remote side. The data cache could lead to incorrect results because |
| 3247 | it doesn't know about volatile variables, thus making it impossible to |
| 3248 | debug targets which use memory mapped I/O devices. `set remotecache |
| 3249 | off' turns the the data cache off. |
| 3250 | |
| 3251 | * Remote targets may have threads |
| 3252 | |
| 3253 | The standard remote protocol now includes support for multiple threads |
| 3254 | in the target system, using new protocol commands 'H' and 'T'. See |
| 3255 | gdb/remote.c for details. |
| 3256 | |
| 3257 | * NetROM support |
| 3258 | |
| 3259 | If GDB is configured with `--enable-netrom', then it will include |
| 3260 | support for the NetROM ROM emulator from XLNT Designs. The NetROM |
| 3261 | acts as though it is a bank of ROM on the target board, but you can |
| 3262 | write into it over the network. GDB's support consists only of |
| 3263 | support for fast loading into the emulated ROM; to debug, you must use |
| 3264 | another protocol, such as standard remote protocol. The usual |
| 3265 | sequence is something like |
| 3266 | |
| 3267 | target nrom <netrom-hostname> |
| 3268 | load <prog> |
| 3269 | target remote <netrom-hostname>:1235 |
| 3270 | |
| 3271 | * Macintosh host |
| 3272 | |
| 3273 | GDB now includes support for the Apple Macintosh, as a host only. It |
| 3274 | may be run as either an MPW tool or as a standalone application, and |
| 3275 | it can debug through the serial port. All the usual GDB commands are |
| 3276 | available, but to the target command, you must supply "serial" as the |
| 3277 | device type instead of "/dev/ttyXX". See mpw-README in the main |
| 3278 | directory for more information on how to build. The MPW configuration |
| 3279 | scripts */mpw-config.in support only a few targets, and only the |
| 3280 | mips-idt-ecoff target has been tested. |
| 3281 | |
| 3282 | * Autoconf |
| 3283 | |
| 3284 | GDB configuration now uses autoconf. This is not user-visible, |
| 3285 | but does simplify configuration and building. |
| 3286 | |
| 3287 | * hpux10 |
| 3288 | |
| 3289 | GDB now supports hpux10. |
| 3290 | |
| 3291 | *** Changes in GDB-4.14: |
| 3292 | |
| 3293 | * New native configurations |
| 3294 | |
| 3295 | x86 FreeBSD i[345]86-*-freebsd |
| 3296 | x86 NetBSD i[345]86-*-netbsd |
| 3297 | NS32k NetBSD ns32k-*-netbsd |
| 3298 | Sparc NetBSD sparc-*-netbsd |
| 3299 | |
| 3300 | * New targets |
| 3301 | |
| 3302 | A29K VxWorks a29k-*-vxworks |
| 3303 | HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro* |
| 3304 | CPU32 EST-300 emulator m68*-*-est* |
| 3305 | PowerPC ELF powerpc-*-elf |
| 3306 | WDC 65816 w65-*-* |
| 3307 | |
| 3308 | * Alpha OSF/1 support for procfs |
| 3309 | |
| 3310 | GDB now supports procfs under OSF/1-2.x and higher, which makes it |
| 3311 | possible to attach to running processes. As the mounting of the /proc |
| 3312 | filesystem is optional on the Alpha, GDB automatically determines |
| 3313 | the availability of /proc during startup. This can lead to problems |
| 3314 | if /proc is unmounted after GDB has been started. |
| 3315 | |
| 3316 | * Arguments to user-defined commands |
| 3317 | |
| 3318 | User commands may accept up to 10 arguments separated by whitespace. |
| 3319 | Arguments are accessed within the user command via $arg0..$arg9. A |
| 3320 | trivial example: |
| 3321 | define adder |
| 3322 | print $arg0 + $arg1 + $arg2 |
| 3323 | |
| 3324 | To execute the command use: |
| 3325 | adder 1 2 3 |
| 3326 | |
| 3327 | Defines the command "adder" which prints the sum of its three arguments. |
| 3328 | Note the arguments are text substitutions, so they may reference variables, |
| 3329 | use complex expressions, or even perform inferior function calls. |
| 3330 | |
| 3331 | * New `if' and `while' commands |
| 3332 | |
| 3333 | This makes it possible to write more sophisticated user-defined |
| 3334 | commands. Both commands take a single argument, which is the |
| 3335 | expression to evaluate, and must be followed by the commands to |
| 3336 | execute, one per line, if the expression is nonzero, the list being |
| 3337 | terminated by the word `end'. The `if' command list may include an |
| 3338 | `else' word, which causes the following commands to be executed only |
| 3339 | if the expression is zero. |
| 3340 | |
| 3341 | * Fortran source language mode |
| 3342 | |
| 3343 | GDB now includes partial support for Fortran 77. It will recognize |
| 3344 | Fortran programs and can evaluate a subset of Fortran expressions, but |
| 3345 | variables and functions may not be handled correctly. GDB will work |
| 3346 | with G77, but does not yet know much about symbols emitted by other |
| 3347 | Fortran compilers. |
| 3348 | |
| 3349 | * Better HPUX support |
| 3350 | |
| 3351 | Most debugging facilities now work on dynamic executables for HPPAs |
| 3352 | running hpux9 or later. You can attach to running dynamically linked |
| 3353 | processes, but by default the dynamic libraries will be read-only, so |
| 3354 | for instance you won't be able to put breakpoints in them. To change |
| 3355 | that behavior do the following before running the program: |
| 3356 | |
| 3357 | adb -w a.out |
| 3358 | __dld_flags?W 0x5 |
| 3359 | control-d |
| 3360 | |
| 3361 | This will cause the libraries to be mapped private and read-write. |
| 3362 | To revert to the normal behavior, do this: |
| 3363 | |
| 3364 | adb -w a.out |
| 3365 | __dld_flags?W 0x4 |
| 3366 | control-d |
| 3367 | |
| 3368 | You cannot set breakpoints or examine data in the library until after |
| 3369 | the library is loaded if the function/data symbols do not have |
| 3370 | external linkage. |
| 3371 | |
| 3372 | GDB can now also read debug symbols produced by the HP C compiler on |
| 3373 | HPPAs (sorry, no C++, Fortran or 68k support). |
| 3374 | |
| 3375 | * Target byte order now dynamically selectable |
| 3376 | |
| 3377 | You can choose which byte order to use with a target system, via the |
| 3378 | commands "set endian big" and "set endian little", and you can see the |
| 3379 | current setting by using "show endian". You can also give the command |
| 3380 | "set endian auto", in which case GDB will use the byte order |
| 3381 | associated with the executable. Currently, only embedded MIPS |
| 3382 | configurations support dynamic selection of target byte order. |
| 3383 | |
| 3384 | * New DOS host serial code |
| 3385 | |
| 3386 | This version uses DPMI interrupts to handle buffered I/O, so you |
| 3387 | no longer need to run asynctsr when debugging boards connected to |
| 3388 | a PC's serial port. |
| 3389 | |
| 3390 | *** Changes in GDB-4.13: |
| 3391 | |
| 3392 | * New "complete" command |
| 3393 | |
| 3394 | This lists all the possible completions for the rest of the line, if it |
| 3395 | were to be given as a command itself. This is intended for use by emacs. |
| 3396 | |
| 3397 | * Trailing space optional in prompt |
| 3398 | |
| 3399 | "set prompt" no longer adds a space for you after the prompt you set. This |
| 3400 | allows you to set a prompt which ends in a space or one that does not. |
| 3401 | |
| 3402 | * Breakpoint hit counts |
| 3403 | |
| 3404 | "info break" now displays a count of the number of times the breakpoint |
| 3405 | has been hit. This is especially useful in conjunction with "ignore"; you |
| 3406 | can ignore a large number of breakpoint hits, look at the breakpoint info |
| 3407 | to see how many times the breakpoint was hit, then run again, ignoring one |
| 3408 | less than that number, and this will get you quickly to the last hit of |
| 3409 | that breakpoint. |
| 3410 | |
| 3411 | * Ability to stop printing at NULL character |
| 3412 | |
| 3413 | "set print null-stop" will cause GDB to stop printing the characters of |
| 3414 | an array when the first NULL is encountered. This is useful when large |
| 3415 | arrays actually contain only short strings. |
| 3416 | |
| 3417 | * Shared library breakpoints |
| 3418 | |
| 3419 | In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set |
| 3420 | breakpoints in shared libraries before the executable is run. |
| 3421 | |
| 3422 | * Hardware watchpoints |
| 3423 | |
| 3424 | There is a new hardware breakpoint for the watch command for sparclite |
| 3425 | targets. See gdb/sparclite/hw_breakpoint.note. |
| 3426 | |
| 3427 | Hardware watchpoints are also now supported under GNU/Linux. |
| 3428 | |
| 3429 | * Annotations |
| 3430 | |
| 3431 | Annotations have been added. These are for use with graphical interfaces, |
| 3432 | and are still experimental. Currently only gdba.el uses these. |
| 3433 | |
| 3434 | * Improved Irix 5 support |
| 3435 | |
| 3436 | GDB now works properly with Irix 5.2. |
| 3437 | |
| 3438 | * Improved HPPA support |
| 3439 | |
| 3440 | GDB now works properly with the latest GCC and GAS. |
| 3441 | |
| 3442 | * New native configurations |
| 3443 | |
| 3444 | Sequent PTX4 i[34]86-sequent-ptx4 |
| 3445 | HPPA running OSF/1 hppa*-*-osf* |
| 3446 | Atari TT running SVR4 m68*-*-sysv4* |
| 3447 | RS/6000 LynxOS rs6000-*-lynxos* |
| 3448 | |
| 3449 | * New targets |
| 3450 | |
| 3451 | OS/9000 i[34]86-*-os9k |
| 3452 | MIPS R4000 mips64*{,el}-*-{ecoff,elf} |
| 3453 | Sparc64 sparc64-*-* |
| 3454 | |
| 3455 | * Hitachi SH7000 and E7000-PC ICE support |
| 3456 | |
| 3457 | There is now support for communicating with the Hitachi E7000-PC ICE. |
| 3458 | This is available automatically when GDB is configured for the SH. |
| 3459 | |
| 3460 | * Fixes |
| 3461 | |
| 3462 | As usual, a variety of small fixes and improvements, both generic |
| 3463 | and configuration-specific. See the ChangeLog for more detail. |
| 3464 | |
| 3465 | *** Changes in GDB-4.12: |
| 3466 | |
| 3467 | * Irix 5 is now supported |
| 3468 | |
| 3469 | * HPPA support |
| 3470 | |
| 3471 | GDB-4.12 on the HPPA has a number of changes which make it unable |
| 3472 | to debug the output from the currently released versions of GCC and |
| 3473 | GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release |
| 3474 | of GCC and GAS, versions of these tools designed to work with GDB-4.12 |
| 3475 | can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist. |
| 3476 | |
| 3477 | |
| 3478 | *** Changes in GDB-4.11: |
| 3479 | |
| 3480 | * User visible changes: |
| 3481 | |
| 3482 | * Remote Debugging |
| 3483 | |
| 3484 | The "set remotedebug" option is now consistent between the mips remote |
| 3485 | target, remote targets using the gdb-specific protocol, UDI (AMD's |
| 3486 | debug protocol for the 29k) and the 88k bug monitor. It is now an |
| 3487 | integer specifying a debug level (normally 0 or 1, but 2 means more |
| 3488 | debugging info for the mips target). |
| 3489 | |
| 3490 | * DEC Alpha native support |
| 3491 | |
| 3492 | GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable |
| 3493 | debug info, but GDB works fairly well with the DEC compiler and should |
| 3494 | work with a future GCC release. See the README file for a few |
| 3495 | Alpha-specific notes. |
| 3496 | |
| 3497 | * Preliminary thread implementation |
| 3498 | |
| 3499 | GDB now has preliminary thread support for both SGI/Irix and LynxOS. |
| 3500 | |
| 3501 | * LynxOS native and target support for 386 |
| 3502 | |
| 3503 | This release has been hosted on LynxOS 2.2, and also can be configured |
| 3504 | to remotely debug programs running under LynxOS (see gdb/gdbserver/README |
| 3505 | for details). |
| 3506 | |
| 3507 | * Improvements in C++ mangling/demangling. |
| 3508 | |
| 3509 | This release has much better g++ debugging, specifically in name |
| 3510 | mangling/demangling, virtual function calls, print virtual table, |
| 3511 | call methods, ...etc. |
| 3512 | |
| 3513 | *** Changes in GDB-4.10: |
| 3514 | |
| 3515 | * User visible changes: |
| 3516 | |
| 3517 | Remote debugging using the GDB-specific (`target remote') protocol now |
| 3518 | supports the `load' command. This is only useful if you have some |
| 3519 | other way of getting the stub to the target system, and you can put it |
| 3520 | somewhere in memory where it won't get clobbered by the download. |
| 3521 | |
| 3522 | Filename completion now works. |
| 3523 | |
| 3524 | When run under emacs mode, the "info line" command now causes the |
| 3525 | arrow to point to the line specified. Also, "info line" prints |
| 3526 | addresses in symbolic form (as well as hex). |
| 3527 | |
| 3528 | All vxworks based targets now support a user settable option, called |
| 3529 | vxworks-timeout. This option represents the number of seconds gdb |
| 3530 | should wait for responses to rpc's. You might want to use this if |
| 3531 | your vxworks target is, perhaps, a slow software simulator or happens |
| 3532 | to be on the far side of a thin network line. |
| 3533 | |
| 3534 | * DEC alpha support |
| 3535 | |
| 3536 | This release contains support for using a DEC alpha as a GDB host for |
| 3537 | cross debugging. Native alpha debugging is not supported yet. |
| 3538 | |
| 3539 | |
| 3540 | *** Changes in GDB-4.9: |
| 3541 | |
| 3542 | * Testsuite |
| 3543 | |
| 3544 | This is the first GDB release which is accompanied by a matching testsuite. |
| 3545 | The testsuite requires installation of dejagnu, which should be available |
| 3546 | via ftp from most sites that carry GNU software. |
| 3547 | |
| 3548 | * C++ demangling |
| 3549 | |
| 3550 | 'Cfront' style demangling has had its name changed to 'ARM' style, to |
| 3551 | emphasize that it was written from the specifications in the C++ Annotated |
| 3552 | Reference Manual, not necessarily to be compatible with AT&T cfront. Despite |
| 3553 | disclaimers, it still generated too much confusion with users attempting to |
| 3554 | use gdb with AT&T cfront. |
| 3555 | |
| 3556 | * Simulators |
| 3557 | |
| 3558 | GDB now uses a standard remote interface to a simulator library. |
| 3559 | So far, the library contains simulators for the Zilog Z8001/2, the |
| 3560 | Hitachi H8/300, H8/500 and Super-H. |
| 3561 | |
| 3562 | * New targets supported |
| 3563 | |
| 3564 | H8/300 simulator h8300-hitachi-hms or h8300hms |
| 3565 | H8/500 simulator h8500-hitachi-hms or h8500hms |
| 3566 | SH simulator sh-hitachi-hms or sh |
| 3567 | Z8000 simulator z8k-zilog-none or z8ksim |
| 3568 | IDT MIPS board over serial line mips-idt-ecoff |
| 3569 | |
| 3570 | Cross-debugging to GO32 targets is supported. It requires a custom |
| 3571 | version of the i386-stub.c module which is integrated with the |
| 3572 | GO32 memory extender. |
| 3573 | |
| 3574 | * New remote protocols |
| 3575 | |
| 3576 | MIPS remote debugging protocol. |
| 3577 | |
| 3578 | * New source languages supported |
| 3579 | |
| 3580 | This version includes preliminary support for Chill, a Pascal like language |
| 3581 | used by telecommunications companies. Chill support is also being integrated |
| 3582 | into the GNU compiler, but we don't know when it will be publically available. |
| 3583 | |
| 3584 | |
| 3585 | *** Changes in GDB-4.8: |
| 3586 | |
| 3587 | * HP Precision Architecture supported |
| 3588 | |
| 3589 | GDB now supports HP PA-RISC machines running HPUX. A preliminary |
| 3590 | version of this support was available as a set of patches from the |
| 3591 | University of Utah. GDB does not support debugging of programs |
| 3592 | compiled with the HP compiler, because HP will not document their file |
| 3593 | format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS |
| 3594 | (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z). |
| 3595 | |
| 3596 | Many problems in the preliminary version have been fixed. |
| 3597 | |
| 3598 | * Faster and better demangling |
| 3599 | |
| 3600 | We have improved template demangling and fixed numerous bugs in the GNU style |
| 3601 | demangler. It can now handle type modifiers such as `static' or `const'. Wide |
| 3602 | character types (wchar_t) are now supported. Demangling of each symbol is now |
| 3603 | only done once, and is cached when the symbol table for a file is read in. |
| 3604 | This results in a small increase in memory usage for C programs, a moderate |
| 3605 | increase in memory usage for C++ programs, and a fantastic speedup in |
| 3606 | symbol lookups. |
| 3607 | |
| 3608 | `Cfront' style demangling still doesn't work with AT&T cfront. It was written |
| 3609 | from the specifications in the Annotated Reference Manual, which AT&T's |
| 3610 | compiler does not actually implement. |
| 3611 | |
| 3612 | * G++ multiple inheritance compiler problem |
| 3613 | |
| 3614 | In the 2.3.2 release of gcc/g++, how the compiler resolves multiple |
| 3615 | inheritance lattices was reworked to properly discover ambiguities. We |
| 3616 | recently found an example which causes this new algorithm to fail in a |
| 3617 | very subtle way, producing bad debug information for those classes. |
| 3618 | The file 'gcc.patch' (in this directory) can be applied to gcc to |
| 3619 | circumvent the problem. A future GCC release will contain a complete |
| 3620 | fix. |
| 3621 | |
| 3622 | The previous G++ debug info problem (mentioned below for the gdb-4.7 |
| 3623 | release) is fixed in gcc version 2.3.2. |
| 3624 | |
| 3625 | * Improved configure script |
| 3626 | |
| 3627 | The `configure' script will now attempt to guess your system type if |
| 3628 | you don't supply a host system type. The old scheme of supplying a |
| 3629 | host system triplet is preferable over using this. All the magic is |
| 3630 | done in the new `config.guess' script. Examine it for details. |
| 3631 | |
| 3632 | We have also brought our configure script much more in line with the FSF's |
| 3633 | version. It now supports the --with-xxx options. In particular, |
| 3634 | `--with-minimal-bfd' can be used to make the GDB binary image smaller. |
| 3635 | The resulting GDB will not be able to read arbitrary object file formats -- |
| 3636 | only the format ``expected'' to be used on the configured target system. |
| 3637 | We hope to make this the default in a future release. |
| 3638 | |
| 3639 | * Documentation improvements |
| 3640 | |
| 3641 | There's new internal documentation on how to modify GDB, and how to |
| 3642 | produce clean changes to the code. We implore people to read it |
| 3643 | before submitting changes. |
| 3644 | |
| 3645 | The GDB manual uses new, sexy Texinfo conditionals, rather than arcane |
| 3646 | M4 macros. The new texinfo.tex is provided in this release. Pre-built |
| 3647 | `info' files are also provided. To build `info' files from scratch, |
| 3648 | you will need the latest `makeinfo' release, which will be available in |
| 3649 | a future texinfo-X.Y release. |
| 3650 | |
| 3651 | *NOTE* The new texinfo.tex can cause old versions of TeX to hang. |
| 3652 | We're not sure exactly which versions have this problem, but it has |
| 3653 | been seen in 3.0. We highly recommend upgrading to TeX version 3.141 |
| 3654 | or better. If that isn't possible, there is a patch in |
| 3655 | `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work |
| 3656 | around this problem. |
| 3657 | |
| 3658 | * New features |
| 3659 | |
| 3660 | GDB now supports array constants that can be used in expressions typed in by |
| 3661 | the user. The syntax is `{element, element, ...}'. Ie: you can now type |
| 3662 | `print {1, 2, 3}', and it will build up an array in memory malloc'd in |
| 3663 | the target program. |
| 3664 | |
| 3665 | The new directory `gdb/sparclite' contains a program that demonstrates |
| 3666 | how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor. |
| 3667 | |
| 3668 | * New native hosts supported |
| 3669 | |
| 3670 | HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux |
| 3671 | 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4 |
| 3672 | |
| 3673 | * New targets supported |
| 3674 | |
| 3675 | AMD 29k family via UDI a29k-amd-udi or udi29k |
| 3676 | |
| 3677 | * New file formats supported |
| 3678 | |
| 3679 | BFD now supports reading HP/PA-RISC executables (SOM file format?), |
| 3680 | HPUX core files, and SCO 3.2v2 core files. |
| 3681 | |
| 3682 | * Major bug fixes |
| 3683 | |
| 3684 | Attaching to processes now works again; thanks for the many bug reports. |
| 3685 | |
| 3686 | We have also stomped on a bunch of core dumps caused by |
| 3687 | printf_filtered("%s") problems. |
| 3688 | |
| 3689 | We eliminated a copyright problem on the rpc and ptrace header files |
| 3690 | for VxWorks, which was discovered at the last minute during the 4.7 |
| 3691 | release. You should now be able to build a VxWorks GDB. |
| 3692 | |
| 3693 | You can now interrupt gdb while an attached process is running. This |
| 3694 | will cause the attached process to stop, and give control back to GDB. |
| 3695 | |
| 3696 | We fixed problems caused by using too many file descriptors |
| 3697 | for reading symbols from object files and libraries. This was |
| 3698 | especially a problem for programs that used many (~100) shared |
| 3699 | libraries. |
| 3700 | |
| 3701 | The `step' command now only enters a subroutine if there is line number |
| 3702 | information for the subroutine. Otherwise it acts like the `next' |
| 3703 | command. Previously, `step' would enter subroutines if there was |
| 3704 | any debugging information about the routine. This avoids problems |
| 3705 | when using `cc -g1' on MIPS machines. |
| 3706 | |
| 3707 | * Internal improvements |
| 3708 | |
| 3709 | GDB's internal interfaces have been improved to make it easier to support |
| 3710 | debugging of multiple languages in the future. |
| 3711 | |
| 3712 | GDB now uses a common structure for symbol information internally. |
| 3713 | Minimal symbols (derived from linkage symbols in object files), partial |
| 3714 | symbols (from a quick scan of debug information), and full symbols |
| 3715 | contain a common subset of information, making it easier to write |
| 3716 | shared code that handles any of them. |
| 3717 | |
| 3718 | * New command line options |
| 3719 | |
| 3720 | We now accept --silent as an alias for --quiet. |
| 3721 | |
| 3722 | * Mmalloc licensing |
| 3723 | |
| 3724 | The memory-mapped-malloc library is now licensed under the GNU Library |
| 3725 | General Public License. |
| 3726 | |
| 3727 | *** Changes in GDB-4.7: |
| 3728 | |
| 3729 | * Host/native/target split |
| 3730 | |
| 3731 | GDB has had some major internal surgery to untangle the support for |
| 3732 | hosts and remote targets. Now, when you configure GDB for a remote |
| 3733 | target, it will no longer load in all of the support for debugging |
| 3734 | local programs on the host. When fully completed and tested, this will |
| 3735 | ensure that arbitrary host/target combinations are possible. |
| 3736 | |
| 3737 | The primary conceptual shift is to separate the non-portable code in |
| 3738 | GDB into three categories. Host specific code is required any time GDB |
| 3739 | is compiled on that host, regardless of the target. Target specific |
| 3740 | code relates to the peculiarities of the target, but can be compiled on |
| 3741 | any host. Native specific code is everything else: it can only be |
| 3742 | built when the host and target are the same system. Child process |
| 3743 | handling and core file support are two common `native' examples. |
| 3744 | |
| 3745 | GDB's use of /proc for controlling Unix child processes is now cleaner. |
| 3746 | It has been split out into a single module under the `target_ops' vector, |
| 3747 | plus two native-dependent functions for each system that uses /proc. |
| 3748 | |
| 3749 | * New hosts supported |
| 3750 | |
| 3751 | HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd |
| 3752 | 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd |
| 3753 | 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco |
| 3754 | |
| 3755 | * New targets supported |
| 3756 | |
| 3757 | Fujitsu SPARClite sparclite-fujitsu-none or sparclite |
| 3758 | 68030 and CPU32 m68030-*-*, m68332-*-* |
| 3759 | |
| 3760 | * New native hosts supported |
| 3761 | |
| 3762 | 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd |
| 3763 | (386bsd is not well tested yet) |
| 3764 | 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco |
| 3765 | |
| 3766 | * New file formats supported |
| 3767 | |
| 3768 | BFD now supports COFF files for the Zilog Z8000 microprocessor. It |
| 3769 | supports reading of `a.out.adobe' object files, which are an a.out |
| 3770 | format extended with minimal information about multiple sections. |
| 3771 | |
| 3772 | * New commands |
| 3773 | |
| 3774 | `show copying' is the same as the old `info copying'. |
| 3775 | `show warranty' is the same as `info warrantee'. |
| 3776 | These were renamed for consistency. The old commands continue to work. |
| 3777 | |
| 3778 | `info handle' is a new alias for `info signals'. |
| 3779 | |
| 3780 | You can now define pre-command hooks, which attach arbitrary command |
| 3781 | scripts to any command. The commands in the hook will be executed |
| 3782 | prior to the user's command. You can also create a hook which will be |
| 3783 | executed whenever the program stops. See gdb.texinfo. |
| 3784 | |
| 3785 | * C++ improvements |
| 3786 | |
| 3787 | We now deal with Cfront style name mangling, and can even extract type |
| 3788 | info from mangled symbols. GDB can automatically figure out which |
| 3789 | symbol mangling style your C++ compiler uses. |
| 3790 | |
| 3791 | Calling of methods and virtual functions has been improved as well. |
| 3792 | |
| 3793 | * Major bug fixes |
| 3794 | |
| 3795 | The crash that occured when debugging Sun Ansi-C compiled binaries is |
| 3796 | fixed. This was due to mishandling of the extra N_SO stabs output |
| 3797 | by the compiler. |
| 3798 | |
| 3799 | We also finally got Ultrix 4.2 running in house, and fixed core file |
| 3800 | support, with help from a dozen people on the net. |
| 3801 | |
| 3802 | John M. Farrell discovered that the reason that single-stepping was so |
| 3803 | slow on all of the Mips based platforms (primarily SGI and DEC) was |
| 3804 | that we were trying to demangle and lookup a symbol used for internal |
| 3805 | purposes on every instruction that was being stepped through. Changing |
| 3806 | the name of that symbol so that it couldn't be mistaken for a C++ |
| 3807 | mangled symbol sped things up a great deal. |
| 3808 | |
| 3809 | Rich Pixley sped up symbol lookups in general by getting much smarter |
| 3810 | about when C++ symbol mangling is necessary. This should make symbol |
| 3811 | completion (TAB on the command line) much faster. It's not as fast as |
| 3812 | we'd like, but it's significantly faster than gdb-4.6. |
| 3813 | |
| 3814 | * AMD 29k support |
| 3815 | |
| 3816 | A new user controllable variable 'call_scratch_address' can |
| 3817 | specify the location of a scratch area to be used when GDB |
| 3818 | calls a function in the target. This is necessary because the |
| 3819 | usual method of putting the scratch area on the stack does not work |
| 3820 | in systems that have separate instruction and data spaces. |
| 3821 | |
| 3822 | We integrated changes to support the 29k UDI (Universal Debugger |
| 3823 | Interface), but discovered at the last minute that we didn't have all |
| 3824 | of the appropriate copyright paperwork. We are working with AMD to |
| 3825 | resolve this, and hope to have it available soon. |
| 3826 | |
| 3827 | * Remote interfaces |
| 3828 | |
| 3829 | We have sped up the remote serial line protocol, especially for targets |
| 3830 | with lots of registers. It now supports a new `expedited status' ('T') |
| 3831 | message which can be used in place of the existing 'S' status message. |
| 3832 | This allows the remote stub to send only the registers that GDB |
| 3833 | needs to make a quick decision about single-stepping or conditional |
| 3834 | breakpoints, eliminating the need to fetch the entire register set for |
| 3835 | each instruction being stepped through. |
| 3836 | |
| 3837 | The GDB remote serial protocol now implements a write-through cache for |
| 3838 | registers, only re-reading the registers if the target has run. |
| 3839 | |
| 3840 | There is also a new remote serial stub for SPARC processors. You can |
| 3841 | find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the |
| 3842 | Fujitsu SPARClite processor, but will run on any stand-alone SPARC |
| 3843 | processor with a serial port. |
| 3844 | |
| 3845 | * Configuration |
| 3846 | |
| 3847 | Configure.in files have become much easier to read and modify. A new |
| 3848 | `table driven' format makes it more obvious what configurations are |
| 3849 | supported, and what files each one uses. |
| 3850 | |
| 3851 | * Library changes |
| 3852 | |
| 3853 | There is a new opcodes library which will eventually contain all of the |
| 3854 | disassembly routines and opcode tables. At present, it only contains |
| 3855 | Sparc and Z8000 routines. This will allow the assembler, debugger, and |
| 3856 | disassembler (binutils/objdump) to share these routines. |
| 3857 | |
| 3858 | The libiberty library is now copylefted under the GNU Library General |
| 3859 | Public License. This allows more liberal use, and was done so libg++ |
| 3860 | can use it. This makes no difference to GDB, since the Library License |
| 3861 | grants all the rights from the General Public License. |
| 3862 | |
| 3863 | * Documentation |
| 3864 | |
| 3865 | The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete |
| 3866 | reference to the stabs symbol info used by the debugger. It is (as far |
| 3867 | as we know) the only published document on this fascinating topic. We |
| 3868 | encourage you to read it, compare it to the stabs information on your |
| 3869 | system, and send improvements on the document in general (to |
| 3870 | bug-gdb@prep.ai.mit.edu). |
| 3871 | |
| 3872 | And, of course, many bugs have been fixed. |
| 3873 | |
| 3874 | |
| 3875 | *** Changes in GDB-4.6: |
| 3876 | |
| 3877 | * Better support for C++ function names |
| 3878 | |
| 3879 | GDB now accepts as input the "demangled form" of C++ overloaded function |
| 3880 | names and member function names, and can do command completion on such names |
| 3881 | (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of |
| 3882 | single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'. |
| 3883 | Make use of command completion, it is your friend. |
| 3884 | |
| 3885 | GDB also now accepts a variety of C++ mangled symbol formats. They are |
| 3886 | the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style. |
| 3887 | You can tell GDB which format to use by doing a 'set demangle-style {gnu, |
| 3888 | lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo' |
| 3889 | for the list of formats. |
| 3890 | |
| 3891 | * G++ symbol mangling problem |
| 3892 | |
| 3893 | Recent versions of gcc have a bug in how they emit debugging information for |
| 3894 | C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this |
| 3895 | directory) can be applied to gcc to fix the problem. Alternatively, if you |
| 3896 | can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The |
| 3897 | usual symptom is difficulty with setting breakpoints on methods. GDB complains |
| 3898 | about the method being non-existent. (We believe that version 2.2.2 of GCC has |
| 3899 | this problem.) |
| 3900 | |
| 3901 | * New 'maintenance' command |
| 3902 | |
| 3903 | All of the commands related to hacking GDB internals have been moved out of |
| 3904 | the main command set, and now live behind the 'maintenance' command. This |
| 3905 | can also be abbreviated as 'mt'. The following changes were made: |
| 3906 | |
| 3907 | dump-me -> maintenance dump-me |
| 3908 | info all-breakpoints -> maintenance info breakpoints |
| 3909 | printmsyms -> maintenance print msyms |
| 3910 | printobjfiles -> maintenance print objfiles |
| 3911 | printpsyms -> maintenance print psymbols |
| 3912 | printsyms -> maintenance print symbols |
| 3913 | |
| 3914 | The following commands are new: |
| 3915 | |
| 3916 | maintenance demangle Call internal GDB demangler routine to |
| 3917 | demangle a C++ link name and prints the result. |
| 3918 | maintenance print type Print a type chain for a given symbol |
| 3919 | |
| 3920 | * Change to .gdbinit file processing |
| 3921 | |
| 3922 | We now read the $HOME/.gdbinit file before processing the argv arguments |
| 3923 | (e.g. reading symbol files or core files). This allows global parameters to |
| 3924 | be set, which will apply during the symbol reading. The ./.gdbinit is still |
| 3925 | read after argv processing. |
| 3926 | |
| 3927 | * New hosts supported |
| 3928 | |
| 3929 | Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2 |
| 3930 | |
| 3931 | GNU/Linux support i386-unknown-linux or linux |
| 3932 | |
| 3933 | We are also including code to support the HP/PA running BSD and HPUX. This |
| 3934 | is almost guaranteed not to work, as we didn't have time to test or build it |
| 3935 | for this release. We are including it so that the more adventurous (or |
| 3936 | masochistic) of you can play with it. We also had major problems with the |
| 3937 | fact that the compiler that we got from HP doesn't support the -g option. |
| 3938 | It costs extra. |
| 3939 | |
| 3940 | * New targets supported |
| 3941 | |
| 3942 | Hitachi H8/300 h8300-hitachi-hms or h8300hms |
| 3943 | |
| 3944 | * More smarts about finding #include files |
| 3945 | |
| 3946 | GDB now remembers the compilation directory for all include files, and for |
| 3947 | all files from which C is generated (like yacc and lex sources). This |
| 3948 | greatly improves GDB's ability to find yacc/lex sources, and include files, |
| 3949 | especially if you are debugging your program from a directory different from |
| 3950 | the one that contains your sources. |
| 3951 | |
| 3952 | We also fixed a bug which caused difficulty with listing and setting |
| 3953 | breakpoints in include files which contain C code. (In the past, you had to |
| 3954 | try twice in order to list an include file that you hadn't looked at before.) |
| 3955 | |
| 3956 | * Interesting infernals change |
| 3957 | |
| 3958 | GDB now deals with arbitrary numbers of sections, where the symbols for each |
| 3959 | section must be relocated relative to that section's landing place in the |
| 3960 | target's address space. This work was needed to support ELF with embedded |
| 3961 | stabs used by Solaris-2.0. |
| 3962 | |
| 3963 | * Bug fixes (of course!) |
| 3964 | |
| 3965 | There have been loads of fixes for the following things: |
| 3966 | mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k, |
| 3967 | i960, stabs, DOS(GO32), procfs, etc... |
| 3968 | |
| 3969 | See the ChangeLog for details. |
| 3970 | |
| 3971 | *** Changes in GDB-4.5: |
| 3972 | |
| 3973 | * New machines supported (host and target) |
| 3974 | |
| 3975 | IBM RS6000 running AIX rs6000-ibm-aix or rs6000 |
| 3976 | |
| 3977 | SGI Irix-4.x mips-sgi-irix4 or iris4 |
| 3978 | |
| 3979 | * New malloc package |
| 3980 | |
| 3981 | GDB now uses a new memory manager called mmalloc, based on gmalloc. |
| 3982 | Mmalloc is capable of handling mutiple heaps of memory. It is also |
| 3983 | capable of saving a heap to a file, and then mapping it back in later. |
| 3984 | This can be used to greatly speedup the startup of GDB by using a |
| 3985 | pre-parsed symbol table which lives in a mmalloc managed heap. For |
| 3986 | more details, please read mmalloc/mmalloc.texi. |
| 3987 | |
| 3988 | * info proc |
| 3989 | |
| 3990 | The 'info proc' command (SVR4 only) has been enhanced quite a bit. See |
| 3991 | 'help info proc' for details. |
| 3992 | |
| 3993 | * MIPS ecoff symbol table format |
| 3994 | |
| 3995 | The code that reads MIPS symbol table format is now supported on all hosts. |
| 3996 | Thanks to MIPS for releasing the sym.h and symconst.h files to make this |
| 3997 | possible. |
| 3998 | |
| 3999 | * File name changes for MS-DOS |
| 4000 | |
| 4001 | Many files in the config directories have been renamed to make it easier to |
| 4002 | support GDB on MS-DOSe systems (which have very restrictive file name |
| 4003 | conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32 |
| 4004 | environment) is close to working but has some remaining problems. Note |
| 4005 | that debugging of DOS programs is not supported, due to limitations |
| 4006 | in the ``operating system'', but it can be used to host cross-debugging. |
| 4007 | |
| 4008 | * Cross byte order fixes |
| 4009 | |
| 4010 | Many fixes have been made to support cross debugging of Sparc and MIPS |
| 4011 | targets from hosts whose byte order differs. |
| 4012 | |
| 4013 | * New -mapped and -readnow options |
| 4014 | |
| 4015 | If memory-mapped files are available on your system through the 'mmap' |
| 4016 | system call, you can use the -mapped option on the `file' or |
| 4017 | `symbol-file' commands to cause GDB to write the symbols from your |
| 4018 | program into a reusable file. If the program you are debugging is |
| 4019 | called `/path/fred', the mapped symbol file will be `./fred.syms'. |
| 4020 | Future GDB debugging sessions will notice the presence of this file, |
| 4021 | and will quickly map in symbol information from it, rather than reading |
| 4022 | the symbol table from the executable program. Using the '-mapped' |
| 4023 | option in a GDB `file' or `symbol-file' command has the same effect as |
| 4024 | starting GDB with the '-mapped' command-line option. |
| 4025 | |
| 4026 | You can cause GDB to read the entire symbol table immediately by using |
| 4027 | the '-readnow' option with any of the commands that load symbol table |
| 4028 | information (or on the GDB command line). This makes the command |
| 4029 | slower, but makes future operations faster. |
| 4030 | |
| 4031 | The -mapped and -readnow options are typically combined in order to |
| 4032 | build a `fred.syms' file that contains complete symbol information. |
| 4033 | A simple GDB invocation to do nothing but build a `.syms' file for future |
| 4034 | use is: |
| 4035 | |
| 4036 | gdb -batch -nx -mapped -readnow programname |
| 4037 | |
| 4038 | The `.syms' file is specific to the host machine on which GDB is run. |
| 4039 | It holds an exact image of GDB's internal symbol table. It cannot be |
| 4040 | shared across multiple host platforms. |
| 4041 | |
| 4042 | * longjmp() handling |
| 4043 | |
| 4044 | GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and |
| 4045 | siglongjmp() without losing control. This feature has not yet been ported to |
| 4046 | all systems. It currently works on many 386 platforms, all MIPS-based |
| 4047 | platforms (SGI, DECstation, etc), and Sun3/4. |
| 4048 | |
| 4049 | * Solaris 2.0 |
| 4050 | |
| 4051 | Preliminary work has been put in to support the new Solaris OS from Sun. At |
| 4052 | this time, it can control and debug processes, but it is not capable of |
| 4053 | reading symbols. |
| 4054 | |
| 4055 | * Bug fixes |
| 4056 | |
| 4057 | As always, many many bug fixes. The major areas were with g++, and mipsread. |
| 4058 | People using the MIPS-based platforms should experience fewer mysterious |
| 4059 | crashes and trashed symbol tables. |
| 4060 | |
| 4061 | *** Changes in GDB-4.4: |
| 4062 | |
| 4063 | * New machines supported (host and target) |
| 4064 | |
| 4065 | SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco |
| 4066 | (except core files) |
| 4067 | BSD Reno on Vax vax-dec-bsd |
| 4068 | Ultrix on Vax vax-dec-ultrix |
| 4069 | |
| 4070 | * New machines supported (target) |
| 4071 | |
| 4072 | AMD 29000 embedded, using EBMON a29k-none-none |
| 4073 | |
| 4074 | * C++ support |
| 4075 | |
| 4076 | GDB continues to improve its handling of C++. `References' work better. |
| 4077 | The demangler has also been improved, and now deals with symbols mangled as |
| 4078 | per the Annotated C++ Reference Guide. |
| 4079 | |
| 4080 | GDB also now handles `stabs' symbol information embedded in MIPS |
| 4081 | `ecoff' symbol tables. Since the ecoff format was not easily |
| 4082 | extensible to handle new languages such as C++, this appeared to be a |
| 4083 | good way to put C++ debugging info into MIPS binaries. This option |
| 4084 | will be supported in the GNU C compiler, version 2, when it is |
| 4085 | released. |
| 4086 | |
| 4087 | * New features for SVR4 |
| 4088 | |
| 4089 | GDB now handles SVR4 shared libraries, in the same fashion as SunOS |
| 4090 | shared libraries. Debugging dynamically linked programs should present |
| 4091 | only minor differences from debugging statically linked programs. |
| 4092 | |
| 4093 | The `info proc' command will print out information about any process |
| 4094 | on an SVR4 system (including the one you are debugging). At the moment, |
| 4095 | it prints the address mappings of the process. |
| 4096 | |
| 4097 | If you bring up GDB on another SVR4 system, please send mail to |
| 4098 | bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any). |
| 4099 | |
| 4100 | * Better dynamic linking support in SunOS |
| 4101 | |
| 4102 | Reading symbols from shared libraries which contain debugging symbols |
| 4103 | now works properly. However, there remain issues such as automatic |
| 4104 | skipping of `transfer vector' code during function calls, which |
| 4105 | make it harder to debug code in a shared library, than to debug the |
| 4106 | same code linked statically. |
| 4107 | |
| 4108 | * New Getopt |
| 4109 | |
| 4110 | GDB is now using the latest `getopt' routines from the FSF. This |
| 4111 | version accepts the -- prefix for options with long names. GDB will |
| 4112 | continue to accept the old forms (-option and +option) as well. |
| 4113 | Various single letter abbreviations for options have been explicity |
| 4114 | added to the option table so that they won't get overshadowed in the |
| 4115 | future by other options that begin with the same letter. |
| 4116 | |
| 4117 | * Bugs fixed |
| 4118 | |
| 4119 | The `cleanup_undefined_types' bug that many of you noticed has been squashed. |
| 4120 | Many assorted bugs have been handled. Many more remain to be handled. |
| 4121 | See the various ChangeLog files (primarily in gdb and bfd) for details. |
| 4122 | |
| 4123 | |
| 4124 | *** Changes in GDB-4.3: |
| 4125 | |
| 4126 | * New machines supported (host and target) |
| 4127 | |
| 4128 | Amiga 3000 running Amix m68k-cbm-svr4 or amix |
| 4129 | NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000 |
| 4130 | Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88 |
| 4131 | |
| 4132 | * Almost SCO Unix support |
| 4133 | |
| 4134 | We had hoped to support: |
| 4135 | SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco |
| 4136 | (except for core file support), but we discovered very late in the release |
| 4137 | that it has problems with process groups that render gdb unusable. Sorry |
| 4138 | about that. I encourage people to fix it and post the fixes. |
| 4139 | |
| 4140 | * Preliminary ELF and DWARF support |
| 4141 | |
| 4142 | GDB can read ELF object files on System V Release 4, and can handle |
| 4143 | debugging records for C, in DWARF format, in ELF files. This support |
| 4144 | is preliminary. If you bring up GDB on another SVR4 system, please |
| 4145 | send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were |
| 4146 | reqired (if any). |
| 4147 | |
| 4148 | * New Readline |
| 4149 | |
| 4150 | GDB now uses the latest `readline' library. One user-visible change |
| 4151 | is that two tabs will list possible command completions, which previously |
| 4152 | required typing M-? (meta-question mark, or ESC ?). |
| 4153 | |
| 4154 | * Bugs fixed |
| 4155 | |
| 4156 | The `stepi' bug that many of you noticed has been squashed. |
| 4157 | Many bugs in C++ have been handled. Many more remain to be handled. |
| 4158 | See the various ChangeLog files (primarily in gdb and bfd) for details. |
| 4159 | |
| 4160 | * State of the MIPS world (in case you wondered): |
| 4161 | |
| 4162 | GDB can understand the symbol tables emitted by the compilers |
| 4163 | supplied by most vendors of MIPS-based machines, including DEC. These |
| 4164 | symbol tables are in a format that essentially nobody else uses. |
| 4165 | |
| 4166 | Some versions of gcc come with an assembler post-processor called |
| 4167 | mips-tfile. This program is required if you want to do source-level |
| 4168 | debugging of gcc-compiled programs. I believe FSF does not ship |
| 4169 | mips-tfile with gcc version 1, but it will eventually come with gcc |
| 4170 | version 2. |
| 4171 | |
| 4172 | Debugging of g++ output remains a problem. g++ version 1.xx does not |
| 4173 | really support it at all. (If you're lucky, you should be able to get |
| 4174 | line numbers and stack traces to work, but no parameters or local |
| 4175 | variables.) With some work it should be possible to improve the |
| 4176 | situation somewhat. |
| 4177 | |
| 4178 | When gcc version 2 is released, you will have somewhat better luck. |
| 4179 | However, even then you will get confusing results for inheritance and |
| 4180 | methods. |
| 4181 | |
| 4182 | We will eventually provide full debugging of g++ output on |
| 4183 | DECstations. This will probably involve some kind of stabs-in-ecoff |
| 4184 | encapulation, but the details have not been worked out yet. |
| 4185 | |
| 4186 | |
| 4187 | *** Changes in GDB-4.2: |
| 4188 | |
| 4189 | * Improved configuration |
| 4190 | |
| 4191 | Only one copy of `configure' exists now, and it is not self-modifying. |
| 4192 | Porting BFD is simpler. |
| 4193 | |
| 4194 | * Stepping improved |
| 4195 | |
| 4196 | The `step' and `next' commands now only stop at the first instruction |
| 4197 | of a source line. This prevents the multiple stops that used to occur |
| 4198 | in switch statements, for-loops, etc. `Step' continues to stop if a |
| 4199 | function that has debugging information is called within the line. |
| 4200 | |
| 4201 | * Bug fixing |
| 4202 | |
| 4203 | Lots of small bugs fixed. More remain. |
| 4204 | |
| 4205 | * New host supported (not target) |
| 4206 | |
| 4207 | Intel 386 PC clone running Mach i386-none-mach |
| 4208 | |
| 4209 | |
| 4210 | *** Changes in GDB-4.1: |
| 4211 | |
| 4212 | * Multiple source language support |
| 4213 | |
| 4214 | GDB now has internal scaffolding to handle several source languages. |
| 4215 | It determines the type of each source file from its filename extension, |
| 4216 | and will switch expression parsing and number formatting to match the |
| 4217 | language of the function in the currently selected stack frame. |
| 4218 | You can also specifically set the language to be used, with |
| 4219 | `set language c' or `set language modula-2'. |
| 4220 | |
| 4221 | * GDB and Modula-2 |
| 4222 | |
| 4223 | GDB now has preliminary support for the GNU Modula-2 compiler, |
| 4224 | currently under development at the State University of New York at |
| 4225 | Buffalo. Development of both GDB and the GNU Modula-2 compiler will |
| 4226 | continue through the fall of 1991 and into 1992. |
| 4227 | |
| 4228 | Other Modula-2 compilers are currently not supported, and attempting to |
| 4229 | debug programs compiled with them will likely result in an error as the |
| 4230 | symbol table is read. Feel free to work on it, though! |
| 4231 | |
| 4232 | There are hooks in GDB for strict type checking and range checking, |
| 4233 | in the `Modula-2 philosophy', but they do not currently work. |
| 4234 | |
| 4235 | * set write on/off |
| 4236 | |
| 4237 | GDB can now write to executable and core files (e.g. patch |
| 4238 | a variable's value). You must turn this switch on, specify |
| 4239 | the file ("exec foo" or "core foo"), *then* modify it, e.g. |
| 4240 | by assigning a new value to a variable. Modifications take |
| 4241 | effect immediately. |
| 4242 | |
| 4243 | * Automatic SunOS shared library reading |
| 4244 | |
| 4245 | When you run your program, GDB automatically determines where its |
| 4246 | shared libraries (if any) have been loaded, and reads their symbols. |
| 4247 | The `share' command is no longer needed. This also works when |
| 4248 | examining core files. |
| 4249 | |
| 4250 | * set listsize |
| 4251 | |
| 4252 | You can specify the number of lines that the `list' command shows. |
| 4253 | The default is 10. |
| 4254 | |
| 4255 | * New machines supported (host and target) |
| 4256 | |
| 4257 | SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris |
| 4258 | Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news |
| 4259 | Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3 |
| 4260 | |
| 4261 | * New hosts supported (not targets) |
| 4262 | |
| 4263 | IBM RT/PC: romp-ibm-aix or rtpc |
| 4264 | |
| 4265 | * New targets supported (not hosts) |
| 4266 | |
| 4267 | AMD 29000 embedded with COFF a29k-none-coff |
| 4268 | AMD 29000 embedded with a.out a29k-none-aout |
| 4269 | Ultracomputer remote kernel debug a29k-nyu-kern |
| 4270 | |
| 4271 | * New remote interfaces |
| 4272 | |
| 4273 | AMD 29000 Adapt |
| 4274 | AMD 29000 Minimon |
| 4275 | |
| 4276 | |
| 4277 | *** Changes in GDB-4.0: |
| 4278 | |
| 4279 | * New Facilities |
| 4280 | |
| 4281 | Wide output is wrapped at good places to make the output more readable. |
| 4282 | |
| 4283 | Gdb now supports cross-debugging from a host machine of one type to a |
| 4284 | target machine of another type. Communication with the target system |
| 4285 | is over serial lines. The ``target'' command handles connecting to the |
| 4286 | remote system; the ``load'' command will download a program into the |
| 4287 | remote system. Serial stubs for the m68k and i386 are provided. Gdb |
| 4288 | also supports debugging of realtime processes running under VxWorks, |
| 4289 | using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger |
| 4290 | stub on the target system. |
| 4291 | |
| 4292 | New CPUs supported include the AMD 29000 and Intel 960. |
| 4293 | |
| 4294 | GDB now reads object files and symbol tables via a ``binary file'' |
| 4295 | library, which allows a single copy of GDB to debug programs of multiple |
| 4296 | object file types such as a.out and coff. |
| 4297 | |
| 4298 | There is now a GDB reference card in "doc/refcard.tex". (Make targets |
| 4299 | refcard.dvi and refcard.ps are available to format it). |
| 4300 | |
| 4301 | |
| 4302 | * Control-Variable user interface simplified |
| 4303 | |
| 4304 | All variables that control the operation of the debugger can be set |
| 4305 | by the ``set'' command, and displayed by the ``show'' command. |
| 4306 | |
| 4307 | For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>. |
| 4308 | ``Show prompt'' produces the response: |
| 4309 | Gdb's prompt is new-gdb=>. |
| 4310 | |
| 4311 | What follows are the NEW set commands. The command ``help set'' will |
| 4312 | print a complete list of old and new set commands. ``help set FOO'' |
| 4313 | will give a longer description of the variable FOO. ``show'' will show |
| 4314 | all of the variable descriptions and their current settings. |
| 4315 | |
| 4316 | confirm on/off: Enables warning questions for operations that are |
| 4317 | hard to recover from, e.g. rerunning the program while |
| 4318 | it is already running. Default is ON. |
| 4319 | |
| 4320 | editing on/off: Enables EMACS style command line editing |
| 4321 | of input. Previous lines can be recalled with |
| 4322 | control-P, the current line can be edited with control-B, |
| 4323 | you can search for commands with control-R, etc. |
| 4324 | Default is ON. |
| 4325 | |
| 4326 | history filename NAME: NAME is where the gdb command history |
| 4327 | will be stored. The default is .gdb_history, |
| 4328 | or the value of the environment variable |
| 4329 | GDBHISTFILE. |
| 4330 | |
| 4331 | history size N: The size, in commands, of the command history. The |
| 4332 | default is 256, or the value of the environment variable |
| 4333 | HISTSIZE. |
| 4334 | |
| 4335 | history save on/off: If this value is set to ON, the history file will |
| 4336 | be saved after exiting gdb. If set to OFF, the |
| 4337 | file will not be saved. The default is OFF. |
| 4338 | |
| 4339 | history expansion on/off: If this value is set to ON, then csh-like |
| 4340 | history expansion will be performed on |
| 4341 | command line input. The default is OFF. |
| 4342 | |
| 4343 | radix N: Sets the default radix for input and output. It can be set |
| 4344 | to 8, 10, or 16. Note that the argument to "radix" is interpreted |
| 4345 | in the current radix, so "set radix 10" is always a no-op. |
| 4346 | |
| 4347 | height N: This integer value is the number of lines on a page. Default |
| 4348 | is 24, the current `stty rows'' setting, or the ``li#'' |
| 4349 | setting from the termcap entry matching the environment |
| 4350 | variable TERM. |
| 4351 | |
| 4352 | width N: This integer value is the number of characters on a line. |
| 4353 | Default is 80, the current `stty cols'' setting, or the ``co#'' |
| 4354 | setting from the termcap entry matching the environment |
| 4355 | variable TERM. |
| 4356 | |
| 4357 | Note: ``set screensize'' is obsolete. Use ``set height'' and |
| 4358 | ``set width'' instead. |
| 4359 | |
| 4360 | print address on/off: Print memory addresses in various command displays, |
| 4361 | such as stack traces and structure values. Gdb looks |
| 4362 | more ``symbolic'' if you turn this off; it looks more |
| 4363 | ``machine level'' with it on. Default is ON. |
| 4364 | |
| 4365 | print array on/off: Prettyprint arrays. New convenient format! Default |
| 4366 | is OFF. |
| 4367 | |
| 4368 | print demangle on/off: Print C++ symbols in "source" form if on, |
| 4369 | "raw" form if off. |
| 4370 | |
| 4371 | print asm-demangle on/off: Same, for assembler level printouts |
| 4372 | like instructions. |
| 4373 | |
| 4374 | print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF. |
| 4375 | |
| 4376 | |
| 4377 | * Support for Epoch Environment. |
| 4378 | |
| 4379 | The epoch environment is a version of Emacs v18 with windowing. One |
| 4380 | new command, ``inspect'', is identical to ``print'', except that if you |
| 4381 | are running in the epoch environment, the value is printed in its own |
| 4382 | window. |
| 4383 | |
| 4384 | |
| 4385 | * Support for Shared Libraries |
| 4386 | |
| 4387 | GDB can now debug programs and core files that use SunOS shared libraries. |
| 4388 | Symbols from a shared library cannot be referenced |
| 4389 | before the shared library has been linked with the program (this |
| 4390 | happens after you type ``run'' and before the function main() is entered). |
| 4391 | At any time after this linking (including when examining core files |
| 4392 | from dynamically linked programs), gdb reads the symbols from each |
| 4393 | shared library when you type the ``sharedlibrary'' command. |
| 4394 | It can be abbreviated ``share''. |
| 4395 | |
| 4396 | sharedlibrary REGEXP: Load shared object library symbols for files |
| 4397 | matching a unix regular expression. No argument |
| 4398 | indicates to load symbols for all shared libraries. |
| 4399 | |
| 4400 | info sharedlibrary: Status of loaded shared libraries. |
| 4401 | |
| 4402 | |
| 4403 | * Watchpoints |
| 4404 | |
| 4405 | A watchpoint stops execution of a program whenever the value of an |
| 4406 | expression changes. Checking for this slows down execution |
| 4407 | tremendously whenever you are in the scope of the expression, but is |
| 4408 | quite useful for catching tough ``bit-spreader'' or pointer misuse |
| 4409 | problems. Some machines such as the 386 have hardware for doing this |
| 4410 | more quickly, and future versions of gdb will use this hardware. |
| 4411 | |
| 4412 | watch EXP: Set a watchpoint (breakpoint) for an expression. |
| 4413 | |
| 4414 | info watchpoints: Information about your watchpoints. |
| 4415 | |
| 4416 | delete N: Deletes watchpoint number N (same as breakpoints). |
| 4417 | disable N: Temporarily turns off watchpoint number N (same as breakpoints). |
| 4418 | enable N: Re-enables watchpoint number N (same as breakpoints). |
| 4419 | |
| 4420 | |
| 4421 | * C++ multiple inheritance |
| 4422 | |
| 4423 | When used with a GCC version 2 compiler, GDB supports multiple inheritance |
| 4424 | for C++ programs. |
| 4425 | |
| 4426 | * C++ exception handling |
| 4427 | |
| 4428 | Gdb now supports limited C++ exception handling. Besides the existing |
| 4429 | ability to breakpoint on an exception handler, gdb can breakpoint on |
| 4430 | the raising of an exception (before the stack is peeled back to the |
| 4431 | handler's context). |
| 4432 | |
| 4433 | catch FOO: If there is a FOO exception handler in the dynamic scope, |
| 4434 | set a breakpoint to catch exceptions which may be raised there. |
| 4435 | Multiple exceptions (``catch foo bar baz'') may be caught. |
| 4436 | |
| 4437 | info catch: Lists all exceptions which may be caught in the |
| 4438 | current stack frame. |
| 4439 | |
| 4440 | |
| 4441 | * Minor command changes |
| 4442 | |
| 4443 | The command ``call func (arg, arg, ...)'' now acts like the print |
| 4444 | command, except it does not print or save a value if the function's result |
| 4445 | is void. This is similar to dbx usage. |
| 4446 | |
| 4447 | The ``up'' and ``down'' commands now always print the frame they end up |
| 4448 | at; ``up-silently'' and `down-silently'' can be used in scripts to change |
| 4449 | frames without printing. |
| 4450 | |
| 4451 | * New directory command |
| 4452 | |
| 4453 | 'dir' now adds directories to the FRONT of the source search path. |
| 4454 | The path starts off empty. Source files that contain debug information |
| 4455 | about the directory in which they were compiled can be found even |
| 4456 | with an empty path; Sun CC and GCC include this information. If GDB can't |
| 4457 | find your source file in the current directory, type "dir .". |
| 4458 | |
| 4459 | * Configuring GDB for compilation |
| 4460 | |
| 4461 | For normal use, type ``./configure host''. See README or gdb.texinfo |
| 4462 | for more details. |
| 4463 | |
| 4464 | GDB now handles cross debugging. If you are remotely debugging between |
| 4465 | two different machines, type ``./configure host -target=targ''. |
| 4466 | Host is the machine where GDB will run; targ is the machine |
| 4467 | where the program that you are debugging will run. |