1 What has changed in GDB?
2 (Organized release by release)
4 *** Changes since GDB 6.5
6 * GDB can now be configured as a cross-debugger targeting native Windows
7 (mingw32) or Cygwin. It can communicate with a remote debugging stub
8 running on a Windows system over TCP/IP to debug Windows programs.
10 * The GDB remote stub, gdbserver, has been updated to support Windows and
11 Cygwin debugging. Both single-threaded and multi-threaded programs are
19 Manage a list of substitution rules that GDB uses to rewrite the name
20 of the directories where the sources are located. This can be useful
21 for instance when the sources were moved to a different location
22 between compilation and debugging.
26 Print each CLI command as it is executed. Each command is prefixed with
27 a number of `+' symbols representing the nesting depth.
28 The source command now has a `-v' option to enable the same feature.
32 The ARM Demon monitor support (RDP protocol, "target rdp").
34 Kernel Object Display, an embedded debugging feature which only worked with
35 an obsolete version of Cisco IOS.
37 The 'set download-write-size' and 'show download-write-size' commands.
42 Tell a stub about GDB client features, and request remote target features.
43 The first feature implemented is PacketSize, which allows the target to
44 specify the size of packets it can handle - to minimize the number of
45 packets required and improve performance when connected to a remote
49 Fetch an OS auxilliary vector from the remote stub. This packet is a
50 more efficient replacement for qPart:auxv:read.
52 * Removed remote packets
55 This packet has been replaced by qXfer:auxv:read. Only GDB 6.4 and 6.5
56 used it, and only gdbserver implemented it.
58 *** Changes in GDB 6.5
62 Renesas M32C/M16C m32c-elf
64 Morpho Technologies ms1 ms1-elf
68 init-if-undefined Initialize a convenience variable, but
69 only if it doesn't already have a value.
71 The following commands are presently only implemented for native GNU/Linux:
73 checkpoint Save a snapshot of the program state.
75 restart <n> Return the program state to a
76 previously saved state.
78 info checkpoints List currently saved checkpoints.
80 delete-checkpoint <n> Delete a previously saved checkpoint.
82 set|show detach-on-fork Tell gdb whether to detach from a newly
83 forked process, or to keep debugging it.
85 info forks List forks of the user program that
86 are available to be debugged.
88 fork <n> Switch to debugging one of several
89 forks of the user program that are
90 available to be debugged.
92 delete-fork <n> Delete a fork from the list of forks
93 that are available to be debugged (and
94 kill the forked process).
96 detach-fork <n> Delete a fork from the list of forks
97 that are available to be debugged (and
98 allow the process to continue).
102 Morpho Technologies ms2 ms1-elf
104 * Improved Windows host support
106 GDB now builds as a cross debugger hosted on i686-mingw32, including
107 native console support, and remote communications using either
108 network sockets or serial ports.
110 * Improved Modula-2 language support
112 GDB can now print most types in the Modula-2 syntax. This includes:
113 basic types, set types, record types, enumerated types, range types,
114 pointer types and ARRAY types. Procedure var parameters are correctly
115 printed and hexadecimal addresses and character constants are also
116 written in the Modula-2 syntax. Best results can be obtained by using
117 GNU Modula-2 together with the -gdwarf-2 command line option.
121 The ARM rdi-share module.
123 The Netware NLM debug server.
125 *** Changes in GDB 6.4
127 * New native configurations
129 OpenBSD/arm arm*-*-openbsd*
130 OpenBSD/mips64 mips64-*-openbsd*
134 Morpho Technologies ms1 ms1-elf
136 * New command line options
138 --batch-silent As for --batch, but totally silent.
139 --return-child-result The debugger will exist with the same value
140 the child (debugged) program exited with.
141 --eval-command COMMAND, -ex COMMAND
142 Execute a single GDB CLI command. This may be
143 specified multiple times and in conjunction
144 with the --command (-x) option.
146 * Deprecated commands removed
148 The following commands, that were deprecated in 2000, have been
152 set|show arm disassembly-flavor set|show arm disassembler
153 othernames set arm disassembler
154 set|show remotedebug set|show debug remote
155 set|show archdebug set|show debug arch
156 set|show eventdebug set|show debug event
159 * New BSD user-level threads support
161 It is now possible to debug programs using the user-level threads
162 library on OpenBSD and FreeBSD. Currently supported (target)
165 FreeBSD/amd64 x86_64-*-freebsd*
166 FreeBSD/i386 i386-*-freebsd*
167 OpenBSD/i386 i386-*-openbsd*
169 Note that the new kernel threads libraries introduced in FreeBSD 5.x
170 are not yet supported.
172 * New support for Matsushita MN10300 w/sim added
173 (Work in progress). mn10300-elf.
175 * REMOVED configurations and files
177 VxWorks and the XDR protocol *-*-vxworks
178 Motorola MCORE mcore-*-*
179 National Semiconductor NS32000 ns32k-*-*
181 * New "set print array-indexes" command
183 After turning this setting "on", GDB prints the index of each element
184 when displaying arrays. The default is "off" to preserve the previous
187 * VAX floating point support
189 GDB now supports the not-quite-ieee VAX F and D floating point formats.
191 * User-defined command support
193 In addition to using $arg0..$arg9 for argument passing, it is now possible
194 to use $argc to determine now many arguments have been passed. See the
195 section on user-defined commands in the user manual for more information.
197 *** Changes in GDB 6.3:
199 * New command line option
201 GDB now accepts -l followed by a number to set the timeout for remote
204 * GDB works with GCC -feliminate-dwarf2-dups
206 GDB now supports a more compact representation of DWARF-2 debug
207 information using DW_FORM_ref_addr references. These are produced
208 by GCC with the option -feliminate-dwarf2-dups and also by some
209 proprietary compilers. With GCC, you must use GCC 3.3.4 or later
210 to use -feliminate-dwarf2-dups.
212 * Internationalization
214 When supported by the host system, GDB will be built with
215 internationalization (libintl). The task of marking up the sources is
216 continued, we're looking forward to our first translation.
220 Initial support for debugging programs compiled with the GNAT
221 implementation of the Ada programming language has been integrated
222 into GDB. In this release, support is limited to expression evaluation.
224 * New native configurations
226 GNU/Linux/m32r m32r-*-linux-gnu
230 GDB's remote protocol now includes support for the 'p' packet. This
231 packet is used to fetch individual registers from a remote inferior.
233 * END-OF-LIFE registers[] compatibility module
235 GDB's internal register infrastructure has been completely rewritten.
236 The new infrastructure making possible the implementation of key new
237 features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit
240 GDB 6.3 will be the last release to include the the registers[]
241 compatibility module that allowed out-of-date configurations to
242 continue to work. This change directly impacts the following
254 Unless there is activity to revive these configurations, they will be
255 made OBSOLETE in GDB 6.4, and REMOVED from GDB 6.5.
257 * OBSOLETE configurations and files
259 Configurations that have been declared obsolete in this release have
260 been commented out. Unless there is activity to revive these
261 configurations, the next release of GDB will have their sources
271 *** Changes in GDB 6.2.1:
273 * MIPS `break main; run' gave an heuristic-fence-post warning
275 When attempting to run even a simple program, a warning about
276 heuristic-fence-post being hit would be reported. This problem has
279 * MIPS IRIX 'long double' crashed GDB
281 When examining a long double variable, GDB would get a segmentation
282 fault. The crash has been fixed (but GDB 6.2 cannot correctly examine
283 IRIX long double values).
287 A bug in the VAX stack code was causing problems with the "next"
288 command. This problem has been fixed.
290 *** Changes in GDB 6.2:
292 * Fix for ``many threads''
294 On GNU/Linux systems that use the NPTL threads library, a program
295 rapidly creating and deleting threads would confuse GDB leading to the
298 ptrace: No such process.
299 thread_db_get_info: cannot get thread info: generic error
301 This problem has been fixed.
303 * "-async" and "-noasync" options removed.
305 Support for the broken "-noasync" option has been removed (it caused
308 * New ``start'' command.
310 This command runs the program until the begining of the main procedure.
312 * New BSD Kernel Data Access Library (libkvm) interface
314 Using ``target kvm'' it is now possible to debug kernel core dumps and
315 live kernel memory images on various FreeBSD, NetBSD and OpenBSD
316 platforms. Currently supported (native-only) configurations are:
318 FreeBSD/amd64 x86_64-*-freebsd*
319 FreeBSD/i386 i?86-*-freebsd*
320 NetBSD/i386 i?86-*-netbsd*
321 NetBSD/m68k m68*-*-netbsd*
322 NetBSD/sparc sparc-*-netbsd*
323 OpenBSD/amd64 x86_64-*-openbsd*
324 OpenBSD/i386 i?86-*-openbsd*
325 OpenBSD/m68k m68*-openbsd*
326 OpenBSD/sparc sparc-*-openbsd*
328 * Signal trampoline code overhauled
330 Many generic problems with GDB's signal handling code have been fixed.
331 These include: backtraces through non-contiguous stacks; recognition
332 of sa_sigaction signal trampolines; backtrace from a NULL pointer
333 call; backtrace through a signal trampoline; step into and out of
334 signal handlers; and single-stepping in the signal trampoline.
336 Please note that kernel bugs are a limiting factor here. These
337 features have been shown to work on an s390 GNU/Linux system that
338 include a 2.6.8-rc1 kernel. Ref PR breakpoints/1702.
340 * Cygwin support for DWARF 2 added.
342 * New native configurations
344 GNU/Linux/hppa hppa*-*-linux*
345 OpenBSD/hppa hppa*-*-openbsd*
346 OpenBSD/m68k m68*-*-openbsd*
347 OpenBSD/m88k m88*-*-openbsd*
348 OpenBSD/powerpc powerpc-*-openbsd*
349 NetBSD/vax vax-*-netbsd*
350 OpenBSD/vax vax-*-openbsd*
352 * END-OF-LIFE frame compatibility module
354 GDB's internal frame infrastructure has been completely rewritten.
355 The new infrastructure making it possible to support key new features
356 including DWARF 2 Call Frame Information. To aid in the task of
357 migrating old configurations to this new infrastructure, a
358 compatibility module, that allowed old configurations to continue to
359 work, was also included.
361 GDB 6.2 will be the last release to include this frame compatibility
362 module. This change directly impacts the following configurations:
372 Unless there is activity to revive these configurations, they will be
373 made OBSOLETE in GDB 6.3, and REMOVED from GDB 6.4.
375 * REMOVED configurations and files
377 Sun 3, running SunOS 3 m68*-*-sunos3*
378 Sun 3, running SunOS 4 m68*-*-sunos4*
379 Sun 2, running SunOS 3 m68000-*-sunos3*
380 Sun 2, running SunOS 4 m68000-*-sunos4*
381 Motorola 680x0 running LynxOS m68*-*-lynxos*
382 AT&T 3b1/Unix pc m68*-att-*
383 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
384 decstation mips-dec-* mips-little-*
385 riscos mips-*-riscos* mips-*-sysv*
387 sysv mips*-*-sysv4* (IRIX 5/6 not included)
389 *** Changes in GDB 6.1.1:
391 * TUI (Text-mode User Interface) built-in (also included in GDB 6.1)
393 The TUI (Text-mode User Interface) is now built as part of a default
394 GDB configuration. It is enabled by either selecting the TUI with the
395 command line option "-i=tui" or by running the separate "gdbtui"
396 program. For more information on the TUI, see the manual "Debugging
399 * Pending breakpoint support (also included in GDB 6.1)
401 Support has been added to allow you to specify breakpoints in shared
402 libraries that have not yet been loaded. If a breakpoint location
403 cannot be found, and the "breakpoint pending" option is set to auto,
404 GDB queries you if you wish to make the breakpoint pending on a future
405 shared-library load. If and when GDB resolves the breakpoint symbol,
406 the pending breakpoint is removed as one or more regular breakpoints
409 Pending breakpoints are very useful for GCJ Java debugging.
411 * Fixed ISO-C build problems
413 The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained
414 non ISO-C code that stopped them being built using a more strict ISO-C
415 compiler (e.g., IBM's C compiler).
417 * Fixed build problem on IRIX 5
419 Due to header problems with <sys/proc.h>, the file gdb/proc-api.c
420 wasn't able to compile compile on an IRIX 5 system.
422 * Added execute permission to gdb/gdbserver/configure
424 The shell script gdb/testsuite/gdb.stabs/configure lacked execute
425 permission. This bug would cause configure to fail on a number of
426 systems (Solaris, IRIX). Ref: server/519.
428 * Fixed build problem on hpux2.0w-hp-hpux11.00 using the HP ANSI C compiler
430 Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c
431 has been updated to use constant array sizes.
433 * Fixed a panic in the DWARF Call Frame Info code on Solaris 2.7
435 GCC 3.3.2, on Solaris 2.7, includes the DW_EH_PE_funcrel encoding in
436 its generated DWARF Call Frame Info. This encoding was causing GDB to
437 panic, that panic has been fixed. Ref: gdb/1628.
439 * Fixed a problem when examining parameters in shared library code.
441 When examining parameters in optimized shared library code generated
442 by a mainline GCC, GDB would incorrectly report ``Variable "..." is
443 not available''. GDB now correctly displays the variable's value.
445 *** Changes in GDB 6.1:
447 * Removed --with-mmalloc
449 Support for the mmalloc memory manager has been removed, as it
450 conflicted with the internal gdb byte cache.
452 * Changes in AMD64 configurations
454 The AMD64 target now includes the %cs and %ss registers. As a result
455 the AMD64 remote protocol has changed; this affects the floating-point
456 and SSE registers. If you rely on those registers for your debugging,
457 you should upgrade gdbserver on the remote side.
459 * Revised SPARC target
461 The SPARC target has been completely revised, incorporating the
462 FreeBSD/sparc64 support that was added for GDB 6.0. As a result
463 support for LynxOS and SunOS 4 has been dropped. Calling functions
464 from within GDB on operating systems with a non-executable stack
465 (Solaris, OpenBSD) now works.
469 GDB has a new C++ demangler which does a better job on the mangled
470 names generated by current versions of g++. It also runs faster, so
471 with this and other changes gdb should now start faster on large C++
474 * DWARF 2 Location Expressions
476 GDB support for location expressions has been extended to support function
477 arguments and frame bases. Older versions of GDB could crash when they
480 * C++ nested types and namespaces
482 GDB's support for nested types and namespaces in C++ has been
483 improved, especially if you use the DWARF 2 debugging format. (This
484 is the default for recent versions of GCC on most platforms.)
485 Specifically, if you have a class "Inner" defined within a class or
486 namespace "Outer", then GDB realizes that the class's name is
487 "Outer::Inner", not simply "Inner". This should greatly reduce the
488 frequency of complaints about not finding RTTI symbols. In addition,
489 if you are stopped at inside of a function defined within a namespace,
490 GDB modifies its name lookup accordingly.
492 * New native configurations
494 NetBSD/amd64 x86_64-*-netbsd*
495 OpenBSD/amd64 x86_64-*-openbsd*
496 OpenBSD/alpha alpha*-*-openbsd*
497 OpenBSD/sparc sparc-*-openbsd*
498 OpenBSD/sparc64 sparc64-*-openbsd*
500 * New debugging protocols
502 M32R with SDI protocol m32r-*-elf*
504 * "set prompt-escape-char" command deleted.
506 The command "set prompt-escape-char" has been deleted. This command,
507 and its very obscure effet on GDB's prompt, was never documented,
508 tested, nor mentioned in the NEWS file.
510 * OBSOLETE configurations and files
512 Configurations that have been declared obsolete in this release have
513 been commented out. Unless there is activity to revive these
514 configurations, the next release of GDB will have their sources
517 Sun 3, running SunOS 3 m68*-*-sunos3*
518 Sun 3, running SunOS 4 m68*-*-sunos4*
519 Sun 2, running SunOS 3 m68000-*-sunos3*
520 Sun 2, running SunOS 4 m68000-*-sunos4*
521 Motorola 680x0 running LynxOS m68*-*-lynxos*
522 AT&T 3b1/Unix pc m68*-att-*
523 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
524 decstation mips-dec-* mips-little-*
525 riscos mips-*-riscos* mips-*-sysv*
527 sysv mips*-*-sysv4* (IRIX 5/6 not included)
529 * REMOVED configurations and files
531 SGI Irix-4.x mips-sgi-irix4 or iris4
532 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
533 Z8000 simulator z8k-zilog-none or z8ksim
534 Matsushita MN10200 w/simulator mn10200-*-*
535 H8/500 simulator h8500-hitachi-hms or h8500hms
536 HP/PA running BSD hppa*-*-bsd*
537 HP/PA running OSF/1 hppa*-*-osf*
538 HP/PA Pro target hppa*-*-pro*
539 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
540 386BSD i[3456]86-*-bsd*
541 Sequent family i[3456]86-sequent-sysv4*
542 i[3456]86-sequent-sysv*
543 i[3456]86-sequent-bsd*
544 SPARC running LynxOS sparc-*-lynxos*
545 SPARC running SunOS 4 sparc-*-sunos4*
546 Tsqware Sparclet sparclet-*-*
547 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
549 *** Changes in GDB 6.0:
553 Support for debugging the Objective-C programming language has been
556 * New backtrace mechanism (includes DWARF 2 Call Frame Information).
558 DWARF 2's Call Frame Information makes available compiler generated
559 information that more exactly describes the program's run-time stack.
560 By using this information, GDB is able to provide more robust stack
563 The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets
564 have been updated to use a new backtrace mechanism which includes
569 GDB's remote protocol has been extended to include support for hosted
570 file I/O (where the remote target uses GDB's file system). See GDB's
571 remote protocol documentation for details.
573 * All targets using the new architecture framework.
575 All of GDB's targets have been updated to use the new internal
576 architecture framework. The way is now open for future GDB releases
577 to include cross-architecture native debugging support (i386 on amd64,
580 * GNU/Linux's Thread Local Storage (TLS)
582 GDB now includes support for for the GNU/Linux implementation of
583 per-thread variables.
585 * GNU/Linux's Native POSIX Thread Library (NPTL)
587 GDB's thread code has been updated to work with either the new
588 GNU/Linux NPTL thread library or the older "LinuxThreads" library.
590 * Separate debug info.
592 GDB, in conjunction with BINUTILS, now supports a mechanism for
593 automatically loading debug information from a separate file. Instead
594 of shipping full debug and non-debug versions of system libraries,
595 system integrators can now instead ship just the stripped libraries
596 and optional debug files.
598 * DWARF 2 Location Expressions
600 DWARF 2 Location Expressions allow the compiler to more completely
601 describe the location of variables (even in optimized code) to the
604 GDB now includes preliminary support for location expressions (support
605 for DW_OP_piece is still missing).
609 A number of long standing bugs that caused GDB to die while starting a
610 Java application have been fixed. GDB's Java support is now
611 considered "useable".
613 * GNU/Linux support for fork, vfork, and exec.
615 The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode"
616 commands are now implemented for GNU/Linux. They require a 2.5.x or later
619 * GDB supports logging output to a file
621 There are two new commands, "set logging" and "show logging", which can be
622 used to capture GDB's output to a file.
624 * The meaning of "detach" has changed for gdbserver
626 The "detach" command will now resume the application, as documented. To
627 disconnect from gdbserver and leave it stopped, use the new "disconnect"
630 * d10v, m68hc11 `regs' command deprecated
632 The `info registers' command has been updated so that it displays the
633 registers using a format identical to the old `regs' command.
637 A new command, "maint set profile on/off", has been added. This command can
638 be used to enable or disable profiling while running GDB, to profile a
639 session or a set of commands. In addition there is a new configure switch,
640 "--enable-profiling", which will cause GDB to be compiled with profiling
641 data, for more informative profiling results.
643 * Default MI syntax changed to "mi2".
645 The default MI (machine interface) syntax, enabled by the command line
646 option "-i=mi", has been changed to "mi2". The previous MI syntax,
647 "mi1", can be enabled by specifying the option "-i=mi1".
649 Support for the original "mi0" syntax (included in GDB 5.0) has been
652 Fix for gdb/192: removed extraneous space when displaying frame level.
653 Fix for gdb/672: update changelist is now output in mi list format.
654 Fix for gdb/702: a -var-assign that updates the value now shows up
655 in a subsequent -var-update.
657 * New native configurations.
659 FreeBSD/amd64 x86_64-*-freebsd*
661 * Multi-arched targets.
663 HP/PA HPUX11 hppa*-*-hpux*
664 Renesas M32R/D w/simulator m32r-*-elf*
666 * OBSOLETE configurations and files
668 Configurations that have been declared obsolete in this release have
669 been commented out. Unless there is activity to revive these
670 configurations, the next release of GDB will have their sources
673 Z8000 simulator z8k-zilog-none or z8ksim
674 Matsushita MN10200 w/simulator mn10200-*-*
675 H8/500 simulator h8500-hitachi-hms or h8500hms
676 HP/PA running BSD hppa*-*-bsd*
677 HP/PA running OSF/1 hppa*-*-osf*
678 HP/PA Pro target hppa*-*-pro*
679 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
680 Sequent family i[3456]86-sequent-sysv4*
681 i[3456]86-sequent-sysv*
682 i[3456]86-sequent-bsd*
683 Tsqware Sparclet sparclet-*-*
684 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
686 * REMOVED configurations and files
689 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
690 IBM AIX PS/2 i[3456]86-*-aix
691 i386 running Mach 3.0 i[3456]86-*-mach3*
692 i386 running Mach i[3456]86-*-mach*
693 i386 running OSF/1 i[3456]86-*osf1mk*
694 HP/Apollo 68k Family m68*-apollo*-sysv*,
696 m68*-hp-bsd*, m68*-hp-hpux*
697 Argonaut Risc Chip (ARC) arc-*-*
698 Mitsubishi D30V d30v-*-*
699 Fujitsu FR30 fr30-*-elf*
700 OS/9000 i[34]86-*-os9k
701 I960 with MON960 i960-*-coff
703 * MIPS $fp behavior changed
705 The convenience variable $fp, for the MIPS, now consistently returns
706 the address of the current frame's base. Previously, depending on the
707 context, $fp could refer to either $sp or the current frame's base
708 address. See ``8.10 Registers'' in the manual ``Debugging with GDB:
709 The GNU Source-Level Debugger''.
711 *** Changes in GDB 5.3:
713 * GNU/Linux shared library multi-threaded performance improved.
715 When debugging a multi-threaded application on GNU/Linux, GDB now uses
716 `/proc', in preference to `ptrace' for memory reads. This may result
717 in an improvement in the start-up time of multi-threaded, shared
718 library applications when run under GDB. One GDB user writes: ``loads
719 shared libs like mad''.
721 * ``gdbserver'' now supports multi-threaded applications on some targets
723 Support for debugging multi-threaded applications which use
724 the GNU/Linux LinuxThreads package has been added for
725 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
726 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
728 * GDB now supports C/C++ preprocessor macros.
730 GDB now expands preprocessor macro invocations in C/C++ expressions,
731 and provides various commands for showing macro definitions and how
734 The new command `macro expand EXPRESSION' expands any macro
735 invocations in expression, and shows the result.
737 The new command `show macro MACRO-NAME' shows the definition of the
738 macro named MACRO-NAME, and where it was defined.
740 Most compilers don't include information about macros in the debugging
741 information by default. In GCC 3.1, for example, you need to compile
742 your program with the options `-gdwarf-2 -g3'. If the macro
743 information is present in the executable, GDB will read it.
745 * Multi-arched targets.
747 DEC Alpha (partial) alpha*-*-*
748 DEC VAX (partial) vax-*-*
750 National Semiconductor NS32000 (partial) ns32k-*-*
751 Motorola 68000 (partial) m68k-*-*
752 Motorola MCORE mcore-*-*
756 Fujitsu FRV architecture added by Red Hat frv*-*-*
759 * New native configurations
761 Alpha NetBSD alpha*-*-netbsd*
762 SH NetBSD sh*-*-netbsdelf*
763 MIPS NetBSD mips*-*-netbsd*
764 UltraSPARC NetBSD sparc64-*-netbsd*
766 * OBSOLETE configurations and files
768 Configurations that have been declared obsolete in this release have
769 been commented out. Unless there is activity to revive these
770 configurations, the next release of GDB will have their sources
773 Mitsubishi D30V d30v-*-*
774 OS/9000 i[34]86-*-os9k
775 IBM AIX PS/2 i[3456]86-*-aix
776 Fujitsu FR30 fr30-*-elf*
777 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
778 Argonaut Risc Chip (ARC) arc-*-*
779 i386 running Mach 3.0 i[3456]86-*-mach3*
780 i386 running Mach i[3456]86-*-mach*
781 i386 running OSF/1 i[3456]86-*osf1mk*
782 HP/Apollo 68k Family m68*-apollo*-sysv*,
784 m68*-hp-bsd*, m68*-hp-hpux*
785 I960 with MON960 i960-*-coff
789 CHILL, a Pascal like language used by telecommunications companies.
791 * REMOVED configurations and files
793 AMD 29k family via UDI a29k-amd-udi, udi29k
794 A29K VxWorks a29k-*-vxworks
795 AMD 29000 embedded, using EBMON a29k-none-none
796 AMD 29000 embedded with COFF a29k-none-coff
797 AMD 29000 embedded with a.out a29k-none-aout
799 testsuite/gdb.hp/gdb.threads-hp/ directory
801 * New command "set max-user-call-depth <nnn>"
803 This command allows the user to limit the call depth of user-defined
804 commands. The default is 1024.
806 * Changes in FreeBSD/i386 native debugging.
808 Support for the "generate-core-file" has been added.
810 * New commands "dump", "append", and "restore".
812 These commands allow data to be copied from target memory
813 to a bfd-format or binary file (dump and append), and back
814 from a file into memory (restore).
816 * Improved "next/step" support on multi-processor Alpha Tru64.
818 The previous single-step mechanism could cause unpredictable problems,
819 including the random appearance of SIGSEGV or SIGTRAP signals. The use
820 of a software single-step mechanism prevents this.
822 *** Changes in GDB 5.2.1:
830 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
831 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
832 Fix, by Joel Brobecker imported from mainline.
834 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
835 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
836 Fix, by Fred Fish, imported from mainline.
838 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
839 Surprisingly enough, it works now.
840 By Michal Ludvig, imported from mainline.
842 i386 hardware watchpoint support:
843 avoid misses on second run for some targets.
844 By Pierre Muller, imported from mainline.
846 *** Changes in GDB 5.2:
848 * New command "set trust-readonly-sections on[off]".
850 This command is a hint that tells gdb that read-only sections
851 really are read-only (ie. that their contents will not change).
852 In this mode, gdb will go to the object file rather than the
853 target to read memory from read-only sections (such as ".text").
854 This can be a significant performance improvement on some
855 (notably embedded) targets.
857 * New command "generate-core-file" (or "gcore").
859 This new gdb command allows the user to drop a core file of the child
860 process state at any time. So far it's been implemented only for
861 GNU/Linux and Solaris, but should be relatively easily ported to other
862 hosts. Argument is core file name (defaults to core.<pid>).
864 * New command line option
866 GDB now accepts --pid or -p followed by a process id.
868 * Change in command line behavior -- corefiles vs. process ids.
870 There is a subtle behavior in the way in which GDB handles
871 command line arguments. The first non-flag argument is always
872 a program to debug, but the second non-flag argument may either
873 be a corefile or a process id. Previously, GDB would attempt to
874 open the second argument as a corefile, and if that failed, would
875 issue a superfluous error message and then attempt to attach it as
876 a process. Now, if the second argument begins with a non-digit,
877 it will be treated as a corefile. If it begins with a digit,
878 GDB will attempt to attach it as a process, and if no such process
879 is found, will then attempt to open it as a corefile.
881 * Changes in ARM configurations.
883 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
884 configuration is fully multi-arch.
886 * New native configurations
888 ARM NetBSD arm*-*-netbsd*
889 x86 OpenBSD i[3456]86-*-openbsd*
890 AMD x86-64 running GNU/Linux x86_64-*-linux-*
891 Sparc64 running FreeBSD sparc64-*-freebsd*
895 Sanyo XStormy16 xstormy16-elf
897 * OBSOLETE configurations and files
899 Configurations that have been declared obsolete in this release have
900 been commented out. Unless there is activity to revive these
901 configurations, the next release of GDB will have their sources
904 AMD 29k family via UDI a29k-amd-udi, udi29k
905 A29K VxWorks a29k-*-vxworks
906 AMD 29000 embedded, using EBMON a29k-none-none
907 AMD 29000 embedded with COFF a29k-none-coff
908 AMD 29000 embedded with a.out a29k-none-aout
910 testsuite/gdb.hp/gdb.threads-hp/ directory
912 * REMOVED configurations and files
914 TI TMS320C80 tic80-*-*
916 PowerPC Solaris powerpcle-*-solaris*
917 PowerPC Windows NT powerpcle-*-cygwin32
918 PowerPC Netware powerpc-*-netware*
919 Harris/CXUX m88k m88*-harris-cxux*
920 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
921 ns32k-utek-sysv* ns32k-utek-*
922 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
923 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
924 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
925 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
926 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
928 * Changes to command line processing
930 The new `--args' feature can be used to specify command-line arguments
931 for the inferior from gdb's command line.
933 * Changes to key bindings
935 There is a new `operate-and-get-next' function bound to `C-o'.
937 *** Changes in GDB 5.1.1
939 Fix compile problem on DJGPP.
941 Fix a problem with floating-point registers on the i386 being
944 Fix to stop GDB crashing on .debug_str debug info.
946 Numerous documentation fixes.
948 Numerous testsuite fixes.
950 *** Changes in GDB 5.1:
952 * New native configurations
954 Alpha FreeBSD alpha*-*-freebsd*
955 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
956 MIPS GNU/Linux mips*-*-linux*
957 MIPS SGI Irix 6.x mips*-sgi-irix6*
959 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
963 Motorola 68HC11 and 68HC12 m68hc11-elf
965 UltraSparc running GNU/Linux sparc64-*-linux*
967 * OBSOLETE configurations and files
969 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
970 Harris/CXUX m88k m88*-harris-cxux*
971 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
972 ns32k-utek-sysv* ns32k-utek-*
973 TI TMS320C80 tic80-*-*
975 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
976 PowerPC Solaris powerpcle-*-solaris*
977 PowerPC Windows NT powerpcle-*-cygwin32
978 PowerPC Netware powerpc-*-netware*
979 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
980 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
981 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
982 Apple Macintosh (MPW) host N/A
984 stuff.c (Program to stuff files into a specially prepared space in kdb)
985 kdb-start.c (Main loop for the standalone kernel debugger)
987 Configurations that have been declared obsolete in this release have
988 been commented out. Unless there is activity to revive these
989 configurations, the next release of GDB will have their sources
992 * REMOVED configurations and files
994 Altos 3068 m68*-altos-*
995 Convex c1-*-*, c2-*-*
997 ARM RISCix arm-*-* (as host)
1001 * GDB has been converted to ISO C.
1003 GDB's source code has been converted to ISO C. In particular, the
1004 sources are fully protoized, and rely on standard headers being
1009 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
1011 * The MI enabled by default.
1013 The new machine oriented interface (MI) introduced in GDB 5.0 has been
1014 revised and enabled by default. Packages which use GDB as a debugging
1015 engine behind a UI or another front end are encouraged to switch to
1016 using the GDB/MI interface, instead of the old annotations interface
1017 which is now deprecated.
1019 * Support for debugging Pascal programs.
1021 GDB now includes support for debugging Pascal programs. The following
1022 main features are supported:
1024 - Pascal-specific data types such as sets;
1026 - automatic recognition of Pascal sources based on file-name
1029 - Pascal-style display of data types, variables, and functions;
1031 - a Pascal expression parser.
1033 However, some important features are not yet supported.
1035 - Pascal string operations are not supported at all;
1037 - there are some problems with boolean types;
1039 - Pascal type hexadecimal constants are not supported
1040 because they conflict with the internal variables format;
1042 - support for Pascal objects and classes is not full yet;
1044 - unlike Pascal, GDB is case-sensitive for symbol names.
1046 * Changes in completion.
1048 Commands such as `shell', `run' and `set args', which pass arguments
1049 to inferior programs, now complete on file names, similar to what
1050 users expect at the shell prompt.
1052 Commands which accept locations, such as `disassemble', `print',
1053 `breakpoint', `until', etc. now complete on filenames as well as
1054 program symbols. Thus, if you type "break foob TAB", and the source
1055 files linked into the programs include `foobar.c', that file name will
1056 be one of the candidates for completion. However, file names are not
1057 considered for completion after you typed a colon that delimits a file
1058 name from a name of a function in that file, as in "break foo.c:bar".
1060 `set demangle-style' completes on available demangling styles.
1062 * New platform-independent commands:
1064 It is now possible to define a post-hook for a command as well as a
1065 hook that runs before the command. For more details, see the
1066 documentation of `hookpost' in the GDB manual.
1068 * Changes in GNU/Linux native debugging.
1070 Support for debugging multi-threaded programs has been completely
1071 revised for all platforms except m68k and sparc. You can now debug as
1072 many threads as your system allows you to have.
1074 Attach/detach is supported for multi-threaded programs.
1076 Support for SSE registers was added for x86. This doesn't work for
1077 multi-threaded programs though.
1079 * Changes in MIPS configurations.
1081 Multi-arch support is enabled for all MIPS configurations.
1083 GDB can now be built as native debugger on SGI Irix 6.x systems for
1084 debugging n32 executables. (Debugging 64-bit executables is not yet
1087 * Unified support for hardware watchpoints in all x86 configurations.
1089 Most (if not all) native x86 configurations support hardware-assisted
1090 breakpoints and watchpoints in a unified manner. This support
1091 implements debug register sharing between watchpoints, which allows to
1092 put a virtually infinite number of watchpoints on the same address,
1093 and also supports watching regions up to 16 bytes with several debug
1096 The new maintenance command `maintenance show-debug-regs' toggles
1097 debugging print-outs in functions that insert, remove, and test
1098 watchpoints and hardware breakpoints.
1100 * Changes in the DJGPP native configuration.
1102 New command ``info dos sysinfo'' displays assorted information about
1103 the CPU, OS, memory, and DPMI server.
1105 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
1106 display information about segment descriptors stored in GDT, LDT, and
1109 New commands ``info dos pde'' and ``info dos pte'' display entries
1110 from Page Directory and Page Tables (for now works with CWSDPMI only).
1111 New command ``info dos address-pte'' displays the Page Table entry for
1112 a given linear address.
1114 GDB can now pass command lines longer than 126 characters to the
1115 program being debugged (requires an update to the libdbg.a library
1116 which is part of the DJGPP development kit).
1118 DWARF2 debug info is now supported.
1120 It is now possible to `step' and `next' through calls to `longjmp'.
1122 * Changes in documentation.
1124 All GDB documentation was converted to GFDL, the GNU Free
1125 Documentation License.
1127 Tracepoints-related commands are now fully documented in the GDB
1130 TUI, the Text-mode User Interface, is now documented in the manual.
1132 Tracepoints-related commands are now fully documented in the GDB
1135 The "GDB Internals" manual now has an index. It also includes
1136 documentation of `ui_out' functions, GDB coding standards, x86
1137 hardware watchpoints, and memory region attributes.
1139 * GDB's version number moved to ``version.in''
1141 The Makefile variable VERSION has been replaced by the file
1142 ``version.in''. People creating GDB distributions should update the
1143 contents of this file.
1147 GUD support is now a standard part of the EMACS distribution.
1149 *** Changes in GDB 5.0:
1151 * Improved support for debugging FP programs on x86 targets
1153 Unified and much-improved support for debugging floating-point
1154 programs on all x86 targets. In particular, ``info float'' now
1155 displays the FP registers in the same format on all x86 targets, with
1156 greater level of detail.
1158 * Improvements and bugfixes in hardware-assisted watchpoints
1160 It is now possible to watch array elements, struct members, and
1161 bitfields with hardware-assisted watchpoints. Data-read watchpoints
1162 on x86 targets no longer erroneously trigger when the address is
1165 * Improvements in the native DJGPP version of GDB
1167 The distribution now includes all the scripts and auxiliary files
1168 necessary to build the native DJGPP version on MS-DOS/MS-Windows
1169 machines ``out of the box''.
1171 The DJGPP version can now debug programs that use signals. It is
1172 possible to catch signals that happened in the debuggee, deliver
1173 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
1174 would kill the program being debugged.) Programs that hook hardware
1175 interrupts (keyboard, timer, etc.) can also be debugged.
1177 It is now possible to debug DJGPP programs that redirect their
1178 standard handles or switch them to raw (as opposed to cooked) mode, or
1179 even close them. The command ``run < foo > bar'' works as expected,
1180 and ``info terminal'' reports useful information about the debuggee's
1181 terminal, including raw/cooked mode, redirection, etc.
1183 The DJGPP version now uses termios functions for console I/O, which
1184 enables debugging graphics programs. Interrupting GDB with Ctrl-C
1187 DOS-style file names with drive letters are now fully supported by
1190 It is now possible to debug DJGPP programs that switch their working
1191 directory. It is also possible to rerun the debuggee any number of
1192 times without restarting GDB; thus, you can use the same setup,
1193 breakpoints, etc. for many debugging sessions.
1195 * New native configurations
1197 ARM GNU/Linux arm*-*-linux*
1198 PowerPC GNU/Linux powerpc-*-linux*
1202 Motorola MCore mcore-*-*
1203 x86 VxWorks i[3456]86-*-vxworks*
1204 PowerPC VxWorks powerpc-*-vxworks*
1205 TI TMS320C80 tic80-*-*
1207 * OBSOLETE configurations
1209 Altos 3068 m68*-altos-*
1210 Convex c1-*-*, c2-*-*
1212 ARM RISCix arm-*-* (as host)
1215 Configurations that have been declared obsolete will be commented out,
1216 but the code will be left in place. If there is no activity to revive
1217 these configurations before the next release of GDB, the sources will
1218 be permanently REMOVED.
1220 * Gould support removed
1222 Support for the Gould PowerNode and NP1 has been removed.
1224 * New features for SVR4
1226 On SVR4 native platforms (such as Solaris), if you attach to a process
1227 without first loading a symbol file, GDB will now attempt to locate and
1228 load symbols from the running process's executable file.
1230 * Many C++ enhancements
1232 C++ support has been greatly improved. Overload resolution now works properly
1233 in almost all cases. RTTI support is on the way.
1235 * Remote targets can connect to a sub-program
1237 A popen(3) style serial-device has been added. This device starts a
1238 sub-process (such as a stand-alone simulator) and then communicates
1239 with that. The sub-program to run is specified using the syntax
1240 ``|<program> <args>'' vis:
1242 (gdb) set remotedebug 1
1243 (gdb) target extended-remote |mn10300-elf-sim program-args
1245 * MIPS 64 remote protocol
1247 A long standing bug in the mips64 remote protocol where by GDB
1248 expected certain 32 bit registers (ex SR) to be transfered as 32
1249 instead of 64 bits has been fixed.
1251 The command ``set remote-mips64-transfers-32bit-regs on'' has been
1252 added to provide backward compatibility with older versions of GDB.
1254 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
1256 The command ``set remotebinarydownload'' command has been replaced by
1257 ``set remote X-packet''. Other commands in ``set remote'' family
1258 include ``set remote P-packet''.
1260 * Breakpoint commands accept ranges.
1262 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
1263 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
1264 ``tracepoint passcount'' also accepts a range of tracepoints.
1266 * ``apropos'' command added.
1268 The ``apropos'' command searches through command names and
1269 documentation strings, printing out matches, making it much easier to
1270 try to find a command that does what you are looking for.
1274 A new machine oriented interface (MI) has been added to GDB. This
1275 interface is designed for debug environments running GDB as a separate
1276 process. This is part of the long term libGDB project. See the
1277 "GDB/MI" chapter of the GDB manual for further information. It can be
1278 enabled by configuring with:
1280 .../configure --enable-gdbmi
1282 *** Changes in GDB-4.18:
1284 * New native configurations
1286 HP-UX 10.20 hppa*-*-hpux10.20
1287 HP-UX 11.x hppa*-*-hpux11.0*
1288 M68K GNU/Linux m68*-*-linux*
1292 Fujitsu FR30 fr30-*-elf*
1293 Intel StrongARM strongarm-*-*
1294 Mitsubishi D30V d30v-*-*
1296 * OBSOLETE configurations
1298 Gould PowerNode, NP1 np1-*-*, pn-*-*
1300 Configurations that have been declared obsolete will be commented out,
1301 but the code will be left in place. If there is no activity to revive
1302 these configurations before the next release of GDB, the sources will
1303 be permanently REMOVED.
1307 As a compatibility experiment, GDB's source files buildsym.h and
1308 buildsym.c have been converted to pure standard C, no longer
1309 containing any K&R compatibility code. We believe that all systems in
1310 use today either come with a standard C compiler, or have a GCC port
1311 available. If this is not true, please report the affected
1312 configuration to bug-gdb@gnu.org immediately. See the README file for
1313 information about getting a standard C compiler if you don't have one
1318 GDB now uses readline 2.2.
1320 * set extension-language
1322 You can now control the mapping between filename extensions and source
1323 languages by using the `set extension-language' command. For instance,
1324 you can ask GDB to treat .c files as C++ by saying
1325 set extension-language .c c++
1326 The command `info extensions' lists all of the recognized extensions
1327 and their associated languages.
1329 * Setting processor type for PowerPC and RS/6000
1331 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
1332 you can use the `set processor' command to specify what variant of the
1333 PowerPC family you are debugging. The command
1337 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
1338 following PowerPC and RS6000 variants:
1340 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
1341 rs6000 IBM RS6000 ("POWER") architecture, user-level view
1343 403GC IBM PowerPC 403GC
1344 505 Motorola PowerPC 505
1345 860 Motorola PowerPC 860 or 850
1346 601 Motorola PowerPC 601
1347 602 Motorola PowerPC 602
1348 603 Motorola/IBM PowerPC 603 or 603e
1349 604 Motorola PowerPC 604 or 604e
1350 750 Motorola/IBM PowerPC 750 or 750
1352 At the moment, this command just tells GDB what to name the
1353 special-purpose processor registers. Since almost all the affected
1354 registers are inaccessible to user-level programs, this command is
1355 only useful for remote debugging in its present form.
1359 Thanks to a major code donation from Hewlett-Packard, GDB now has much
1360 more extensive support for HP-UX. Added features include shared
1361 library support, kernel threads and hardware watchpoints for 11.00,
1362 support for HP's ANSI C and C++ compilers, and a compatibility mode
1363 for xdb and dbx commands.
1367 HP's donation includes the new concept of catchpoints, which is a
1368 generalization of the old catch command. On HP-UX, it is now possible
1369 to catch exec, fork, and vfork, as well as library loading.
1371 This means that the existing catch command has changed; its first
1372 argument now specifies the type of catch to be set up. See the
1373 output of "help catch" for a list of catchpoint types.
1375 * Debugging across forks
1377 On HP-UX, you can choose which process to debug when a fork() happens
1382 HP has donated a curses-based terminal user interface (TUI). To get
1383 it, build with --enable-tui. Although this can be enabled for any
1384 configuration, at present it only works for native HP debugging.
1386 * GDB remote protocol additions
1388 A new protocol packet 'X' that writes binary data is now available.
1389 Default behavior is to try 'X', then drop back to 'M' if the stub
1390 fails to respond. The settable variable `remotebinarydownload'
1391 allows explicit control over the use of 'X'.
1393 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
1394 full 64-bit address. The command
1396 set remoteaddresssize 32
1398 can be used to revert to the old behaviour. For existing remote stubs
1399 the change should not be noticed, as the additional address information
1402 In order to assist in debugging stubs, you may use the maintenance
1403 command `packet' to send any text string to the stub. For instance,
1405 maint packet heythere
1407 sends the packet "$heythere#<checksum>". Note that it is very easy to
1408 disrupt a debugging session by sending the wrong packet at the wrong
1411 The compare-sections command allows you to compare section data on the
1412 target to what is in the executable file without uploading or
1413 downloading, by comparing CRC checksums.
1415 * Tracing can collect general expressions
1417 You may now collect general expressions at tracepoints. This requires
1418 further additions to the target-side stub; see tracepoint.c and
1419 doc/agentexpr.texi for further details.
1421 * mask-address variable for Mips
1423 For Mips targets, you may control the zeroing of the upper 32 bits of
1424 a 64-bit address by entering `set mask-address on'. This is mainly
1425 of interest to users of embedded R4xxx and R5xxx processors.
1427 * Higher serial baud rates
1429 GDB's serial code now allows you to specify baud rates 57600, 115200,
1430 230400, and 460800 baud. (Note that your host system may not be able
1431 to achieve all of these rates.)
1435 The i960 configuration now includes an initial implementation of a
1436 builtin simulator, contributed by Jim Wilson.
1439 *** Changes in GDB-4.17:
1441 * New native configurations
1443 Alpha GNU/Linux alpha*-*-linux*
1444 Unixware 2.x i[3456]86-unixware2*
1445 Irix 6.x mips*-sgi-irix6*
1446 PowerPC GNU/Linux powerpc-*-linux*
1447 PowerPC Solaris powerpcle-*-solaris*
1448 Sparc GNU/Linux sparc-*-linux*
1449 Motorola sysV68 R3V7.1 m68k-motorola-sysv
1453 Argonaut Risc Chip (ARC) arc-*-*
1454 Hitachi H8/300S h8300*-*-*
1455 Matsushita MN10200 w/simulator mn10200-*-*
1456 Matsushita MN10300 w/simulator mn10300-*-*
1457 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
1458 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
1459 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
1460 Mitsubishi D10V w/simulator d10v-*-*
1461 Mitsubishi M32R/D w/simulator m32r-*-elf*
1462 Tsqware Sparclet sparclet-*-*
1463 NEC V850 w/simulator v850-*-*
1465 * New debugging protocols
1467 ARM with RDI protocol arm*-*-*
1468 M68K with dBUG monitor m68*-*-{aout,coff,elf}
1469 DDB and LSI variants of PMON protocol mips*-*-*
1470 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
1471 PowerPC with SDS protocol powerpc{,le}-*-eabi
1472 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
1476 All configurations can now understand and use the DWARF 2 debugging
1477 format. The choice is automatic, if the symbol file contains DWARF 2
1482 GDB now includes basic Java language support. This support is
1483 only useful with Java compilers that produce native machine code.
1485 * solib-absolute-prefix and solib-search-path
1487 For SunOS and SVR4 shared libraries, you may now set the prefix for
1488 loading absolute shared library symbol files, and the search path for
1489 locating non-absolute shared library symbol files.
1491 * Live range splitting
1493 GDB can now effectively debug code for which GCC has performed live
1494 range splitting as part of its optimization. See gdb/doc/LRS for
1495 more details on the expected format of the stabs information.
1499 GDB's support for the GNU Hurd, including thread debugging, has been
1500 updated to work with current versions of the Hurd.
1504 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
1505 instruction set. ARM GDB automatically detects when Thumb
1506 instructions are in use, and adjusts disassembly and backtracing
1511 GDB's MIPS target configurations now handle the MIP16 16-bit
1516 GDB now includes support for overlays; if an executable has been
1517 linked such that multiple sections are based at the same address, GDB
1518 will decide which section to use for symbolic info. You can choose to
1519 control the decision manually, using overlay commands, or implement
1520 additional target-side support and use "overlay load-target" to bring
1521 in the overlay mapping. Do "help overlay" for more detail.
1525 The command "info symbol <address>" displays information about
1526 the symbol at the specified address.
1530 The standard remote protocol now includes an extension that allows
1531 asynchronous collection and display of trace data. This requires
1532 extensive support in the target-side debugging stub. Tracing mode
1533 includes a new interaction mode in GDB and new commands: see the
1534 file tracepoint.c for more details.
1538 Configurations for embedded MIPS now include a simulator contributed
1539 by Cygnus Solutions. The simulator supports the instruction sets
1540 of most MIPS variants.
1544 Sparc configurations may now include the ERC32 simulator contributed
1545 by the European Space Agency. The simulator is not built into
1546 Sparc targets by default; configure with --enable-sim to include it.
1550 For target configurations that may include multiple variants of a
1551 basic architecture (such as MIPS and SH), you may now set the
1552 architecture explicitly. "set arch" sets, "info arch" lists
1553 the possible architectures.
1555 *** Changes in GDB-4.16:
1557 * New native configurations
1559 Windows 95, x86 Windows NT i[345]86-*-cygwin32
1560 M68K NetBSD m68k-*-netbsd*
1561 PowerPC AIX 4.x powerpc-*-aix*
1562 PowerPC MacOS powerpc-*-macos*
1563 PowerPC Windows NT powerpcle-*-cygwin32
1564 RS/6000 AIX 4.x rs6000-*-aix4*
1568 ARM with RDP protocol arm-*-*
1569 I960 with MON960 i960-*-coff
1570 MIPS VxWorks mips*-*-vxworks*
1571 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
1572 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
1574 Matra Sparclet sparclet-*-*
1578 The powerpc-eabi configuration now includes the PSIM simulator,
1579 contributed by Andrew Cagney, with assistance from Mike Meissner.
1580 PSIM is a very elaborate model of the PowerPC, including not only
1581 basic instruction set execution, but also details of execution unit
1582 performance and I/O hardware. See sim/ppc/README for more details.
1586 GDB now works with Solaris 2.5.
1588 * Windows 95/NT native
1590 GDB will now work as a native debugger on Windows 95 and Windows NT.
1591 To build it from source, you must use the "gnu-win32" environment,
1592 which uses a DLL to emulate enough of Unix to run the GNU tools.
1593 Further information, binaries, and sources are available at
1594 ftp.cygnus.com, under pub/gnu-win32.
1596 * dont-repeat command
1598 If a user-defined command includes the command `dont-repeat', then the
1599 command will not be repeated if the user just types return. This is
1600 useful if the command is time-consuming to run, so that accidental
1601 extra keystrokes don't run the same command many times.
1603 * Send break instead of ^C
1605 The standard remote protocol now includes an option to send a break
1606 rather than a ^C to the target in order to interrupt it. By default,
1607 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
1609 * Remote protocol timeout
1611 The standard remote protocol includes a new variable `remotetimeout'
1612 that allows you to set the number of seconds before GDB gives up trying
1613 to read from the target. The default value is 2.
1615 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
1617 By default GDB will automatically keep track of objects as they are
1618 loaded and unloaded by the dynamic linker. By using the command `set
1619 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
1620 when shared library events occur, thus allowing you to set breakpoints
1621 in shared libraries which are explicitly loaded by the inferior.
1623 Note this feature does not work on hpux8. On hpux9 you must link
1624 /usr/lib/end.o into your program. This feature should work
1625 automatically on hpux10.
1627 * Irix 5.x hardware watchpoint support
1629 Irix 5 configurations now support the use of hardware watchpoints.
1631 * Mips protocol "SYN garbage limit"
1633 When debugging a Mips target using the `target mips' protocol, you
1634 may set the number of characters that GDB will ignore by setting
1635 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
1636 every character. The default value is 1050.
1638 * Recording and replaying remote debug sessions
1640 If you set `remotelogfile' to the name of a file, gdb will write to it
1641 a recording of a remote debug session. This recording may then be
1642 replayed back to gdb using "gdbreplay". See gdbserver/README for
1643 details. This is useful when you have a problem with GDB while doing
1644 remote debugging; you can make a recording of the session and send it
1645 to someone else, who can then recreate the problem.
1647 * Speedups for remote debugging
1649 GDB includes speedups for downloading and stepping MIPS systems using
1650 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
1651 and more efficient S-record downloading.
1653 * Memory use reductions and statistics collection
1655 GDB now uses less memory and reports statistics about memory usage.
1656 Try the `maint print statistics' command, for example.
1658 *** Changes in GDB-4.15:
1660 * Psymtabs for XCOFF
1662 The symbol reader for AIX GDB now uses partial symbol tables. This
1663 can greatly improve startup time, especially for large executables.
1665 * Remote targets use caching
1667 Remote targets now use a data cache to speed up communication with the
1668 remote side. The data cache could lead to incorrect results because
1669 it doesn't know about volatile variables, thus making it impossible to
1670 debug targets which use memory mapped I/O devices. `set remotecache
1671 off' turns the the data cache off.
1673 * Remote targets may have threads
1675 The standard remote protocol now includes support for multiple threads
1676 in the target system, using new protocol commands 'H' and 'T'. See
1677 gdb/remote.c for details.
1681 If GDB is configured with `--enable-netrom', then it will include
1682 support for the NetROM ROM emulator from XLNT Designs. The NetROM
1683 acts as though it is a bank of ROM on the target board, but you can
1684 write into it over the network. GDB's support consists only of
1685 support for fast loading into the emulated ROM; to debug, you must use
1686 another protocol, such as standard remote protocol. The usual
1687 sequence is something like
1689 target nrom <netrom-hostname>
1691 target remote <netrom-hostname>:1235
1695 GDB now includes support for the Apple Macintosh, as a host only. It
1696 may be run as either an MPW tool or as a standalone application, and
1697 it can debug through the serial port. All the usual GDB commands are
1698 available, but to the target command, you must supply "serial" as the
1699 device type instead of "/dev/ttyXX". See mpw-README in the main
1700 directory for more information on how to build. The MPW configuration
1701 scripts */mpw-config.in support only a few targets, and only the
1702 mips-idt-ecoff target has been tested.
1706 GDB configuration now uses autoconf. This is not user-visible,
1707 but does simplify configuration and building.
1711 GDB now supports hpux10.
1713 *** Changes in GDB-4.14:
1715 * New native configurations
1717 x86 FreeBSD i[345]86-*-freebsd
1718 x86 NetBSD i[345]86-*-netbsd
1719 NS32k NetBSD ns32k-*-netbsd
1720 Sparc NetBSD sparc-*-netbsd
1724 A29K VxWorks a29k-*-vxworks
1725 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1726 CPU32 EST-300 emulator m68*-*-est*
1727 PowerPC ELF powerpc-*-elf
1730 * Alpha OSF/1 support for procfs
1732 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1733 possible to attach to running processes. As the mounting of the /proc
1734 filesystem is optional on the Alpha, GDB automatically determines
1735 the availability of /proc during startup. This can lead to problems
1736 if /proc is unmounted after GDB has been started.
1738 * Arguments to user-defined commands
1740 User commands may accept up to 10 arguments separated by whitespace.
1741 Arguments are accessed within the user command via $arg0..$arg9. A
1744 print $arg0 + $arg1 + $arg2
1746 To execute the command use:
1749 Defines the command "adder" which prints the sum of its three arguments.
1750 Note the arguments are text substitutions, so they may reference variables,
1751 use complex expressions, or even perform inferior function calls.
1753 * New `if' and `while' commands
1755 This makes it possible to write more sophisticated user-defined
1756 commands. Both commands take a single argument, which is the
1757 expression to evaluate, and must be followed by the commands to
1758 execute, one per line, if the expression is nonzero, the list being
1759 terminated by the word `end'. The `if' command list may include an
1760 `else' word, which causes the following commands to be executed only
1761 if the expression is zero.
1763 * Fortran source language mode
1765 GDB now includes partial support for Fortran 77. It will recognize
1766 Fortran programs and can evaluate a subset of Fortran expressions, but
1767 variables and functions may not be handled correctly. GDB will work
1768 with G77, but does not yet know much about symbols emitted by other
1771 * Better HPUX support
1773 Most debugging facilities now work on dynamic executables for HPPAs
1774 running hpux9 or later. You can attach to running dynamically linked
1775 processes, but by default the dynamic libraries will be read-only, so
1776 for instance you won't be able to put breakpoints in them. To change
1777 that behavior do the following before running the program:
1783 This will cause the libraries to be mapped private and read-write.
1784 To revert to the normal behavior, do this:
1790 You cannot set breakpoints or examine data in the library until after
1791 the library is loaded if the function/data symbols do not have
1794 GDB can now also read debug symbols produced by the HP C compiler on
1795 HPPAs (sorry, no C++, Fortran or 68k support).
1797 * Target byte order now dynamically selectable
1799 You can choose which byte order to use with a target system, via the
1800 commands "set endian big" and "set endian little", and you can see the
1801 current setting by using "show endian". You can also give the command
1802 "set endian auto", in which case GDB will use the byte order
1803 associated with the executable. Currently, only embedded MIPS
1804 configurations support dynamic selection of target byte order.
1806 * New DOS host serial code
1808 This version uses DPMI interrupts to handle buffered I/O, so you
1809 no longer need to run asynctsr when debugging boards connected to
1812 *** Changes in GDB-4.13:
1814 * New "complete" command
1816 This lists all the possible completions for the rest of the line, if it
1817 were to be given as a command itself. This is intended for use by emacs.
1819 * Trailing space optional in prompt
1821 "set prompt" no longer adds a space for you after the prompt you set. This
1822 allows you to set a prompt which ends in a space or one that does not.
1824 * Breakpoint hit counts
1826 "info break" now displays a count of the number of times the breakpoint
1827 has been hit. This is especially useful in conjunction with "ignore"; you
1828 can ignore a large number of breakpoint hits, look at the breakpoint info
1829 to see how many times the breakpoint was hit, then run again, ignoring one
1830 less than that number, and this will get you quickly to the last hit of
1833 * Ability to stop printing at NULL character
1835 "set print null-stop" will cause GDB to stop printing the characters of
1836 an array when the first NULL is encountered. This is useful when large
1837 arrays actually contain only short strings.
1839 * Shared library breakpoints
1841 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1842 breakpoints in shared libraries before the executable is run.
1844 * Hardware watchpoints
1846 There is a new hardware breakpoint for the watch command for sparclite
1847 targets. See gdb/sparclite/hw_breakpoint.note.
1849 Hardware watchpoints are also now supported under GNU/Linux.
1853 Annotations have been added. These are for use with graphical interfaces,
1854 and are still experimental. Currently only gdba.el uses these.
1856 * Improved Irix 5 support
1858 GDB now works properly with Irix 5.2.
1860 * Improved HPPA support
1862 GDB now works properly with the latest GCC and GAS.
1864 * New native configurations
1866 Sequent PTX4 i[34]86-sequent-ptx4
1867 HPPA running OSF/1 hppa*-*-osf*
1868 Atari TT running SVR4 m68*-*-sysv4*
1869 RS/6000 LynxOS rs6000-*-lynxos*
1873 OS/9000 i[34]86-*-os9k
1874 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1877 * Hitachi SH7000 and E7000-PC ICE support
1879 There is now support for communicating with the Hitachi E7000-PC ICE.
1880 This is available automatically when GDB is configured for the SH.
1884 As usual, a variety of small fixes and improvements, both generic
1885 and configuration-specific. See the ChangeLog for more detail.
1887 *** Changes in GDB-4.12:
1889 * Irix 5 is now supported
1893 GDB-4.12 on the HPPA has a number of changes which make it unable
1894 to debug the output from the currently released versions of GCC and
1895 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1896 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1897 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1900 *** Changes in GDB-4.11:
1902 * User visible changes:
1906 The "set remotedebug" option is now consistent between the mips remote
1907 target, remote targets using the gdb-specific protocol, UDI (AMD's
1908 debug protocol for the 29k) and the 88k bug monitor. It is now an
1909 integer specifying a debug level (normally 0 or 1, but 2 means more
1910 debugging info for the mips target).
1912 * DEC Alpha native support
1914 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1915 debug info, but GDB works fairly well with the DEC compiler and should
1916 work with a future GCC release. See the README file for a few
1917 Alpha-specific notes.
1919 * Preliminary thread implementation
1921 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1923 * LynxOS native and target support for 386
1925 This release has been hosted on LynxOS 2.2, and also can be configured
1926 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1929 * Improvements in C++ mangling/demangling.
1931 This release has much better g++ debugging, specifically in name
1932 mangling/demangling, virtual function calls, print virtual table,
1933 call methods, ...etc.
1935 *** Changes in GDB-4.10:
1937 * User visible changes:
1939 Remote debugging using the GDB-specific (`target remote') protocol now
1940 supports the `load' command. This is only useful if you have some
1941 other way of getting the stub to the target system, and you can put it
1942 somewhere in memory where it won't get clobbered by the download.
1944 Filename completion now works.
1946 When run under emacs mode, the "info line" command now causes the
1947 arrow to point to the line specified. Also, "info line" prints
1948 addresses in symbolic form (as well as hex).
1950 All vxworks based targets now support a user settable option, called
1951 vxworks-timeout. This option represents the number of seconds gdb
1952 should wait for responses to rpc's. You might want to use this if
1953 your vxworks target is, perhaps, a slow software simulator or happens
1954 to be on the far side of a thin network line.
1958 This release contains support for using a DEC alpha as a GDB host for
1959 cross debugging. Native alpha debugging is not supported yet.
1962 *** Changes in GDB-4.9:
1966 This is the first GDB release which is accompanied by a matching testsuite.
1967 The testsuite requires installation of dejagnu, which should be available
1968 via ftp from most sites that carry GNU software.
1972 'Cfront' style demangling has had its name changed to 'ARM' style, to
1973 emphasize that it was written from the specifications in the C++ Annotated
1974 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1975 disclaimers, it still generated too much confusion with users attempting to
1976 use gdb with AT&T cfront.
1980 GDB now uses a standard remote interface to a simulator library.
1981 So far, the library contains simulators for the Zilog Z8001/2, the
1982 Hitachi H8/300, H8/500 and Super-H.
1984 * New targets supported
1986 H8/300 simulator h8300-hitachi-hms or h8300hms
1987 H8/500 simulator h8500-hitachi-hms or h8500hms
1988 SH simulator sh-hitachi-hms or sh
1989 Z8000 simulator z8k-zilog-none or z8ksim
1990 IDT MIPS board over serial line mips-idt-ecoff
1992 Cross-debugging to GO32 targets is supported. It requires a custom
1993 version of the i386-stub.c module which is integrated with the
1994 GO32 memory extender.
1996 * New remote protocols
1998 MIPS remote debugging protocol.
2000 * New source languages supported
2002 This version includes preliminary support for Chill, a Pascal like language
2003 used by telecommunications companies. Chill support is also being integrated
2004 into the GNU compiler, but we don't know when it will be publically available.
2007 *** Changes in GDB-4.8:
2009 * HP Precision Architecture supported
2011 GDB now supports HP PA-RISC machines running HPUX. A preliminary
2012 version of this support was available as a set of patches from the
2013 University of Utah. GDB does not support debugging of programs
2014 compiled with the HP compiler, because HP will not document their file
2015 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
2016 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
2018 Many problems in the preliminary version have been fixed.
2020 * Faster and better demangling
2022 We have improved template demangling and fixed numerous bugs in the GNU style
2023 demangler. It can now handle type modifiers such as `static' or `const'. Wide
2024 character types (wchar_t) are now supported. Demangling of each symbol is now
2025 only done once, and is cached when the symbol table for a file is read in.
2026 This results in a small increase in memory usage for C programs, a moderate
2027 increase in memory usage for C++ programs, and a fantastic speedup in
2030 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
2031 from the specifications in the Annotated Reference Manual, which AT&T's
2032 compiler does not actually implement.
2034 * G++ multiple inheritance compiler problem
2036 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
2037 inheritance lattices was reworked to properly discover ambiguities. We
2038 recently found an example which causes this new algorithm to fail in a
2039 very subtle way, producing bad debug information for those classes.
2040 The file 'gcc.patch' (in this directory) can be applied to gcc to
2041 circumvent the problem. A future GCC release will contain a complete
2044 The previous G++ debug info problem (mentioned below for the gdb-4.7
2045 release) is fixed in gcc version 2.3.2.
2047 * Improved configure script
2049 The `configure' script will now attempt to guess your system type if
2050 you don't supply a host system type. The old scheme of supplying a
2051 host system triplet is preferable over using this. All the magic is
2052 done in the new `config.guess' script. Examine it for details.
2054 We have also brought our configure script much more in line with the FSF's
2055 version. It now supports the --with-xxx options. In particular,
2056 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
2057 The resulting GDB will not be able to read arbitrary object file formats --
2058 only the format ``expected'' to be used on the configured target system.
2059 We hope to make this the default in a future release.
2061 * Documentation improvements
2063 There's new internal documentation on how to modify GDB, and how to
2064 produce clean changes to the code. We implore people to read it
2065 before submitting changes.
2067 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
2068 M4 macros. The new texinfo.tex is provided in this release. Pre-built
2069 `info' files are also provided. To build `info' files from scratch,
2070 you will need the latest `makeinfo' release, which will be available in
2071 a future texinfo-X.Y release.
2073 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
2074 We're not sure exactly which versions have this problem, but it has
2075 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
2076 or better. If that isn't possible, there is a patch in
2077 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
2078 around this problem.
2082 GDB now supports array constants that can be used in expressions typed in by
2083 the user. The syntax is `{element, element, ...}'. Ie: you can now type
2084 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
2087 The new directory `gdb/sparclite' contains a program that demonstrates
2088 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
2090 * New native hosts supported
2092 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
2093 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
2095 * New targets supported
2097 AMD 29k family via UDI a29k-amd-udi or udi29k
2099 * New file formats supported
2101 BFD now supports reading HP/PA-RISC executables (SOM file format?),
2102 HPUX core files, and SCO 3.2v2 core files.
2106 Attaching to processes now works again; thanks for the many bug reports.
2108 We have also stomped on a bunch of core dumps caused by
2109 printf_filtered("%s") problems.
2111 We eliminated a copyright problem on the rpc and ptrace header files
2112 for VxWorks, which was discovered at the last minute during the 4.7
2113 release. You should now be able to build a VxWorks GDB.
2115 You can now interrupt gdb while an attached process is running. This
2116 will cause the attached process to stop, and give control back to GDB.
2118 We fixed problems caused by using too many file descriptors
2119 for reading symbols from object files and libraries. This was
2120 especially a problem for programs that used many (~100) shared
2123 The `step' command now only enters a subroutine if there is line number
2124 information for the subroutine. Otherwise it acts like the `next'
2125 command. Previously, `step' would enter subroutines if there was
2126 any debugging information about the routine. This avoids problems
2127 when using `cc -g1' on MIPS machines.
2129 * Internal improvements
2131 GDB's internal interfaces have been improved to make it easier to support
2132 debugging of multiple languages in the future.
2134 GDB now uses a common structure for symbol information internally.
2135 Minimal symbols (derived from linkage symbols in object files), partial
2136 symbols (from a quick scan of debug information), and full symbols
2137 contain a common subset of information, making it easier to write
2138 shared code that handles any of them.
2140 * New command line options
2142 We now accept --silent as an alias for --quiet.
2146 The memory-mapped-malloc library is now licensed under the GNU Library
2147 General Public License.
2149 *** Changes in GDB-4.7:
2151 * Host/native/target split
2153 GDB has had some major internal surgery to untangle the support for
2154 hosts and remote targets. Now, when you configure GDB for a remote
2155 target, it will no longer load in all of the support for debugging
2156 local programs on the host. When fully completed and tested, this will
2157 ensure that arbitrary host/target combinations are possible.
2159 The primary conceptual shift is to separate the non-portable code in
2160 GDB into three categories. Host specific code is required any time GDB
2161 is compiled on that host, regardless of the target. Target specific
2162 code relates to the peculiarities of the target, but can be compiled on
2163 any host. Native specific code is everything else: it can only be
2164 built when the host and target are the same system. Child process
2165 handling and core file support are two common `native' examples.
2167 GDB's use of /proc for controlling Unix child processes is now cleaner.
2168 It has been split out into a single module under the `target_ops' vector,
2169 plus two native-dependent functions for each system that uses /proc.
2171 * New hosts supported
2173 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
2174 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2175 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
2177 * New targets supported
2179 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
2180 68030 and CPU32 m68030-*-*, m68332-*-*
2182 * New native hosts supported
2184 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2185 (386bsd is not well tested yet)
2186 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
2188 * New file formats supported
2190 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
2191 supports reading of `a.out.adobe' object files, which are an a.out
2192 format extended with minimal information about multiple sections.
2196 `show copying' is the same as the old `info copying'.
2197 `show warranty' is the same as `info warrantee'.
2198 These were renamed for consistency. The old commands continue to work.
2200 `info handle' is a new alias for `info signals'.
2202 You can now define pre-command hooks, which attach arbitrary command
2203 scripts to any command. The commands in the hook will be executed
2204 prior to the user's command. You can also create a hook which will be
2205 executed whenever the program stops. See gdb.texinfo.
2209 We now deal with Cfront style name mangling, and can even extract type
2210 info from mangled symbols. GDB can automatically figure out which
2211 symbol mangling style your C++ compiler uses.
2213 Calling of methods and virtual functions has been improved as well.
2217 The crash that occured when debugging Sun Ansi-C compiled binaries is
2218 fixed. This was due to mishandling of the extra N_SO stabs output
2221 We also finally got Ultrix 4.2 running in house, and fixed core file
2222 support, with help from a dozen people on the net.
2224 John M. Farrell discovered that the reason that single-stepping was so
2225 slow on all of the Mips based platforms (primarily SGI and DEC) was
2226 that we were trying to demangle and lookup a symbol used for internal
2227 purposes on every instruction that was being stepped through. Changing
2228 the name of that symbol so that it couldn't be mistaken for a C++
2229 mangled symbol sped things up a great deal.
2231 Rich Pixley sped up symbol lookups in general by getting much smarter
2232 about when C++ symbol mangling is necessary. This should make symbol
2233 completion (TAB on the command line) much faster. It's not as fast as
2234 we'd like, but it's significantly faster than gdb-4.6.
2238 A new user controllable variable 'call_scratch_address' can
2239 specify the location of a scratch area to be used when GDB
2240 calls a function in the target. This is necessary because the
2241 usual method of putting the scratch area on the stack does not work
2242 in systems that have separate instruction and data spaces.
2244 We integrated changes to support the 29k UDI (Universal Debugger
2245 Interface), but discovered at the last minute that we didn't have all
2246 of the appropriate copyright paperwork. We are working with AMD to
2247 resolve this, and hope to have it available soon.
2251 We have sped up the remote serial line protocol, especially for targets
2252 with lots of registers. It now supports a new `expedited status' ('T')
2253 message which can be used in place of the existing 'S' status message.
2254 This allows the remote stub to send only the registers that GDB
2255 needs to make a quick decision about single-stepping or conditional
2256 breakpoints, eliminating the need to fetch the entire register set for
2257 each instruction being stepped through.
2259 The GDB remote serial protocol now implements a write-through cache for
2260 registers, only re-reading the registers if the target has run.
2262 There is also a new remote serial stub for SPARC processors. You can
2263 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
2264 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
2265 processor with a serial port.
2269 Configure.in files have become much easier to read and modify. A new
2270 `table driven' format makes it more obvious what configurations are
2271 supported, and what files each one uses.
2275 There is a new opcodes library which will eventually contain all of the
2276 disassembly routines and opcode tables. At present, it only contains
2277 Sparc and Z8000 routines. This will allow the assembler, debugger, and
2278 disassembler (binutils/objdump) to share these routines.
2280 The libiberty library is now copylefted under the GNU Library General
2281 Public License. This allows more liberal use, and was done so libg++
2282 can use it. This makes no difference to GDB, since the Library License
2283 grants all the rights from the General Public License.
2287 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
2288 reference to the stabs symbol info used by the debugger. It is (as far
2289 as we know) the only published document on this fascinating topic. We
2290 encourage you to read it, compare it to the stabs information on your
2291 system, and send improvements on the document in general (to
2292 bug-gdb@prep.ai.mit.edu).
2294 And, of course, many bugs have been fixed.
2297 *** Changes in GDB-4.6:
2299 * Better support for C++ function names
2301 GDB now accepts as input the "demangled form" of C++ overloaded function
2302 names and member function names, and can do command completion on such names
2303 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
2304 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
2305 Make use of command completion, it is your friend.
2307 GDB also now accepts a variety of C++ mangled symbol formats. They are
2308 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
2309 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
2310 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
2311 for the list of formats.
2313 * G++ symbol mangling problem
2315 Recent versions of gcc have a bug in how they emit debugging information for
2316 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
2317 directory) can be applied to gcc to fix the problem. Alternatively, if you
2318 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
2319 usual symptom is difficulty with setting breakpoints on methods. GDB complains
2320 about the method being non-existent. (We believe that version 2.2.2 of GCC has
2323 * New 'maintenance' command
2325 All of the commands related to hacking GDB internals have been moved out of
2326 the main command set, and now live behind the 'maintenance' command. This
2327 can also be abbreviated as 'mt'. The following changes were made:
2329 dump-me -> maintenance dump-me
2330 info all-breakpoints -> maintenance info breakpoints
2331 printmsyms -> maintenance print msyms
2332 printobjfiles -> maintenance print objfiles
2333 printpsyms -> maintenance print psymbols
2334 printsyms -> maintenance print symbols
2336 The following commands are new:
2338 maintenance demangle Call internal GDB demangler routine to
2339 demangle a C++ link name and prints the result.
2340 maintenance print type Print a type chain for a given symbol
2342 * Change to .gdbinit file processing
2344 We now read the $HOME/.gdbinit file before processing the argv arguments
2345 (e.g. reading symbol files or core files). This allows global parameters to
2346 be set, which will apply during the symbol reading. The ./.gdbinit is still
2347 read after argv processing.
2349 * New hosts supported
2351 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
2353 GNU/Linux support i386-unknown-linux or linux
2355 We are also including code to support the HP/PA running BSD and HPUX. This
2356 is almost guaranteed not to work, as we didn't have time to test or build it
2357 for this release. We are including it so that the more adventurous (or
2358 masochistic) of you can play with it. We also had major problems with the
2359 fact that the compiler that we got from HP doesn't support the -g option.
2362 * New targets supported
2364 Hitachi H8/300 h8300-hitachi-hms or h8300hms
2366 * More smarts about finding #include files
2368 GDB now remembers the compilation directory for all include files, and for
2369 all files from which C is generated (like yacc and lex sources). This
2370 greatly improves GDB's ability to find yacc/lex sources, and include files,
2371 especially if you are debugging your program from a directory different from
2372 the one that contains your sources.
2374 We also fixed a bug which caused difficulty with listing and setting
2375 breakpoints in include files which contain C code. (In the past, you had to
2376 try twice in order to list an include file that you hadn't looked at before.)
2378 * Interesting infernals change
2380 GDB now deals with arbitrary numbers of sections, where the symbols for each
2381 section must be relocated relative to that section's landing place in the
2382 target's address space. This work was needed to support ELF with embedded
2383 stabs used by Solaris-2.0.
2385 * Bug fixes (of course!)
2387 There have been loads of fixes for the following things:
2388 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
2389 i960, stabs, DOS(GO32), procfs, etc...
2391 See the ChangeLog for details.
2393 *** Changes in GDB-4.5:
2395 * New machines supported (host and target)
2397 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
2399 SGI Irix-4.x mips-sgi-irix4 or iris4
2401 * New malloc package
2403 GDB now uses a new memory manager called mmalloc, based on gmalloc.
2404 Mmalloc is capable of handling mutiple heaps of memory. It is also
2405 capable of saving a heap to a file, and then mapping it back in later.
2406 This can be used to greatly speedup the startup of GDB by using a
2407 pre-parsed symbol table which lives in a mmalloc managed heap. For
2408 more details, please read mmalloc/mmalloc.texi.
2412 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
2413 'help info proc' for details.
2415 * MIPS ecoff symbol table format
2417 The code that reads MIPS symbol table format is now supported on all hosts.
2418 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
2421 * File name changes for MS-DOS
2423 Many files in the config directories have been renamed to make it easier to
2424 support GDB on MS-DOSe systems (which have very restrictive file name
2425 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
2426 environment) is close to working but has some remaining problems. Note
2427 that debugging of DOS programs is not supported, due to limitations
2428 in the ``operating system'', but it can be used to host cross-debugging.
2430 * Cross byte order fixes
2432 Many fixes have been made to support cross debugging of Sparc and MIPS
2433 targets from hosts whose byte order differs.
2435 * New -mapped and -readnow options
2437 If memory-mapped files are available on your system through the 'mmap'
2438 system call, you can use the -mapped option on the `file' or
2439 `symbol-file' commands to cause GDB to write the symbols from your
2440 program into a reusable file. If the program you are debugging is
2441 called `/path/fred', the mapped symbol file will be `./fred.syms'.
2442 Future GDB debugging sessions will notice the presence of this file,
2443 and will quickly map in symbol information from it, rather than reading
2444 the symbol table from the executable program. Using the '-mapped'
2445 option in a GDB `file' or `symbol-file' command has the same effect as
2446 starting GDB with the '-mapped' command-line option.
2448 You can cause GDB to read the entire symbol table immediately by using
2449 the '-readnow' option with any of the commands that load symbol table
2450 information (or on the GDB command line). This makes the command
2451 slower, but makes future operations faster.
2453 The -mapped and -readnow options are typically combined in order to
2454 build a `fred.syms' file that contains complete symbol information.
2455 A simple GDB invocation to do nothing but build a `.syms' file for future
2458 gdb -batch -nx -mapped -readnow programname
2460 The `.syms' file is specific to the host machine on which GDB is run.
2461 It holds an exact image of GDB's internal symbol table. It cannot be
2462 shared across multiple host platforms.
2464 * longjmp() handling
2466 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
2467 siglongjmp() without losing control. This feature has not yet been ported to
2468 all systems. It currently works on many 386 platforms, all MIPS-based
2469 platforms (SGI, DECstation, etc), and Sun3/4.
2473 Preliminary work has been put in to support the new Solaris OS from Sun. At
2474 this time, it can control and debug processes, but it is not capable of
2479 As always, many many bug fixes. The major areas were with g++, and mipsread.
2480 People using the MIPS-based platforms should experience fewer mysterious
2481 crashes and trashed symbol tables.
2483 *** Changes in GDB-4.4:
2485 * New machines supported (host and target)
2487 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2489 BSD Reno on Vax vax-dec-bsd
2490 Ultrix on Vax vax-dec-ultrix
2492 * New machines supported (target)
2494 AMD 29000 embedded, using EBMON a29k-none-none
2498 GDB continues to improve its handling of C++. `References' work better.
2499 The demangler has also been improved, and now deals with symbols mangled as
2500 per the Annotated C++ Reference Guide.
2502 GDB also now handles `stabs' symbol information embedded in MIPS
2503 `ecoff' symbol tables. Since the ecoff format was not easily
2504 extensible to handle new languages such as C++, this appeared to be a
2505 good way to put C++ debugging info into MIPS binaries. This option
2506 will be supported in the GNU C compiler, version 2, when it is
2509 * New features for SVR4
2511 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
2512 shared libraries. Debugging dynamically linked programs should present
2513 only minor differences from debugging statically linked programs.
2515 The `info proc' command will print out information about any process
2516 on an SVR4 system (including the one you are debugging). At the moment,
2517 it prints the address mappings of the process.
2519 If you bring up GDB on another SVR4 system, please send mail to
2520 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
2522 * Better dynamic linking support in SunOS
2524 Reading symbols from shared libraries which contain debugging symbols
2525 now works properly. However, there remain issues such as automatic
2526 skipping of `transfer vector' code during function calls, which
2527 make it harder to debug code in a shared library, than to debug the
2528 same code linked statically.
2532 GDB is now using the latest `getopt' routines from the FSF. This
2533 version accepts the -- prefix for options with long names. GDB will
2534 continue to accept the old forms (-option and +option) as well.
2535 Various single letter abbreviations for options have been explicity
2536 added to the option table so that they won't get overshadowed in the
2537 future by other options that begin with the same letter.
2541 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
2542 Many assorted bugs have been handled. Many more remain to be handled.
2543 See the various ChangeLog files (primarily in gdb and bfd) for details.
2546 *** Changes in GDB-4.3:
2548 * New machines supported (host and target)
2550 Amiga 3000 running Amix m68k-cbm-svr4 or amix
2551 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
2552 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
2554 * Almost SCO Unix support
2556 We had hoped to support:
2557 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2558 (except for core file support), but we discovered very late in the release
2559 that it has problems with process groups that render gdb unusable. Sorry
2560 about that. I encourage people to fix it and post the fixes.
2562 * Preliminary ELF and DWARF support
2564 GDB can read ELF object files on System V Release 4, and can handle
2565 debugging records for C, in DWARF format, in ELF files. This support
2566 is preliminary. If you bring up GDB on another SVR4 system, please
2567 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
2572 GDB now uses the latest `readline' library. One user-visible change
2573 is that two tabs will list possible command completions, which previously
2574 required typing M-? (meta-question mark, or ESC ?).
2578 The `stepi' bug that many of you noticed has been squashed.
2579 Many bugs in C++ have been handled. Many more remain to be handled.
2580 See the various ChangeLog files (primarily in gdb and bfd) for details.
2582 * State of the MIPS world (in case you wondered):
2584 GDB can understand the symbol tables emitted by the compilers
2585 supplied by most vendors of MIPS-based machines, including DEC. These
2586 symbol tables are in a format that essentially nobody else uses.
2588 Some versions of gcc come with an assembler post-processor called
2589 mips-tfile. This program is required if you want to do source-level
2590 debugging of gcc-compiled programs. I believe FSF does not ship
2591 mips-tfile with gcc version 1, but it will eventually come with gcc
2594 Debugging of g++ output remains a problem. g++ version 1.xx does not
2595 really support it at all. (If you're lucky, you should be able to get
2596 line numbers and stack traces to work, but no parameters or local
2597 variables.) With some work it should be possible to improve the
2600 When gcc version 2 is released, you will have somewhat better luck.
2601 However, even then you will get confusing results for inheritance and
2604 We will eventually provide full debugging of g++ output on
2605 DECstations. This will probably involve some kind of stabs-in-ecoff
2606 encapulation, but the details have not been worked out yet.
2609 *** Changes in GDB-4.2:
2611 * Improved configuration
2613 Only one copy of `configure' exists now, and it is not self-modifying.
2614 Porting BFD is simpler.
2618 The `step' and `next' commands now only stop at the first instruction
2619 of a source line. This prevents the multiple stops that used to occur
2620 in switch statements, for-loops, etc. `Step' continues to stop if a
2621 function that has debugging information is called within the line.
2625 Lots of small bugs fixed. More remain.
2627 * New host supported (not target)
2629 Intel 386 PC clone running Mach i386-none-mach
2632 *** Changes in GDB-4.1:
2634 * Multiple source language support
2636 GDB now has internal scaffolding to handle several source languages.
2637 It determines the type of each source file from its filename extension,
2638 and will switch expression parsing and number formatting to match the
2639 language of the function in the currently selected stack frame.
2640 You can also specifically set the language to be used, with
2641 `set language c' or `set language modula-2'.
2645 GDB now has preliminary support for the GNU Modula-2 compiler,
2646 currently under development at the State University of New York at
2647 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
2648 continue through the fall of 1991 and into 1992.
2650 Other Modula-2 compilers are currently not supported, and attempting to
2651 debug programs compiled with them will likely result in an error as the
2652 symbol table is read. Feel free to work on it, though!
2654 There are hooks in GDB for strict type checking and range checking,
2655 in the `Modula-2 philosophy', but they do not currently work.
2659 GDB can now write to executable and core files (e.g. patch
2660 a variable's value). You must turn this switch on, specify
2661 the file ("exec foo" or "core foo"), *then* modify it, e.g.
2662 by assigning a new value to a variable. Modifications take
2665 * Automatic SunOS shared library reading
2667 When you run your program, GDB automatically determines where its
2668 shared libraries (if any) have been loaded, and reads their symbols.
2669 The `share' command is no longer needed. This also works when
2670 examining core files.
2674 You can specify the number of lines that the `list' command shows.
2677 * New machines supported (host and target)
2679 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
2680 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
2681 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
2683 * New hosts supported (not targets)
2685 IBM RT/PC: romp-ibm-aix or rtpc
2687 * New targets supported (not hosts)
2689 AMD 29000 embedded with COFF a29k-none-coff
2690 AMD 29000 embedded with a.out a29k-none-aout
2691 Ultracomputer remote kernel debug a29k-nyu-kern
2693 * New remote interfaces
2699 *** Changes in GDB-4.0:
2703 Wide output is wrapped at good places to make the output more readable.
2705 Gdb now supports cross-debugging from a host machine of one type to a
2706 target machine of another type. Communication with the target system
2707 is over serial lines. The ``target'' command handles connecting to the
2708 remote system; the ``load'' command will download a program into the
2709 remote system. Serial stubs for the m68k and i386 are provided. Gdb
2710 also supports debugging of realtime processes running under VxWorks,
2711 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
2712 stub on the target system.
2714 New CPUs supported include the AMD 29000 and Intel 960.
2716 GDB now reads object files and symbol tables via a ``binary file''
2717 library, which allows a single copy of GDB to debug programs of multiple
2718 object file types such as a.out and coff.
2720 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2721 refcard.dvi and refcard.ps are available to format it).
2724 * Control-Variable user interface simplified
2726 All variables that control the operation of the debugger can be set
2727 by the ``set'' command, and displayed by the ``show'' command.
2729 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2730 ``Show prompt'' produces the response:
2731 Gdb's prompt is new-gdb=>.
2733 What follows are the NEW set commands. The command ``help set'' will
2734 print a complete list of old and new set commands. ``help set FOO''
2735 will give a longer description of the variable FOO. ``show'' will show
2736 all of the variable descriptions and their current settings.
2738 confirm on/off: Enables warning questions for operations that are
2739 hard to recover from, e.g. rerunning the program while
2740 it is already running. Default is ON.
2742 editing on/off: Enables EMACS style command line editing
2743 of input. Previous lines can be recalled with
2744 control-P, the current line can be edited with control-B,
2745 you can search for commands with control-R, etc.
2748 history filename NAME: NAME is where the gdb command history
2749 will be stored. The default is .gdb_history,
2750 or the value of the environment variable
2753 history size N: The size, in commands, of the command history. The
2754 default is 256, or the value of the environment variable
2757 history save on/off: If this value is set to ON, the history file will
2758 be saved after exiting gdb. If set to OFF, the
2759 file will not be saved. The default is OFF.
2761 history expansion on/off: If this value is set to ON, then csh-like
2762 history expansion will be performed on
2763 command line input. The default is OFF.
2765 radix N: Sets the default radix for input and output. It can be set
2766 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2767 in the current radix, so "set radix 10" is always a no-op.
2769 height N: This integer value is the number of lines on a page. Default
2770 is 24, the current `stty rows'' setting, or the ``li#''
2771 setting from the termcap entry matching the environment
2774 width N: This integer value is the number of characters on a line.
2775 Default is 80, the current `stty cols'' setting, or the ``co#''
2776 setting from the termcap entry matching the environment
2779 Note: ``set screensize'' is obsolete. Use ``set height'' and
2780 ``set width'' instead.
2782 print address on/off: Print memory addresses in various command displays,
2783 such as stack traces and structure values. Gdb looks
2784 more ``symbolic'' if you turn this off; it looks more
2785 ``machine level'' with it on. Default is ON.
2787 print array on/off: Prettyprint arrays. New convenient format! Default
2790 print demangle on/off: Print C++ symbols in "source" form if on,
2793 print asm-demangle on/off: Same, for assembler level printouts
2796 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2799 * Support for Epoch Environment.
2801 The epoch environment is a version of Emacs v18 with windowing. One
2802 new command, ``inspect'', is identical to ``print'', except that if you
2803 are running in the epoch environment, the value is printed in its own
2807 * Support for Shared Libraries
2809 GDB can now debug programs and core files that use SunOS shared libraries.
2810 Symbols from a shared library cannot be referenced
2811 before the shared library has been linked with the program (this
2812 happens after you type ``run'' and before the function main() is entered).
2813 At any time after this linking (including when examining core files
2814 from dynamically linked programs), gdb reads the symbols from each
2815 shared library when you type the ``sharedlibrary'' command.
2816 It can be abbreviated ``share''.
2818 sharedlibrary REGEXP: Load shared object library symbols for files
2819 matching a unix regular expression. No argument
2820 indicates to load symbols for all shared libraries.
2822 info sharedlibrary: Status of loaded shared libraries.
2827 A watchpoint stops execution of a program whenever the value of an
2828 expression changes. Checking for this slows down execution
2829 tremendously whenever you are in the scope of the expression, but is
2830 quite useful for catching tough ``bit-spreader'' or pointer misuse
2831 problems. Some machines such as the 386 have hardware for doing this
2832 more quickly, and future versions of gdb will use this hardware.
2834 watch EXP: Set a watchpoint (breakpoint) for an expression.
2836 info watchpoints: Information about your watchpoints.
2838 delete N: Deletes watchpoint number N (same as breakpoints).
2839 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2840 enable N: Re-enables watchpoint number N (same as breakpoints).
2843 * C++ multiple inheritance
2845 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2848 * C++ exception handling
2850 Gdb now supports limited C++ exception handling. Besides the existing
2851 ability to breakpoint on an exception handler, gdb can breakpoint on
2852 the raising of an exception (before the stack is peeled back to the
2855 catch FOO: If there is a FOO exception handler in the dynamic scope,
2856 set a breakpoint to catch exceptions which may be raised there.
2857 Multiple exceptions (``catch foo bar baz'') may be caught.
2859 info catch: Lists all exceptions which may be caught in the
2860 current stack frame.
2863 * Minor command changes
2865 The command ``call func (arg, arg, ...)'' now acts like the print
2866 command, except it does not print or save a value if the function's result
2867 is void. This is similar to dbx usage.
2869 The ``up'' and ``down'' commands now always print the frame they end up
2870 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2871 frames without printing.
2873 * New directory command
2875 'dir' now adds directories to the FRONT of the source search path.
2876 The path starts off empty. Source files that contain debug information
2877 about the directory in which they were compiled can be found even
2878 with an empty path; Sun CC and GCC include this information. If GDB can't
2879 find your source file in the current directory, type "dir .".
2881 * Configuring GDB for compilation
2883 For normal use, type ``./configure host''. See README or gdb.texinfo
2886 GDB now handles cross debugging. If you are remotely debugging between
2887 two different machines, type ``./configure host -target=targ''.
2888 Host is the machine where GDB will run; targ is the machine
2889 where the program that you are debugging will run.
projects / thirdparty / binutils-gdb.git / blob