1 What has changed in GDB?
2 (Organized release by release)
4 *** Changes since GDB 6.6
6 * The GDB remote stub, gdbserver, now has lower overhead for high
7 frequency signals (e.g. SIGALRM) via the QPassSignals packet.
12 Ignore the specified signals; pass them directly to the debugged program
13 without stopping other threads or reporting them to GDB.
16 *** Changes in GDB 6.6
21 Cell Broadband Engine SPU spu-elf
23 * GDB can now be configured as a cross-debugger targeting native Windows
24 (mingw32) or Cygwin. It can communicate with a remote debugging stub
25 running on a Windows system over TCP/IP to debug Windows programs.
27 * The GDB remote stub, gdbserver, has been updated to support Windows and
28 Cygwin debugging. Both single-threaded and multi-threaded programs are
31 * The "set trust-readonly-sections" command works again. This command was
32 broken in GDB 6.3, 6.4, and 6.5.
34 * Support for GNU/Linux Thread Local Storage (TLS, per-thread variables) no
35 longer requires symbolic debug information (e.g. DWARF-2).
42 Manage a list of substitution rules that GDB uses to rewrite the name
43 of the directories where the sources are located. This can be useful
44 for instance when the sources were moved to a different location
45 between compilation and debugging.
49 Print each CLI command as it is executed. Each command is prefixed with
50 a number of `+' symbols representing the nesting depth.
51 The source command now has a `-v' option to enable the same feature.
55 The ARM Demon monitor support (RDP protocol, "target rdp").
57 Kernel Object Display, an embedded debugging feature which only worked with
58 an obsolete version of Cisco IOS.
60 The 'set download-write-size' and 'show download-write-size' commands.
65 Tell a stub about GDB client features, and request remote target features.
66 The first feature implemented is PacketSize, which allows the target to
67 specify the size of packets it can handle - to minimize the number of
68 packets required and improve performance when connected to a remote
72 Fetch an OS auxilliary vector from the remote stub. This packet is a
73 more efficient replacement for qPart:auxv:read.
75 * Removed remote packets
78 This packet has been replaced by qXfer:auxv:read. Only GDB 6.4 and 6.5
79 used it, and only gdbserver implemented it.
81 *** Changes in GDB 6.5
85 Renesas M32C/M16C m32c-elf
87 Morpho Technologies ms1 ms1-elf
91 init-if-undefined Initialize a convenience variable, but
92 only if it doesn't already have a value.
94 The following commands are presently only implemented for native GNU/Linux:
96 checkpoint Save a snapshot of the program state.
98 restart <n> Return the program state to a
99 previously saved state.
101 info checkpoints List currently saved checkpoints.
103 delete-checkpoint <n> Delete a previously saved checkpoint.
105 set|show detach-on-fork Tell gdb whether to detach from a newly
106 forked process, or to keep debugging it.
108 info forks List forks of the user program that
109 are available to be debugged.
111 fork <n> Switch to debugging one of several
112 forks of the user program that are
113 available to be debugged.
115 delete-fork <n> Delete a fork from the list of forks
116 that are available to be debugged (and
117 kill the forked process).
119 detach-fork <n> Delete a fork from the list of forks
120 that are available to be debugged (and
121 allow the process to continue).
125 Morpho Technologies ms2 ms1-elf
127 * Improved Windows host support
129 GDB now builds as a cross debugger hosted on i686-mingw32, including
130 native console support, and remote communications using either
131 network sockets or serial ports.
133 * Improved Modula-2 language support
135 GDB can now print most types in the Modula-2 syntax. This includes:
136 basic types, set types, record types, enumerated types, range types,
137 pointer types and ARRAY types. Procedure var parameters are correctly
138 printed and hexadecimal addresses and character constants are also
139 written in the Modula-2 syntax. Best results can be obtained by using
140 GNU Modula-2 together with the -gdwarf-2 command line option.
144 The ARM rdi-share module.
146 The Netware NLM debug server.
148 *** Changes in GDB 6.4
150 * New native configurations
152 OpenBSD/arm arm*-*-openbsd*
153 OpenBSD/mips64 mips64-*-openbsd*
157 Morpho Technologies ms1 ms1-elf
159 * New command line options
161 --batch-silent As for --batch, but totally silent.
162 --return-child-result The debugger will exist with the same value
163 the child (debugged) program exited with.
164 --eval-command COMMAND, -ex COMMAND
165 Execute a single GDB CLI command. This may be
166 specified multiple times and in conjunction
167 with the --command (-x) option.
169 * Deprecated commands removed
171 The following commands, that were deprecated in 2000, have been
175 set|show arm disassembly-flavor set|show arm disassembler
176 othernames set arm disassembler
177 set|show remotedebug set|show debug remote
178 set|show archdebug set|show debug arch
179 set|show eventdebug set|show debug event
182 * New BSD user-level threads support
184 It is now possible to debug programs using the user-level threads
185 library on OpenBSD and FreeBSD. Currently supported (target)
188 FreeBSD/amd64 x86_64-*-freebsd*
189 FreeBSD/i386 i386-*-freebsd*
190 OpenBSD/i386 i386-*-openbsd*
192 Note that the new kernel threads libraries introduced in FreeBSD 5.x
193 are not yet supported.
195 * New support for Matsushita MN10300 w/sim added
196 (Work in progress). mn10300-elf.
198 * REMOVED configurations and files
200 VxWorks and the XDR protocol *-*-vxworks
201 Motorola MCORE mcore-*-*
202 National Semiconductor NS32000 ns32k-*-*
204 * New "set print array-indexes" command
206 After turning this setting "on", GDB prints the index of each element
207 when displaying arrays. The default is "off" to preserve the previous
210 * VAX floating point support
212 GDB now supports the not-quite-ieee VAX F and D floating point formats.
214 * User-defined command support
216 In addition to using $arg0..$arg9 for argument passing, it is now possible
217 to use $argc to determine now many arguments have been passed. See the
218 section on user-defined commands in the user manual for more information.
220 *** Changes in GDB 6.3:
222 * New command line option
224 GDB now accepts -l followed by a number to set the timeout for remote
227 * GDB works with GCC -feliminate-dwarf2-dups
229 GDB now supports a more compact representation of DWARF-2 debug
230 information using DW_FORM_ref_addr references. These are produced
231 by GCC with the option -feliminate-dwarf2-dups and also by some
232 proprietary compilers. With GCC, you must use GCC 3.3.4 or later
233 to use -feliminate-dwarf2-dups.
235 * Internationalization
237 When supported by the host system, GDB will be built with
238 internationalization (libintl). The task of marking up the sources is
239 continued, we're looking forward to our first translation.
243 Initial support for debugging programs compiled with the GNAT
244 implementation of the Ada programming language has been integrated
245 into GDB. In this release, support is limited to expression evaluation.
247 * New native configurations
249 GNU/Linux/m32r m32r-*-linux-gnu
253 GDB's remote protocol now includes support for the 'p' packet. This
254 packet is used to fetch individual registers from a remote inferior.
256 * END-OF-LIFE registers[] compatibility module
258 GDB's internal register infrastructure has been completely rewritten.
259 The new infrastructure making possible the implementation of key new
260 features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit
263 GDB 6.3 will be the last release to include the the registers[]
264 compatibility module that allowed out-of-date configurations to
265 continue to work. This change directly impacts the following
277 Unless there is activity to revive these configurations, they will be
278 made OBSOLETE in GDB 6.4, and REMOVED from GDB 6.5.
280 * OBSOLETE configurations and files
282 Configurations that have been declared obsolete in this release have
283 been commented out. Unless there is activity to revive these
284 configurations, the next release of GDB will have their sources
294 *** Changes in GDB 6.2.1:
296 * MIPS `break main; run' gave an heuristic-fence-post warning
298 When attempting to run even a simple program, a warning about
299 heuristic-fence-post being hit would be reported. This problem has
302 * MIPS IRIX 'long double' crashed GDB
304 When examining a long double variable, GDB would get a segmentation
305 fault. The crash has been fixed (but GDB 6.2 cannot correctly examine
306 IRIX long double values).
310 A bug in the VAX stack code was causing problems with the "next"
311 command. This problem has been fixed.
313 *** Changes in GDB 6.2:
315 * Fix for ``many threads''
317 On GNU/Linux systems that use the NPTL threads library, a program
318 rapidly creating and deleting threads would confuse GDB leading to the
321 ptrace: No such process.
322 thread_db_get_info: cannot get thread info: generic error
324 This problem has been fixed.
326 * "-async" and "-noasync" options removed.
328 Support for the broken "-noasync" option has been removed (it caused
331 * New ``start'' command.
333 This command runs the program until the begining of the main procedure.
335 * New BSD Kernel Data Access Library (libkvm) interface
337 Using ``target kvm'' it is now possible to debug kernel core dumps and
338 live kernel memory images on various FreeBSD, NetBSD and OpenBSD
339 platforms. Currently supported (native-only) configurations are:
341 FreeBSD/amd64 x86_64-*-freebsd*
342 FreeBSD/i386 i?86-*-freebsd*
343 NetBSD/i386 i?86-*-netbsd*
344 NetBSD/m68k m68*-*-netbsd*
345 NetBSD/sparc sparc-*-netbsd*
346 OpenBSD/amd64 x86_64-*-openbsd*
347 OpenBSD/i386 i?86-*-openbsd*
348 OpenBSD/m68k m68*-openbsd*
349 OpenBSD/sparc sparc-*-openbsd*
351 * Signal trampoline code overhauled
353 Many generic problems with GDB's signal handling code have been fixed.
354 These include: backtraces through non-contiguous stacks; recognition
355 of sa_sigaction signal trampolines; backtrace from a NULL pointer
356 call; backtrace through a signal trampoline; step into and out of
357 signal handlers; and single-stepping in the signal trampoline.
359 Please note that kernel bugs are a limiting factor here. These
360 features have been shown to work on an s390 GNU/Linux system that
361 include a 2.6.8-rc1 kernel. Ref PR breakpoints/1702.
363 * Cygwin support for DWARF 2 added.
365 * New native configurations
367 GNU/Linux/hppa hppa*-*-linux*
368 OpenBSD/hppa hppa*-*-openbsd*
369 OpenBSD/m68k m68*-*-openbsd*
370 OpenBSD/m88k m88*-*-openbsd*
371 OpenBSD/powerpc powerpc-*-openbsd*
372 NetBSD/vax vax-*-netbsd*
373 OpenBSD/vax vax-*-openbsd*
375 * END-OF-LIFE frame compatibility module
377 GDB's internal frame infrastructure has been completely rewritten.
378 The new infrastructure making it possible to support key new features
379 including DWARF 2 Call Frame Information. To aid in the task of
380 migrating old configurations to this new infrastructure, a
381 compatibility module, that allowed old configurations to continue to
382 work, was also included.
384 GDB 6.2 will be the last release to include this frame compatibility
385 module. This change directly impacts the following configurations:
395 Unless there is activity to revive these configurations, they will be
396 made OBSOLETE in GDB 6.3, and REMOVED from GDB 6.4.
398 * REMOVED configurations and files
400 Sun 3, running SunOS 3 m68*-*-sunos3*
401 Sun 3, running SunOS 4 m68*-*-sunos4*
402 Sun 2, running SunOS 3 m68000-*-sunos3*
403 Sun 2, running SunOS 4 m68000-*-sunos4*
404 Motorola 680x0 running LynxOS m68*-*-lynxos*
405 AT&T 3b1/Unix pc m68*-att-*
406 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
407 decstation mips-dec-* mips-little-*
408 riscos mips-*-riscos* mips-*-sysv*
410 sysv mips*-*-sysv4* (IRIX 5/6 not included)
412 *** Changes in GDB 6.1.1:
414 * TUI (Text-mode User Interface) built-in (also included in GDB 6.1)
416 The TUI (Text-mode User Interface) is now built as part of a default
417 GDB configuration. It is enabled by either selecting the TUI with the
418 command line option "-i=tui" or by running the separate "gdbtui"
419 program. For more information on the TUI, see the manual "Debugging
422 * Pending breakpoint support (also included in GDB 6.1)
424 Support has been added to allow you to specify breakpoints in shared
425 libraries that have not yet been loaded. If a breakpoint location
426 cannot be found, and the "breakpoint pending" option is set to auto,
427 GDB queries you if you wish to make the breakpoint pending on a future
428 shared-library load. If and when GDB resolves the breakpoint symbol,
429 the pending breakpoint is removed as one or more regular breakpoints
432 Pending breakpoints are very useful for GCJ Java debugging.
434 * Fixed ISO-C build problems
436 The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained
437 non ISO-C code that stopped them being built using a more strict ISO-C
438 compiler (e.g., IBM's C compiler).
440 * Fixed build problem on IRIX 5
442 Due to header problems with <sys/proc.h>, the file gdb/proc-api.c
443 wasn't able to compile compile on an IRIX 5 system.
445 * Added execute permission to gdb/gdbserver/configure
447 The shell script gdb/testsuite/gdb.stabs/configure lacked execute
448 permission. This bug would cause configure to fail on a number of
449 systems (Solaris, IRIX). Ref: server/519.
451 * Fixed build problem on hpux2.0w-hp-hpux11.00 using the HP ANSI C compiler
453 Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c
454 has been updated to use constant array sizes.
456 * Fixed a panic in the DWARF Call Frame Info code on Solaris 2.7
458 GCC 3.3.2, on Solaris 2.7, includes the DW_EH_PE_funcrel encoding in
459 its generated DWARF Call Frame Info. This encoding was causing GDB to
460 panic, that panic has been fixed. Ref: gdb/1628.
462 * Fixed a problem when examining parameters in shared library code.
464 When examining parameters in optimized shared library code generated
465 by a mainline GCC, GDB would incorrectly report ``Variable "..." is
466 not available''. GDB now correctly displays the variable's value.
468 *** Changes in GDB 6.1:
470 * Removed --with-mmalloc
472 Support for the mmalloc memory manager has been removed, as it
473 conflicted with the internal gdb byte cache.
475 * Changes in AMD64 configurations
477 The AMD64 target now includes the %cs and %ss registers. As a result
478 the AMD64 remote protocol has changed; this affects the floating-point
479 and SSE registers. If you rely on those registers for your debugging,
480 you should upgrade gdbserver on the remote side.
482 * Revised SPARC target
484 The SPARC target has been completely revised, incorporating the
485 FreeBSD/sparc64 support that was added for GDB 6.0. As a result
486 support for LynxOS and SunOS 4 has been dropped. Calling functions
487 from within GDB on operating systems with a non-executable stack
488 (Solaris, OpenBSD) now works.
492 GDB has a new C++ demangler which does a better job on the mangled
493 names generated by current versions of g++. It also runs faster, so
494 with this and other changes gdb should now start faster on large C++
497 * DWARF 2 Location Expressions
499 GDB support for location expressions has been extended to support function
500 arguments and frame bases. Older versions of GDB could crash when they
503 * C++ nested types and namespaces
505 GDB's support for nested types and namespaces in C++ has been
506 improved, especially if you use the DWARF 2 debugging format. (This
507 is the default for recent versions of GCC on most platforms.)
508 Specifically, if you have a class "Inner" defined within a class or
509 namespace "Outer", then GDB realizes that the class's name is
510 "Outer::Inner", not simply "Inner". This should greatly reduce the
511 frequency of complaints about not finding RTTI symbols. In addition,
512 if you are stopped at inside of a function defined within a namespace,
513 GDB modifies its name lookup accordingly.
515 * New native configurations
517 NetBSD/amd64 x86_64-*-netbsd*
518 OpenBSD/amd64 x86_64-*-openbsd*
519 OpenBSD/alpha alpha*-*-openbsd*
520 OpenBSD/sparc sparc-*-openbsd*
521 OpenBSD/sparc64 sparc64-*-openbsd*
523 * New debugging protocols
525 M32R with SDI protocol m32r-*-elf*
527 * "set prompt-escape-char" command deleted.
529 The command "set prompt-escape-char" has been deleted. This command,
530 and its very obscure effet on GDB's prompt, was never documented,
531 tested, nor mentioned in the NEWS file.
533 * OBSOLETE configurations and files
535 Configurations that have been declared obsolete in this release have
536 been commented out. Unless there is activity to revive these
537 configurations, the next release of GDB will have their sources
540 Sun 3, running SunOS 3 m68*-*-sunos3*
541 Sun 3, running SunOS 4 m68*-*-sunos4*
542 Sun 2, running SunOS 3 m68000-*-sunos3*
543 Sun 2, running SunOS 4 m68000-*-sunos4*
544 Motorola 680x0 running LynxOS m68*-*-lynxos*
545 AT&T 3b1/Unix pc m68*-att-*
546 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
547 decstation mips-dec-* mips-little-*
548 riscos mips-*-riscos* mips-*-sysv*
550 sysv mips*-*-sysv4* (IRIX 5/6 not included)
552 * REMOVED configurations and files
554 SGI Irix-4.x mips-sgi-irix4 or iris4
555 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
556 Z8000 simulator z8k-zilog-none or z8ksim
557 Matsushita MN10200 w/simulator mn10200-*-*
558 H8/500 simulator h8500-hitachi-hms or h8500hms
559 HP/PA running BSD hppa*-*-bsd*
560 HP/PA running OSF/1 hppa*-*-osf*
561 HP/PA Pro target hppa*-*-pro*
562 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
563 386BSD i[3456]86-*-bsd*
564 Sequent family i[3456]86-sequent-sysv4*
565 i[3456]86-sequent-sysv*
566 i[3456]86-sequent-bsd*
567 SPARC running LynxOS sparc-*-lynxos*
568 SPARC running SunOS 4 sparc-*-sunos4*
569 Tsqware Sparclet sparclet-*-*
570 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
572 *** Changes in GDB 6.0:
576 Support for debugging the Objective-C programming language has been
579 * New backtrace mechanism (includes DWARF 2 Call Frame Information).
581 DWARF 2's Call Frame Information makes available compiler generated
582 information that more exactly describes the program's run-time stack.
583 By using this information, GDB is able to provide more robust stack
586 The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets
587 have been updated to use a new backtrace mechanism which includes
592 GDB's remote protocol has been extended to include support for hosted
593 file I/O (where the remote target uses GDB's file system). See GDB's
594 remote protocol documentation for details.
596 * All targets using the new architecture framework.
598 All of GDB's targets have been updated to use the new internal
599 architecture framework. The way is now open for future GDB releases
600 to include cross-architecture native debugging support (i386 on amd64,
603 * GNU/Linux's Thread Local Storage (TLS)
605 GDB now includes support for for the GNU/Linux implementation of
606 per-thread variables.
608 * GNU/Linux's Native POSIX Thread Library (NPTL)
610 GDB's thread code has been updated to work with either the new
611 GNU/Linux NPTL thread library or the older "LinuxThreads" library.
613 * Separate debug info.
615 GDB, in conjunction with BINUTILS, now supports a mechanism for
616 automatically loading debug information from a separate file. Instead
617 of shipping full debug and non-debug versions of system libraries,
618 system integrators can now instead ship just the stripped libraries
619 and optional debug files.
621 * DWARF 2 Location Expressions
623 DWARF 2 Location Expressions allow the compiler to more completely
624 describe the location of variables (even in optimized code) to the
627 GDB now includes preliminary support for location expressions (support
628 for DW_OP_piece is still missing).
632 A number of long standing bugs that caused GDB to die while starting a
633 Java application have been fixed. GDB's Java support is now
634 considered "useable".
636 * GNU/Linux support for fork, vfork, and exec.
638 The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode"
639 commands are now implemented for GNU/Linux. They require a 2.5.x or later
642 * GDB supports logging output to a file
644 There are two new commands, "set logging" and "show logging", which can be
645 used to capture GDB's output to a file.
647 * The meaning of "detach" has changed for gdbserver
649 The "detach" command will now resume the application, as documented. To
650 disconnect from gdbserver and leave it stopped, use the new "disconnect"
653 * d10v, m68hc11 `regs' command deprecated
655 The `info registers' command has been updated so that it displays the
656 registers using a format identical to the old `regs' command.
660 A new command, "maint set profile on/off", has been added. This command can
661 be used to enable or disable profiling while running GDB, to profile a
662 session or a set of commands. In addition there is a new configure switch,
663 "--enable-profiling", which will cause GDB to be compiled with profiling
664 data, for more informative profiling results.
666 * Default MI syntax changed to "mi2".
668 The default MI (machine interface) syntax, enabled by the command line
669 option "-i=mi", has been changed to "mi2". The previous MI syntax,
670 "mi1", can be enabled by specifying the option "-i=mi1".
672 Support for the original "mi0" syntax (included in GDB 5.0) has been
675 Fix for gdb/192: removed extraneous space when displaying frame level.
676 Fix for gdb/672: update changelist is now output in mi list format.
677 Fix for gdb/702: a -var-assign that updates the value now shows up
678 in a subsequent -var-update.
680 * New native configurations.
682 FreeBSD/amd64 x86_64-*-freebsd*
684 * Multi-arched targets.
686 HP/PA HPUX11 hppa*-*-hpux*
687 Renesas M32R/D w/simulator m32r-*-elf*
689 * OBSOLETE configurations and files
691 Configurations that have been declared obsolete in this release have
692 been commented out. Unless there is activity to revive these
693 configurations, the next release of GDB will have their sources
696 Z8000 simulator z8k-zilog-none or z8ksim
697 Matsushita MN10200 w/simulator mn10200-*-*
698 H8/500 simulator h8500-hitachi-hms or h8500hms
699 HP/PA running BSD hppa*-*-bsd*
700 HP/PA running OSF/1 hppa*-*-osf*
701 HP/PA Pro target hppa*-*-pro*
702 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
703 Sequent family i[3456]86-sequent-sysv4*
704 i[3456]86-sequent-sysv*
705 i[3456]86-sequent-bsd*
706 Tsqware Sparclet sparclet-*-*
707 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
709 * REMOVED configurations and files
712 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
713 IBM AIX PS/2 i[3456]86-*-aix
714 i386 running Mach 3.0 i[3456]86-*-mach3*
715 i386 running Mach i[3456]86-*-mach*
716 i386 running OSF/1 i[3456]86-*osf1mk*
717 HP/Apollo 68k Family m68*-apollo*-sysv*,
719 m68*-hp-bsd*, m68*-hp-hpux*
720 Argonaut Risc Chip (ARC) arc-*-*
721 Mitsubishi D30V d30v-*-*
722 Fujitsu FR30 fr30-*-elf*
723 OS/9000 i[34]86-*-os9k
724 I960 with MON960 i960-*-coff
726 * MIPS $fp behavior changed
728 The convenience variable $fp, for the MIPS, now consistently returns
729 the address of the current frame's base. Previously, depending on the
730 context, $fp could refer to either $sp or the current frame's base
731 address. See ``8.10 Registers'' in the manual ``Debugging with GDB:
732 The GNU Source-Level Debugger''.
734 *** Changes in GDB 5.3:
736 * GNU/Linux shared library multi-threaded performance improved.
738 When debugging a multi-threaded application on GNU/Linux, GDB now uses
739 `/proc', in preference to `ptrace' for memory reads. This may result
740 in an improvement in the start-up time of multi-threaded, shared
741 library applications when run under GDB. One GDB user writes: ``loads
742 shared libs like mad''.
744 * ``gdbserver'' now supports multi-threaded applications on some targets
746 Support for debugging multi-threaded applications which use
747 the GNU/Linux LinuxThreads package has been added for
748 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
749 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
751 * GDB now supports C/C++ preprocessor macros.
753 GDB now expands preprocessor macro invocations in C/C++ expressions,
754 and provides various commands for showing macro definitions and how
757 The new command `macro expand EXPRESSION' expands any macro
758 invocations in expression, and shows the result.
760 The new command `show macro MACRO-NAME' shows the definition of the
761 macro named MACRO-NAME, and where it was defined.
763 Most compilers don't include information about macros in the debugging
764 information by default. In GCC 3.1, for example, you need to compile
765 your program with the options `-gdwarf-2 -g3'. If the macro
766 information is present in the executable, GDB will read it.
768 * Multi-arched targets.
770 DEC Alpha (partial) alpha*-*-*
771 DEC VAX (partial) vax-*-*
773 National Semiconductor NS32000 (partial) ns32k-*-*
774 Motorola 68000 (partial) m68k-*-*
775 Motorola MCORE mcore-*-*
779 Fujitsu FRV architecture added by Red Hat frv*-*-*
782 * New native configurations
784 Alpha NetBSD alpha*-*-netbsd*
785 SH NetBSD sh*-*-netbsdelf*
786 MIPS NetBSD mips*-*-netbsd*
787 UltraSPARC NetBSD sparc64-*-netbsd*
789 * OBSOLETE configurations and files
791 Configurations that have been declared obsolete in this release have
792 been commented out. Unless there is activity to revive these
793 configurations, the next release of GDB will have their sources
796 Mitsubishi D30V d30v-*-*
797 OS/9000 i[34]86-*-os9k
798 IBM AIX PS/2 i[3456]86-*-aix
799 Fujitsu FR30 fr30-*-elf*
800 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
801 Argonaut Risc Chip (ARC) arc-*-*
802 i386 running Mach 3.0 i[3456]86-*-mach3*
803 i386 running Mach i[3456]86-*-mach*
804 i386 running OSF/1 i[3456]86-*osf1mk*
805 HP/Apollo 68k Family m68*-apollo*-sysv*,
807 m68*-hp-bsd*, m68*-hp-hpux*
808 I960 with MON960 i960-*-coff
812 CHILL, a Pascal like language used by telecommunications companies.
814 * REMOVED configurations and files
816 AMD 29k family via UDI a29k-amd-udi, udi29k
817 A29K VxWorks a29k-*-vxworks
818 AMD 29000 embedded, using EBMON a29k-none-none
819 AMD 29000 embedded with COFF a29k-none-coff
820 AMD 29000 embedded with a.out a29k-none-aout
822 testsuite/gdb.hp/gdb.threads-hp/ directory
824 * New command "set max-user-call-depth <nnn>"
826 This command allows the user to limit the call depth of user-defined
827 commands. The default is 1024.
829 * Changes in FreeBSD/i386 native debugging.
831 Support for the "generate-core-file" has been added.
833 * New commands "dump", "append", and "restore".
835 These commands allow data to be copied from target memory
836 to a bfd-format or binary file (dump and append), and back
837 from a file into memory (restore).
839 * Improved "next/step" support on multi-processor Alpha Tru64.
841 The previous single-step mechanism could cause unpredictable problems,
842 including the random appearance of SIGSEGV or SIGTRAP signals. The use
843 of a software single-step mechanism prevents this.
845 *** Changes in GDB 5.2.1:
853 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
854 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
855 Fix, by Joel Brobecker imported from mainline.
857 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
858 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
859 Fix, by Fred Fish, imported from mainline.
861 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
862 Surprisingly enough, it works now.
863 By Michal Ludvig, imported from mainline.
865 i386 hardware watchpoint support:
866 avoid misses on second run for some targets.
867 By Pierre Muller, imported from mainline.
869 *** Changes in GDB 5.2:
871 * New command "set trust-readonly-sections on[off]".
873 This command is a hint that tells gdb that read-only sections
874 really are read-only (ie. that their contents will not change).
875 In this mode, gdb will go to the object file rather than the
876 target to read memory from read-only sections (such as ".text").
877 This can be a significant performance improvement on some
878 (notably embedded) targets.
880 * New command "generate-core-file" (or "gcore").
882 This new gdb command allows the user to drop a core file of the child
883 process state at any time. So far it's been implemented only for
884 GNU/Linux and Solaris, but should be relatively easily ported to other
885 hosts. Argument is core file name (defaults to core.<pid>).
887 * New command line option
889 GDB now accepts --pid or -p followed by a process id.
891 * Change in command line behavior -- corefiles vs. process ids.
893 There is a subtle behavior in the way in which GDB handles
894 command line arguments. The first non-flag argument is always
895 a program to debug, but the second non-flag argument may either
896 be a corefile or a process id. Previously, GDB would attempt to
897 open the second argument as a corefile, and if that failed, would
898 issue a superfluous error message and then attempt to attach it as
899 a process. Now, if the second argument begins with a non-digit,
900 it will be treated as a corefile. If it begins with a digit,
901 GDB will attempt to attach it as a process, and if no such process
902 is found, will then attempt to open it as a corefile.
904 * Changes in ARM configurations.
906 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
907 configuration is fully multi-arch.
909 * New native configurations
911 ARM NetBSD arm*-*-netbsd*
912 x86 OpenBSD i[3456]86-*-openbsd*
913 AMD x86-64 running GNU/Linux x86_64-*-linux-*
914 Sparc64 running FreeBSD sparc64-*-freebsd*
918 Sanyo XStormy16 xstormy16-elf
920 * OBSOLETE configurations and files
922 Configurations that have been declared obsolete in this release have
923 been commented out. Unless there is activity to revive these
924 configurations, the next release of GDB will have their sources
927 AMD 29k family via UDI a29k-amd-udi, udi29k
928 A29K VxWorks a29k-*-vxworks
929 AMD 29000 embedded, using EBMON a29k-none-none
930 AMD 29000 embedded with COFF a29k-none-coff
931 AMD 29000 embedded with a.out a29k-none-aout
933 testsuite/gdb.hp/gdb.threads-hp/ directory
935 * REMOVED configurations and files
937 TI TMS320C80 tic80-*-*
939 PowerPC Solaris powerpcle-*-solaris*
940 PowerPC Windows NT powerpcle-*-cygwin32
941 PowerPC Netware powerpc-*-netware*
942 Harris/CXUX m88k m88*-harris-cxux*
943 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
944 ns32k-utek-sysv* ns32k-utek-*
945 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
946 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
947 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
948 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
949 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
951 * Changes to command line processing
953 The new `--args' feature can be used to specify command-line arguments
954 for the inferior from gdb's command line.
956 * Changes to key bindings
958 There is a new `operate-and-get-next' function bound to `C-o'.
960 *** Changes in GDB 5.1.1
962 Fix compile problem on DJGPP.
964 Fix a problem with floating-point registers on the i386 being
967 Fix to stop GDB crashing on .debug_str debug info.
969 Numerous documentation fixes.
971 Numerous testsuite fixes.
973 *** Changes in GDB 5.1:
975 * New native configurations
977 Alpha FreeBSD alpha*-*-freebsd*
978 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
979 MIPS GNU/Linux mips*-*-linux*
980 MIPS SGI Irix 6.x mips*-sgi-irix6*
982 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
986 Motorola 68HC11 and 68HC12 m68hc11-elf
988 UltraSparc running GNU/Linux sparc64-*-linux*
990 * OBSOLETE configurations and files
992 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
993 Harris/CXUX m88k m88*-harris-cxux*
994 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
995 ns32k-utek-sysv* ns32k-utek-*
996 TI TMS320C80 tic80-*-*
998 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
999 PowerPC Solaris powerpcle-*-solaris*
1000 PowerPC Windows NT powerpcle-*-cygwin32
1001 PowerPC Netware powerpc-*-netware*
1002 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
1003 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
1004 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
1005 Apple Macintosh (MPW) host N/A
1007 stuff.c (Program to stuff files into a specially prepared space in kdb)
1008 kdb-start.c (Main loop for the standalone kernel debugger)
1010 Configurations that have been declared obsolete in this release have
1011 been commented out. Unless there is activity to revive these
1012 configurations, the next release of GDB will have their sources
1013 permanently REMOVED.
1015 * REMOVED configurations and files
1017 Altos 3068 m68*-altos-*
1018 Convex c1-*-*, c2-*-*
1020 ARM RISCix arm-*-* (as host)
1024 * GDB has been converted to ISO C.
1026 GDB's source code has been converted to ISO C. In particular, the
1027 sources are fully protoized, and rely on standard headers being
1032 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
1034 * The MI enabled by default.
1036 The new machine oriented interface (MI) introduced in GDB 5.0 has been
1037 revised and enabled by default. Packages which use GDB as a debugging
1038 engine behind a UI or another front end are encouraged to switch to
1039 using the GDB/MI interface, instead of the old annotations interface
1040 which is now deprecated.
1042 * Support for debugging Pascal programs.
1044 GDB now includes support for debugging Pascal programs. The following
1045 main features are supported:
1047 - Pascal-specific data types such as sets;
1049 - automatic recognition of Pascal sources based on file-name
1052 - Pascal-style display of data types, variables, and functions;
1054 - a Pascal expression parser.
1056 However, some important features are not yet supported.
1058 - Pascal string operations are not supported at all;
1060 - there are some problems with boolean types;
1062 - Pascal type hexadecimal constants are not supported
1063 because they conflict with the internal variables format;
1065 - support for Pascal objects and classes is not full yet;
1067 - unlike Pascal, GDB is case-sensitive for symbol names.
1069 * Changes in completion.
1071 Commands such as `shell', `run' and `set args', which pass arguments
1072 to inferior programs, now complete on file names, similar to what
1073 users expect at the shell prompt.
1075 Commands which accept locations, such as `disassemble', `print',
1076 `breakpoint', `until', etc. now complete on filenames as well as
1077 program symbols. Thus, if you type "break foob TAB", and the source
1078 files linked into the programs include `foobar.c', that file name will
1079 be one of the candidates for completion. However, file names are not
1080 considered for completion after you typed a colon that delimits a file
1081 name from a name of a function in that file, as in "break foo.c:bar".
1083 `set demangle-style' completes on available demangling styles.
1085 * New platform-independent commands:
1087 It is now possible to define a post-hook for a command as well as a
1088 hook that runs before the command. For more details, see the
1089 documentation of `hookpost' in the GDB manual.
1091 * Changes in GNU/Linux native debugging.
1093 Support for debugging multi-threaded programs has been completely
1094 revised for all platforms except m68k and sparc. You can now debug as
1095 many threads as your system allows you to have.
1097 Attach/detach is supported for multi-threaded programs.
1099 Support for SSE registers was added for x86. This doesn't work for
1100 multi-threaded programs though.
1102 * Changes in MIPS configurations.
1104 Multi-arch support is enabled for all MIPS configurations.
1106 GDB can now be built as native debugger on SGI Irix 6.x systems for
1107 debugging n32 executables. (Debugging 64-bit executables is not yet
1110 * Unified support for hardware watchpoints in all x86 configurations.
1112 Most (if not all) native x86 configurations support hardware-assisted
1113 breakpoints and watchpoints in a unified manner. This support
1114 implements debug register sharing between watchpoints, which allows to
1115 put a virtually infinite number of watchpoints on the same address,
1116 and also supports watching regions up to 16 bytes with several debug
1119 The new maintenance command `maintenance show-debug-regs' toggles
1120 debugging print-outs in functions that insert, remove, and test
1121 watchpoints and hardware breakpoints.
1123 * Changes in the DJGPP native configuration.
1125 New command ``info dos sysinfo'' displays assorted information about
1126 the CPU, OS, memory, and DPMI server.
1128 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
1129 display information about segment descriptors stored in GDT, LDT, and
1132 New commands ``info dos pde'' and ``info dos pte'' display entries
1133 from Page Directory and Page Tables (for now works with CWSDPMI only).
1134 New command ``info dos address-pte'' displays the Page Table entry for
1135 a given linear address.
1137 GDB can now pass command lines longer than 126 characters to the
1138 program being debugged (requires an update to the libdbg.a library
1139 which is part of the DJGPP development kit).
1141 DWARF2 debug info is now supported.
1143 It is now possible to `step' and `next' through calls to `longjmp'.
1145 * Changes in documentation.
1147 All GDB documentation was converted to GFDL, the GNU Free
1148 Documentation License.
1150 Tracepoints-related commands are now fully documented in the GDB
1153 TUI, the Text-mode User Interface, is now documented in the manual.
1155 Tracepoints-related commands are now fully documented in the GDB
1158 The "GDB Internals" manual now has an index. It also includes
1159 documentation of `ui_out' functions, GDB coding standards, x86
1160 hardware watchpoints, and memory region attributes.
1162 * GDB's version number moved to ``version.in''
1164 The Makefile variable VERSION has been replaced by the file
1165 ``version.in''. People creating GDB distributions should update the
1166 contents of this file.
1170 GUD support is now a standard part of the EMACS distribution.
1172 *** Changes in GDB 5.0:
1174 * Improved support for debugging FP programs on x86 targets
1176 Unified and much-improved support for debugging floating-point
1177 programs on all x86 targets. In particular, ``info float'' now
1178 displays the FP registers in the same format on all x86 targets, with
1179 greater level of detail.
1181 * Improvements and bugfixes in hardware-assisted watchpoints
1183 It is now possible to watch array elements, struct members, and
1184 bitfields with hardware-assisted watchpoints. Data-read watchpoints
1185 on x86 targets no longer erroneously trigger when the address is
1188 * Improvements in the native DJGPP version of GDB
1190 The distribution now includes all the scripts and auxiliary files
1191 necessary to build the native DJGPP version on MS-DOS/MS-Windows
1192 machines ``out of the box''.
1194 The DJGPP version can now debug programs that use signals. It is
1195 possible to catch signals that happened in the debuggee, deliver
1196 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
1197 would kill the program being debugged.) Programs that hook hardware
1198 interrupts (keyboard, timer, etc.) can also be debugged.
1200 It is now possible to debug DJGPP programs that redirect their
1201 standard handles or switch them to raw (as opposed to cooked) mode, or
1202 even close them. The command ``run < foo > bar'' works as expected,
1203 and ``info terminal'' reports useful information about the debuggee's
1204 terminal, including raw/cooked mode, redirection, etc.
1206 The DJGPP version now uses termios functions for console I/O, which
1207 enables debugging graphics programs. Interrupting GDB with Ctrl-C
1210 DOS-style file names with drive letters are now fully supported by
1213 It is now possible to debug DJGPP programs that switch their working
1214 directory. It is also possible to rerun the debuggee any number of
1215 times without restarting GDB; thus, you can use the same setup,
1216 breakpoints, etc. for many debugging sessions.
1218 * New native configurations
1220 ARM GNU/Linux arm*-*-linux*
1221 PowerPC GNU/Linux powerpc-*-linux*
1225 Motorola MCore mcore-*-*
1226 x86 VxWorks i[3456]86-*-vxworks*
1227 PowerPC VxWorks powerpc-*-vxworks*
1228 TI TMS320C80 tic80-*-*
1230 * OBSOLETE configurations
1232 Altos 3068 m68*-altos-*
1233 Convex c1-*-*, c2-*-*
1235 ARM RISCix arm-*-* (as host)
1238 Configurations that have been declared obsolete will be commented out,
1239 but the code will be left in place. If there is no activity to revive
1240 these configurations before the next release of GDB, the sources will
1241 be permanently REMOVED.
1243 * Gould support removed
1245 Support for the Gould PowerNode and NP1 has been removed.
1247 * New features for SVR4
1249 On SVR4 native platforms (such as Solaris), if you attach to a process
1250 without first loading a symbol file, GDB will now attempt to locate and
1251 load symbols from the running process's executable file.
1253 * Many C++ enhancements
1255 C++ support has been greatly improved. Overload resolution now works properly
1256 in almost all cases. RTTI support is on the way.
1258 * Remote targets can connect to a sub-program
1260 A popen(3) style serial-device has been added. This device starts a
1261 sub-process (such as a stand-alone simulator) and then communicates
1262 with that. The sub-program to run is specified using the syntax
1263 ``|<program> <args>'' vis:
1265 (gdb) set remotedebug 1
1266 (gdb) target extended-remote |mn10300-elf-sim program-args
1268 * MIPS 64 remote protocol
1270 A long standing bug in the mips64 remote protocol where by GDB
1271 expected certain 32 bit registers (ex SR) to be transfered as 32
1272 instead of 64 bits has been fixed.
1274 The command ``set remote-mips64-transfers-32bit-regs on'' has been
1275 added to provide backward compatibility with older versions of GDB.
1277 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
1279 The command ``set remotebinarydownload'' command has been replaced by
1280 ``set remote X-packet''. Other commands in ``set remote'' family
1281 include ``set remote P-packet''.
1283 * Breakpoint commands accept ranges.
1285 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
1286 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
1287 ``tracepoint passcount'' also accepts a range of tracepoints.
1289 * ``apropos'' command added.
1291 The ``apropos'' command searches through command names and
1292 documentation strings, printing out matches, making it much easier to
1293 try to find a command that does what you are looking for.
1297 A new machine oriented interface (MI) has been added to GDB. This
1298 interface is designed for debug environments running GDB as a separate
1299 process. This is part of the long term libGDB project. See the
1300 "GDB/MI" chapter of the GDB manual for further information. It can be
1301 enabled by configuring with:
1303 .../configure --enable-gdbmi
1305 *** Changes in GDB-4.18:
1307 * New native configurations
1309 HP-UX 10.20 hppa*-*-hpux10.20
1310 HP-UX 11.x hppa*-*-hpux11.0*
1311 M68K GNU/Linux m68*-*-linux*
1315 Fujitsu FR30 fr30-*-elf*
1316 Intel StrongARM strongarm-*-*
1317 Mitsubishi D30V d30v-*-*
1319 * OBSOLETE configurations
1321 Gould PowerNode, NP1 np1-*-*, pn-*-*
1323 Configurations that have been declared obsolete will be commented out,
1324 but the code will be left in place. If there is no activity to revive
1325 these configurations before the next release of GDB, the sources will
1326 be permanently REMOVED.
1330 As a compatibility experiment, GDB's source files buildsym.h and
1331 buildsym.c have been converted to pure standard C, no longer
1332 containing any K&R compatibility code. We believe that all systems in
1333 use today either come with a standard C compiler, or have a GCC port
1334 available. If this is not true, please report the affected
1335 configuration to bug-gdb@gnu.org immediately. See the README file for
1336 information about getting a standard C compiler if you don't have one
1341 GDB now uses readline 2.2.
1343 * set extension-language
1345 You can now control the mapping between filename extensions and source
1346 languages by using the `set extension-language' command. For instance,
1347 you can ask GDB to treat .c files as C++ by saying
1348 set extension-language .c c++
1349 The command `info extensions' lists all of the recognized extensions
1350 and their associated languages.
1352 * Setting processor type for PowerPC and RS/6000
1354 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
1355 you can use the `set processor' command to specify what variant of the
1356 PowerPC family you are debugging. The command
1360 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
1361 following PowerPC and RS6000 variants:
1363 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
1364 rs6000 IBM RS6000 ("POWER") architecture, user-level view
1366 403GC IBM PowerPC 403GC
1367 505 Motorola PowerPC 505
1368 860 Motorola PowerPC 860 or 850
1369 601 Motorola PowerPC 601
1370 602 Motorola PowerPC 602
1371 603 Motorola/IBM PowerPC 603 or 603e
1372 604 Motorola PowerPC 604 or 604e
1373 750 Motorola/IBM PowerPC 750 or 750
1375 At the moment, this command just tells GDB what to name the
1376 special-purpose processor registers. Since almost all the affected
1377 registers are inaccessible to user-level programs, this command is
1378 only useful for remote debugging in its present form.
1382 Thanks to a major code donation from Hewlett-Packard, GDB now has much
1383 more extensive support for HP-UX. Added features include shared
1384 library support, kernel threads and hardware watchpoints for 11.00,
1385 support for HP's ANSI C and C++ compilers, and a compatibility mode
1386 for xdb and dbx commands.
1390 HP's donation includes the new concept of catchpoints, which is a
1391 generalization of the old catch command. On HP-UX, it is now possible
1392 to catch exec, fork, and vfork, as well as library loading.
1394 This means that the existing catch command has changed; its first
1395 argument now specifies the type of catch to be set up. See the
1396 output of "help catch" for a list of catchpoint types.
1398 * Debugging across forks
1400 On HP-UX, you can choose which process to debug when a fork() happens
1405 HP has donated a curses-based terminal user interface (TUI). To get
1406 it, build with --enable-tui. Although this can be enabled for any
1407 configuration, at present it only works for native HP debugging.
1409 * GDB remote protocol additions
1411 A new protocol packet 'X' that writes binary data is now available.
1412 Default behavior is to try 'X', then drop back to 'M' if the stub
1413 fails to respond. The settable variable `remotebinarydownload'
1414 allows explicit control over the use of 'X'.
1416 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
1417 full 64-bit address. The command
1419 set remoteaddresssize 32
1421 can be used to revert to the old behaviour. For existing remote stubs
1422 the change should not be noticed, as the additional address information
1425 In order to assist in debugging stubs, you may use the maintenance
1426 command `packet' to send any text string to the stub. For instance,
1428 maint packet heythere
1430 sends the packet "$heythere#<checksum>". Note that it is very easy to
1431 disrupt a debugging session by sending the wrong packet at the wrong
1434 The compare-sections command allows you to compare section data on the
1435 target to what is in the executable file without uploading or
1436 downloading, by comparing CRC checksums.
1438 * Tracing can collect general expressions
1440 You may now collect general expressions at tracepoints. This requires
1441 further additions to the target-side stub; see tracepoint.c and
1442 doc/agentexpr.texi for further details.
1444 * mask-address variable for Mips
1446 For Mips targets, you may control the zeroing of the upper 32 bits of
1447 a 64-bit address by entering `set mask-address on'. This is mainly
1448 of interest to users of embedded R4xxx and R5xxx processors.
1450 * Higher serial baud rates
1452 GDB's serial code now allows you to specify baud rates 57600, 115200,
1453 230400, and 460800 baud. (Note that your host system may not be able
1454 to achieve all of these rates.)
1458 The i960 configuration now includes an initial implementation of a
1459 builtin simulator, contributed by Jim Wilson.
1462 *** Changes in GDB-4.17:
1464 * New native configurations
1466 Alpha GNU/Linux alpha*-*-linux*
1467 Unixware 2.x i[3456]86-unixware2*
1468 Irix 6.x mips*-sgi-irix6*
1469 PowerPC GNU/Linux powerpc-*-linux*
1470 PowerPC Solaris powerpcle-*-solaris*
1471 Sparc GNU/Linux sparc-*-linux*
1472 Motorola sysV68 R3V7.1 m68k-motorola-sysv
1476 Argonaut Risc Chip (ARC) arc-*-*
1477 Hitachi H8/300S h8300*-*-*
1478 Matsushita MN10200 w/simulator mn10200-*-*
1479 Matsushita MN10300 w/simulator mn10300-*-*
1480 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
1481 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
1482 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
1483 Mitsubishi D10V w/simulator d10v-*-*
1484 Mitsubishi M32R/D w/simulator m32r-*-elf*
1485 Tsqware Sparclet sparclet-*-*
1486 NEC V850 w/simulator v850-*-*
1488 * New debugging protocols
1490 ARM with RDI protocol arm*-*-*
1491 M68K with dBUG monitor m68*-*-{aout,coff,elf}
1492 DDB and LSI variants of PMON protocol mips*-*-*
1493 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
1494 PowerPC with SDS protocol powerpc{,le}-*-eabi
1495 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
1499 All configurations can now understand and use the DWARF 2 debugging
1500 format. The choice is automatic, if the symbol file contains DWARF 2
1505 GDB now includes basic Java language support. This support is
1506 only useful with Java compilers that produce native machine code.
1508 * solib-absolute-prefix and solib-search-path
1510 For SunOS and SVR4 shared libraries, you may now set the prefix for
1511 loading absolute shared library symbol files, and the search path for
1512 locating non-absolute shared library symbol files.
1514 * Live range splitting
1516 GDB can now effectively debug code for which GCC has performed live
1517 range splitting as part of its optimization. See gdb/doc/LRS for
1518 more details on the expected format of the stabs information.
1522 GDB's support for the GNU Hurd, including thread debugging, has been
1523 updated to work with current versions of the Hurd.
1527 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
1528 instruction set. ARM GDB automatically detects when Thumb
1529 instructions are in use, and adjusts disassembly and backtracing
1534 GDB's MIPS target configurations now handle the MIP16 16-bit
1539 GDB now includes support for overlays; if an executable has been
1540 linked such that multiple sections are based at the same address, GDB
1541 will decide which section to use for symbolic info. You can choose to
1542 control the decision manually, using overlay commands, or implement
1543 additional target-side support and use "overlay load-target" to bring
1544 in the overlay mapping. Do "help overlay" for more detail.
1548 The command "info symbol <address>" displays information about
1549 the symbol at the specified address.
1553 The standard remote protocol now includes an extension that allows
1554 asynchronous collection and display of trace data. This requires
1555 extensive support in the target-side debugging stub. Tracing mode
1556 includes a new interaction mode in GDB and new commands: see the
1557 file tracepoint.c for more details.
1561 Configurations for embedded MIPS now include a simulator contributed
1562 by Cygnus Solutions. The simulator supports the instruction sets
1563 of most MIPS variants.
1567 Sparc configurations may now include the ERC32 simulator contributed
1568 by the European Space Agency. The simulator is not built into
1569 Sparc targets by default; configure with --enable-sim to include it.
1573 For target configurations that may include multiple variants of a
1574 basic architecture (such as MIPS and SH), you may now set the
1575 architecture explicitly. "set arch" sets, "info arch" lists
1576 the possible architectures.
1578 *** Changes in GDB-4.16:
1580 * New native configurations
1582 Windows 95, x86 Windows NT i[345]86-*-cygwin32
1583 M68K NetBSD m68k-*-netbsd*
1584 PowerPC AIX 4.x powerpc-*-aix*
1585 PowerPC MacOS powerpc-*-macos*
1586 PowerPC Windows NT powerpcle-*-cygwin32
1587 RS/6000 AIX 4.x rs6000-*-aix4*
1591 ARM with RDP protocol arm-*-*
1592 I960 with MON960 i960-*-coff
1593 MIPS VxWorks mips*-*-vxworks*
1594 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
1595 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
1597 Matra Sparclet sparclet-*-*
1601 The powerpc-eabi configuration now includes the PSIM simulator,
1602 contributed by Andrew Cagney, with assistance from Mike Meissner.
1603 PSIM is a very elaborate model of the PowerPC, including not only
1604 basic instruction set execution, but also details of execution unit
1605 performance and I/O hardware. See sim/ppc/README for more details.
1609 GDB now works with Solaris 2.5.
1611 * Windows 95/NT native
1613 GDB will now work as a native debugger on Windows 95 and Windows NT.
1614 To build it from source, you must use the "gnu-win32" environment,
1615 which uses a DLL to emulate enough of Unix to run the GNU tools.
1616 Further information, binaries, and sources are available at
1617 ftp.cygnus.com, under pub/gnu-win32.
1619 * dont-repeat command
1621 If a user-defined command includes the command `dont-repeat', then the
1622 command will not be repeated if the user just types return. This is
1623 useful if the command is time-consuming to run, so that accidental
1624 extra keystrokes don't run the same command many times.
1626 * Send break instead of ^C
1628 The standard remote protocol now includes an option to send a break
1629 rather than a ^C to the target in order to interrupt it. By default,
1630 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
1632 * Remote protocol timeout
1634 The standard remote protocol includes a new variable `remotetimeout'
1635 that allows you to set the number of seconds before GDB gives up trying
1636 to read from the target. The default value is 2.
1638 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
1640 By default GDB will automatically keep track of objects as they are
1641 loaded and unloaded by the dynamic linker. By using the command `set
1642 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
1643 when shared library events occur, thus allowing you to set breakpoints
1644 in shared libraries which are explicitly loaded by the inferior.
1646 Note this feature does not work on hpux8. On hpux9 you must link
1647 /usr/lib/end.o into your program. This feature should work
1648 automatically on hpux10.
1650 * Irix 5.x hardware watchpoint support
1652 Irix 5 configurations now support the use of hardware watchpoints.
1654 * Mips protocol "SYN garbage limit"
1656 When debugging a Mips target using the `target mips' protocol, you
1657 may set the number of characters that GDB will ignore by setting
1658 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
1659 every character. The default value is 1050.
1661 * Recording and replaying remote debug sessions
1663 If you set `remotelogfile' to the name of a file, gdb will write to it
1664 a recording of a remote debug session. This recording may then be
1665 replayed back to gdb using "gdbreplay". See gdbserver/README for
1666 details. This is useful when you have a problem with GDB while doing
1667 remote debugging; you can make a recording of the session and send it
1668 to someone else, who can then recreate the problem.
1670 * Speedups for remote debugging
1672 GDB includes speedups for downloading and stepping MIPS systems using
1673 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
1674 and more efficient S-record downloading.
1676 * Memory use reductions and statistics collection
1678 GDB now uses less memory and reports statistics about memory usage.
1679 Try the `maint print statistics' command, for example.
1681 *** Changes in GDB-4.15:
1683 * Psymtabs for XCOFF
1685 The symbol reader for AIX GDB now uses partial symbol tables. This
1686 can greatly improve startup time, especially for large executables.
1688 * Remote targets use caching
1690 Remote targets now use a data cache to speed up communication with the
1691 remote side. The data cache could lead to incorrect results because
1692 it doesn't know about volatile variables, thus making it impossible to
1693 debug targets which use memory mapped I/O devices. `set remotecache
1694 off' turns the the data cache off.
1696 * Remote targets may have threads
1698 The standard remote protocol now includes support for multiple threads
1699 in the target system, using new protocol commands 'H' and 'T'. See
1700 gdb/remote.c for details.
1704 If GDB is configured with `--enable-netrom', then it will include
1705 support for the NetROM ROM emulator from XLNT Designs. The NetROM
1706 acts as though it is a bank of ROM on the target board, but you can
1707 write into it over the network. GDB's support consists only of
1708 support for fast loading into the emulated ROM; to debug, you must use
1709 another protocol, such as standard remote protocol. The usual
1710 sequence is something like
1712 target nrom <netrom-hostname>
1714 target remote <netrom-hostname>:1235
1718 GDB now includes support for the Apple Macintosh, as a host only. It
1719 may be run as either an MPW tool or as a standalone application, and
1720 it can debug through the serial port. All the usual GDB commands are
1721 available, but to the target command, you must supply "serial" as the
1722 device type instead of "/dev/ttyXX". See mpw-README in the main
1723 directory for more information on how to build. The MPW configuration
1724 scripts */mpw-config.in support only a few targets, and only the
1725 mips-idt-ecoff target has been tested.
1729 GDB configuration now uses autoconf. This is not user-visible,
1730 but does simplify configuration and building.
1734 GDB now supports hpux10.
1736 *** Changes in GDB-4.14:
1738 * New native configurations
1740 x86 FreeBSD i[345]86-*-freebsd
1741 x86 NetBSD i[345]86-*-netbsd
1742 NS32k NetBSD ns32k-*-netbsd
1743 Sparc NetBSD sparc-*-netbsd
1747 A29K VxWorks a29k-*-vxworks
1748 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1749 CPU32 EST-300 emulator m68*-*-est*
1750 PowerPC ELF powerpc-*-elf
1753 * Alpha OSF/1 support for procfs
1755 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1756 possible to attach to running processes. As the mounting of the /proc
1757 filesystem is optional on the Alpha, GDB automatically determines
1758 the availability of /proc during startup. This can lead to problems
1759 if /proc is unmounted after GDB has been started.
1761 * Arguments to user-defined commands
1763 User commands may accept up to 10 arguments separated by whitespace.
1764 Arguments are accessed within the user command via $arg0..$arg9. A
1767 print $arg0 + $arg1 + $arg2
1769 To execute the command use:
1772 Defines the command "adder" which prints the sum of its three arguments.
1773 Note the arguments are text substitutions, so they may reference variables,
1774 use complex expressions, or even perform inferior function calls.
1776 * New `if' and `while' commands
1778 This makes it possible to write more sophisticated user-defined
1779 commands. Both commands take a single argument, which is the
1780 expression to evaluate, and must be followed by the commands to
1781 execute, one per line, if the expression is nonzero, the list being
1782 terminated by the word `end'. The `if' command list may include an
1783 `else' word, which causes the following commands to be executed only
1784 if the expression is zero.
1786 * Fortran source language mode
1788 GDB now includes partial support for Fortran 77. It will recognize
1789 Fortran programs and can evaluate a subset of Fortran expressions, but
1790 variables and functions may not be handled correctly. GDB will work
1791 with G77, but does not yet know much about symbols emitted by other
1794 * Better HPUX support
1796 Most debugging facilities now work on dynamic executables for HPPAs
1797 running hpux9 or later. You can attach to running dynamically linked
1798 processes, but by default the dynamic libraries will be read-only, so
1799 for instance you won't be able to put breakpoints in them. To change
1800 that behavior do the following before running the program:
1806 This will cause the libraries to be mapped private and read-write.
1807 To revert to the normal behavior, do this:
1813 You cannot set breakpoints or examine data in the library until after
1814 the library is loaded if the function/data symbols do not have
1817 GDB can now also read debug symbols produced by the HP C compiler on
1818 HPPAs (sorry, no C++, Fortran or 68k support).
1820 * Target byte order now dynamically selectable
1822 You can choose which byte order to use with a target system, via the
1823 commands "set endian big" and "set endian little", and you can see the
1824 current setting by using "show endian". You can also give the command
1825 "set endian auto", in which case GDB will use the byte order
1826 associated with the executable. Currently, only embedded MIPS
1827 configurations support dynamic selection of target byte order.
1829 * New DOS host serial code
1831 This version uses DPMI interrupts to handle buffered I/O, so you
1832 no longer need to run asynctsr when debugging boards connected to
1835 *** Changes in GDB-4.13:
1837 * New "complete" command
1839 This lists all the possible completions for the rest of the line, if it
1840 were to be given as a command itself. This is intended for use by emacs.
1842 * Trailing space optional in prompt
1844 "set prompt" no longer adds a space for you after the prompt you set. This
1845 allows you to set a prompt which ends in a space or one that does not.
1847 * Breakpoint hit counts
1849 "info break" now displays a count of the number of times the breakpoint
1850 has been hit. This is especially useful in conjunction with "ignore"; you
1851 can ignore a large number of breakpoint hits, look at the breakpoint info
1852 to see how many times the breakpoint was hit, then run again, ignoring one
1853 less than that number, and this will get you quickly to the last hit of
1856 * Ability to stop printing at NULL character
1858 "set print null-stop" will cause GDB to stop printing the characters of
1859 an array when the first NULL is encountered. This is useful when large
1860 arrays actually contain only short strings.
1862 * Shared library breakpoints
1864 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1865 breakpoints in shared libraries before the executable is run.
1867 * Hardware watchpoints
1869 There is a new hardware breakpoint for the watch command for sparclite
1870 targets. See gdb/sparclite/hw_breakpoint.note.
1872 Hardware watchpoints are also now supported under GNU/Linux.
1876 Annotations have been added. These are for use with graphical interfaces,
1877 and are still experimental. Currently only gdba.el uses these.
1879 * Improved Irix 5 support
1881 GDB now works properly with Irix 5.2.
1883 * Improved HPPA support
1885 GDB now works properly with the latest GCC and GAS.
1887 * New native configurations
1889 Sequent PTX4 i[34]86-sequent-ptx4
1890 HPPA running OSF/1 hppa*-*-osf*
1891 Atari TT running SVR4 m68*-*-sysv4*
1892 RS/6000 LynxOS rs6000-*-lynxos*
1896 OS/9000 i[34]86-*-os9k
1897 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1900 * Hitachi SH7000 and E7000-PC ICE support
1902 There is now support for communicating with the Hitachi E7000-PC ICE.
1903 This is available automatically when GDB is configured for the SH.
1907 As usual, a variety of small fixes and improvements, both generic
1908 and configuration-specific. See the ChangeLog for more detail.
1910 *** Changes in GDB-4.12:
1912 * Irix 5 is now supported
1916 GDB-4.12 on the HPPA has a number of changes which make it unable
1917 to debug the output from the currently released versions of GCC and
1918 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1919 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1920 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1923 *** Changes in GDB-4.11:
1925 * User visible changes:
1929 The "set remotedebug" option is now consistent between the mips remote
1930 target, remote targets using the gdb-specific protocol, UDI (AMD's
1931 debug protocol for the 29k) and the 88k bug monitor. It is now an
1932 integer specifying a debug level (normally 0 or 1, but 2 means more
1933 debugging info for the mips target).
1935 * DEC Alpha native support
1937 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1938 debug info, but GDB works fairly well with the DEC compiler and should
1939 work with a future GCC release. See the README file for a few
1940 Alpha-specific notes.
1942 * Preliminary thread implementation
1944 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1946 * LynxOS native and target support for 386
1948 This release has been hosted on LynxOS 2.2, and also can be configured
1949 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1952 * Improvements in C++ mangling/demangling.
1954 This release has much better g++ debugging, specifically in name
1955 mangling/demangling, virtual function calls, print virtual table,
1956 call methods, ...etc.
1958 *** Changes in GDB-4.10:
1960 * User visible changes:
1962 Remote debugging using the GDB-specific (`target remote') protocol now
1963 supports the `load' command. This is only useful if you have some
1964 other way of getting the stub to the target system, and you can put it
1965 somewhere in memory where it won't get clobbered by the download.
1967 Filename completion now works.
1969 When run under emacs mode, the "info line" command now causes the
1970 arrow to point to the line specified. Also, "info line" prints
1971 addresses in symbolic form (as well as hex).
1973 All vxworks based targets now support a user settable option, called
1974 vxworks-timeout. This option represents the number of seconds gdb
1975 should wait for responses to rpc's. You might want to use this if
1976 your vxworks target is, perhaps, a slow software simulator or happens
1977 to be on the far side of a thin network line.
1981 This release contains support for using a DEC alpha as a GDB host for
1982 cross debugging. Native alpha debugging is not supported yet.
1985 *** Changes in GDB-4.9:
1989 This is the first GDB release which is accompanied by a matching testsuite.
1990 The testsuite requires installation of dejagnu, which should be available
1991 via ftp from most sites that carry GNU software.
1995 'Cfront' style demangling has had its name changed to 'ARM' style, to
1996 emphasize that it was written from the specifications in the C++ Annotated
1997 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1998 disclaimers, it still generated too much confusion with users attempting to
1999 use gdb with AT&T cfront.
2003 GDB now uses a standard remote interface to a simulator library.
2004 So far, the library contains simulators for the Zilog Z8001/2, the
2005 Hitachi H8/300, H8/500 and Super-H.
2007 * New targets supported
2009 H8/300 simulator h8300-hitachi-hms or h8300hms
2010 H8/500 simulator h8500-hitachi-hms or h8500hms
2011 SH simulator sh-hitachi-hms or sh
2012 Z8000 simulator z8k-zilog-none or z8ksim
2013 IDT MIPS board over serial line mips-idt-ecoff
2015 Cross-debugging to GO32 targets is supported. It requires a custom
2016 version of the i386-stub.c module which is integrated with the
2017 GO32 memory extender.
2019 * New remote protocols
2021 MIPS remote debugging protocol.
2023 * New source languages supported
2025 This version includes preliminary support for Chill, a Pascal like language
2026 used by telecommunications companies. Chill support is also being integrated
2027 into the GNU compiler, but we don't know when it will be publically available.
2030 *** Changes in GDB-4.8:
2032 * HP Precision Architecture supported
2034 GDB now supports HP PA-RISC machines running HPUX. A preliminary
2035 version of this support was available as a set of patches from the
2036 University of Utah. GDB does not support debugging of programs
2037 compiled with the HP compiler, because HP will not document their file
2038 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
2039 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
2041 Many problems in the preliminary version have been fixed.
2043 * Faster and better demangling
2045 We have improved template demangling and fixed numerous bugs in the GNU style
2046 demangler. It can now handle type modifiers such as `static' or `const'. Wide
2047 character types (wchar_t) are now supported. Demangling of each symbol is now
2048 only done once, and is cached when the symbol table for a file is read in.
2049 This results in a small increase in memory usage for C programs, a moderate
2050 increase in memory usage for C++ programs, and a fantastic speedup in
2053 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
2054 from the specifications in the Annotated Reference Manual, which AT&T's
2055 compiler does not actually implement.
2057 * G++ multiple inheritance compiler problem
2059 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
2060 inheritance lattices was reworked to properly discover ambiguities. We
2061 recently found an example which causes this new algorithm to fail in a
2062 very subtle way, producing bad debug information for those classes.
2063 The file 'gcc.patch' (in this directory) can be applied to gcc to
2064 circumvent the problem. A future GCC release will contain a complete
2067 The previous G++ debug info problem (mentioned below for the gdb-4.7
2068 release) is fixed in gcc version 2.3.2.
2070 * Improved configure script
2072 The `configure' script will now attempt to guess your system type if
2073 you don't supply a host system type. The old scheme of supplying a
2074 host system triplet is preferable over using this. All the magic is
2075 done in the new `config.guess' script. Examine it for details.
2077 We have also brought our configure script much more in line with the FSF's
2078 version. It now supports the --with-xxx options. In particular,
2079 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
2080 The resulting GDB will not be able to read arbitrary object file formats --
2081 only the format ``expected'' to be used on the configured target system.
2082 We hope to make this the default in a future release.
2084 * Documentation improvements
2086 There's new internal documentation on how to modify GDB, and how to
2087 produce clean changes to the code. We implore people to read it
2088 before submitting changes.
2090 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
2091 M4 macros. The new texinfo.tex is provided in this release. Pre-built
2092 `info' files are also provided. To build `info' files from scratch,
2093 you will need the latest `makeinfo' release, which will be available in
2094 a future texinfo-X.Y release.
2096 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
2097 We're not sure exactly which versions have this problem, but it has
2098 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
2099 or better. If that isn't possible, there is a patch in
2100 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
2101 around this problem.
2105 GDB now supports array constants that can be used in expressions typed in by
2106 the user. The syntax is `{element, element, ...}'. Ie: you can now type
2107 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
2110 The new directory `gdb/sparclite' contains a program that demonstrates
2111 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
2113 * New native hosts supported
2115 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
2116 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
2118 * New targets supported
2120 AMD 29k family via UDI a29k-amd-udi or udi29k
2122 * New file formats supported
2124 BFD now supports reading HP/PA-RISC executables (SOM file format?),
2125 HPUX core files, and SCO 3.2v2 core files.
2129 Attaching to processes now works again; thanks for the many bug reports.
2131 We have also stomped on a bunch of core dumps caused by
2132 printf_filtered("%s") problems.
2134 We eliminated a copyright problem on the rpc and ptrace header files
2135 for VxWorks, which was discovered at the last minute during the 4.7
2136 release. You should now be able to build a VxWorks GDB.
2138 You can now interrupt gdb while an attached process is running. This
2139 will cause the attached process to stop, and give control back to GDB.
2141 We fixed problems caused by using too many file descriptors
2142 for reading symbols from object files and libraries. This was
2143 especially a problem for programs that used many (~100) shared
2146 The `step' command now only enters a subroutine if there is line number
2147 information for the subroutine. Otherwise it acts like the `next'
2148 command. Previously, `step' would enter subroutines if there was
2149 any debugging information about the routine. This avoids problems
2150 when using `cc -g1' on MIPS machines.
2152 * Internal improvements
2154 GDB's internal interfaces have been improved to make it easier to support
2155 debugging of multiple languages in the future.
2157 GDB now uses a common structure for symbol information internally.
2158 Minimal symbols (derived from linkage symbols in object files), partial
2159 symbols (from a quick scan of debug information), and full symbols
2160 contain a common subset of information, making it easier to write
2161 shared code that handles any of them.
2163 * New command line options
2165 We now accept --silent as an alias for --quiet.
2169 The memory-mapped-malloc library is now licensed under the GNU Library
2170 General Public License.
2172 *** Changes in GDB-4.7:
2174 * Host/native/target split
2176 GDB has had some major internal surgery to untangle the support for
2177 hosts and remote targets. Now, when you configure GDB for a remote
2178 target, it will no longer load in all of the support for debugging
2179 local programs on the host. When fully completed and tested, this will
2180 ensure that arbitrary host/target combinations are possible.
2182 The primary conceptual shift is to separate the non-portable code in
2183 GDB into three categories. Host specific code is required any time GDB
2184 is compiled on that host, regardless of the target. Target specific
2185 code relates to the peculiarities of the target, but can be compiled on
2186 any host. Native specific code is everything else: it can only be
2187 built when the host and target are the same system. Child process
2188 handling and core file support are two common `native' examples.
2190 GDB's use of /proc for controlling Unix child processes is now cleaner.
2191 It has been split out into a single module under the `target_ops' vector,
2192 plus two native-dependent functions for each system that uses /proc.
2194 * New hosts supported
2196 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
2197 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2198 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
2200 * New targets supported
2202 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
2203 68030 and CPU32 m68030-*-*, m68332-*-*
2205 * New native hosts supported
2207 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2208 (386bsd is not well tested yet)
2209 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
2211 * New file formats supported
2213 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
2214 supports reading of `a.out.adobe' object files, which are an a.out
2215 format extended with minimal information about multiple sections.
2219 `show copying' is the same as the old `info copying'.
2220 `show warranty' is the same as `info warrantee'.
2221 These were renamed for consistency. The old commands continue to work.
2223 `info handle' is a new alias for `info signals'.
2225 You can now define pre-command hooks, which attach arbitrary command
2226 scripts to any command. The commands in the hook will be executed
2227 prior to the user's command. You can also create a hook which will be
2228 executed whenever the program stops. See gdb.texinfo.
2232 We now deal with Cfront style name mangling, and can even extract type
2233 info from mangled symbols. GDB can automatically figure out which
2234 symbol mangling style your C++ compiler uses.
2236 Calling of methods and virtual functions has been improved as well.
2240 The crash that occured when debugging Sun Ansi-C compiled binaries is
2241 fixed. This was due to mishandling of the extra N_SO stabs output
2244 We also finally got Ultrix 4.2 running in house, and fixed core file
2245 support, with help from a dozen people on the net.
2247 John M. Farrell discovered that the reason that single-stepping was so
2248 slow on all of the Mips based platforms (primarily SGI and DEC) was
2249 that we were trying to demangle and lookup a symbol used for internal
2250 purposes on every instruction that was being stepped through. Changing
2251 the name of that symbol so that it couldn't be mistaken for a C++
2252 mangled symbol sped things up a great deal.
2254 Rich Pixley sped up symbol lookups in general by getting much smarter
2255 about when C++ symbol mangling is necessary. This should make symbol
2256 completion (TAB on the command line) much faster. It's not as fast as
2257 we'd like, but it's significantly faster than gdb-4.6.
2261 A new user controllable variable 'call_scratch_address' can
2262 specify the location of a scratch area to be used when GDB
2263 calls a function in the target. This is necessary because the
2264 usual method of putting the scratch area on the stack does not work
2265 in systems that have separate instruction and data spaces.
2267 We integrated changes to support the 29k UDI (Universal Debugger
2268 Interface), but discovered at the last minute that we didn't have all
2269 of the appropriate copyright paperwork. We are working with AMD to
2270 resolve this, and hope to have it available soon.
2274 We have sped up the remote serial line protocol, especially for targets
2275 with lots of registers. It now supports a new `expedited status' ('T')
2276 message which can be used in place of the existing 'S' status message.
2277 This allows the remote stub to send only the registers that GDB
2278 needs to make a quick decision about single-stepping or conditional
2279 breakpoints, eliminating the need to fetch the entire register set for
2280 each instruction being stepped through.
2282 The GDB remote serial protocol now implements a write-through cache for
2283 registers, only re-reading the registers if the target has run.
2285 There is also a new remote serial stub for SPARC processors. You can
2286 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
2287 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
2288 processor with a serial port.
2292 Configure.in files have become much easier to read and modify. A new
2293 `table driven' format makes it more obvious what configurations are
2294 supported, and what files each one uses.
2298 There is a new opcodes library which will eventually contain all of the
2299 disassembly routines and opcode tables. At present, it only contains
2300 Sparc and Z8000 routines. This will allow the assembler, debugger, and
2301 disassembler (binutils/objdump) to share these routines.
2303 The libiberty library is now copylefted under the GNU Library General
2304 Public License. This allows more liberal use, and was done so libg++
2305 can use it. This makes no difference to GDB, since the Library License
2306 grants all the rights from the General Public License.
2310 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
2311 reference to the stabs symbol info used by the debugger. It is (as far
2312 as we know) the only published document on this fascinating topic. We
2313 encourage you to read it, compare it to the stabs information on your
2314 system, and send improvements on the document in general (to
2315 bug-gdb@prep.ai.mit.edu).
2317 And, of course, many bugs have been fixed.
2320 *** Changes in GDB-4.6:
2322 * Better support for C++ function names
2324 GDB now accepts as input the "demangled form" of C++ overloaded function
2325 names and member function names, and can do command completion on such names
2326 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
2327 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
2328 Make use of command completion, it is your friend.
2330 GDB also now accepts a variety of C++ mangled symbol formats. They are
2331 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
2332 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
2333 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
2334 for the list of formats.
2336 * G++ symbol mangling problem
2338 Recent versions of gcc have a bug in how they emit debugging information for
2339 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
2340 directory) can be applied to gcc to fix the problem. Alternatively, if you
2341 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
2342 usual symptom is difficulty with setting breakpoints on methods. GDB complains
2343 about the method being non-existent. (We believe that version 2.2.2 of GCC has
2346 * New 'maintenance' command
2348 All of the commands related to hacking GDB internals have been moved out of
2349 the main command set, and now live behind the 'maintenance' command. This
2350 can also be abbreviated as 'mt'. The following changes were made:
2352 dump-me -> maintenance dump-me
2353 info all-breakpoints -> maintenance info breakpoints
2354 printmsyms -> maintenance print msyms
2355 printobjfiles -> maintenance print objfiles
2356 printpsyms -> maintenance print psymbols
2357 printsyms -> maintenance print symbols
2359 The following commands are new:
2361 maintenance demangle Call internal GDB demangler routine to
2362 demangle a C++ link name and prints the result.
2363 maintenance print type Print a type chain for a given symbol
2365 * Change to .gdbinit file processing
2367 We now read the $HOME/.gdbinit file before processing the argv arguments
2368 (e.g. reading symbol files or core files). This allows global parameters to
2369 be set, which will apply during the symbol reading. The ./.gdbinit is still
2370 read after argv processing.
2372 * New hosts supported
2374 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
2376 GNU/Linux support i386-unknown-linux or linux
2378 We are also including code to support the HP/PA running BSD and HPUX. This
2379 is almost guaranteed not to work, as we didn't have time to test or build it
2380 for this release. We are including it so that the more adventurous (or
2381 masochistic) of you can play with it. We also had major problems with the
2382 fact that the compiler that we got from HP doesn't support the -g option.
2385 * New targets supported
2387 Hitachi H8/300 h8300-hitachi-hms or h8300hms
2389 * More smarts about finding #include files
2391 GDB now remembers the compilation directory for all include files, and for
2392 all files from which C is generated (like yacc and lex sources). This
2393 greatly improves GDB's ability to find yacc/lex sources, and include files,
2394 especially if you are debugging your program from a directory different from
2395 the one that contains your sources.
2397 We also fixed a bug which caused difficulty with listing and setting
2398 breakpoints in include files which contain C code. (In the past, you had to
2399 try twice in order to list an include file that you hadn't looked at before.)
2401 * Interesting infernals change
2403 GDB now deals with arbitrary numbers of sections, where the symbols for each
2404 section must be relocated relative to that section's landing place in the
2405 target's address space. This work was needed to support ELF with embedded
2406 stabs used by Solaris-2.0.
2408 * Bug fixes (of course!)
2410 There have been loads of fixes for the following things:
2411 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
2412 i960, stabs, DOS(GO32), procfs, etc...
2414 See the ChangeLog for details.
2416 *** Changes in GDB-4.5:
2418 * New machines supported (host and target)
2420 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
2422 SGI Irix-4.x mips-sgi-irix4 or iris4
2424 * New malloc package
2426 GDB now uses a new memory manager called mmalloc, based on gmalloc.
2427 Mmalloc is capable of handling mutiple heaps of memory. It is also
2428 capable of saving a heap to a file, and then mapping it back in later.
2429 This can be used to greatly speedup the startup of GDB by using a
2430 pre-parsed symbol table which lives in a mmalloc managed heap. For
2431 more details, please read mmalloc/mmalloc.texi.
2435 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
2436 'help info proc' for details.
2438 * MIPS ecoff symbol table format
2440 The code that reads MIPS symbol table format is now supported on all hosts.
2441 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
2444 * File name changes for MS-DOS
2446 Many files in the config directories have been renamed to make it easier to
2447 support GDB on MS-DOSe systems (which have very restrictive file name
2448 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
2449 environment) is close to working but has some remaining problems. Note
2450 that debugging of DOS programs is not supported, due to limitations
2451 in the ``operating system'', but it can be used to host cross-debugging.
2453 * Cross byte order fixes
2455 Many fixes have been made to support cross debugging of Sparc and MIPS
2456 targets from hosts whose byte order differs.
2458 * New -mapped and -readnow options
2460 If memory-mapped files are available on your system through the 'mmap'
2461 system call, you can use the -mapped option on the `file' or
2462 `symbol-file' commands to cause GDB to write the symbols from your
2463 program into a reusable file. If the program you are debugging is
2464 called `/path/fred', the mapped symbol file will be `./fred.syms'.
2465 Future GDB debugging sessions will notice the presence of this file,
2466 and will quickly map in symbol information from it, rather than reading
2467 the symbol table from the executable program. Using the '-mapped'
2468 option in a GDB `file' or `symbol-file' command has the same effect as
2469 starting GDB with the '-mapped' command-line option.
2471 You can cause GDB to read the entire symbol table immediately by using
2472 the '-readnow' option with any of the commands that load symbol table
2473 information (or on the GDB command line). This makes the command
2474 slower, but makes future operations faster.
2476 The -mapped and -readnow options are typically combined in order to
2477 build a `fred.syms' file that contains complete symbol information.
2478 A simple GDB invocation to do nothing but build a `.syms' file for future
2481 gdb -batch -nx -mapped -readnow programname
2483 The `.syms' file is specific to the host machine on which GDB is run.
2484 It holds an exact image of GDB's internal symbol table. It cannot be
2485 shared across multiple host platforms.
2487 * longjmp() handling
2489 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
2490 siglongjmp() without losing control. This feature has not yet been ported to
2491 all systems. It currently works on many 386 platforms, all MIPS-based
2492 platforms (SGI, DECstation, etc), and Sun3/4.
2496 Preliminary work has been put in to support the new Solaris OS from Sun. At
2497 this time, it can control and debug processes, but it is not capable of
2502 As always, many many bug fixes. The major areas were with g++, and mipsread.
2503 People using the MIPS-based platforms should experience fewer mysterious
2504 crashes and trashed symbol tables.
2506 *** Changes in GDB-4.4:
2508 * New machines supported (host and target)
2510 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2512 BSD Reno on Vax vax-dec-bsd
2513 Ultrix on Vax vax-dec-ultrix
2515 * New machines supported (target)
2517 AMD 29000 embedded, using EBMON a29k-none-none
2521 GDB continues to improve its handling of C++. `References' work better.
2522 The demangler has also been improved, and now deals with symbols mangled as
2523 per the Annotated C++ Reference Guide.
2525 GDB also now handles `stabs' symbol information embedded in MIPS
2526 `ecoff' symbol tables. Since the ecoff format was not easily
2527 extensible to handle new languages such as C++, this appeared to be a
2528 good way to put C++ debugging info into MIPS binaries. This option
2529 will be supported in the GNU C compiler, version 2, when it is
2532 * New features for SVR4
2534 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
2535 shared libraries. Debugging dynamically linked programs should present
2536 only minor differences from debugging statically linked programs.
2538 The `info proc' command will print out information about any process
2539 on an SVR4 system (including the one you are debugging). At the moment,
2540 it prints the address mappings of the process.
2542 If you bring up GDB on another SVR4 system, please send mail to
2543 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
2545 * Better dynamic linking support in SunOS
2547 Reading symbols from shared libraries which contain debugging symbols
2548 now works properly. However, there remain issues such as automatic
2549 skipping of `transfer vector' code during function calls, which
2550 make it harder to debug code in a shared library, than to debug the
2551 same code linked statically.
2555 GDB is now using the latest `getopt' routines from the FSF. This
2556 version accepts the -- prefix for options with long names. GDB will
2557 continue to accept the old forms (-option and +option) as well.
2558 Various single letter abbreviations for options have been explicity
2559 added to the option table so that they won't get overshadowed in the
2560 future by other options that begin with the same letter.
2564 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
2565 Many assorted bugs have been handled. Many more remain to be handled.
2566 See the various ChangeLog files (primarily in gdb and bfd) for details.
2569 *** Changes in GDB-4.3:
2571 * New machines supported (host and target)
2573 Amiga 3000 running Amix m68k-cbm-svr4 or amix
2574 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
2575 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
2577 * Almost SCO Unix support
2579 We had hoped to support:
2580 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2581 (except for core file support), but we discovered very late in the release
2582 that it has problems with process groups that render gdb unusable. Sorry
2583 about that. I encourage people to fix it and post the fixes.
2585 * Preliminary ELF and DWARF support
2587 GDB can read ELF object files on System V Release 4, and can handle
2588 debugging records for C, in DWARF format, in ELF files. This support
2589 is preliminary. If you bring up GDB on another SVR4 system, please
2590 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
2595 GDB now uses the latest `readline' library. One user-visible change
2596 is that two tabs will list possible command completions, which previously
2597 required typing M-? (meta-question mark, or ESC ?).
2601 The `stepi' bug that many of you noticed has been squashed.
2602 Many bugs in C++ have been handled. Many more remain to be handled.
2603 See the various ChangeLog files (primarily in gdb and bfd) for details.
2605 * State of the MIPS world (in case you wondered):
2607 GDB can understand the symbol tables emitted by the compilers
2608 supplied by most vendors of MIPS-based machines, including DEC. These
2609 symbol tables are in a format that essentially nobody else uses.
2611 Some versions of gcc come with an assembler post-processor called
2612 mips-tfile. This program is required if you want to do source-level
2613 debugging of gcc-compiled programs. I believe FSF does not ship
2614 mips-tfile with gcc version 1, but it will eventually come with gcc
2617 Debugging of g++ output remains a problem. g++ version 1.xx does not
2618 really support it at all. (If you're lucky, you should be able to get
2619 line numbers and stack traces to work, but no parameters or local
2620 variables.) With some work it should be possible to improve the
2623 When gcc version 2 is released, you will have somewhat better luck.
2624 However, even then you will get confusing results for inheritance and
2627 We will eventually provide full debugging of g++ output on
2628 DECstations. This will probably involve some kind of stabs-in-ecoff
2629 encapulation, but the details have not been worked out yet.
2632 *** Changes in GDB-4.2:
2634 * Improved configuration
2636 Only one copy of `configure' exists now, and it is not self-modifying.
2637 Porting BFD is simpler.
2641 The `step' and `next' commands now only stop at the first instruction
2642 of a source line. This prevents the multiple stops that used to occur
2643 in switch statements, for-loops, etc. `Step' continues to stop if a
2644 function that has debugging information is called within the line.
2648 Lots of small bugs fixed. More remain.
2650 * New host supported (not target)
2652 Intel 386 PC clone running Mach i386-none-mach
2655 *** Changes in GDB-4.1:
2657 * Multiple source language support
2659 GDB now has internal scaffolding to handle several source languages.
2660 It determines the type of each source file from its filename extension,
2661 and will switch expression parsing and number formatting to match the
2662 language of the function in the currently selected stack frame.
2663 You can also specifically set the language to be used, with
2664 `set language c' or `set language modula-2'.
2668 GDB now has preliminary support for the GNU Modula-2 compiler,
2669 currently under development at the State University of New York at
2670 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
2671 continue through the fall of 1991 and into 1992.
2673 Other Modula-2 compilers are currently not supported, and attempting to
2674 debug programs compiled with them will likely result in an error as the
2675 symbol table is read. Feel free to work on it, though!
2677 There are hooks in GDB for strict type checking and range checking,
2678 in the `Modula-2 philosophy', but they do not currently work.
2682 GDB can now write to executable and core files (e.g. patch
2683 a variable's value). You must turn this switch on, specify
2684 the file ("exec foo" or "core foo"), *then* modify it, e.g.
2685 by assigning a new value to a variable. Modifications take
2688 * Automatic SunOS shared library reading
2690 When you run your program, GDB automatically determines where its
2691 shared libraries (if any) have been loaded, and reads their symbols.
2692 The `share' command is no longer needed. This also works when
2693 examining core files.
2697 You can specify the number of lines that the `list' command shows.
2700 * New machines supported (host and target)
2702 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
2703 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
2704 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
2706 * New hosts supported (not targets)
2708 IBM RT/PC: romp-ibm-aix or rtpc
2710 * New targets supported (not hosts)
2712 AMD 29000 embedded with COFF a29k-none-coff
2713 AMD 29000 embedded with a.out a29k-none-aout
2714 Ultracomputer remote kernel debug a29k-nyu-kern
2716 * New remote interfaces
2722 *** Changes in GDB-4.0:
2726 Wide output is wrapped at good places to make the output more readable.
2728 Gdb now supports cross-debugging from a host machine of one type to a
2729 target machine of another type. Communication with the target system
2730 is over serial lines. The ``target'' command handles connecting to the
2731 remote system; the ``load'' command will download a program into the
2732 remote system. Serial stubs for the m68k and i386 are provided. Gdb
2733 also supports debugging of realtime processes running under VxWorks,
2734 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
2735 stub on the target system.
2737 New CPUs supported include the AMD 29000 and Intel 960.
2739 GDB now reads object files and symbol tables via a ``binary file''
2740 library, which allows a single copy of GDB to debug programs of multiple
2741 object file types such as a.out and coff.
2743 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2744 refcard.dvi and refcard.ps are available to format it).
2747 * Control-Variable user interface simplified
2749 All variables that control the operation of the debugger can be set
2750 by the ``set'' command, and displayed by the ``show'' command.
2752 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2753 ``Show prompt'' produces the response:
2754 Gdb's prompt is new-gdb=>.
2756 What follows are the NEW set commands. The command ``help set'' will
2757 print a complete list of old and new set commands. ``help set FOO''
2758 will give a longer description of the variable FOO. ``show'' will show
2759 all of the variable descriptions and their current settings.
2761 confirm on/off: Enables warning questions for operations that are
2762 hard to recover from, e.g. rerunning the program while
2763 it is already running. Default is ON.
2765 editing on/off: Enables EMACS style command line editing
2766 of input. Previous lines can be recalled with
2767 control-P, the current line can be edited with control-B,
2768 you can search for commands with control-R, etc.
2771 history filename NAME: NAME is where the gdb command history
2772 will be stored. The default is .gdb_history,
2773 or the value of the environment variable
2776 history size N: The size, in commands, of the command history. The
2777 default is 256, or the value of the environment variable
2780 history save on/off: If this value is set to ON, the history file will
2781 be saved after exiting gdb. If set to OFF, the
2782 file will not be saved. The default is OFF.
2784 history expansion on/off: If this value is set to ON, then csh-like
2785 history expansion will be performed on
2786 command line input. The default is OFF.
2788 radix N: Sets the default radix for input and output. It can be set
2789 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2790 in the current radix, so "set radix 10" is always a no-op.
2792 height N: This integer value is the number of lines on a page. Default
2793 is 24, the current `stty rows'' setting, or the ``li#''
2794 setting from the termcap entry matching the environment
2797 width N: This integer value is the number of characters on a line.
2798 Default is 80, the current `stty cols'' setting, or the ``co#''
2799 setting from the termcap entry matching the environment
2802 Note: ``set screensize'' is obsolete. Use ``set height'' and
2803 ``set width'' instead.
2805 print address on/off: Print memory addresses in various command displays,
2806 such as stack traces and structure values. Gdb looks
2807 more ``symbolic'' if you turn this off; it looks more
2808 ``machine level'' with it on. Default is ON.
2810 print array on/off: Prettyprint arrays. New convenient format! Default
2813 print demangle on/off: Print C++ symbols in "source" form if on,
2816 print asm-demangle on/off: Same, for assembler level printouts
2819 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2822 * Support for Epoch Environment.
2824 The epoch environment is a version of Emacs v18 with windowing. One
2825 new command, ``inspect'', is identical to ``print'', except that if you
2826 are running in the epoch environment, the value is printed in its own
2830 * Support for Shared Libraries
2832 GDB can now debug programs and core files that use SunOS shared libraries.
2833 Symbols from a shared library cannot be referenced
2834 before the shared library has been linked with the program (this
2835 happens after you type ``run'' and before the function main() is entered).
2836 At any time after this linking (including when examining core files
2837 from dynamically linked programs), gdb reads the symbols from each
2838 shared library when you type the ``sharedlibrary'' command.
2839 It can be abbreviated ``share''.
2841 sharedlibrary REGEXP: Load shared object library symbols for files
2842 matching a unix regular expression. No argument
2843 indicates to load symbols for all shared libraries.
2845 info sharedlibrary: Status of loaded shared libraries.
2850 A watchpoint stops execution of a program whenever the value of an
2851 expression changes. Checking for this slows down execution
2852 tremendously whenever you are in the scope of the expression, but is
2853 quite useful for catching tough ``bit-spreader'' or pointer misuse
2854 problems. Some machines such as the 386 have hardware for doing this
2855 more quickly, and future versions of gdb will use this hardware.
2857 watch EXP: Set a watchpoint (breakpoint) for an expression.
2859 info watchpoints: Information about your watchpoints.
2861 delete N: Deletes watchpoint number N (same as breakpoints).
2862 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2863 enable N: Re-enables watchpoint number N (same as breakpoints).
2866 * C++ multiple inheritance
2868 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2871 * C++ exception handling
2873 Gdb now supports limited C++ exception handling. Besides the existing
2874 ability to breakpoint on an exception handler, gdb can breakpoint on
2875 the raising of an exception (before the stack is peeled back to the
2878 catch FOO: If there is a FOO exception handler in the dynamic scope,
2879 set a breakpoint to catch exceptions which may be raised there.
2880 Multiple exceptions (``catch foo bar baz'') may be caught.
2882 info catch: Lists all exceptions which may be caught in the
2883 current stack frame.
2886 * Minor command changes
2888 The command ``call func (arg, arg, ...)'' now acts like the print
2889 command, except it does not print or save a value if the function's result
2890 is void. This is similar to dbx usage.
2892 The ``up'' and ``down'' commands now always print the frame they end up
2893 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2894 frames without printing.
2896 * New directory command
2898 'dir' now adds directories to the FRONT of the source search path.
2899 The path starts off empty. Source files that contain debug information
2900 about the directory in which they were compiled can be found even
2901 with an empty path; Sun CC and GCC include this information. If GDB can't
2902 find your source file in the current directory, type "dir .".
2904 * Configuring GDB for compilation
2906 For normal use, type ``./configure host''. See README or gdb.texinfo
2909 GDB now handles cross debugging. If you are remotely debugging between
2910 two different machines, type ``./configure host -target=targ''.
2911 Host is the machine where GDB will run; targ is the machine
2912 where the program that you are debugging will run.
projects / deliverable / binutils-gdb.git / blob