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
14 * The "set trust-readonly-sections" command works again. This command was
15 broken in GDB 6.3, 6.4, and 6.5.
22 Manage a list of substitution rules that GDB uses to rewrite the name
23 of the directories where the sources are located. This can be useful
24 for instance when the sources were moved to a different location
25 between compilation and debugging.
29 Print each CLI command as it is executed. Each command is prefixed with
30 a number of `+' symbols representing the nesting depth.
31 The source command now has a `-v' option to enable the same feature.
35 The ARM Demon monitor support (RDP protocol, "target rdp").
37 Kernel Object Display, an embedded debugging feature which only worked with
38 an obsolete version of Cisco IOS.
40 The 'set download-write-size' and 'show download-write-size' commands.
45 Tell a stub about GDB client features, and request remote target features.
46 The first feature implemented is PacketSize, which allows the target to
47 specify the size of packets it can handle - to minimize the number of
48 packets required and improve performance when connected to a remote
52 Fetch an OS auxilliary vector from the remote stub. This packet is a
53 more efficient replacement for qPart:auxv:read.
55 * Removed remote packets
58 This packet has been replaced by qXfer:auxv:read. Only GDB 6.4 and 6.5
59 used it, and only gdbserver implemented it.
61 *** Changes in GDB 6.5
65 Renesas M32C/M16C m32c-elf
67 Morpho Technologies ms1 ms1-elf
71 init-if-undefined Initialize a convenience variable, but
72 only if it doesn't already have a value.
74 The following commands are presently only implemented for native GNU/Linux:
76 checkpoint Save a snapshot of the program state.
78 restart <n> Return the program state to a
79 previously saved state.
81 info checkpoints List currently saved checkpoints.
83 delete-checkpoint <n> Delete a previously saved checkpoint.
85 set|show detach-on-fork Tell gdb whether to detach from a newly
86 forked process, or to keep debugging it.
88 info forks List forks of the user program that
89 are available to be debugged.
91 fork <n> Switch to debugging one of several
92 forks of the user program that are
93 available to be debugged.
95 delete-fork <n> Delete a fork from the list of forks
96 that are available to be debugged (and
97 kill the forked process).
99 detach-fork <n> Delete a fork from the list of forks
100 that are available to be debugged (and
101 allow the process to continue).
105 Morpho Technologies ms2 ms1-elf
107 * Improved Windows host support
109 GDB now builds as a cross debugger hosted on i686-mingw32, including
110 native console support, and remote communications using either
111 network sockets or serial ports.
113 * Improved Modula-2 language support
115 GDB can now print most types in the Modula-2 syntax. This includes:
116 basic types, set types, record types, enumerated types, range types,
117 pointer types and ARRAY types. Procedure var parameters are correctly
118 printed and hexadecimal addresses and character constants are also
119 written in the Modula-2 syntax. Best results can be obtained by using
120 GNU Modula-2 together with the -gdwarf-2 command line option.
124 The ARM rdi-share module.
126 The Netware NLM debug server.
128 *** Changes in GDB 6.4
130 * New native configurations
132 OpenBSD/arm arm*-*-openbsd*
133 OpenBSD/mips64 mips64-*-openbsd*
137 Morpho Technologies ms1 ms1-elf
139 * New command line options
141 --batch-silent As for --batch, but totally silent.
142 --return-child-result The debugger will exist with the same value
143 the child (debugged) program exited with.
144 --eval-command COMMAND, -ex COMMAND
145 Execute a single GDB CLI command. This may be
146 specified multiple times and in conjunction
147 with the --command (-x) option.
149 * Deprecated commands removed
151 The following commands, that were deprecated in 2000, have been
155 set|show arm disassembly-flavor set|show arm disassembler
156 othernames set arm disassembler
157 set|show remotedebug set|show debug remote
158 set|show archdebug set|show debug arch
159 set|show eventdebug set|show debug event
162 * New BSD user-level threads support
164 It is now possible to debug programs using the user-level threads
165 library on OpenBSD and FreeBSD. Currently supported (target)
168 FreeBSD/amd64 x86_64-*-freebsd*
169 FreeBSD/i386 i386-*-freebsd*
170 OpenBSD/i386 i386-*-openbsd*
172 Note that the new kernel threads libraries introduced in FreeBSD 5.x
173 are not yet supported.
175 * New support for Matsushita MN10300 w/sim added
176 (Work in progress). mn10300-elf.
178 * REMOVED configurations and files
180 VxWorks and the XDR protocol *-*-vxworks
181 Motorola MCORE mcore-*-*
182 National Semiconductor NS32000 ns32k-*-*
184 * New "set print array-indexes" command
186 After turning this setting "on", GDB prints the index of each element
187 when displaying arrays. The default is "off" to preserve the previous
190 * VAX floating point support
192 GDB now supports the not-quite-ieee VAX F and D floating point formats.
194 * User-defined command support
196 In addition to using $arg0..$arg9 for argument passing, it is now possible
197 to use $argc to determine now many arguments have been passed. See the
198 section on user-defined commands in the user manual for more information.
200 *** Changes in GDB 6.3:
202 * New command line option
204 GDB now accepts -l followed by a number to set the timeout for remote
207 * GDB works with GCC -feliminate-dwarf2-dups
209 GDB now supports a more compact representation of DWARF-2 debug
210 information using DW_FORM_ref_addr references. These are produced
211 by GCC with the option -feliminate-dwarf2-dups and also by some
212 proprietary compilers. With GCC, you must use GCC 3.3.4 or later
213 to use -feliminate-dwarf2-dups.
215 * Internationalization
217 When supported by the host system, GDB will be built with
218 internationalization (libintl). The task of marking up the sources is
219 continued, we're looking forward to our first translation.
223 Initial support for debugging programs compiled with the GNAT
224 implementation of the Ada programming language has been integrated
225 into GDB. In this release, support is limited to expression evaluation.
227 * New native configurations
229 GNU/Linux/m32r m32r-*-linux-gnu
233 GDB's remote protocol now includes support for the 'p' packet. This
234 packet is used to fetch individual registers from a remote inferior.
236 * END-OF-LIFE registers[] compatibility module
238 GDB's internal register infrastructure has been completely rewritten.
239 The new infrastructure making possible the implementation of key new
240 features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit
243 GDB 6.3 will be the last release to include the the registers[]
244 compatibility module that allowed out-of-date configurations to
245 continue to work. This change directly impacts the following
257 Unless there is activity to revive these configurations, they will be
258 made OBSOLETE in GDB 6.4, and REMOVED from GDB 6.5.
260 * OBSOLETE configurations and files
262 Configurations that have been declared obsolete in this release have
263 been commented out. Unless there is activity to revive these
264 configurations, the next release of GDB will have their sources
274 *** Changes in GDB 6.2.1:
276 * MIPS `break main; run' gave an heuristic-fence-post warning
278 When attempting to run even a simple program, a warning about
279 heuristic-fence-post being hit would be reported. This problem has
282 * MIPS IRIX 'long double' crashed GDB
284 When examining a long double variable, GDB would get a segmentation
285 fault. The crash has been fixed (but GDB 6.2 cannot correctly examine
286 IRIX long double values).
290 A bug in the VAX stack code was causing problems with the "next"
291 command. This problem has been fixed.
293 *** Changes in GDB 6.2:
295 * Fix for ``many threads''
297 On GNU/Linux systems that use the NPTL threads library, a program
298 rapidly creating and deleting threads would confuse GDB leading to the
301 ptrace: No such process.
302 thread_db_get_info: cannot get thread info: generic error
304 This problem has been fixed.
306 * "-async" and "-noasync" options removed.
308 Support for the broken "-noasync" option has been removed (it caused
311 * New ``start'' command.
313 This command runs the program until the begining of the main procedure.
315 * New BSD Kernel Data Access Library (libkvm) interface
317 Using ``target kvm'' it is now possible to debug kernel core dumps and
318 live kernel memory images on various FreeBSD, NetBSD and OpenBSD
319 platforms. Currently supported (native-only) configurations are:
321 FreeBSD/amd64 x86_64-*-freebsd*
322 FreeBSD/i386 i?86-*-freebsd*
323 NetBSD/i386 i?86-*-netbsd*
324 NetBSD/m68k m68*-*-netbsd*
325 NetBSD/sparc sparc-*-netbsd*
326 OpenBSD/amd64 x86_64-*-openbsd*
327 OpenBSD/i386 i?86-*-openbsd*
328 OpenBSD/m68k m68*-openbsd*
329 OpenBSD/sparc sparc-*-openbsd*
331 * Signal trampoline code overhauled
333 Many generic problems with GDB's signal handling code have been fixed.
334 These include: backtraces through non-contiguous stacks; recognition
335 of sa_sigaction signal trampolines; backtrace from a NULL pointer
336 call; backtrace through a signal trampoline; step into and out of
337 signal handlers; and single-stepping in the signal trampoline.
339 Please note that kernel bugs are a limiting factor here. These
340 features have been shown to work on an s390 GNU/Linux system that
341 include a 2.6.8-rc1 kernel. Ref PR breakpoints/1702.
343 * Cygwin support for DWARF 2 added.
345 * New native configurations
347 GNU/Linux/hppa hppa*-*-linux*
348 OpenBSD/hppa hppa*-*-openbsd*
349 OpenBSD/m68k m68*-*-openbsd*
350 OpenBSD/m88k m88*-*-openbsd*
351 OpenBSD/powerpc powerpc-*-openbsd*
352 NetBSD/vax vax-*-netbsd*
353 OpenBSD/vax vax-*-openbsd*
355 * END-OF-LIFE frame compatibility module
357 GDB's internal frame infrastructure has been completely rewritten.
358 The new infrastructure making it possible to support key new features
359 including DWARF 2 Call Frame Information. To aid in the task of
360 migrating old configurations to this new infrastructure, a
361 compatibility module, that allowed old configurations to continue to
362 work, was also included.
364 GDB 6.2 will be the last release to include this frame compatibility
365 module. This change directly impacts the following configurations:
375 Unless there is activity to revive these configurations, they will be
376 made OBSOLETE in GDB 6.3, and REMOVED from GDB 6.4.
378 * REMOVED configurations and files
380 Sun 3, running SunOS 3 m68*-*-sunos3*
381 Sun 3, running SunOS 4 m68*-*-sunos4*
382 Sun 2, running SunOS 3 m68000-*-sunos3*
383 Sun 2, running SunOS 4 m68000-*-sunos4*
384 Motorola 680x0 running LynxOS m68*-*-lynxos*
385 AT&T 3b1/Unix pc m68*-att-*
386 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
387 decstation mips-dec-* mips-little-*
388 riscos mips-*-riscos* mips-*-sysv*
390 sysv mips*-*-sysv4* (IRIX 5/6 not included)
392 *** Changes in GDB 6.1.1:
394 * TUI (Text-mode User Interface) built-in (also included in GDB 6.1)
396 The TUI (Text-mode User Interface) is now built as part of a default
397 GDB configuration. It is enabled by either selecting the TUI with the
398 command line option "-i=tui" or by running the separate "gdbtui"
399 program. For more information on the TUI, see the manual "Debugging
402 * Pending breakpoint support (also included in GDB 6.1)
404 Support has been added to allow you to specify breakpoints in shared
405 libraries that have not yet been loaded. If a breakpoint location
406 cannot be found, and the "breakpoint pending" option is set to auto,
407 GDB queries you if you wish to make the breakpoint pending on a future
408 shared-library load. If and when GDB resolves the breakpoint symbol,
409 the pending breakpoint is removed as one or more regular breakpoints
412 Pending breakpoints are very useful for GCJ Java debugging.
414 * Fixed ISO-C build problems
416 The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained
417 non ISO-C code that stopped them being built using a more strict ISO-C
418 compiler (e.g., IBM's C compiler).
420 * Fixed build problem on IRIX 5
422 Due to header problems with <sys/proc.h>, the file gdb/proc-api.c
423 wasn't able to compile compile on an IRIX 5 system.
425 * Added execute permission to gdb/gdbserver/configure
427 The shell script gdb/testsuite/gdb.stabs/configure lacked execute
428 permission. This bug would cause configure to fail on a number of
429 systems (Solaris, IRIX). Ref: server/519.
431 * Fixed build problem on hpux2.0w-hp-hpux11.00 using the HP ANSI C compiler
433 Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c
434 has been updated to use constant array sizes.
436 * Fixed a panic in the DWARF Call Frame Info code on Solaris 2.7
438 GCC 3.3.2, on Solaris 2.7, includes the DW_EH_PE_funcrel encoding in
439 its generated DWARF Call Frame Info. This encoding was causing GDB to
440 panic, that panic has been fixed. Ref: gdb/1628.
442 * Fixed a problem when examining parameters in shared library code.
444 When examining parameters in optimized shared library code generated
445 by a mainline GCC, GDB would incorrectly report ``Variable "..." is
446 not available''. GDB now correctly displays the variable's value.
448 *** Changes in GDB 6.1:
450 * Removed --with-mmalloc
452 Support for the mmalloc memory manager has been removed, as it
453 conflicted with the internal gdb byte cache.
455 * Changes in AMD64 configurations
457 The AMD64 target now includes the %cs and %ss registers. As a result
458 the AMD64 remote protocol has changed; this affects the floating-point
459 and SSE registers. If you rely on those registers for your debugging,
460 you should upgrade gdbserver on the remote side.
462 * Revised SPARC target
464 The SPARC target has been completely revised, incorporating the
465 FreeBSD/sparc64 support that was added for GDB 6.0. As a result
466 support for LynxOS and SunOS 4 has been dropped. Calling functions
467 from within GDB on operating systems with a non-executable stack
468 (Solaris, OpenBSD) now works.
472 GDB has a new C++ demangler which does a better job on the mangled
473 names generated by current versions of g++. It also runs faster, so
474 with this and other changes gdb should now start faster on large C++
477 * DWARF 2 Location Expressions
479 GDB support for location expressions has been extended to support function
480 arguments and frame bases. Older versions of GDB could crash when they
483 * C++ nested types and namespaces
485 GDB's support for nested types and namespaces in C++ has been
486 improved, especially if you use the DWARF 2 debugging format. (This
487 is the default for recent versions of GCC on most platforms.)
488 Specifically, if you have a class "Inner" defined within a class or
489 namespace "Outer", then GDB realizes that the class's name is
490 "Outer::Inner", not simply "Inner". This should greatly reduce the
491 frequency of complaints about not finding RTTI symbols. In addition,
492 if you are stopped at inside of a function defined within a namespace,
493 GDB modifies its name lookup accordingly.
495 * New native configurations
497 NetBSD/amd64 x86_64-*-netbsd*
498 OpenBSD/amd64 x86_64-*-openbsd*
499 OpenBSD/alpha alpha*-*-openbsd*
500 OpenBSD/sparc sparc-*-openbsd*
501 OpenBSD/sparc64 sparc64-*-openbsd*
503 * New debugging protocols
505 M32R with SDI protocol m32r-*-elf*
507 * "set prompt-escape-char" command deleted.
509 The command "set prompt-escape-char" has been deleted. This command,
510 and its very obscure effet on GDB's prompt, was never documented,
511 tested, nor mentioned in the NEWS file.
513 * OBSOLETE configurations and files
515 Configurations that have been declared obsolete in this release have
516 been commented out. Unless there is activity to revive these
517 configurations, the next release of GDB will have their sources
520 Sun 3, running SunOS 3 m68*-*-sunos3*
521 Sun 3, running SunOS 4 m68*-*-sunos4*
522 Sun 2, running SunOS 3 m68000-*-sunos3*
523 Sun 2, running SunOS 4 m68000-*-sunos4*
524 Motorola 680x0 running LynxOS m68*-*-lynxos*
525 AT&T 3b1/Unix pc m68*-att-*
526 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
527 decstation mips-dec-* mips-little-*
528 riscos mips-*-riscos* mips-*-sysv*
530 sysv mips*-*-sysv4* (IRIX 5/6 not included)
532 * REMOVED configurations and files
534 SGI Irix-4.x mips-sgi-irix4 or iris4
535 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
536 Z8000 simulator z8k-zilog-none or z8ksim
537 Matsushita MN10200 w/simulator mn10200-*-*
538 H8/500 simulator h8500-hitachi-hms or h8500hms
539 HP/PA running BSD hppa*-*-bsd*
540 HP/PA running OSF/1 hppa*-*-osf*
541 HP/PA Pro target hppa*-*-pro*
542 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
543 386BSD i[3456]86-*-bsd*
544 Sequent family i[3456]86-sequent-sysv4*
545 i[3456]86-sequent-sysv*
546 i[3456]86-sequent-bsd*
547 SPARC running LynxOS sparc-*-lynxos*
548 SPARC running SunOS 4 sparc-*-sunos4*
549 Tsqware Sparclet sparclet-*-*
550 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
552 *** Changes in GDB 6.0:
556 Support for debugging the Objective-C programming language has been
559 * New backtrace mechanism (includes DWARF 2 Call Frame Information).
561 DWARF 2's Call Frame Information makes available compiler generated
562 information that more exactly describes the program's run-time stack.
563 By using this information, GDB is able to provide more robust stack
566 The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets
567 have been updated to use a new backtrace mechanism which includes
572 GDB's remote protocol has been extended to include support for hosted
573 file I/O (where the remote target uses GDB's file system). See GDB's
574 remote protocol documentation for details.
576 * All targets using the new architecture framework.
578 All of GDB's targets have been updated to use the new internal
579 architecture framework. The way is now open for future GDB releases
580 to include cross-architecture native debugging support (i386 on amd64,
583 * GNU/Linux's Thread Local Storage (TLS)
585 GDB now includes support for for the GNU/Linux implementation of
586 per-thread variables.
588 * GNU/Linux's Native POSIX Thread Library (NPTL)
590 GDB's thread code has been updated to work with either the new
591 GNU/Linux NPTL thread library or the older "LinuxThreads" library.
593 * Separate debug info.
595 GDB, in conjunction with BINUTILS, now supports a mechanism for
596 automatically loading debug information from a separate file. Instead
597 of shipping full debug and non-debug versions of system libraries,
598 system integrators can now instead ship just the stripped libraries
599 and optional debug files.
601 * DWARF 2 Location Expressions
603 DWARF 2 Location Expressions allow the compiler to more completely
604 describe the location of variables (even in optimized code) to the
607 GDB now includes preliminary support for location expressions (support
608 for DW_OP_piece is still missing).
612 A number of long standing bugs that caused GDB to die while starting a
613 Java application have been fixed. GDB's Java support is now
614 considered "useable".
616 * GNU/Linux support for fork, vfork, and exec.
618 The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode"
619 commands are now implemented for GNU/Linux. They require a 2.5.x or later
622 * GDB supports logging output to a file
624 There are two new commands, "set logging" and "show logging", which can be
625 used to capture GDB's output to a file.
627 * The meaning of "detach" has changed for gdbserver
629 The "detach" command will now resume the application, as documented. To
630 disconnect from gdbserver and leave it stopped, use the new "disconnect"
633 * d10v, m68hc11 `regs' command deprecated
635 The `info registers' command has been updated so that it displays the
636 registers using a format identical to the old `regs' command.
640 A new command, "maint set profile on/off", has been added. This command can
641 be used to enable or disable profiling while running GDB, to profile a
642 session or a set of commands. In addition there is a new configure switch,
643 "--enable-profiling", which will cause GDB to be compiled with profiling
644 data, for more informative profiling results.
646 * Default MI syntax changed to "mi2".
648 The default MI (machine interface) syntax, enabled by the command line
649 option "-i=mi", has been changed to "mi2". The previous MI syntax,
650 "mi1", can be enabled by specifying the option "-i=mi1".
652 Support for the original "mi0" syntax (included in GDB 5.0) has been
655 Fix for gdb/192: removed extraneous space when displaying frame level.
656 Fix for gdb/672: update changelist is now output in mi list format.
657 Fix for gdb/702: a -var-assign that updates the value now shows up
658 in a subsequent -var-update.
660 * New native configurations.
662 FreeBSD/amd64 x86_64-*-freebsd*
664 * Multi-arched targets.
666 HP/PA HPUX11 hppa*-*-hpux*
667 Renesas M32R/D w/simulator m32r-*-elf*
669 * OBSOLETE configurations and files
671 Configurations that have been declared obsolete in this release have
672 been commented out. Unless there is activity to revive these
673 configurations, the next release of GDB will have their sources
676 Z8000 simulator z8k-zilog-none or z8ksim
677 Matsushita MN10200 w/simulator mn10200-*-*
678 H8/500 simulator h8500-hitachi-hms or h8500hms
679 HP/PA running BSD hppa*-*-bsd*
680 HP/PA running OSF/1 hppa*-*-osf*
681 HP/PA Pro target hppa*-*-pro*
682 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
683 Sequent family i[3456]86-sequent-sysv4*
684 i[3456]86-sequent-sysv*
685 i[3456]86-sequent-bsd*
686 Tsqware Sparclet sparclet-*-*
687 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
689 * REMOVED configurations and files
692 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
693 IBM AIX PS/2 i[3456]86-*-aix
694 i386 running Mach 3.0 i[3456]86-*-mach3*
695 i386 running Mach i[3456]86-*-mach*
696 i386 running OSF/1 i[3456]86-*osf1mk*
697 HP/Apollo 68k Family m68*-apollo*-sysv*,
699 m68*-hp-bsd*, m68*-hp-hpux*
700 Argonaut Risc Chip (ARC) arc-*-*
701 Mitsubishi D30V d30v-*-*
702 Fujitsu FR30 fr30-*-elf*
703 OS/9000 i[34]86-*-os9k
704 I960 with MON960 i960-*-coff
706 * MIPS $fp behavior changed
708 The convenience variable $fp, for the MIPS, now consistently returns
709 the address of the current frame's base. Previously, depending on the
710 context, $fp could refer to either $sp or the current frame's base
711 address. See ``8.10 Registers'' in the manual ``Debugging with GDB:
712 The GNU Source-Level Debugger''.
714 *** Changes in GDB 5.3:
716 * GNU/Linux shared library multi-threaded performance improved.
718 When debugging a multi-threaded application on GNU/Linux, GDB now uses
719 `/proc', in preference to `ptrace' for memory reads. This may result
720 in an improvement in the start-up time of multi-threaded, shared
721 library applications when run under GDB. One GDB user writes: ``loads
722 shared libs like mad''.
724 * ``gdbserver'' now supports multi-threaded applications on some targets
726 Support for debugging multi-threaded applications which use
727 the GNU/Linux LinuxThreads package has been added for
728 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
729 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
731 * GDB now supports C/C++ preprocessor macros.
733 GDB now expands preprocessor macro invocations in C/C++ expressions,
734 and provides various commands for showing macro definitions and how
737 The new command `macro expand EXPRESSION' expands any macro
738 invocations in expression, and shows the result.
740 The new command `show macro MACRO-NAME' shows the definition of the
741 macro named MACRO-NAME, and where it was defined.
743 Most compilers don't include information about macros in the debugging
744 information by default. In GCC 3.1, for example, you need to compile
745 your program with the options `-gdwarf-2 -g3'. If the macro
746 information is present in the executable, GDB will read it.
748 * Multi-arched targets.
750 DEC Alpha (partial) alpha*-*-*
751 DEC VAX (partial) vax-*-*
753 National Semiconductor NS32000 (partial) ns32k-*-*
754 Motorola 68000 (partial) m68k-*-*
755 Motorola MCORE mcore-*-*
759 Fujitsu FRV architecture added by Red Hat frv*-*-*
762 * New native configurations
764 Alpha NetBSD alpha*-*-netbsd*
765 SH NetBSD sh*-*-netbsdelf*
766 MIPS NetBSD mips*-*-netbsd*
767 UltraSPARC NetBSD sparc64-*-netbsd*
769 * OBSOLETE configurations and files
771 Configurations that have been declared obsolete in this release have
772 been commented out. Unless there is activity to revive these
773 configurations, the next release of GDB will have their sources
776 Mitsubishi D30V d30v-*-*
777 OS/9000 i[34]86-*-os9k
778 IBM AIX PS/2 i[3456]86-*-aix
779 Fujitsu FR30 fr30-*-elf*
780 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
781 Argonaut Risc Chip (ARC) arc-*-*
782 i386 running Mach 3.0 i[3456]86-*-mach3*
783 i386 running Mach i[3456]86-*-mach*
784 i386 running OSF/1 i[3456]86-*osf1mk*
785 HP/Apollo 68k Family m68*-apollo*-sysv*,
787 m68*-hp-bsd*, m68*-hp-hpux*
788 I960 with MON960 i960-*-coff
792 CHILL, a Pascal like language used by telecommunications companies.
794 * REMOVED configurations and files
796 AMD 29k family via UDI a29k-amd-udi, udi29k
797 A29K VxWorks a29k-*-vxworks
798 AMD 29000 embedded, using EBMON a29k-none-none
799 AMD 29000 embedded with COFF a29k-none-coff
800 AMD 29000 embedded with a.out a29k-none-aout
802 testsuite/gdb.hp/gdb.threads-hp/ directory
804 * New command "set max-user-call-depth <nnn>"
806 This command allows the user to limit the call depth of user-defined
807 commands. The default is 1024.
809 * Changes in FreeBSD/i386 native debugging.
811 Support for the "generate-core-file" has been added.
813 * New commands "dump", "append", and "restore".
815 These commands allow data to be copied from target memory
816 to a bfd-format or binary file (dump and append), and back
817 from a file into memory (restore).
819 * Improved "next/step" support on multi-processor Alpha Tru64.
821 The previous single-step mechanism could cause unpredictable problems,
822 including the random appearance of SIGSEGV or SIGTRAP signals. The use
823 of a software single-step mechanism prevents this.
825 *** Changes in GDB 5.2.1:
833 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
834 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
835 Fix, by Joel Brobecker imported from mainline.
837 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
838 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
839 Fix, by Fred Fish, imported from mainline.
841 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
842 Surprisingly enough, it works now.
843 By Michal Ludvig, imported from mainline.
845 i386 hardware watchpoint support:
846 avoid misses on second run for some targets.
847 By Pierre Muller, imported from mainline.
849 *** Changes in GDB 5.2:
851 * New command "set trust-readonly-sections on[off]".
853 This command is a hint that tells gdb that read-only sections
854 really are read-only (ie. that their contents will not change).
855 In this mode, gdb will go to the object file rather than the
856 target to read memory from read-only sections (such as ".text").
857 This can be a significant performance improvement on some
858 (notably embedded) targets.
860 * New command "generate-core-file" (or "gcore").
862 This new gdb command allows the user to drop a core file of the child
863 process state at any time. So far it's been implemented only for
864 GNU/Linux and Solaris, but should be relatively easily ported to other
865 hosts. Argument is core file name (defaults to core.<pid>).
867 * New command line option
869 GDB now accepts --pid or -p followed by a process id.
871 * Change in command line behavior -- corefiles vs. process ids.
873 There is a subtle behavior in the way in which GDB handles
874 command line arguments. The first non-flag argument is always
875 a program to debug, but the second non-flag argument may either
876 be a corefile or a process id. Previously, GDB would attempt to
877 open the second argument as a corefile, and if that failed, would
878 issue a superfluous error message and then attempt to attach it as
879 a process. Now, if the second argument begins with a non-digit,
880 it will be treated as a corefile. If it begins with a digit,
881 GDB will attempt to attach it as a process, and if no such process
882 is found, will then attempt to open it as a corefile.
884 * Changes in ARM configurations.
886 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
887 configuration is fully multi-arch.
889 * New native configurations
891 ARM NetBSD arm*-*-netbsd*
892 x86 OpenBSD i[3456]86-*-openbsd*
893 AMD x86-64 running GNU/Linux x86_64-*-linux-*
894 Sparc64 running FreeBSD sparc64-*-freebsd*
898 Sanyo XStormy16 xstormy16-elf
900 * OBSOLETE configurations and files
902 Configurations that have been declared obsolete in this release have
903 been commented out. Unless there is activity to revive these
904 configurations, the next release of GDB will have their sources
907 AMD 29k family via UDI a29k-amd-udi, udi29k
908 A29K VxWorks a29k-*-vxworks
909 AMD 29000 embedded, using EBMON a29k-none-none
910 AMD 29000 embedded with COFF a29k-none-coff
911 AMD 29000 embedded with a.out a29k-none-aout
913 testsuite/gdb.hp/gdb.threads-hp/ directory
915 * REMOVED configurations and files
917 TI TMS320C80 tic80-*-*
919 PowerPC Solaris powerpcle-*-solaris*
920 PowerPC Windows NT powerpcle-*-cygwin32
921 PowerPC Netware powerpc-*-netware*
922 Harris/CXUX m88k m88*-harris-cxux*
923 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
924 ns32k-utek-sysv* ns32k-utek-*
925 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
926 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
927 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
928 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
929 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
931 * Changes to command line processing
933 The new `--args' feature can be used to specify command-line arguments
934 for the inferior from gdb's command line.
936 * Changes to key bindings
938 There is a new `operate-and-get-next' function bound to `C-o'.
940 *** Changes in GDB 5.1.1
942 Fix compile problem on DJGPP.
944 Fix a problem with floating-point registers on the i386 being
947 Fix to stop GDB crashing on .debug_str debug info.
949 Numerous documentation fixes.
951 Numerous testsuite fixes.
953 *** Changes in GDB 5.1:
955 * New native configurations
957 Alpha FreeBSD alpha*-*-freebsd*
958 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
959 MIPS GNU/Linux mips*-*-linux*
960 MIPS SGI Irix 6.x mips*-sgi-irix6*
962 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
966 Motorola 68HC11 and 68HC12 m68hc11-elf
968 UltraSparc running GNU/Linux sparc64-*-linux*
970 * OBSOLETE configurations and files
972 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
973 Harris/CXUX m88k m88*-harris-cxux*
974 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
975 ns32k-utek-sysv* ns32k-utek-*
976 TI TMS320C80 tic80-*-*
978 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
979 PowerPC Solaris powerpcle-*-solaris*
980 PowerPC Windows NT powerpcle-*-cygwin32
981 PowerPC Netware powerpc-*-netware*
982 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
983 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
984 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
985 Apple Macintosh (MPW) host N/A
987 stuff.c (Program to stuff files into a specially prepared space in kdb)
988 kdb-start.c (Main loop for the standalone kernel debugger)
990 Configurations that have been declared obsolete in this release have
991 been commented out. Unless there is activity to revive these
992 configurations, the next release of GDB will have their sources
995 * REMOVED configurations and files
997 Altos 3068 m68*-altos-*
998 Convex c1-*-*, c2-*-*
1000 ARM RISCix arm-*-* (as host)
1004 * GDB has been converted to ISO C.
1006 GDB's source code has been converted to ISO C. In particular, the
1007 sources are fully protoized, and rely on standard headers being
1012 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
1014 * The MI enabled by default.
1016 The new machine oriented interface (MI) introduced in GDB 5.0 has been
1017 revised and enabled by default. Packages which use GDB as a debugging
1018 engine behind a UI or another front end are encouraged to switch to
1019 using the GDB/MI interface, instead of the old annotations interface
1020 which is now deprecated.
1022 * Support for debugging Pascal programs.
1024 GDB now includes support for debugging Pascal programs. The following
1025 main features are supported:
1027 - Pascal-specific data types such as sets;
1029 - automatic recognition of Pascal sources based on file-name
1032 - Pascal-style display of data types, variables, and functions;
1034 - a Pascal expression parser.
1036 However, some important features are not yet supported.
1038 - Pascal string operations are not supported at all;
1040 - there are some problems with boolean types;
1042 - Pascal type hexadecimal constants are not supported
1043 because they conflict with the internal variables format;
1045 - support for Pascal objects and classes is not full yet;
1047 - unlike Pascal, GDB is case-sensitive for symbol names.
1049 * Changes in completion.
1051 Commands such as `shell', `run' and `set args', which pass arguments
1052 to inferior programs, now complete on file names, similar to what
1053 users expect at the shell prompt.
1055 Commands which accept locations, such as `disassemble', `print',
1056 `breakpoint', `until', etc. now complete on filenames as well as
1057 program symbols. Thus, if you type "break foob TAB", and the source
1058 files linked into the programs include `foobar.c', that file name will
1059 be one of the candidates for completion. However, file names are not
1060 considered for completion after you typed a colon that delimits a file
1061 name from a name of a function in that file, as in "break foo.c:bar".
1063 `set demangle-style' completes on available demangling styles.
1065 * New platform-independent commands:
1067 It is now possible to define a post-hook for a command as well as a
1068 hook that runs before the command. For more details, see the
1069 documentation of `hookpost' in the GDB manual.
1071 * Changes in GNU/Linux native debugging.
1073 Support for debugging multi-threaded programs has been completely
1074 revised for all platforms except m68k and sparc. You can now debug as
1075 many threads as your system allows you to have.
1077 Attach/detach is supported for multi-threaded programs.
1079 Support for SSE registers was added for x86. This doesn't work for
1080 multi-threaded programs though.
1082 * Changes in MIPS configurations.
1084 Multi-arch support is enabled for all MIPS configurations.
1086 GDB can now be built as native debugger on SGI Irix 6.x systems for
1087 debugging n32 executables. (Debugging 64-bit executables is not yet
1090 * Unified support for hardware watchpoints in all x86 configurations.
1092 Most (if not all) native x86 configurations support hardware-assisted
1093 breakpoints and watchpoints in a unified manner. This support
1094 implements debug register sharing between watchpoints, which allows to
1095 put a virtually infinite number of watchpoints on the same address,
1096 and also supports watching regions up to 16 bytes with several debug
1099 The new maintenance command `maintenance show-debug-regs' toggles
1100 debugging print-outs in functions that insert, remove, and test
1101 watchpoints and hardware breakpoints.
1103 * Changes in the DJGPP native configuration.
1105 New command ``info dos sysinfo'' displays assorted information about
1106 the CPU, OS, memory, and DPMI server.
1108 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
1109 display information about segment descriptors stored in GDT, LDT, and
1112 New commands ``info dos pde'' and ``info dos pte'' display entries
1113 from Page Directory and Page Tables (for now works with CWSDPMI only).
1114 New command ``info dos address-pte'' displays the Page Table entry for
1115 a given linear address.
1117 GDB can now pass command lines longer than 126 characters to the
1118 program being debugged (requires an update to the libdbg.a library
1119 which is part of the DJGPP development kit).
1121 DWARF2 debug info is now supported.
1123 It is now possible to `step' and `next' through calls to `longjmp'.
1125 * Changes in documentation.
1127 All GDB documentation was converted to GFDL, the GNU Free
1128 Documentation License.
1130 Tracepoints-related commands are now fully documented in the GDB
1133 TUI, the Text-mode User Interface, is now documented in the manual.
1135 Tracepoints-related commands are now fully documented in the GDB
1138 The "GDB Internals" manual now has an index. It also includes
1139 documentation of `ui_out' functions, GDB coding standards, x86
1140 hardware watchpoints, and memory region attributes.
1142 * GDB's version number moved to ``version.in''
1144 The Makefile variable VERSION has been replaced by the file
1145 ``version.in''. People creating GDB distributions should update the
1146 contents of this file.
1150 GUD support is now a standard part of the EMACS distribution.
1152 *** Changes in GDB 5.0:
1154 * Improved support for debugging FP programs on x86 targets
1156 Unified and much-improved support for debugging floating-point
1157 programs on all x86 targets. In particular, ``info float'' now
1158 displays the FP registers in the same format on all x86 targets, with
1159 greater level of detail.
1161 * Improvements and bugfixes in hardware-assisted watchpoints
1163 It is now possible to watch array elements, struct members, and
1164 bitfields with hardware-assisted watchpoints. Data-read watchpoints
1165 on x86 targets no longer erroneously trigger when the address is
1168 * Improvements in the native DJGPP version of GDB
1170 The distribution now includes all the scripts and auxiliary files
1171 necessary to build the native DJGPP version on MS-DOS/MS-Windows
1172 machines ``out of the box''.
1174 The DJGPP version can now debug programs that use signals. It is
1175 possible to catch signals that happened in the debuggee, deliver
1176 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
1177 would kill the program being debugged.) Programs that hook hardware
1178 interrupts (keyboard, timer, etc.) can also be debugged.
1180 It is now possible to debug DJGPP programs that redirect their
1181 standard handles or switch them to raw (as opposed to cooked) mode, or
1182 even close them. The command ``run < foo > bar'' works as expected,
1183 and ``info terminal'' reports useful information about the debuggee's
1184 terminal, including raw/cooked mode, redirection, etc.
1186 The DJGPP version now uses termios functions for console I/O, which
1187 enables debugging graphics programs. Interrupting GDB with Ctrl-C
1190 DOS-style file names with drive letters are now fully supported by
1193 It is now possible to debug DJGPP programs that switch their working
1194 directory. It is also possible to rerun the debuggee any number of
1195 times without restarting GDB; thus, you can use the same setup,
1196 breakpoints, etc. for many debugging sessions.
1198 * New native configurations
1200 ARM GNU/Linux arm*-*-linux*
1201 PowerPC GNU/Linux powerpc-*-linux*
1205 Motorola MCore mcore-*-*
1206 x86 VxWorks i[3456]86-*-vxworks*
1207 PowerPC VxWorks powerpc-*-vxworks*
1208 TI TMS320C80 tic80-*-*
1210 * OBSOLETE configurations
1212 Altos 3068 m68*-altos-*
1213 Convex c1-*-*, c2-*-*
1215 ARM RISCix arm-*-* (as host)
1218 Configurations that have been declared obsolete will be commented out,
1219 but the code will be left in place. If there is no activity to revive
1220 these configurations before the next release of GDB, the sources will
1221 be permanently REMOVED.
1223 * Gould support removed
1225 Support for the Gould PowerNode and NP1 has been removed.
1227 * New features for SVR4
1229 On SVR4 native platforms (such as Solaris), if you attach to a process
1230 without first loading a symbol file, GDB will now attempt to locate and
1231 load symbols from the running process's executable file.
1233 * Many C++ enhancements
1235 C++ support has been greatly improved. Overload resolution now works properly
1236 in almost all cases. RTTI support is on the way.
1238 * Remote targets can connect to a sub-program
1240 A popen(3) style serial-device has been added. This device starts a
1241 sub-process (such as a stand-alone simulator) and then communicates
1242 with that. The sub-program to run is specified using the syntax
1243 ``|<program> <args>'' vis:
1245 (gdb) set remotedebug 1
1246 (gdb) target extended-remote |mn10300-elf-sim program-args
1248 * MIPS 64 remote protocol
1250 A long standing bug in the mips64 remote protocol where by GDB
1251 expected certain 32 bit registers (ex SR) to be transfered as 32
1252 instead of 64 bits has been fixed.
1254 The command ``set remote-mips64-transfers-32bit-regs on'' has been
1255 added to provide backward compatibility with older versions of GDB.
1257 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
1259 The command ``set remotebinarydownload'' command has been replaced by
1260 ``set remote X-packet''. Other commands in ``set remote'' family
1261 include ``set remote P-packet''.
1263 * Breakpoint commands accept ranges.
1265 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
1266 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
1267 ``tracepoint passcount'' also accepts a range of tracepoints.
1269 * ``apropos'' command added.
1271 The ``apropos'' command searches through command names and
1272 documentation strings, printing out matches, making it much easier to
1273 try to find a command that does what you are looking for.
1277 A new machine oriented interface (MI) has been added to GDB. This
1278 interface is designed for debug environments running GDB as a separate
1279 process. This is part of the long term libGDB project. See the
1280 "GDB/MI" chapter of the GDB manual for further information. It can be
1281 enabled by configuring with:
1283 .../configure --enable-gdbmi
1285 *** Changes in GDB-4.18:
1287 * New native configurations
1289 HP-UX 10.20 hppa*-*-hpux10.20
1290 HP-UX 11.x hppa*-*-hpux11.0*
1291 M68K GNU/Linux m68*-*-linux*
1295 Fujitsu FR30 fr30-*-elf*
1296 Intel StrongARM strongarm-*-*
1297 Mitsubishi D30V d30v-*-*
1299 * OBSOLETE configurations
1301 Gould PowerNode, NP1 np1-*-*, pn-*-*
1303 Configurations that have been declared obsolete will be commented out,
1304 but the code will be left in place. If there is no activity to revive
1305 these configurations before the next release of GDB, the sources will
1306 be permanently REMOVED.
1310 As a compatibility experiment, GDB's source files buildsym.h and
1311 buildsym.c have been converted to pure standard C, no longer
1312 containing any K&R compatibility code. We believe that all systems in
1313 use today either come with a standard C compiler, or have a GCC port
1314 available. If this is not true, please report the affected
1315 configuration to bug-gdb@gnu.org immediately. See the README file for
1316 information about getting a standard C compiler if you don't have one
1321 GDB now uses readline 2.2.
1323 * set extension-language
1325 You can now control the mapping between filename extensions and source
1326 languages by using the `set extension-language' command. For instance,
1327 you can ask GDB to treat .c files as C++ by saying
1328 set extension-language .c c++
1329 The command `info extensions' lists all of the recognized extensions
1330 and their associated languages.
1332 * Setting processor type for PowerPC and RS/6000
1334 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
1335 you can use the `set processor' command to specify what variant of the
1336 PowerPC family you are debugging. The command
1340 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
1341 following PowerPC and RS6000 variants:
1343 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
1344 rs6000 IBM RS6000 ("POWER") architecture, user-level view
1346 403GC IBM PowerPC 403GC
1347 505 Motorola PowerPC 505
1348 860 Motorola PowerPC 860 or 850
1349 601 Motorola PowerPC 601
1350 602 Motorola PowerPC 602
1351 603 Motorola/IBM PowerPC 603 or 603e
1352 604 Motorola PowerPC 604 or 604e
1353 750 Motorola/IBM PowerPC 750 or 750
1355 At the moment, this command just tells GDB what to name the
1356 special-purpose processor registers. Since almost all the affected
1357 registers are inaccessible to user-level programs, this command is
1358 only useful for remote debugging in its present form.
1362 Thanks to a major code donation from Hewlett-Packard, GDB now has much
1363 more extensive support for HP-UX. Added features include shared
1364 library support, kernel threads and hardware watchpoints for 11.00,
1365 support for HP's ANSI C and C++ compilers, and a compatibility mode
1366 for xdb and dbx commands.
1370 HP's donation includes the new concept of catchpoints, which is a
1371 generalization of the old catch command. On HP-UX, it is now possible
1372 to catch exec, fork, and vfork, as well as library loading.
1374 This means that the existing catch command has changed; its first
1375 argument now specifies the type of catch to be set up. See the
1376 output of "help catch" for a list of catchpoint types.
1378 * Debugging across forks
1380 On HP-UX, you can choose which process to debug when a fork() happens
1385 HP has donated a curses-based terminal user interface (TUI). To get
1386 it, build with --enable-tui. Although this can be enabled for any
1387 configuration, at present it only works for native HP debugging.
1389 * GDB remote protocol additions
1391 A new protocol packet 'X' that writes binary data is now available.
1392 Default behavior is to try 'X', then drop back to 'M' if the stub
1393 fails to respond. The settable variable `remotebinarydownload'
1394 allows explicit control over the use of 'X'.
1396 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
1397 full 64-bit address. The command
1399 set remoteaddresssize 32
1401 can be used to revert to the old behaviour. For existing remote stubs
1402 the change should not be noticed, as the additional address information
1405 In order to assist in debugging stubs, you may use the maintenance
1406 command `packet' to send any text string to the stub. For instance,
1408 maint packet heythere
1410 sends the packet "$heythere#<checksum>". Note that it is very easy to
1411 disrupt a debugging session by sending the wrong packet at the wrong
1414 The compare-sections command allows you to compare section data on the
1415 target to what is in the executable file without uploading or
1416 downloading, by comparing CRC checksums.
1418 * Tracing can collect general expressions
1420 You may now collect general expressions at tracepoints. This requires
1421 further additions to the target-side stub; see tracepoint.c and
1422 doc/agentexpr.texi for further details.
1424 * mask-address variable for Mips
1426 For Mips targets, you may control the zeroing of the upper 32 bits of
1427 a 64-bit address by entering `set mask-address on'. This is mainly
1428 of interest to users of embedded R4xxx and R5xxx processors.
1430 * Higher serial baud rates
1432 GDB's serial code now allows you to specify baud rates 57600, 115200,
1433 230400, and 460800 baud. (Note that your host system may not be able
1434 to achieve all of these rates.)
1438 The i960 configuration now includes an initial implementation of a
1439 builtin simulator, contributed by Jim Wilson.
1442 *** Changes in GDB-4.17:
1444 * New native configurations
1446 Alpha GNU/Linux alpha*-*-linux*
1447 Unixware 2.x i[3456]86-unixware2*
1448 Irix 6.x mips*-sgi-irix6*
1449 PowerPC GNU/Linux powerpc-*-linux*
1450 PowerPC Solaris powerpcle-*-solaris*
1451 Sparc GNU/Linux sparc-*-linux*
1452 Motorola sysV68 R3V7.1 m68k-motorola-sysv
1456 Argonaut Risc Chip (ARC) arc-*-*
1457 Hitachi H8/300S h8300*-*-*
1458 Matsushita MN10200 w/simulator mn10200-*-*
1459 Matsushita MN10300 w/simulator mn10300-*-*
1460 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
1461 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
1462 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
1463 Mitsubishi D10V w/simulator d10v-*-*
1464 Mitsubishi M32R/D w/simulator m32r-*-elf*
1465 Tsqware Sparclet sparclet-*-*
1466 NEC V850 w/simulator v850-*-*
1468 * New debugging protocols
1470 ARM with RDI protocol arm*-*-*
1471 M68K with dBUG monitor m68*-*-{aout,coff,elf}
1472 DDB and LSI variants of PMON protocol mips*-*-*
1473 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
1474 PowerPC with SDS protocol powerpc{,le}-*-eabi
1475 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
1479 All configurations can now understand and use the DWARF 2 debugging
1480 format. The choice is automatic, if the symbol file contains DWARF 2
1485 GDB now includes basic Java language support. This support is
1486 only useful with Java compilers that produce native machine code.
1488 * solib-absolute-prefix and solib-search-path
1490 For SunOS and SVR4 shared libraries, you may now set the prefix for
1491 loading absolute shared library symbol files, and the search path for
1492 locating non-absolute shared library symbol files.
1494 * Live range splitting
1496 GDB can now effectively debug code for which GCC has performed live
1497 range splitting as part of its optimization. See gdb/doc/LRS for
1498 more details on the expected format of the stabs information.
1502 GDB's support for the GNU Hurd, including thread debugging, has been
1503 updated to work with current versions of the Hurd.
1507 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
1508 instruction set. ARM GDB automatically detects when Thumb
1509 instructions are in use, and adjusts disassembly and backtracing
1514 GDB's MIPS target configurations now handle the MIP16 16-bit
1519 GDB now includes support for overlays; if an executable has been
1520 linked such that multiple sections are based at the same address, GDB
1521 will decide which section to use for symbolic info. You can choose to
1522 control the decision manually, using overlay commands, or implement
1523 additional target-side support and use "overlay load-target" to bring
1524 in the overlay mapping. Do "help overlay" for more detail.
1528 The command "info symbol <address>" displays information about
1529 the symbol at the specified address.
1533 The standard remote protocol now includes an extension that allows
1534 asynchronous collection and display of trace data. This requires
1535 extensive support in the target-side debugging stub. Tracing mode
1536 includes a new interaction mode in GDB and new commands: see the
1537 file tracepoint.c for more details.
1541 Configurations for embedded MIPS now include a simulator contributed
1542 by Cygnus Solutions. The simulator supports the instruction sets
1543 of most MIPS variants.
1547 Sparc configurations may now include the ERC32 simulator contributed
1548 by the European Space Agency. The simulator is not built into
1549 Sparc targets by default; configure with --enable-sim to include it.
1553 For target configurations that may include multiple variants of a
1554 basic architecture (such as MIPS and SH), you may now set the
1555 architecture explicitly. "set arch" sets, "info arch" lists
1556 the possible architectures.
1558 *** Changes in GDB-4.16:
1560 * New native configurations
1562 Windows 95, x86 Windows NT i[345]86-*-cygwin32
1563 M68K NetBSD m68k-*-netbsd*
1564 PowerPC AIX 4.x powerpc-*-aix*
1565 PowerPC MacOS powerpc-*-macos*
1566 PowerPC Windows NT powerpcle-*-cygwin32
1567 RS/6000 AIX 4.x rs6000-*-aix4*
1571 ARM with RDP protocol arm-*-*
1572 I960 with MON960 i960-*-coff
1573 MIPS VxWorks mips*-*-vxworks*
1574 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
1575 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
1577 Matra Sparclet sparclet-*-*
1581 The powerpc-eabi configuration now includes the PSIM simulator,
1582 contributed by Andrew Cagney, with assistance from Mike Meissner.
1583 PSIM is a very elaborate model of the PowerPC, including not only
1584 basic instruction set execution, but also details of execution unit
1585 performance and I/O hardware. See sim/ppc/README for more details.
1589 GDB now works with Solaris 2.5.
1591 * Windows 95/NT native
1593 GDB will now work as a native debugger on Windows 95 and Windows NT.
1594 To build it from source, you must use the "gnu-win32" environment,
1595 which uses a DLL to emulate enough of Unix to run the GNU tools.
1596 Further information, binaries, and sources are available at
1597 ftp.cygnus.com, under pub/gnu-win32.
1599 * dont-repeat command
1601 If a user-defined command includes the command `dont-repeat', then the
1602 command will not be repeated if the user just types return. This is
1603 useful if the command is time-consuming to run, so that accidental
1604 extra keystrokes don't run the same command many times.
1606 * Send break instead of ^C
1608 The standard remote protocol now includes an option to send a break
1609 rather than a ^C to the target in order to interrupt it. By default,
1610 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
1612 * Remote protocol timeout
1614 The standard remote protocol includes a new variable `remotetimeout'
1615 that allows you to set the number of seconds before GDB gives up trying
1616 to read from the target. The default value is 2.
1618 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
1620 By default GDB will automatically keep track of objects as they are
1621 loaded and unloaded by the dynamic linker. By using the command `set
1622 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
1623 when shared library events occur, thus allowing you to set breakpoints
1624 in shared libraries which are explicitly loaded by the inferior.
1626 Note this feature does not work on hpux8. On hpux9 you must link
1627 /usr/lib/end.o into your program. This feature should work
1628 automatically on hpux10.
1630 * Irix 5.x hardware watchpoint support
1632 Irix 5 configurations now support the use of hardware watchpoints.
1634 * Mips protocol "SYN garbage limit"
1636 When debugging a Mips target using the `target mips' protocol, you
1637 may set the number of characters that GDB will ignore by setting
1638 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
1639 every character. The default value is 1050.
1641 * Recording and replaying remote debug sessions
1643 If you set `remotelogfile' to the name of a file, gdb will write to it
1644 a recording of a remote debug session. This recording may then be
1645 replayed back to gdb using "gdbreplay". See gdbserver/README for
1646 details. This is useful when you have a problem with GDB while doing
1647 remote debugging; you can make a recording of the session and send it
1648 to someone else, who can then recreate the problem.
1650 * Speedups for remote debugging
1652 GDB includes speedups for downloading and stepping MIPS systems using
1653 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
1654 and more efficient S-record downloading.
1656 * Memory use reductions and statistics collection
1658 GDB now uses less memory and reports statistics about memory usage.
1659 Try the `maint print statistics' command, for example.
1661 *** Changes in GDB-4.15:
1663 * Psymtabs for XCOFF
1665 The symbol reader for AIX GDB now uses partial symbol tables. This
1666 can greatly improve startup time, especially for large executables.
1668 * Remote targets use caching
1670 Remote targets now use a data cache to speed up communication with the
1671 remote side. The data cache could lead to incorrect results because
1672 it doesn't know about volatile variables, thus making it impossible to
1673 debug targets which use memory mapped I/O devices. `set remotecache
1674 off' turns the the data cache off.
1676 * Remote targets may have threads
1678 The standard remote protocol now includes support for multiple threads
1679 in the target system, using new protocol commands 'H' and 'T'. See
1680 gdb/remote.c for details.
1684 If GDB is configured with `--enable-netrom', then it will include
1685 support for the NetROM ROM emulator from XLNT Designs. The NetROM
1686 acts as though it is a bank of ROM on the target board, but you can
1687 write into it over the network. GDB's support consists only of
1688 support for fast loading into the emulated ROM; to debug, you must use
1689 another protocol, such as standard remote protocol. The usual
1690 sequence is something like
1692 target nrom <netrom-hostname>
1694 target remote <netrom-hostname>:1235
1698 GDB now includes support for the Apple Macintosh, as a host only. It
1699 may be run as either an MPW tool or as a standalone application, and
1700 it can debug through the serial port. All the usual GDB commands are
1701 available, but to the target command, you must supply "serial" as the
1702 device type instead of "/dev/ttyXX". See mpw-README in the main
1703 directory for more information on how to build. The MPW configuration
1704 scripts */mpw-config.in support only a few targets, and only the
1705 mips-idt-ecoff target has been tested.
1709 GDB configuration now uses autoconf. This is not user-visible,
1710 but does simplify configuration and building.
1714 GDB now supports hpux10.
1716 *** Changes in GDB-4.14:
1718 * New native configurations
1720 x86 FreeBSD i[345]86-*-freebsd
1721 x86 NetBSD i[345]86-*-netbsd
1722 NS32k NetBSD ns32k-*-netbsd
1723 Sparc NetBSD sparc-*-netbsd
1727 A29K VxWorks a29k-*-vxworks
1728 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1729 CPU32 EST-300 emulator m68*-*-est*
1730 PowerPC ELF powerpc-*-elf
1733 * Alpha OSF/1 support for procfs
1735 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1736 possible to attach to running processes. As the mounting of the /proc
1737 filesystem is optional on the Alpha, GDB automatically determines
1738 the availability of /proc during startup. This can lead to problems
1739 if /proc is unmounted after GDB has been started.
1741 * Arguments to user-defined commands
1743 User commands may accept up to 10 arguments separated by whitespace.
1744 Arguments are accessed within the user command via $arg0..$arg9. A
1747 print $arg0 + $arg1 + $arg2
1749 To execute the command use:
1752 Defines the command "adder" which prints the sum of its three arguments.
1753 Note the arguments are text substitutions, so they may reference variables,
1754 use complex expressions, or even perform inferior function calls.
1756 * New `if' and `while' commands
1758 This makes it possible to write more sophisticated user-defined
1759 commands. Both commands take a single argument, which is the
1760 expression to evaluate, and must be followed by the commands to
1761 execute, one per line, if the expression is nonzero, the list being
1762 terminated by the word `end'. The `if' command list may include an
1763 `else' word, which causes the following commands to be executed only
1764 if the expression is zero.
1766 * Fortran source language mode
1768 GDB now includes partial support for Fortran 77. It will recognize
1769 Fortran programs and can evaluate a subset of Fortran expressions, but
1770 variables and functions may not be handled correctly. GDB will work
1771 with G77, but does not yet know much about symbols emitted by other
1774 * Better HPUX support
1776 Most debugging facilities now work on dynamic executables for HPPAs
1777 running hpux9 or later. You can attach to running dynamically linked
1778 processes, but by default the dynamic libraries will be read-only, so
1779 for instance you won't be able to put breakpoints in them. To change
1780 that behavior do the following before running the program:
1786 This will cause the libraries to be mapped private and read-write.
1787 To revert to the normal behavior, do this:
1793 You cannot set breakpoints or examine data in the library until after
1794 the library is loaded if the function/data symbols do not have
1797 GDB can now also read debug symbols produced by the HP C compiler on
1798 HPPAs (sorry, no C++, Fortran or 68k support).
1800 * Target byte order now dynamically selectable
1802 You can choose which byte order to use with a target system, via the
1803 commands "set endian big" and "set endian little", and you can see the
1804 current setting by using "show endian". You can also give the command
1805 "set endian auto", in which case GDB will use the byte order
1806 associated with the executable. Currently, only embedded MIPS
1807 configurations support dynamic selection of target byte order.
1809 * New DOS host serial code
1811 This version uses DPMI interrupts to handle buffered I/O, so you
1812 no longer need to run asynctsr when debugging boards connected to
1815 *** Changes in GDB-4.13:
1817 * New "complete" command
1819 This lists all the possible completions for the rest of the line, if it
1820 were to be given as a command itself. This is intended for use by emacs.
1822 * Trailing space optional in prompt
1824 "set prompt" no longer adds a space for you after the prompt you set. This
1825 allows you to set a prompt which ends in a space or one that does not.
1827 * Breakpoint hit counts
1829 "info break" now displays a count of the number of times the breakpoint
1830 has been hit. This is especially useful in conjunction with "ignore"; you
1831 can ignore a large number of breakpoint hits, look at the breakpoint info
1832 to see how many times the breakpoint was hit, then run again, ignoring one
1833 less than that number, and this will get you quickly to the last hit of
1836 * Ability to stop printing at NULL character
1838 "set print null-stop" will cause GDB to stop printing the characters of
1839 an array when the first NULL is encountered. This is useful when large
1840 arrays actually contain only short strings.
1842 * Shared library breakpoints
1844 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1845 breakpoints in shared libraries before the executable is run.
1847 * Hardware watchpoints
1849 There is a new hardware breakpoint for the watch command for sparclite
1850 targets. See gdb/sparclite/hw_breakpoint.note.
1852 Hardware watchpoints are also now supported under GNU/Linux.
1856 Annotations have been added. These are for use with graphical interfaces,
1857 and are still experimental. Currently only gdba.el uses these.
1859 * Improved Irix 5 support
1861 GDB now works properly with Irix 5.2.
1863 * Improved HPPA support
1865 GDB now works properly with the latest GCC and GAS.
1867 * New native configurations
1869 Sequent PTX4 i[34]86-sequent-ptx4
1870 HPPA running OSF/1 hppa*-*-osf*
1871 Atari TT running SVR4 m68*-*-sysv4*
1872 RS/6000 LynxOS rs6000-*-lynxos*
1876 OS/9000 i[34]86-*-os9k
1877 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1880 * Hitachi SH7000 and E7000-PC ICE support
1882 There is now support for communicating with the Hitachi E7000-PC ICE.
1883 This is available automatically when GDB is configured for the SH.
1887 As usual, a variety of small fixes and improvements, both generic
1888 and configuration-specific. See the ChangeLog for more detail.
1890 *** Changes in GDB-4.12:
1892 * Irix 5 is now supported
1896 GDB-4.12 on the HPPA has a number of changes which make it unable
1897 to debug the output from the currently released versions of GCC and
1898 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1899 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1900 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1903 *** Changes in GDB-4.11:
1905 * User visible changes:
1909 The "set remotedebug" option is now consistent between the mips remote
1910 target, remote targets using the gdb-specific protocol, UDI (AMD's
1911 debug protocol for the 29k) and the 88k bug monitor. It is now an
1912 integer specifying a debug level (normally 0 or 1, but 2 means more
1913 debugging info for the mips target).
1915 * DEC Alpha native support
1917 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1918 debug info, but GDB works fairly well with the DEC compiler and should
1919 work with a future GCC release. See the README file for a few
1920 Alpha-specific notes.
1922 * Preliminary thread implementation
1924 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1926 * LynxOS native and target support for 386
1928 This release has been hosted on LynxOS 2.2, and also can be configured
1929 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1932 * Improvements in C++ mangling/demangling.
1934 This release has much better g++ debugging, specifically in name
1935 mangling/demangling, virtual function calls, print virtual table,
1936 call methods, ...etc.
1938 *** Changes in GDB-4.10:
1940 * User visible changes:
1942 Remote debugging using the GDB-specific (`target remote') protocol now
1943 supports the `load' command. This is only useful if you have some
1944 other way of getting the stub to the target system, and you can put it
1945 somewhere in memory where it won't get clobbered by the download.
1947 Filename completion now works.
1949 When run under emacs mode, the "info line" command now causes the
1950 arrow to point to the line specified. Also, "info line" prints
1951 addresses in symbolic form (as well as hex).
1953 All vxworks based targets now support a user settable option, called
1954 vxworks-timeout. This option represents the number of seconds gdb
1955 should wait for responses to rpc's. You might want to use this if
1956 your vxworks target is, perhaps, a slow software simulator or happens
1957 to be on the far side of a thin network line.
1961 This release contains support for using a DEC alpha as a GDB host for
1962 cross debugging. Native alpha debugging is not supported yet.
1965 *** Changes in GDB-4.9:
1969 This is the first GDB release which is accompanied by a matching testsuite.
1970 The testsuite requires installation of dejagnu, which should be available
1971 via ftp from most sites that carry GNU software.
1975 'Cfront' style demangling has had its name changed to 'ARM' style, to
1976 emphasize that it was written from the specifications in the C++ Annotated
1977 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1978 disclaimers, it still generated too much confusion with users attempting to
1979 use gdb with AT&T cfront.
1983 GDB now uses a standard remote interface to a simulator library.
1984 So far, the library contains simulators for the Zilog Z8001/2, the
1985 Hitachi H8/300, H8/500 and Super-H.
1987 * New targets supported
1989 H8/300 simulator h8300-hitachi-hms or h8300hms
1990 H8/500 simulator h8500-hitachi-hms or h8500hms
1991 SH simulator sh-hitachi-hms or sh
1992 Z8000 simulator z8k-zilog-none or z8ksim
1993 IDT MIPS board over serial line mips-idt-ecoff
1995 Cross-debugging to GO32 targets is supported. It requires a custom
1996 version of the i386-stub.c module which is integrated with the
1997 GO32 memory extender.
1999 * New remote protocols
2001 MIPS remote debugging protocol.
2003 * New source languages supported
2005 This version includes preliminary support for Chill, a Pascal like language
2006 used by telecommunications companies. Chill support is also being integrated
2007 into the GNU compiler, but we don't know when it will be publically available.
2010 *** Changes in GDB-4.8:
2012 * HP Precision Architecture supported
2014 GDB now supports HP PA-RISC machines running HPUX. A preliminary
2015 version of this support was available as a set of patches from the
2016 University of Utah. GDB does not support debugging of programs
2017 compiled with the HP compiler, because HP will not document their file
2018 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
2019 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
2021 Many problems in the preliminary version have been fixed.
2023 * Faster and better demangling
2025 We have improved template demangling and fixed numerous bugs in the GNU style
2026 demangler. It can now handle type modifiers such as `static' or `const'. Wide
2027 character types (wchar_t) are now supported. Demangling of each symbol is now
2028 only done once, and is cached when the symbol table for a file is read in.
2029 This results in a small increase in memory usage for C programs, a moderate
2030 increase in memory usage for C++ programs, and a fantastic speedup in
2033 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
2034 from the specifications in the Annotated Reference Manual, which AT&T's
2035 compiler does not actually implement.
2037 * G++ multiple inheritance compiler problem
2039 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
2040 inheritance lattices was reworked to properly discover ambiguities. We
2041 recently found an example which causes this new algorithm to fail in a
2042 very subtle way, producing bad debug information for those classes.
2043 The file 'gcc.patch' (in this directory) can be applied to gcc to
2044 circumvent the problem. A future GCC release will contain a complete
2047 The previous G++ debug info problem (mentioned below for the gdb-4.7
2048 release) is fixed in gcc version 2.3.2.
2050 * Improved configure script
2052 The `configure' script will now attempt to guess your system type if
2053 you don't supply a host system type. The old scheme of supplying a
2054 host system triplet is preferable over using this. All the magic is
2055 done in the new `config.guess' script. Examine it for details.
2057 We have also brought our configure script much more in line with the FSF's
2058 version. It now supports the --with-xxx options. In particular,
2059 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
2060 The resulting GDB will not be able to read arbitrary object file formats --
2061 only the format ``expected'' to be used on the configured target system.
2062 We hope to make this the default in a future release.
2064 * Documentation improvements
2066 There's new internal documentation on how to modify GDB, and how to
2067 produce clean changes to the code. We implore people to read it
2068 before submitting changes.
2070 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
2071 M4 macros. The new texinfo.tex is provided in this release. Pre-built
2072 `info' files are also provided. To build `info' files from scratch,
2073 you will need the latest `makeinfo' release, which will be available in
2074 a future texinfo-X.Y release.
2076 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
2077 We're not sure exactly which versions have this problem, but it has
2078 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
2079 or better. If that isn't possible, there is a patch in
2080 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
2081 around this problem.
2085 GDB now supports array constants that can be used in expressions typed in by
2086 the user. The syntax is `{element, element, ...}'. Ie: you can now type
2087 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
2090 The new directory `gdb/sparclite' contains a program that demonstrates
2091 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
2093 * New native hosts supported
2095 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
2096 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
2098 * New targets supported
2100 AMD 29k family via UDI a29k-amd-udi or udi29k
2102 * New file formats supported
2104 BFD now supports reading HP/PA-RISC executables (SOM file format?),
2105 HPUX core files, and SCO 3.2v2 core files.
2109 Attaching to processes now works again; thanks for the many bug reports.
2111 We have also stomped on a bunch of core dumps caused by
2112 printf_filtered("%s") problems.
2114 We eliminated a copyright problem on the rpc and ptrace header files
2115 for VxWorks, which was discovered at the last minute during the 4.7
2116 release. You should now be able to build a VxWorks GDB.
2118 You can now interrupt gdb while an attached process is running. This
2119 will cause the attached process to stop, and give control back to GDB.
2121 We fixed problems caused by using too many file descriptors
2122 for reading symbols from object files and libraries. This was
2123 especially a problem for programs that used many (~100) shared
2126 The `step' command now only enters a subroutine if there is line number
2127 information for the subroutine. Otherwise it acts like the `next'
2128 command. Previously, `step' would enter subroutines if there was
2129 any debugging information about the routine. This avoids problems
2130 when using `cc -g1' on MIPS machines.
2132 * Internal improvements
2134 GDB's internal interfaces have been improved to make it easier to support
2135 debugging of multiple languages in the future.
2137 GDB now uses a common structure for symbol information internally.
2138 Minimal symbols (derived from linkage symbols in object files), partial
2139 symbols (from a quick scan of debug information), and full symbols
2140 contain a common subset of information, making it easier to write
2141 shared code that handles any of them.
2143 * New command line options
2145 We now accept --silent as an alias for --quiet.
2149 The memory-mapped-malloc library is now licensed under the GNU Library
2150 General Public License.
2152 *** Changes in GDB-4.7:
2154 * Host/native/target split
2156 GDB has had some major internal surgery to untangle the support for
2157 hosts and remote targets. Now, when you configure GDB for a remote
2158 target, it will no longer load in all of the support for debugging
2159 local programs on the host. When fully completed and tested, this will
2160 ensure that arbitrary host/target combinations are possible.
2162 The primary conceptual shift is to separate the non-portable code in
2163 GDB into three categories. Host specific code is required any time GDB
2164 is compiled on that host, regardless of the target. Target specific
2165 code relates to the peculiarities of the target, but can be compiled on
2166 any host. Native specific code is everything else: it can only be
2167 built when the host and target are the same system. Child process
2168 handling and core file support are two common `native' examples.
2170 GDB's use of /proc for controlling Unix child processes is now cleaner.
2171 It has been split out into a single module under the `target_ops' vector,
2172 plus two native-dependent functions for each system that uses /proc.
2174 * New hosts supported
2176 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
2177 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2178 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
2180 * New targets supported
2182 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
2183 68030 and CPU32 m68030-*-*, m68332-*-*
2185 * New native hosts supported
2187 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2188 (386bsd is not well tested yet)
2189 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
2191 * New file formats supported
2193 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
2194 supports reading of `a.out.adobe' object files, which are an a.out
2195 format extended with minimal information about multiple sections.
2199 `show copying' is the same as the old `info copying'.
2200 `show warranty' is the same as `info warrantee'.
2201 These were renamed for consistency. The old commands continue to work.
2203 `info handle' is a new alias for `info signals'.
2205 You can now define pre-command hooks, which attach arbitrary command
2206 scripts to any command. The commands in the hook will be executed
2207 prior to the user's command. You can also create a hook which will be
2208 executed whenever the program stops. See gdb.texinfo.
2212 We now deal with Cfront style name mangling, and can even extract type
2213 info from mangled symbols. GDB can automatically figure out which
2214 symbol mangling style your C++ compiler uses.
2216 Calling of methods and virtual functions has been improved as well.
2220 The crash that occured when debugging Sun Ansi-C compiled binaries is
2221 fixed. This was due to mishandling of the extra N_SO stabs output
2224 We also finally got Ultrix 4.2 running in house, and fixed core file
2225 support, with help from a dozen people on the net.
2227 John M. Farrell discovered that the reason that single-stepping was so
2228 slow on all of the Mips based platforms (primarily SGI and DEC) was
2229 that we were trying to demangle and lookup a symbol used for internal
2230 purposes on every instruction that was being stepped through. Changing
2231 the name of that symbol so that it couldn't be mistaken for a C++
2232 mangled symbol sped things up a great deal.
2234 Rich Pixley sped up symbol lookups in general by getting much smarter
2235 about when C++ symbol mangling is necessary. This should make symbol
2236 completion (TAB on the command line) much faster. It's not as fast as
2237 we'd like, but it's significantly faster than gdb-4.6.
2241 A new user controllable variable 'call_scratch_address' can
2242 specify the location of a scratch area to be used when GDB
2243 calls a function in the target. This is necessary because the
2244 usual method of putting the scratch area on the stack does not work
2245 in systems that have separate instruction and data spaces.
2247 We integrated changes to support the 29k UDI (Universal Debugger
2248 Interface), but discovered at the last minute that we didn't have all
2249 of the appropriate copyright paperwork. We are working with AMD to
2250 resolve this, and hope to have it available soon.
2254 We have sped up the remote serial line protocol, especially for targets
2255 with lots of registers. It now supports a new `expedited status' ('T')
2256 message which can be used in place of the existing 'S' status message.
2257 This allows the remote stub to send only the registers that GDB
2258 needs to make a quick decision about single-stepping or conditional
2259 breakpoints, eliminating the need to fetch the entire register set for
2260 each instruction being stepped through.
2262 The GDB remote serial protocol now implements a write-through cache for
2263 registers, only re-reading the registers if the target has run.
2265 There is also a new remote serial stub for SPARC processors. You can
2266 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
2267 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
2268 processor with a serial port.
2272 Configure.in files have become much easier to read and modify. A new
2273 `table driven' format makes it more obvious what configurations are
2274 supported, and what files each one uses.
2278 There is a new opcodes library which will eventually contain all of the
2279 disassembly routines and opcode tables. At present, it only contains
2280 Sparc and Z8000 routines. This will allow the assembler, debugger, and
2281 disassembler (binutils/objdump) to share these routines.
2283 The libiberty library is now copylefted under the GNU Library General
2284 Public License. This allows more liberal use, and was done so libg++
2285 can use it. This makes no difference to GDB, since the Library License
2286 grants all the rights from the General Public License.
2290 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
2291 reference to the stabs symbol info used by the debugger. It is (as far
2292 as we know) the only published document on this fascinating topic. We
2293 encourage you to read it, compare it to the stabs information on your
2294 system, and send improvements on the document in general (to
2295 bug-gdb@prep.ai.mit.edu).
2297 And, of course, many bugs have been fixed.
2300 *** Changes in GDB-4.6:
2302 * Better support for C++ function names
2304 GDB now accepts as input the "demangled form" of C++ overloaded function
2305 names and member function names, and can do command completion on such names
2306 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
2307 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
2308 Make use of command completion, it is your friend.
2310 GDB also now accepts a variety of C++ mangled symbol formats. They are
2311 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
2312 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
2313 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
2314 for the list of formats.
2316 * G++ symbol mangling problem
2318 Recent versions of gcc have a bug in how they emit debugging information for
2319 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
2320 directory) can be applied to gcc to fix the problem. Alternatively, if you
2321 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
2322 usual symptom is difficulty with setting breakpoints on methods. GDB complains
2323 about the method being non-existent. (We believe that version 2.2.2 of GCC has
2326 * New 'maintenance' command
2328 All of the commands related to hacking GDB internals have been moved out of
2329 the main command set, and now live behind the 'maintenance' command. This
2330 can also be abbreviated as 'mt'. The following changes were made:
2332 dump-me -> maintenance dump-me
2333 info all-breakpoints -> maintenance info breakpoints
2334 printmsyms -> maintenance print msyms
2335 printobjfiles -> maintenance print objfiles
2336 printpsyms -> maintenance print psymbols
2337 printsyms -> maintenance print symbols
2339 The following commands are new:
2341 maintenance demangle Call internal GDB demangler routine to
2342 demangle a C++ link name and prints the result.
2343 maintenance print type Print a type chain for a given symbol
2345 * Change to .gdbinit file processing
2347 We now read the $HOME/.gdbinit file before processing the argv arguments
2348 (e.g. reading symbol files or core files). This allows global parameters to
2349 be set, which will apply during the symbol reading. The ./.gdbinit is still
2350 read after argv processing.
2352 * New hosts supported
2354 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
2356 GNU/Linux support i386-unknown-linux or linux
2358 We are also including code to support the HP/PA running BSD and HPUX. This
2359 is almost guaranteed not to work, as we didn't have time to test or build it
2360 for this release. We are including it so that the more adventurous (or
2361 masochistic) of you can play with it. We also had major problems with the
2362 fact that the compiler that we got from HP doesn't support the -g option.
2365 * New targets supported
2367 Hitachi H8/300 h8300-hitachi-hms or h8300hms
2369 * More smarts about finding #include files
2371 GDB now remembers the compilation directory for all include files, and for
2372 all files from which C is generated (like yacc and lex sources). This
2373 greatly improves GDB's ability to find yacc/lex sources, and include files,
2374 especially if you are debugging your program from a directory different from
2375 the one that contains your sources.
2377 We also fixed a bug which caused difficulty with listing and setting
2378 breakpoints in include files which contain C code. (In the past, you had to
2379 try twice in order to list an include file that you hadn't looked at before.)
2381 * Interesting infernals change
2383 GDB now deals with arbitrary numbers of sections, where the symbols for each
2384 section must be relocated relative to that section's landing place in the
2385 target's address space. This work was needed to support ELF with embedded
2386 stabs used by Solaris-2.0.
2388 * Bug fixes (of course!)
2390 There have been loads of fixes for the following things:
2391 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
2392 i960, stabs, DOS(GO32), procfs, etc...
2394 See the ChangeLog for details.
2396 *** Changes in GDB-4.5:
2398 * New machines supported (host and target)
2400 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
2402 SGI Irix-4.x mips-sgi-irix4 or iris4
2404 * New malloc package
2406 GDB now uses a new memory manager called mmalloc, based on gmalloc.
2407 Mmalloc is capable of handling mutiple heaps of memory. It is also
2408 capable of saving a heap to a file, and then mapping it back in later.
2409 This can be used to greatly speedup the startup of GDB by using a
2410 pre-parsed symbol table which lives in a mmalloc managed heap. For
2411 more details, please read mmalloc/mmalloc.texi.
2415 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
2416 'help info proc' for details.
2418 * MIPS ecoff symbol table format
2420 The code that reads MIPS symbol table format is now supported on all hosts.
2421 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
2424 * File name changes for MS-DOS
2426 Many files in the config directories have been renamed to make it easier to
2427 support GDB on MS-DOSe systems (which have very restrictive file name
2428 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
2429 environment) is close to working but has some remaining problems. Note
2430 that debugging of DOS programs is not supported, due to limitations
2431 in the ``operating system'', but it can be used to host cross-debugging.
2433 * Cross byte order fixes
2435 Many fixes have been made to support cross debugging of Sparc and MIPS
2436 targets from hosts whose byte order differs.
2438 * New -mapped and -readnow options
2440 If memory-mapped files are available on your system through the 'mmap'
2441 system call, you can use the -mapped option on the `file' or
2442 `symbol-file' commands to cause GDB to write the symbols from your
2443 program into a reusable file. If the program you are debugging is
2444 called `/path/fred', the mapped symbol file will be `./fred.syms'.
2445 Future GDB debugging sessions will notice the presence of this file,
2446 and will quickly map in symbol information from it, rather than reading
2447 the symbol table from the executable program. Using the '-mapped'
2448 option in a GDB `file' or `symbol-file' command has the same effect as
2449 starting GDB with the '-mapped' command-line option.
2451 You can cause GDB to read the entire symbol table immediately by using
2452 the '-readnow' option with any of the commands that load symbol table
2453 information (or on the GDB command line). This makes the command
2454 slower, but makes future operations faster.
2456 The -mapped and -readnow options are typically combined in order to
2457 build a `fred.syms' file that contains complete symbol information.
2458 A simple GDB invocation to do nothing but build a `.syms' file for future
2461 gdb -batch -nx -mapped -readnow programname
2463 The `.syms' file is specific to the host machine on which GDB is run.
2464 It holds an exact image of GDB's internal symbol table. It cannot be
2465 shared across multiple host platforms.
2467 * longjmp() handling
2469 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
2470 siglongjmp() without losing control. This feature has not yet been ported to
2471 all systems. It currently works on many 386 platforms, all MIPS-based
2472 platforms (SGI, DECstation, etc), and Sun3/4.
2476 Preliminary work has been put in to support the new Solaris OS from Sun. At
2477 this time, it can control and debug processes, but it is not capable of
2482 As always, many many bug fixes. The major areas were with g++, and mipsread.
2483 People using the MIPS-based platforms should experience fewer mysterious
2484 crashes and trashed symbol tables.
2486 *** Changes in GDB-4.4:
2488 * New machines supported (host and target)
2490 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2492 BSD Reno on Vax vax-dec-bsd
2493 Ultrix on Vax vax-dec-ultrix
2495 * New machines supported (target)
2497 AMD 29000 embedded, using EBMON a29k-none-none
2501 GDB continues to improve its handling of C++. `References' work better.
2502 The demangler has also been improved, and now deals with symbols mangled as
2503 per the Annotated C++ Reference Guide.
2505 GDB also now handles `stabs' symbol information embedded in MIPS
2506 `ecoff' symbol tables. Since the ecoff format was not easily
2507 extensible to handle new languages such as C++, this appeared to be a
2508 good way to put C++ debugging info into MIPS binaries. This option
2509 will be supported in the GNU C compiler, version 2, when it is
2512 * New features for SVR4
2514 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
2515 shared libraries. Debugging dynamically linked programs should present
2516 only minor differences from debugging statically linked programs.
2518 The `info proc' command will print out information about any process
2519 on an SVR4 system (including the one you are debugging). At the moment,
2520 it prints the address mappings of the process.
2522 If you bring up GDB on another SVR4 system, please send mail to
2523 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
2525 * Better dynamic linking support in SunOS
2527 Reading symbols from shared libraries which contain debugging symbols
2528 now works properly. However, there remain issues such as automatic
2529 skipping of `transfer vector' code during function calls, which
2530 make it harder to debug code in a shared library, than to debug the
2531 same code linked statically.
2535 GDB is now using the latest `getopt' routines from the FSF. This
2536 version accepts the -- prefix for options with long names. GDB will
2537 continue to accept the old forms (-option and +option) as well.
2538 Various single letter abbreviations for options have been explicity
2539 added to the option table so that they won't get overshadowed in the
2540 future by other options that begin with the same letter.
2544 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
2545 Many assorted bugs have been handled. Many more remain to be handled.
2546 See the various ChangeLog files (primarily in gdb and bfd) for details.
2549 *** Changes in GDB-4.3:
2551 * New machines supported (host and target)
2553 Amiga 3000 running Amix m68k-cbm-svr4 or amix
2554 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
2555 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
2557 * Almost SCO Unix support
2559 We had hoped to support:
2560 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2561 (except for core file support), but we discovered very late in the release
2562 that it has problems with process groups that render gdb unusable. Sorry
2563 about that. I encourage people to fix it and post the fixes.
2565 * Preliminary ELF and DWARF support
2567 GDB can read ELF object files on System V Release 4, and can handle
2568 debugging records for C, in DWARF format, in ELF files. This support
2569 is preliminary. If you bring up GDB on another SVR4 system, please
2570 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
2575 GDB now uses the latest `readline' library. One user-visible change
2576 is that two tabs will list possible command completions, which previously
2577 required typing M-? (meta-question mark, or ESC ?).
2581 The `stepi' bug that many of you noticed has been squashed.
2582 Many bugs in C++ have been handled. Many more remain to be handled.
2583 See the various ChangeLog files (primarily in gdb and bfd) for details.
2585 * State of the MIPS world (in case you wondered):
2587 GDB can understand the symbol tables emitted by the compilers
2588 supplied by most vendors of MIPS-based machines, including DEC. These
2589 symbol tables are in a format that essentially nobody else uses.
2591 Some versions of gcc come with an assembler post-processor called
2592 mips-tfile. This program is required if you want to do source-level
2593 debugging of gcc-compiled programs. I believe FSF does not ship
2594 mips-tfile with gcc version 1, but it will eventually come with gcc
2597 Debugging of g++ output remains a problem. g++ version 1.xx does not
2598 really support it at all. (If you're lucky, you should be able to get
2599 line numbers and stack traces to work, but no parameters or local
2600 variables.) With some work it should be possible to improve the
2603 When gcc version 2 is released, you will have somewhat better luck.
2604 However, even then you will get confusing results for inheritance and
2607 We will eventually provide full debugging of g++ output on
2608 DECstations. This will probably involve some kind of stabs-in-ecoff
2609 encapulation, but the details have not been worked out yet.
2612 *** Changes in GDB-4.2:
2614 * Improved configuration
2616 Only one copy of `configure' exists now, and it is not self-modifying.
2617 Porting BFD is simpler.
2621 The `step' and `next' commands now only stop at the first instruction
2622 of a source line. This prevents the multiple stops that used to occur
2623 in switch statements, for-loops, etc. `Step' continues to stop if a
2624 function that has debugging information is called within the line.
2628 Lots of small bugs fixed. More remain.
2630 * New host supported (not target)
2632 Intel 386 PC clone running Mach i386-none-mach
2635 *** Changes in GDB-4.1:
2637 * Multiple source language support
2639 GDB now has internal scaffolding to handle several source languages.
2640 It determines the type of each source file from its filename extension,
2641 and will switch expression parsing and number formatting to match the
2642 language of the function in the currently selected stack frame.
2643 You can also specifically set the language to be used, with
2644 `set language c' or `set language modula-2'.
2648 GDB now has preliminary support for the GNU Modula-2 compiler,
2649 currently under development at the State University of New York at
2650 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
2651 continue through the fall of 1991 and into 1992.
2653 Other Modula-2 compilers are currently not supported, and attempting to
2654 debug programs compiled with them will likely result in an error as the
2655 symbol table is read. Feel free to work on it, though!
2657 There are hooks in GDB for strict type checking and range checking,
2658 in the `Modula-2 philosophy', but they do not currently work.
2662 GDB can now write to executable and core files (e.g. patch
2663 a variable's value). You must turn this switch on, specify
2664 the file ("exec foo" or "core foo"), *then* modify it, e.g.
2665 by assigning a new value to a variable. Modifications take
2668 * Automatic SunOS shared library reading
2670 When you run your program, GDB automatically determines where its
2671 shared libraries (if any) have been loaded, and reads their symbols.
2672 The `share' command is no longer needed. This also works when
2673 examining core files.
2677 You can specify the number of lines that the `list' command shows.
2680 * New machines supported (host and target)
2682 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
2683 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
2684 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
2686 * New hosts supported (not targets)
2688 IBM RT/PC: romp-ibm-aix or rtpc
2690 * New targets supported (not hosts)
2692 AMD 29000 embedded with COFF a29k-none-coff
2693 AMD 29000 embedded with a.out a29k-none-aout
2694 Ultracomputer remote kernel debug a29k-nyu-kern
2696 * New remote interfaces
2702 *** Changes in GDB-4.0:
2706 Wide output is wrapped at good places to make the output more readable.
2708 Gdb now supports cross-debugging from a host machine of one type to a
2709 target machine of another type. Communication with the target system
2710 is over serial lines. The ``target'' command handles connecting to the
2711 remote system; the ``load'' command will download a program into the
2712 remote system. Serial stubs for the m68k and i386 are provided. Gdb
2713 also supports debugging of realtime processes running under VxWorks,
2714 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
2715 stub on the target system.
2717 New CPUs supported include the AMD 29000 and Intel 960.
2719 GDB now reads object files and symbol tables via a ``binary file''
2720 library, which allows a single copy of GDB to debug programs of multiple
2721 object file types such as a.out and coff.
2723 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2724 refcard.dvi and refcard.ps are available to format it).
2727 * Control-Variable user interface simplified
2729 All variables that control the operation of the debugger can be set
2730 by the ``set'' command, and displayed by the ``show'' command.
2732 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2733 ``Show prompt'' produces the response:
2734 Gdb's prompt is new-gdb=>.
2736 What follows are the NEW set commands. The command ``help set'' will
2737 print a complete list of old and new set commands. ``help set FOO''
2738 will give a longer description of the variable FOO. ``show'' will show
2739 all of the variable descriptions and their current settings.
2741 confirm on/off: Enables warning questions for operations that are
2742 hard to recover from, e.g. rerunning the program while
2743 it is already running. Default is ON.
2745 editing on/off: Enables EMACS style command line editing
2746 of input. Previous lines can be recalled with
2747 control-P, the current line can be edited with control-B,
2748 you can search for commands with control-R, etc.
2751 history filename NAME: NAME is where the gdb command history
2752 will be stored. The default is .gdb_history,
2753 or the value of the environment variable
2756 history size N: The size, in commands, of the command history. The
2757 default is 256, or the value of the environment variable
2760 history save on/off: If this value is set to ON, the history file will
2761 be saved after exiting gdb. If set to OFF, the
2762 file will not be saved. The default is OFF.
2764 history expansion on/off: If this value is set to ON, then csh-like
2765 history expansion will be performed on
2766 command line input. The default is OFF.
2768 radix N: Sets the default radix for input and output. It can be set
2769 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2770 in the current radix, so "set radix 10" is always a no-op.
2772 height N: This integer value is the number of lines on a page. Default
2773 is 24, the current `stty rows'' setting, or the ``li#''
2774 setting from the termcap entry matching the environment
2777 width N: This integer value is the number of characters on a line.
2778 Default is 80, the current `stty cols'' setting, or the ``co#''
2779 setting from the termcap entry matching the environment
2782 Note: ``set screensize'' is obsolete. Use ``set height'' and
2783 ``set width'' instead.
2785 print address on/off: Print memory addresses in various command displays,
2786 such as stack traces and structure values. Gdb looks
2787 more ``symbolic'' if you turn this off; it looks more
2788 ``machine level'' with it on. Default is ON.
2790 print array on/off: Prettyprint arrays. New convenient format! Default
2793 print demangle on/off: Print C++ symbols in "source" form if on,
2796 print asm-demangle on/off: Same, for assembler level printouts
2799 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2802 * Support for Epoch Environment.
2804 The epoch environment is a version of Emacs v18 with windowing. One
2805 new command, ``inspect'', is identical to ``print'', except that if you
2806 are running in the epoch environment, the value is printed in its own
2810 * Support for Shared Libraries
2812 GDB can now debug programs and core files that use SunOS shared libraries.
2813 Symbols from a shared library cannot be referenced
2814 before the shared library has been linked with the program (this
2815 happens after you type ``run'' and before the function main() is entered).
2816 At any time after this linking (including when examining core files
2817 from dynamically linked programs), gdb reads the symbols from each
2818 shared library when you type the ``sharedlibrary'' command.
2819 It can be abbreviated ``share''.
2821 sharedlibrary REGEXP: Load shared object library symbols for files
2822 matching a unix regular expression. No argument
2823 indicates to load symbols for all shared libraries.
2825 info sharedlibrary: Status of loaded shared libraries.
2830 A watchpoint stops execution of a program whenever the value of an
2831 expression changes. Checking for this slows down execution
2832 tremendously whenever you are in the scope of the expression, but is
2833 quite useful for catching tough ``bit-spreader'' or pointer misuse
2834 problems. Some machines such as the 386 have hardware for doing this
2835 more quickly, and future versions of gdb will use this hardware.
2837 watch EXP: Set a watchpoint (breakpoint) for an expression.
2839 info watchpoints: Information about your watchpoints.
2841 delete N: Deletes watchpoint number N (same as breakpoints).
2842 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2843 enable N: Re-enables watchpoint number N (same as breakpoints).
2846 * C++ multiple inheritance
2848 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2851 * C++ exception handling
2853 Gdb now supports limited C++ exception handling. Besides the existing
2854 ability to breakpoint on an exception handler, gdb can breakpoint on
2855 the raising of an exception (before the stack is peeled back to the
2858 catch FOO: If there is a FOO exception handler in the dynamic scope,
2859 set a breakpoint to catch exceptions which may be raised there.
2860 Multiple exceptions (``catch foo bar baz'') may be caught.
2862 info catch: Lists all exceptions which may be caught in the
2863 current stack frame.
2866 * Minor command changes
2868 The command ``call func (arg, arg, ...)'' now acts like the print
2869 command, except it does not print or save a value if the function's result
2870 is void. This is similar to dbx usage.
2872 The ``up'' and ``down'' commands now always print the frame they end up
2873 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2874 frames without printing.
2876 * New directory command
2878 'dir' now adds directories to the FRONT of the source search path.
2879 The path starts off empty. Source files that contain debug information
2880 about the directory in which they were compiled can be found even
2881 with an empty path; Sun CC and GCC include this information. If GDB can't
2882 find your source file in the current directory, type "dir .".
2884 * Configuring GDB for compilation
2886 For normal use, type ``./configure host''. See README or gdb.texinfo
2889 GDB now handles cross debugging. If you are remotely debugging between
2890 two different machines, type ``./configure host -target=targ''.
2891 Host is the machine where GDB will run; targ is the machine
2892 where the program that you are debugging will run.
projects / deliverable / binutils-gdb.git / blob