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.
17 * Support for GNU/Linux Thread Local Storage (TLS, per-thread variables) no
18 longer requires symbolic debug information (e.g. DWARF-2).
25 Manage a list of substitution rules that GDB uses to rewrite the name
26 of the directories where the sources are located. This can be useful
27 for instance when the sources were moved to a different location
28 between compilation and debugging.
32 Print each CLI command as it is executed. Each command is prefixed with
33 a number of `+' symbols representing the nesting depth.
34 The source command now has a `-v' option to enable the same feature.
38 The ARM Demon monitor support (RDP protocol, "target rdp").
40 Kernel Object Display, an embedded debugging feature which only worked with
41 an obsolete version of Cisco IOS.
43 The 'set download-write-size' and 'show download-write-size' commands.
48 Tell a stub about GDB client features, and request remote target features.
49 The first feature implemented is PacketSize, which allows the target to
50 specify the size of packets it can handle - to minimize the number of
51 packets required and improve performance when connected to a remote
55 Fetch an OS auxilliary vector from the remote stub. This packet is a
56 more efficient replacement for qPart:auxv:read.
58 * Removed remote packets
61 This packet has been replaced by qXfer:auxv:read. Only GDB 6.4 and 6.5
62 used it, and only gdbserver implemented it.
64 *** Changes in GDB 6.5
68 Renesas M32C/M16C m32c-elf
70 Morpho Technologies ms1 ms1-elf
74 init-if-undefined Initialize a convenience variable, but
75 only if it doesn't already have a value.
77 The following commands are presently only implemented for native GNU/Linux:
79 checkpoint Save a snapshot of the program state.
81 restart <n> Return the program state to a
82 previously saved state.
84 info checkpoints List currently saved checkpoints.
86 delete-checkpoint <n> Delete a previously saved checkpoint.
88 set|show detach-on-fork Tell gdb whether to detach from a newly
89 forked process, or to keep debugging it.
91 info forks List forks of the user program that
92 are available to be debugged.
94 fork <n> Switch to debugging one of several
95 forks of the user program that are
96 available to be debugged.
98 delete-fork <n> Delete a fork from the list of forks
99 that are available to be debugged (and
100 kill the forked process).
102 detach-fork <n> Delete a fork from the list of forks
103 that are available to be debugged (and
104 allow the process to continue).
108 Morpho Technologies ms2 ms1-elf
110 * Improved Windows host support
112 GDB now builds as a cross debugger hosted on i686-mingw32, including
113 native console support, and remote communications using either
114 network sockets or serial ports.
116 * Improved Modula-2 language support
118 GDB can now print most types in the Modula-2 syntax. This includes:
119 basic types, set types, record types, enumerated types, range types,
120 pointer types and ARRAY types. Procedure var parameters are correctly
121 printed and hexadecimal addresses and character constants are also
122 written in the Modula-2 syntax. Best results can be obtained by using
123 GNU Modula-2 together with the -gdwarf-2 command line option.
127 The ARM rdi-share module.
129 The Netware NLM debug server.
131 *** Changes in GDB 6.4
133 * New native configurations
135 OpenBSD/arm arm*-*-openbsd*
136 OpenBSD/mips64 mips64-*-openbsd*
140 Morpho Technologies ms1 ms1-elf
142 * New command line options
144 --batch-silent As for --batch, but totally silent.
145 --return-child-result The debugger will exist with the same value
146 the child (debugged) program exited with.
147 --eval-command COMMAND, -ex COMMAND
148 Execute a single GDB CLI command. This may be
149 specified multiple times and in conjunction
150 with the --command (-x) option.
152 * Deprecated commands removed
154 The following commands, that were deprecated in 2000, have been
158 set|show arm disassembly-flavor set|show arm disassembler
159 othernames set arm disassembler
160 set|show remotedebug set|show debug remote
161 set|show archdebug set|show debug arch
162 set|show eventdebug set|show debug event
165 * New BSD user-level threads support
167 It is now possible to debug programs using the user-level threads
168 library on OpenBSD and FreeBSD. Currently supported (target)
171 FreeBSD/amd64 x86_64-*-freebsd*
172 FreeBSD/i386 i386-*-freebsd*
173 OpenBSD/i386 i386-*-openbsd*
175 Note that the new kernel threads libraries introduced in FreeBSD 5.x
176 are not yet supported.
178 * New support for Matsushita MN10300 w/sim added
179 (Work in progress). mn10300-elf.
181 * REMOVED configurations and files
183 VxWorks and the XDR protocol *-*-vxworks
184 Motorola MCORE mcore-*-*
185 National Semiconductor NS32000 ns32k-*-*
187 * New "set print array-indexes" command
189 After turning this setting "on", GDB prints the index of each element
190 when displaying arrays. The default is "off" to preserve the previous
193 * VAX floating point support
195 GDB now supports the not-quite-ieee VAX F and D floating point formats.
197 * User-defined command support
199 In addition to using $arg0..$arg9 for argument passing, it is now possible
200 to use $argc to determine now many arguments have been passed. See the
201 section on user-defined commands in the user manual for more information.
203 *** Changes in GDB 6.3:
205 * New command line option
207 GDB now accepts -l followed by a number to set the timeout for remote
210 * GDB works with GCC -feliminate-dwarf2-dups
212 GDB now supports a more compact representation of DWARF-2 debug
213 information using DW_FORM_ref_addr references. These are produced
214 by GCC with the option -feliminate-dwarf2-dups and also by some
215 proprietary compilers. With GCC, you must use GCC 3.3.4 or later
216 to use -feliminate-dwarf2-dups.
218 * Internationalization
220 When supported by the host system, GDB will be built with
221 internationalization (libintl). The task of marking up the sources is
222 continued, we're looking forward to our first translation.
226 Initial support for debugging programs compiled with the GNAT
227 implementation of the Ada programming language has been integrated
228 into GDB. In this release, support is limited to expression evaluation.
230 * New native configurations
232 GNU/Linux/m32r m32r-*-linux-gnu
236 GDB's remote protocol now includes support for the 'p' packet. This
237 packet is used to fetch individual registers from a remote inferior.
239 * END-OF-LIFE registers[] compatibility module
241 GDB's internal register infrastructure has been completely rewritten.
242 The new infrastructure making possible the implementation of key new
243 features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit
246 GDB 6.3 will be the last release to include the the registers[]
247 compatibility module that allowed out-of-date configurations to
248 continue to work. This change directly impacts the following
260 Unless there is activity to revive these configurations, they will be
261 made OBSOLETE in GDB 6.4, and REMOVED from GDB 6.5.
263 * OBSOLETE configurations and files
265 Configurations that have been declared obsolete in this release have
266 been commented out. Unless there is activity to revive these
267 configurations, the next release of GDB will have their sources
277 *** Changes in GDB 6.2.1:
279 * MIPS `break main; run' gave an heuristic-fence-post warning
281 When attempting to run even a simple program, a warning about
282 heuristic-fence-post being hit would be reported. This problem has
285 * MIPS IRIX 'long double' crashed GDB
287 When examining a long double variable, GDB would get a segmentation
288 fault. The crash has been fixed (but GDB 6.2 cannot correctly examine
289 IRIX long double values).
293 A bug in the VAX stack code was causing problems with the "next"
294 command. This problem has been fixed.
296 *** Changes in GDB 6.2:
298 * Fix for ``many threads''
300 On GNU/Linux systems that use the NPTL threads library, a program
301 rapidly creating and deleting threads would confuse GDB leading to the
304 ptrace: No such process.
305 thread_db_get_info: cannot get thread info: generic error
307 This problem has been fixed.
309 * "-async" and "-noasync" options removed.
311 Support for the broken "-noasync" option has been removed (it caused
314 * New ``start'' command.
316 This command runs the program until the begining of the main procedure.
318 * New BSD Kernel Data Access Library (libkvm) interface
320 Using ``target kvm'' it is now possible to debug kernel core dumps and
321 live kernel memory images on various FreeBSD, NetBSD and OpenBSD
322 platforms. Currently supported (native-only) configurations are:
324 FreeBSD/amd64 x86_64-*-freebsd*
325 FreeBSD/i386 i?86-*-freebsd*
326 NetBSD/i386 i?86-*-netbsd*
327 NetBSD/m68k m68*-*-netbsd*
328 NetBSD/sparc sparc-*-netbsd*
329 OpenBSD/amd64 x86_64-*-openbsd*
330 OpenBSD/i386 i?86-*-openbsd*
331 OpenBSD/m68k m68*-openbsd*
332 OpenBSD/sparc sparc-*-openbsd*
334 * Signal trampoline code overhauled
336 Many generic problems with GDB's signal handling code have been fixed.
337 These include: backtraces through non-contiguous stacks; recognition
338 of sa_sigaction signal trampolines; backtrace from a NULL pointer
339 call; backtrace through a signal trampoline; step into and out of
340 signal handlers; and single-stepping in the signal trampoline.
342 Please note that kernel bugs are a limiting factor here. These
343 features have been shown to work on an s390 GNU/Linux system that
344 include a 2.6.8-rc1 kernel. Ref PR breakpoints/1702.
346 * Cygwin support for DWARF 2 added.
348 * New native configurations
350 GNU/Linux/hppa hppa*-*-linux*
351 OpenBSD/hppa hppa*-*-openbsd*
352 OpenBSD/m68k m68*-*-openbsd*
353 OpenBSD/m88k m88*-*-openbsd*
354 OpenBSD/powerpc powerpc-*-openbsd*
355 NetBSD/vax vax-*-netbsd*
356 OpenBSD/vax vax-*-openbsd*
358 * END-OF-LIFE frame compatibility module
360 GDB's internal frame infrastructure has been completely rewritten.
361 The new infrastructure making it possible to support key new features
362 including DWARF 2 Call Frame Information. To aid in the task of
363 migrating old configurations to this new infrastructure, a
364 compatibility module, that allowed old configurations to continue to
365 work, was also included.
367 GDB 6.2 will be the last release to include this frame compatibility
368 module. This change directly impacts the following configurations:
378 Unless there is activity to revive these configurations, they will be
379 made OBSOLETE in GDB 6.3, and REMOVED from GDB 6.4.
381 * REMOVED configurations and files
383 Sun 3, running SunOS 3 m68*-*-sunos3*
384 Sun 3, running SunOS 4 m68*-*-sunos4*
385 Sun 2, running SunOS 3 m68000-*-sunos3*
386 Sun 2, running SunOS 4 m68000-*-sunos4*
387 Motorola 680x0 running LynxOS m68*-*-lynxos*
388 AT&T 3b1/Unix pc m68*-att-*
389 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
390 decstation mips-dec-* mips-little-*
391 riscos mips-*-riscos* mips-*-sysv*
393 sysv mips*-*-sysv4* (IRIX 5/6 not included)
395 *** Changes in GDB 6.1.1:
397 * TUI (Text-mode User Interface) built-in (also included in GDB 6.1)
399 The TUI (Text-mode User Interface) is now built as part of a default
400 GDB configuration. It is enabled by either selecting the TUI with the
401 command line option "-i=tui" or by running the separate "gdbtui"
402 program. For more information on the TUI, see the manual "Debugging
405 * Pending breakpoint support (also included in GDB 6.1)
407 Support has been added to allow you to specify breakpoints in shared
408 libraries that have not yet been loaded. If a breakpoint location
409 cannot be found, and the "breakpoint pending" option is set to auto,
410 GDB queries you if you wish to make the breakpoint pending on a future
411 shared-library load. If and when GDB resolves the breakpoint symbol,
412 the pending breakpoint is removed as one or more regular breakpoints
415 Pending breakpoints are very useful for GCJ Java debugging.
417 * Fixed ISO-C build problems
419 The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained
420 non ISO-C code that stopped them being built using a more strict ISO-C
421 compiler (e.g., IBM's C compiler).
423 * Fixed build problem on IRIX 5
425 Due to header problems with <sys/proc.h>, the file gdb/proc-api.c
426 wasn't able to compile compile on an IRIX 5 system.
428 * Added execute permission to gdb/gdbserver/configure
430 The shell script gdb/testsuite/gdb.stabs/configure lacked execute
431 permission. This bug would cause configure to fail on a number of
432 systems (Solaris, IRIX). Ref: server/519.
434 * Fixed build problem on hpux2.0w-hp-hpux11.00 using the HP ANSI C compiler
436 Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c
437 has been updated to use constant array sizes.
439 * Fixed a panic in the DWARF Call Frame Info code on Solaris 2.7
441 GCC 3.3.2, on Solaris 2.7, includes the DW_EH_PE_funcrel encoding in
442 its generated DWARF Call Frame Info. This encoding was causing GDB to
443 panic, that panic has been fixed. Ref: gdb/1628.
445 * Fixed a problem when examining parameters in shared library code.
447 When examining parameters in optimized shared library code generated
448 by a mainline GCC, GDB would incorrectly report ``Variable "..." is
449 not available''. GDB now correctly displays the variable's value.
451 *** Changes in GDB 6.1:
453 * Removed --with-mmalloc
455 Support for the mmalloc memory manager has been removed, as it
456 conflicted with the internal gdb byte cache.
458 * Changes in AMD64 configurations
460 The AMD64 target now includes the %cs and %ss registers. As a result
461 the AMD64 remote protocol has changed; this affects the floating-point
462 and SSE registers. If you rely on those registers for your debugging,
463 you should upgrade gdbserver on the remote side.
465 * Revised SPARC target
467 The SPARC target has been completely revised, incorporating the
468 FreeBSD/sparc64 support that was added for GDB 6.0. As a result
469 support for LynxOS and SunOS 4 has been dropped. Calling functions
470 from within GDB on operating systems with a non-executable stack
471 (Solaris, OpenBSD) now works.
475 GDB has a new C++ demangler which does a better job on the mangled
476 names generated by current versions of g++. It also runs faster, so
477 with this and other changes gdb should now start faster on large C++
480 * DWARF 2 Location Expressions
482 GDB support for location expressions has been extended to support function
483 arguments and frame bases. Older versions of GDB could crash when they
486 * C++ nested types and namespaces
488 GDB's support for nested types and namespaces in C++ has been
489 improved, especially if you use the DWARF 2 debugging format. (This
490 is the default for recent versions of GCC on most platforms.)
491 Specifically, if you have a class "Inner" defined within a class or
492 namespace "Outer", then GDB realizes that the class's name is
493 "Outer::Inner", not simply "Inner". This should greatly reduce the
494 frequency of complaints about not finding RTTI symbols. In addition,
495 if you are stopped at inside of a function defined within a namespace,
496 GDB modifies its name lookup accordingly.
498 * New native configurations
500 NetBSD/amd64 x86_64-*-netbsd*
501 OpenBSD/amd64 x86_64-*-openbsd*
502 OpenBSD/alpha alpha*-*-openbsd*
503 OpenBSD/sparc sparc-*-openbsd*
504 OpenBSD/sparc64 sparc64-*-openbsd*
506 * New debugging protocols
508 M32R with SDI protocol m32r-*-elf*
510 * "set prompt-escape-char" command deleted.
512 The command "set prompt-escape-char" has been deleted. This command,
513 and its very obscure effet on GDB's prompt, was never documented,
514 tested, nor mentioned in the NEWS file.
516 * OBSOLETE configurations and files
518 Configurations that have been declared obsolete in this release have
519 been commented out. Unless there is activity to revive these
520 configurations, the next release of GDB will have their sources
523 Sun 3, running SunOS 3 m68*-*-sunos3*
524 Sun 3, running SunOS 4 m68*-*-sunos4*
525 Sun 2, running SunOS 3 m68000-*-sunos3*
526 Sun 2, running SunOS 4 m68000-*-sunos4*
527 Motorola 680x0 running LynxOS m68*-*-lynxos*
528 AT&T 3b1/Unix pc m68*-att-*
529 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
530 decstation mips-dec-* mips-little-*
531 riscos mips-*-riscos* mips-*-sysv*
533 sysv mips*-*-sysv4* (IRIX 5/6 not included)
535 * REMOVED configurations and files
537 SGI Irix-4.x mips-sgi-irix4 or iris4
538 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
539 Z8000 simulator z8k-zilog-none or z8ksim
540 Matsushita MN10200 w/simulator mn10200-*-*
541 H8/500 simulator h8500-hitachi-hms or h8500hms
542 HP/PA running BSD hppa*-*-bsd*
543 HP/PA running OSF/1 hppa*-*-osf*
544 HP/PA Pro target hppa*-*-pro*
545 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
546 386BSD i[3456]86-*-bsd*
547 Sequent family i[3456]86-sequent-sysv4*
548 i[3456]86-sequent-sysv*
549 i[3456]86-sequent-bsd*
550 SPARC running LynxOS sparc-*-lynxos*
551 SPARC running SunOS 4 sparc-*-sunos4*
552 Tsqware Sparclet sparclet-*-*
553 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
555 *** Changes in GDB 6.0:
559 Support for debugging the Objective-C programming language has been
562 * New backtrace mechanism (includes DWARF 2 Call Frame Information).
564 DWARF 2's Call Frame Information makes available compiler generated
565 information that more exactly describes the program's run-time stack.
566 By using this information, GDB is able to provide more robust stack
569 The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets
570 have been updated to use a new backtrace mechanism which includes
575 GDB's remote protocol has been extended to include support for hosted
576 file I/O (where the remote target uses GDB's file system). See GDB's
577 remote protocol documentation for details.
579 * All targets using the new architecture framework.
581 All of GDB's targets have been updated to use the new internal
582 architecture framework. The way is now open for future GDB releases
583 to include cross-architecture native debugging support (i386 on amd64,
586 * GNU/Linux's Thread Local Storage (TLS)
588 GDB now includes support for for the GNU/Linux implementation of
589 per-thread variables.
591 * GNU/Linux's Native POSIX Thread Library (NPTL)
593 GDB's thread code has been updated to work with either the new
594 GNU/Linux NPTL thread library or the older "LinuxThreads" library.
596 * Separate debug info.
598 GDB, in conjunction with BINUTILS, now supports a mechanism for
599 automatically loading debug information from a separate file. Instead
600 of shipping full debug and non-debug versions of system libraries,
601 system integrators can now instead ship just the stripped libraries
602 and optional debug files.
604 * DWARF 2 Location Expressions
606 DWARF 2 Location Expressions allow the compiler to more completely
607 describe the location of variables (even in optimized code) to the
610 GDB now includes preliminary support for location expressions (support
611 for DW_OP_piece is still missing).
615 A number of long standing bugs that caused GDB to die while starting a
616 Java application have been fixed. GDB's Java support is now
617 considered "useable".
619 * GNU/Linux support for fork, vfork, and exec.
621 The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode"
622 commands are now implemented for GNU/Linux. They require a 2.5.x or later
625 * GDB supports logging output to a file
627 There are two new commands, "set logging" and "show logging", which can be
628 used to capture GDB's output to a file.
630 * The meaning of "detach" has changed for gdbserver
632 The "detach" command will now resume the application, as documented. To
633 disconnect from gdbserver and leave it stopped, use the new "disconnect"
636 * d10v, m68hc11 `regs' command deprecated
638 The `info registers' command has been updated so that it displays the
639 registers using a format identical to the old `regs' command.
643 A new command, "maint set profile on/off", has been added. This command can
644 be used to enable or disable profiling while running GDB, to profile a
645 session or a set of commands. In addition there is a new configure switch,
646 "--enable-profiling", which will cause GDB to be compiled with profiling
647 data, for more informative profiling results.
649 * Default MI syntax changed to "mi2".
651 The default MI (machine interface) syntax, enabled by the command line
652 option "-i=mi", has been changed to "mi2". The previous MI syntax,
653 "mi1", can be enabled by specifying the option "-i=mi1".
655 Support for the original "mi0" syntax (included in GDB 5.0) has been
658 Fix for gdb/192: removed extraneous space when displaying frame level.
659 Fix for gdb/672: update changelist is now output in mi list format.
660 Fix for gdb/702: a -var-assign that updates the value now shows up
661 in a subsequent -var-update.
663 * New native configurations.
665 FreeBSD/amd64 x86_64-*-freebsd*
667 * Multi-arched targets.
669 HP/PA HPUX11 hppa*-*-hpux*
670 Renesas M32R/D w/simulator m32r-*-elf*
672 * OBSOLETE configurations and files
674 Configurations that have been declared obsolete in this release have
675 been commented out. Unless there is activity to revive these
676 configurations, the next release of GDB will have their sources
679 Z8000 simulator z8k-zilog-none or z8ksim
680 Matsushita MN10200 w/simulator mn10200-*-*
681 H8/500 simulator h8500-hitachi-hms or h8500hms
682 HP/PA running BSD hppa*-*-bsd*
683 HP/PA running OSF/1 hppa*-*-osf*
684 HP/PA Pro target hppa*-*-pro*
685 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
686 Sequent family i[3456]86-sequent-sysv4*
687 i[3456]86-sequent-sysv*
688 i[3456]86-sequent-bsd*
689 Tsqware Sparclet sparclet-*-*
690 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
692 * REMOVED configurations and files
695 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
696 IBM AIX PS/2 i[3456]86-*-aix
697 i386 running Mach 3.0 i[3456]86-*-mach3*
698 i386 running Mach i[3456]86-*-mach*
699 i386 running OSF/1 i[3456]86-*osf1mk*
700 HP/Apollo 68k Family m68*-apollo*-sysv*,
702 m68*-hp-bsd*, m68*-hp-hpux*
703 Argonaut Risc Chip (ARC) arc-*-*
704 Mitsubishi D30V d30v-*-*
705 Fujitsu FR30 fr30-*-elf*
706 OS/9000 i[34]86-*-os9k
707 I960 with MON960 i960-*-coff
709 * MIPS $fp behavior changed
711 The convenience variable $fp, for the MIPS, now consistently returns
712 the address of the current frame's base. Previously, depending on the
713 context, $fp could refer to either $sp or the current frame's base
714 address. See ``8.10 Registers'' in the manual ``Debugging with GDB:
715 The GNU Source-Level Debugger''.
717 *** Changes in GDB 5.3:
719 * GNU/Linux shared library multi-threaded performance improved.
721 When debugging a multi-threaded application on GNU/Linux, GDB now uses
722 `/proc', in preference to `ptrace' for memory reads. This may result
723 in an improvement in the start-up time of multi-threaded, shared
724 library applications when run under GDB. One GDB user writes: ``loads
725 shared libs like mad''.
727 * ``gdbserver'' now supports multi-threaded applications on some targets
729 Support for debugging multi-threaded applications which use
730 the GNU/Linux LinuxThreads package has been added for
731 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
732 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
734 * GDB now supports C/C++ preprocessor macros.
736 GDB now expands preprocessor macro invocations in C/C++ expressions,
737 and provides various commands for showing macro definitions and how
740 The new command `macro expand EXPRESSION' expands any macro
741 invocations in expression, and shows the result.
743 The new command `show macro MACRO-NAME' shows the definition of the
744 macro named MACRO-NAME, and where it was defined.
746 Most compilers don't include information about macros in the debugging
747 information by default. In GCC 3.1, for example, you need to compile
748 your program with the options `-gdwarf-2 -g3'. If the macro
749 information is present in the executable, GDB will read it.
751 * Multi-arched targets.
753 DEC Alpha (partial) alpha*-*-*
754 DEC VAX (partial) vax-*-*
756 National Semiconductor NS32000 (partial) ns32k-*-*
757 Motorola 68000 (partial) m68k-*-*
758 Motorola MCORE mcore-*-*
762 Fujitsu FRV architecture added by Red Hat frv*-*-*
765 * New native configurations
767 Alpha NetBSD alpha*-*-netbsd*
768 SH NetBSD sh*-*-netbsdelf*
769 MIPS NetBSD mips*-*-netbsd*
770 UltraSPARC NetBSD sparc64-*-netbsd*
772 * OBSOLETE configurations and files
774 Configurations that have been declared obsolete in this release have
775 been commented out. Unless there is activity to revive these
776 configurations, the next release of GDB will have their sources
779 Mitsubishi D30V d30v-*-*
780 OS/9000 i[34]86-*-os9k
781 IBM AIX PS/2 i[3456]86-*-aix
782 Fujitsu FR30 fr30-*-elf*
783 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
784 Argonaut Risc Chip (ARC) arc-*-*
785 i386 running Mach 3.0 i[3456]86-*-mach3*
786 i386 running Mach i[3456]86-*-mach*
787 i386 running OSF/1 i[3456]86-*osf1mk*
788 HP/Apollo 68k Family m68*-apollo*-sysv*,
790 m68*-hp-bsd*, m68*-hp-hpux*
791 I960 with MON960 i960-*-coff
795 CHILL, a Pascal like language used by telecommunications companies.
797 * REMOVED configurations and files
799 AMD 29k family via UDI a29k-amd-udi, udi29k
800 A29K VxWorks a29k-*-vxworks
801 AMD 29000 embedded, using EBMON a29k-none-none
802 AMD 29000 embedded with COFF a29k-none-coff
803 AMD 29000 embedded with a.out a29k-none-aout
805 testsuite/gdb.hp/gdb.threads-hp/ directory
807 * New command "set max-user-call-depth <nnn>"
809 This command allows the user to limit the call depth of user-defined
810 commands. The default is 1024.
812 * Changes in FreeBSD/i386 native debugging.
814 Support for the "generate-core-file" has been added.
816 * New commands "dump", "append", and "restore".
818 These commands allow data to be copied from target memory
819 to a bfd-format or binary file (dump and append), and back
820 from a file into memory (restore).
822 * Improved "next/step" support on multi-processor Alpha Tru64.
824 The previous single-step mechanism could cause unpredictable problems,
825 including the random appearance of SIGSEGV or SIGTRAP signals. The use
826 of a software single-step mechanism prevents this.
828 *** Changes in GDB 5.2.1:
836 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
837 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
838 Fix, by Joel Brobecker imported from mainline.
840 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
841 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
842 Fix, by Fred Fish, imported from mainline.
844 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
845 Surprisingly enough, it works now.
846 By Michal Ludvig, imported from mainline.
848 i386 hardware watchpoint support:
849 avoid misses on second run for some targets.
850 By Pierre Muller, imported from mainline.
852 *** Changes in GDB 5.2:
854 * New command "set trust-readonly-sections on[off]".
856 This command is a hint that tells gdb that read-only sections
857 really are read-only (ie. that their contents will not change).
858 In this mode, gdb will go to the object file rather than the
859 target to read memory from read-only sections (such as ".text").
860 This can be a significant performance improvement on some
861 (notably embedded) targets.
863 * New command "generate-core-file" (or "gcore").
865 This new gdb command allows the user to drop a core file of the child
866 process state at any time. So far it's been implemented only for
867 GNU/Linux and Solaris, but should be relatively easily ported to other
868 hosts. Argument is core file name (defaults to core.<pid>).
870 * New command line option
872 GDB now accepts --pid or -p followed by a process id.
874 * Change in command line behavior -- corefiles vs. process ids.
876 There is a subtle behavior in the way in which GDB handles
877 command line arguments. The first non-flag argument is always
878 a program to debug, but the second non-flag argument may either
879 be a corefile or a process id. Previously, GDB would attempt to
880 open the second argument as a corefile, and if that failed, would
881 issue a superfluous error message and then attempt to attach it as
882 a process. Now, if the second argument begins with a non-digit,
883 it will be treated as a corefile. If it begins with a digit,
884 GDB will attempt to attach it as a process, and if no such process
885 is found, will then attempt to open it as a corefile.
887 * Changes in ARM configurations.
889 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
890 configuration is fully multi-arch.
892 * New native configurations
894 ARM NetBSD arm*-*-netbsd*
895 x86 OpenBSD i[3456]86-*-openbsd*
896 AMD x86-64 running GNU/Linux x86_64-*-linux-*
897 Sparc64 running FreeBSD sparc64-*-freebsd*
901 Sanyo XStormy16 xstormy16-elf
903 * OBSOLETE configurations and files
905 Configurations that have been declared obsolete in this release have
906 been commented out. Unless there is activity to revive these
907 configurations, the next release of GDB will have their sources
910 AMD 29k family via UDI a29k-amd-udi, udi29k
911 A29K VxWorks a29k-*-vxworks
912 AMD 29000 embedded, using EBMON a29k-none-none
913 AMD 29000 embedded with COFF a29k-none-coff
914 AMD 29000 embedded with a.out a29k-none-aout
916 testsuite/gdb.hp/gdb.threads-hp/ directory
918 * REMOVED configurations and files
920 TI TMS320C80 tic80-*-*
922 PowerPC Solaris powerpcle-*-solaris*
923 PowerPC Windows NT powerpcle-*-cygwin32
924 PowerPC Netware powerpc-*-netware*
925 Harris/CXUX m88k m88*-harris-cxux*
926 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
927 ns32k-utek-sysv* ns32k-utek-*
928 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
929 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
930 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
931 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
932 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
934 * Changes to command line processing
936 The new `--args' feature can be used to specify command-line arguments
937 for the inferior from gdb's command line.
939 * Changes to key bindings
941 There is a new `operate-and-get-next' function bound to `C-o'.
943 *** Changes in GDB 5.1.1
945 Fix compile problem on DJGPP.
947 Fix a problem with floating-point registers on the i386 being
950 Fix to stop GDB crashing on .debug_str debug info.
952 Numerous documentation fixes.
954 Numerous testsuite fixes.
956 *** Changes in GDB 5.1:
958 * New native configurations
960 Alpha FreeBSD alpha*-*-freebsd*
961 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
962 MIPS GNU/Linux mips*-*-linux*
963 MIPS SGI Irix 6.x mips*-sgi-irix6*
965 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
969 Motorola 68HC11 and 68HC12 m68hc11-elf
971 UltraSparc running GNU/Linux sparc64-*-linux*
973 * OBSOLETE configurations and files
975 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
976 Harris/CXUX m88k m88*-harris-cxux*
977 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
978 ns32k-utek-sysv* ns32k-utek-*
979 TI TMS320C80 tic80-*-*
981 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
982 PowerPC Solaris powerpcle-*-solaris*
983 PowerPC Windows NT powerpcle-*-cygwin32
984 PowerPC Netware powerpc-*-netware*
985 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
986 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
987 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
988 Apple Macintosh (MPW) host N/A
990 stuff.c (Program to stuff files into a specially prepared space in kdb)
991 kdb-start.c (Main loop for the standalone kernel debugger)
993 Configurations that have been declared obsolete in this release have
994 been commented out. Unless there is activity to revive these
995 configurations, the next release of GDB will have their sources
998 * REMOVED configurations and files
1000 Altos 3068 m68*-altos-*
1001 Convex c1-*-*, c2-*-*
1003 ARM RISCix arm-*-* (as host)
1007 * GDB has been converted to ISO C.
1009 GDB's source code has been converted to ISO C. In particular, the
1010 sources are fully protoized, and rely on standard headers being
1015 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
1017 * The MI enabled by default.
1019 The new machine oriented interface (MI) introduced in GDB 5.0 has been
1020 revised and enabled by default. Packages which use GDB as a debugging
1021 engine behind a UI or another front end are encouraged to switch to
1022 using the GDB/MI interface, instead of the old annotations interface
1023 which is now deprecated.
1025 * Support for debugging Pascal programs.
1027 GDB now includes support for debugging Pascal programs. The following
1028 main features are supported:
1030 - Pascal-specific data types such as sets;
1032 - automatic recognition of Pascal sources based on file-name
1035 - Pascal-style display of data types, variables, and functions;
1037 - a Pascal expression parser.
1039 However, some important features are not yet supported.
1041 - Pascal string operations are not supported at all;
1043 - there are some problems with boolean types;
1045 - Pascal type hexadecimal constants are not supported
1046 because they conflict with the internal variables format;
1048 - support for Pascal objects and classes is not full yet;
1050 - unlike Pascal, GDB is case-sensitive for symbol names.
1052 * Changes in completion.
1054 Commands such as `shell', `run' and `set args', which pass arguments
1055 to inferior programs, now complete on file names, similar to what
1056 users expect at the shell prompt.
1058 Commands which accept locations, such as `disassemble', `print',
1059 `breakpoint', `until', etc. now complete on filenames as well as
1060 program symbols. Thus, if you type "break foob TAB", and the source
1061 files linked into the programs include `foobar.c', that file name will
1062 be one of the candidates for completion. However, file names are not
1063 considered for completion after you typed a colon that delimits a file
1064 name from a name of a function in that file, as in "break foo.c:bar".
1066 `set demangle-style' completes on available demangling styles.
1068 * New platform-independent commands:
1070 It is now possible to define a post-hook for a command as well as a
1071 hook that runs before the command. For more details, see the
1072 documentation of `hookpost' in the GDB manual.
1074 * Changes in GNU/Linux native debugging.
1076 Support for debugging multi-threaded programs has been completely
1077 revised for all platforms except m68k and sparc. You can now debug as
1078 many threads as your system allows you to have.
1080 Attach/detach is supported for multi-threaded programs.
1082 Support for SSE registers was added for x86. This doesn't work for
1083 multi-threaded programs though.
1085 * Changes in MIPS configurations.
1087 Multi-arch support is enabled for all MIPS configurations.
1089 GDB can now be built as native debugger on SGI Irix 6.x systems for
1090 debugging n32 executables. (Debugging 64-bit executables is not yet
1093 * Unified support for hardware watchpoints in all x86 configurations.
1095 Most (if not all) native x86 configurations support hardware-assisted
1096 breakpoints and watchpoints in a unified manner. This support
1097 implements debug register sharing between watchpoints, which allows to
1098 put a virtually infinite number of watchpoints on the same address,
1099 and also supports watching regions up to 16 bytes with several debug
1102 The new maintenance command `maintenance show-debug-regs' toggles
1103 debugging print-outs in functions that insert, remove, and test
1104 watchpoints and hardware breakpoints.
1106 * Changes in the DJGPP native configuration.
1108 New command ``info dos sysinfo'' displays assorted information about
1109 the CPU, OS, memory, and DPMI server.
1111 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
1112 display information about segment descriptors stored in GDT, LDT, and
1115 New commands ``info dos pde'' and ``info dos pte'' display entries
1116 from Page Directory and Page Tables (for now works with CWSDPMI only).
1117 New command ``info dos address-pte'' displays the Page Table entry for
1118 a given linear address.
1120 GDB can now pass command lines longer than 126 characters to the
1121 program being debugged (requires an update to the libdbg.a library
1122 which is part of the DJGPP development kit).
1124 DWARF2 debug info is now supported.
1126 It is now possible to `step' and `next' through calls to `longjmp'.
1128 * Changes in documentation.
1130 All GDB documentation was converted to GFDL, the GNU Free
1131 Documentation License.
1133 Tracepoints-related commands are now fully documented in the GDB
1136 TUI, the Text-mode User Interface, is now documented in the manual.
1138 Tracepoints-related commands are now fully documented in the GDB
1141 The "GDB Internals" manual now has an index. It also includes
1142 documentation of `ui_out' functions, GDB coding standards, x86
1143 hardware watchpoints, and memory region attributes.
1145 * GDB's version number moved to ``version.in''
1147 The Makefile variable VERSION has been replaced by the file
1148 ``version.in''. People creating GDB distributions should update the
1149 contents of this file.
1153 GUD support is now a standard part of the EMACS distribution.
1155 *** Changes in GDB 5.0:
1157 * Improved support for debugging FP programs on x86 targets
1159 Unified and much-improved support for debugging floating-point
1160 programs on all x86 targets. In particular, ``info float'' now
1161 displays the FP registers in the same format on all x86 targets, with
1162 greater level of detail.
1164 * Improvements and bugfixes in hardware-assisted watchpoints
1166 It is now possible to watch array elements, struct members, and
1167 bitfields with hardware-assisted watchpoints. Data-read watchpoints
1168 on x86 targets no longer erroneously trigger when the address is
1171 * Improvements in the native DJGPP version of GDB
1173 The distribution now includes all the scripts and auxiliary files
1174 necessary to build the native DJGPP version on MS-DOS/MS-Windows
1175 machines ``out of the box''.
1177 The DJGPP version can now debug programs that use signals. It is
1178 possible to catch signals that happened in the debuggee, deliver
1179 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
1180 would kill the program being debugged.) Programs that hook hardware
1181 interrupts (keyboard, timer, etc.) can also be debugged.
1183 It is now possible to debug DJGPP programs that redirect their
1184 standard handles or switch them to raw (as opposed to cooked) mode, or
1185 even close them. The command ``run < foo > bar'' works as expected,
1186 and ``info terminal'' reports useful information about the debuggee's
1187 terminal, including raw/cooked mode, redirection, etc.
1189 The DJGPP version now uses termios functions for console I/O, which
1190 enables debugging graphics programs. Interrupting GDB with Ctrl-C
1193 DOS-style file names with drive letters are now fully supported by
1196 It is now possible to debug DJGPP programs that switch their working
1197 directory. It is also possible to rerun the debuggee any number of
1198 times without restarting GDB; thus, you can use the same setup,
1199 breakpoints, etc. for many debugging sessions.
1201 * New native configurations
1203 ARM GNU/Linux arm*-*-linux*
1204 PowerPC GNU/Linux powerpc-*-linux*
1208 Motorola MCore mcore-*-*
1209 x86 VxWorks i[3456]86-*-vxworks*
1210 PowerPC VxWorks powerpc-*-vxworks*
1211 TI TMS320C80 tic80-*-*
1213 * OBSOLETE configurations
1215 Altos 3068 m68*-altos-*
1216 Convex c1-*-*, c2-*-*
1218 ARM RISCix arm-*-* (as host)
1221 Configurations that have been declared obsolete will be commented out,
1222 but the code will be left in place. If there is no activity to revive
1223 these configurations before the next release of GDB, the sources will
1224 be permanently REMOVED.
1226 * Gould support removed
1228 Support for the Gould PowerNode and NP1 has been removed.
1230 * New features for SVR4
1232 On SVR4 native platforms (such as Solaris), if you attach to a process
1233 without first loading a symbol file, GDB will now attempt to locate and
1234 load symbols from the running process's executable file.
1236 * Many C++ enhancements
1238 C++ support has been greatly improved. Overload resolution now works properly
1239 in almost all cases. RTTI support is on the way.
1241 * Remote targets can connect to a sub-program
1243 A popen(3) style serial-device has been added. This device starts a
1244 sub-process (such as a stand-alone simulator) and then communicates
1245 with that. The sub-program to run is specified using the syntax
1246 ``|<program> <args>'' vis:
1248 (gdb) set remotedebug 1
1249 (gdb) target extended-remote |mn10300-elf-sim program-args
1251 * MIPS 64 remote protocol
1253 A long standing bug in the mips64 remote protocol where by GDB
1254 expected certain 32 bit registers (ex SR) to be transfered as 32
1255 instead of 64 bits has been fixed.
1257 The command ``set remote-mips64-transfers-32bit-regs on'' has been
1258 added to provide backward compatibility with older versions of GDB.
1260 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
1262 The command ``set remotebinarydownload'' command has been replaced by
1263 ``set remote X-packet''. Other commands in ``set remote'' family
1264 include ``set remote P-packet''.
1266 * Breakpoint commands accept ranges.
1268 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
1269 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
1270 ``tracepoint passcount'' also accepts a range of tracepoints.
1272 * ``apropos'' command added.
1274 The ``apropos'' command searches through command names and
1275 documentation strings, printing out matches, making it much easier to
1276 try to find a command that does what you are looking for.
1280 A new machine oriented interface (MI) has been added to GDB. This
1281 interface is designed for debug environments running GDB as a separate
1282 process. This is part of the long term libGDB project. See the
1283 "GDB/MI" chapter of the GDB manual for further information. It can be
1284 enabled by configuring with:
1286 .../configure --enable-gdbmi
1288 *** Changes in GDB-4.18:
1290 * New native configurations
1292 HP-UX 10.20 hppa*-*-hpux10.20
1293 HP-UX 11.x hppa*-*-hpux11.0*
1294 M68K GNU/Linux m68*-*-linux*
1298 Fujitsu FR30 fr30-*-elf*
1299 Intel StrongARM strongarm-*-*
1300 Mitsubishi D30V d30v-*-*
1302 * OBSOLETE configurations
1304 Gould PowerNode, NP1 np1-*-*, pn-*-*
1306 Configurations that have been declared obsolete will be commented out,
1307 but the code will be left in place. If there is no activity to revive
1308 these configurations before the next release of GDB, the sources will
1309 be permanently REMOVED.
1313 As a compatibility experiment, GDB's source files buildsym.h and
1314 buildsym.c have been converted to pure standard C, no longer
1315 containing any K&R compatibility code. We believe that all systems in
1316 use today either come with a standard C compiler, or have a GCC port
1317 available. If this is not true, please report the affected
1318 configuration to bug-gdb@gnu.org immediately. See the README file for
1319 information about getting a standard C compiler if you don't have one
1324 GDB now uses readline 2.2.
1326 * set extension-language
1328 You can now control the mapping between filename extensions and source
1329 languages by using the `set extension-language' command. For instance,
1330 you can ask GDB to treat .c files as C++ by saying
1331 set extension-language .c c++
1332 The command `info extensions' lists all of the recognized extensions
1333 and their associated languages.
1335 * Setting processor type for PowerPC and RS/6000
1337 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
1338 you can use the `set processor' command to specify what variant of the
1339 PowerPC family you are debugging. The command
1343 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
1344 following PowerPC and RS6000 variants:
1346 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
1347 rs6000 IBM RS6000 ("POWER") architecture, user-level view
1349 403GC IBM PowerPC 403GC
1350 505 Motorola PowerPC 505
1351 860 Motorola PowerPC 860 or 850
1352 601 Motorola PowerPC 601
1353 602 Motorola PowerPC 602
1354 603 Motorola/IBM PowerPC 603 or 603e
1355 604 Motorola PowerPC 604 or 604e
1356 750 Motorola/IBM PowerPC 750 or 750
1358 At the moment, this command just tells GDB what to name the
1359 special-purpose processor registers. Since almost all the affected
1360 registers are inaccessible to user-level programs, this command is
1361 only useful for remote debugging in its present form.
1365 Thanks to a major code donation from Hewlett-Packard, GDB now has much
1366 more extensive support for HP-UX. Added features include shared
1367 library support, kernel threads and hardware watchpoints for 11.00,
1368 support for HP's ANSI C and C++ compilers, and a compatibility mode
1369 for xdb and dbx commands.
1373 HP's donation includes the new concept of catchpoints, which is a
1374 generalization of the old catch command. On HP-UX, it is now possible
1375 to catch exec, fork, and vfork, as well as library loading.
1377 This means that the existing catch command has changed; its first
1378 argument now specifies the type of catch to be set up. See the
1379 output of "help catch" for a list of catchpoint types.
1381 * Debugging across forks
1383 On HP-UX, you can choose which process to debug when a fork() happens
1388 HP has donated a curses-based terminal user interface (TUI). To get
1389 it, build with --enable-tui. Although this can be enabled for any
1390 configuration, at present it only works for native HP debugging.
1392 * GDB remote protocol additions
1394 A new protocol packet 'X' that writes binary data is now available.
1395 Default behavior is to try 'X', then drop back to 'M' if the stub
1396 fails to respond. The settable variable `remotebinarydownload'
1397 allows explicit control over the use of 'X'.
1399 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
1400 full 64-bit address. The command
1402 set remoteaddresssize 32
1404 can be used to revert to the old behaviour. For existing remote stubs
1405 the change should not be noticed, as the additional address information
1408 In order to assist in debugging stubs, you may use the maintenance
1409 command `packet' to send any text string to the stub. For instance,
1411 maint packet heythere
1413 sends the packet "$heythere#<checksum>". Note that it is very easy to
1414 disrupt a debugging session by sending the wrong packet at the wrong
1417 The compare-sections command allows you to compare section data on the
1418 target to what is in the executable file without uploading or
1419 downloading, by comparing CRC checksums.
1421 * Tracing can collect general expressions
1423 You may now collect general expressions at tracepoints. This requires
1424 further additions to the target-side stub; see tracepoint.c and
1425 doc/agentexpr.texi for further details.
1427 * mask-address variable for Mips
1429 For Mips targets, you may control the zeroing of the upper 32 bits of
1430 a 64-bit address by entering `set mask-address on'. This is mainly
1431 of interest to users of embedded R4xxx and R5xxx processors.
1433 * Higher serial baud rates
1435 GDB's serial code now allows you to specify baud rates 57600, 115200,
1436 230400, and 460800 baud. (Note that your host system may not be able
1437 to achieve all of these rates.)
1441 The i960 configuration now includes an initial implementation of a
1442 builtin simulator, contributed by Jim Wilson.
1445 *** Changes in GDB-4.17:
1447 * New native configurations
1449 Alpha GNU/Linux alpha*-*-linux*
1450 Unixware 2.x i[3456]86-unixware2*
1451 Irix 6.x mips*-sgi-irix6*
1452 PowerPC GNU/Linux powerpc-*-linux*
1453 PowerPC Solaris powerpcle-*-solaris*
1454 Sparc GNU/Linux sparc-*-linux*
1455 Motorola sysV68 R3V7.1 m68k-motorola-sysv
1459 Argonaut Risc Chip (ARC) arc-*-*
1460 Hitachi H8/300S h8300*-*-*
1461 Matsushita MN10200 w/simulator mn10200-*-*
1462 Matsushita MN10300 w/simulator mn10300-*-*
1463 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
1464 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
1465 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
1466 Mitsubishi D10V w/simulator d10v-*-*
1467 Mitsubishi M32R/D w/simulator m32r-*-elf*
1468 Tsqware Sparclet sparclet-*-*
1469 NEC V850 w/simulator v850-*-*
1471 * New debugging protocols
1473 ARM with RDI protocol arm*-*-*
1474 M68K with dBUG monitor m68*-*-{aout,coff,elf}
1475 DDB and LSI variants of PMON protocol mips*-*-*
1476 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
1477 PowerPC with SDS protocol powerpc{,le}-*-eabi
1478 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
1482 All configurations can now understand and use the DWARF 2 debugging
1483 format. The choice is automatic, if the symbol file contains DWARF 2
1488 GDB now includes basic Java language support. This support is
1489 only useful with Java compilers that produce native machine code.
1491 * solib-absolute-prefix and solib-search-path
1493 For SunOS and SVR4 shared libraries, you may now set the prefix for
1494 loading absolute shared library symbol files, and the search path for
1495 locating non-absolute shared library symbol files.
1497 * Live range splitting
1499 GDB can now effectively debug code for which GCC has performed live
1500 range splitting as part of its optimization. See gdb/doc/LRS for
1501 more details on the expected format of the stabs information.
1505 GDB's support for the GNU Hurd, including thread debugging, has been
1506 updated to work with current versions of the Hurd.
1510 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
1511 instruction set. ARM GDB automatically detects when Thumb
1512 instructions are in use, and adjusts disassembly and backtracing
1517 GDB's MIPS target configurations now handle the MIP16 16-bit
1522 GDB now includes support for overlays; if an executable has been
1523 linked such that multiple sections are based at the same address, GDB
1524 will decide which section to use for symbolic info. You can choose to
1525 control the decision manually, using overlay commands, or implement
1526 additional target-side support and use "overlay load-target" to bring
1527 in the overlay mapping. Do "help overlay" for more detail.
1531 The command "info symbol <address>" displays information about
1532 the symbol at the specified address.
1536 The standard remote protocol now includes an extension that allows
1537 asynchronous collection and display of trace data. This requires
1538 extensive support in the target-side debugging stub. Tracing mode
1539 includes a new interaction mode in GDB and new commands: see the
1540 file tracepoint.c for more details.
1544 Configurations for embedded MIPS now include a simulator contributed
1545 by Cygnus Solutions. The simulator supports the instruction sets
1546 of most MIPS variants.
1550 Sparc configurations may now include the ERC32 simulator contributed
1551 by the European Space Agency. The simulator is not built into
1552 Sparc targets by default; configure with --enable-sim to include it.
1556 For target configurations that may include multiple variants of a
1557 basic architecture (such as MIPS and SH), you may now set the
1558 architecture explicitly. "set arch" sets, "info arch" lists
1559 the possible architectures.
1561 *** Changes in GDB-4.16:
1563 * New native configurations
1565 Windows 95, x86 Windows NT i[345]86-*-cygwin32
1566 M68K NetBSD m68k-*-netbsd*
1567 PowerPC AIX 4.x powerpc-*-aix*
1568 PowerPC MacOS powerpc-*-macos*
1569 PowerPC Windows NT powerpcle-*-cygwin32
1570 RS/6000 AIX 4.x rs6000-*-aix4*
1574 ARM with RDP protocol arm-*-*
1575 I960 with MON960 i960-*-coff
1576 MIPS VxWorks mips*-*-vxworks*
1577 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
1578 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
1580 Matra Sparclet sparclet-*-*
1584 The powerpc-eabi configuration now includes the PSIM simulator,
1585 contributed by Andrew Cagney, with assistance from Mike Meissner.
1586 PSIM is a very elaborate model of the PowerPC, including not only
1587 basic instruction set execution, but also details of execution unit
1588 performance and I/O hardware. See sim/ppc/README for more details.
1592 GDB now works with Solaris 2.5.
1594 * Windows 95/NT native
1596 GDB will now work as a native debugger on Windows 95 and Windows NT.
1597 To build it from source, you must use the "gnu-win32" environment,
1598 which uses a DLL to emulate enough of Unix to run the GNU tools.
1599 Further information, binaries, and sources are available at
1600 ftp.cygnus.com, under pub/gnu-win32.
1602 * dont-repeat command
1604 If a user-defined command includes the command `dont-repeat', then the
1605 command will not be repeated if the user just types return. This is
1606 useful if the command is time-consuming to run, so that accidental
1607 extra keystrokes don't run the same command many times.
1609 * Send break instead of ^C
1611 The standard remote protocol now includes an option to send a break
1612 rather than a ^C to the target in order to interrupt it. By default,
1613 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
1615 * Remote protocol timeout
1617 The standard remote protocol includes a new variable `remotetimeout'
1618 that allows you to set the number of seconds before GDB gives up trying
1619 to read from the target. The default value is 2.
1621 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
1623 By default GDB will automatically keep track of objects as they are
1624 loaded and unloaded by the dynamic linker. By using the command `set
1625 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
1626 when shared library events occur, thus allowing you to set breakpoints
1627 in shared libraries which are explicitly loaded by the inferior.
1629 Note this feature does not work on hpux8. On hpux9 you must link
1630 /usr/lib/end.o into your program. This feature should work
1631 automatically on hpux10.
1633 * Irix 5.x hardware watchpoint support
1635 Irix 5 configurations now support the use of hardware watchpoints.
1637 * Mips protocol "SYN garbage limit"
1639 When debugging a Mips target using the `target mips' protocol, you
1640 may set the number of characters that GDB will ignore by setting
1641 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
1642 every character. The default value is 1050.
1644 * Recording and replaying remote debug sessions
1646 If you set `remotelogfile' to the name of a file, gdb will write to it
1647 a recording of a remote debug session. This recording may then be
1648 replayed back to gdb using "gdbreplay". See gdbserver/README for
1649 details. This is useful when you have a problem with GDB while doing
1650 remote debugging; you can make a recording of the session and send it
1651 to someone else, who can then recreate the problem.
1653 * Speedups for remote debugging
1655 GDB includes speedups for downloading and stepping MIPS systems using
1656 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
1657 and more efficient S-record downloading.
1659 * Memory use reductions and statistics collection
1661 GDB now uses less memory and reports statistics about memory usage.
1662 Try the `maint print statistics' command, for example.
1664 *** Changes in GDB-4.15:
1666 * Psymtabs for XCOFF
1668 The symbol reader for AIX GDB now uses partial symbol tables. This
1669 can greatly improve startup time, especially for large executables.
1671 * Remote targets use caching
1673 Remote targets now use a data cache to speed up communication with the
1674 remote side. The data cache could lead to incorrect results because
1675 it doesn't know about volatile variables, thus making it impossible to
1676 debug targets which use memory mapped I/O devices. `set remotecache
1677 off' turns the the data cache off.
1679 * Remote targets may have threads
1681 The standard remote protocol now includes support for multiple threads
1682 in the target system, using new protocol commands 'H' and 'T'. See
1683 gdb/remote.c for details.
1687 If GDB is configured with `--enable-netrom', then it will include
1688 support for the NetROM ROM emulator from XLNT Designs. The NetROM
1689 acts as though it is a bank of ROM on the target board, but you can
1690 write into it over the network. GDB's support consists only of
1691 support for fast loading into the emulated ROM; to debug, you must use
1692 another protocol, such as standard remote protocol. The usual
1693 sequence is something like
1695 target nrom <netrom-hostname>
1697 target remote <netrom-hostname>:1235
1701 GDB now includes support for the Apple Macintosh, as a host only. It
1702 may be run as either an MPW tool or as a standalone application, and
1703 it can debug through the serial port. All the usual GDB commands are
1704 available, but to the target command, you must supply "serial" as the
1705 device type instead of "/dev/ttyXX". See mpw-README in the main
1706 directory for more information on how to build. The MPW configuration
1707 scripts */mpw-config.in support only a few targets, and only the
1708 mips-idt-ecoff target has been tested.
1712 GDB configuration now uses autoconf. This is not user-visible,
1713 but does simplify configuration and building.
1717 GDB now supports hpux10.
1719 *** Changes in GDB-4.14:
1721 * New native configurations
1723 x86 FreeBSD i[345]86-*-freebsd
1724 x86 NetBSD i[345]86-*-netbsd
1725 NS32k NetBSD ns32k-*-netbsd
1726 Sparc NetBSD sparc-*-netbsd
1730 A29K VxWorks a29k-*-vxworks
1731 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1732 CPU32 EST-300 emulator m68*-*-est*
1733 PowerPC ELF powerpc-*-elf
1736 * Alpha OSF/1 support for procfs
1738 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1739 possible to attach to running processes. As the mounting of the /proc
1740 filesystem is optional on the Alpha, GDB automatically determines
1741 the availability of /proc during startup. This can lead to problems
1742 if /proc is unmounted after GDB has been started.
1744 * Arguments to user-defined commands
1746 User commands may accept up to 10 arguments separated by whitespace.
1747 Arguments are accessed within the user command via $arg0..$arg9. A
1750 print $arg0 + $arg1 + $arg2
1752 To execute the command use:
1755 Defines the command "adder" which prints the sum of its three arguments.
1756 Note the arguments are text substitutions, so they may reference variables,
1757 use complex expressions, or even perform inferior function calls.
1759 * New `if' and `while' commands
1761 This makes it possible to write more sophisticated user-defined
1762 commands. Both commands take a single argument, which is the
1763 expression to evaluate, and must be followed by the commands to
1764 execute, one per line, if the expression is nonzero, the list being
1765 terminated by the word `end'. The `if' command list may include an
1766 `else' word, which causes the following commands to be executed only
1767 if the expression is zero.
1769 * Fortran source language mode
1771 GDB now includes partial support for Fortran 77. It will recognize
1772 Fortran programs and can evaluate a subset of Fortran expressions, but
1773 variables and functions may not be handled correctly. GDB will work
1774 with G77, but does not yet know much about symbols emitted by other
1777 * Better HPUX support
1779 Most debugging facilities now work on dynamic executables for HPPAs
1780 running hpux9 or later. You can attach to running dynamically linked
1781 processes, but by default the dynamic libraries will be read-only, so
1782 for instance you won't be able to put breakpoints in them. To change
1783 that behavior do the following before running the program:
1789 This will cause the libraries to be mapped private and read-write.
1790 To revert to the normal behavior, do this:
1796 You cannot set breakpoints or examine data in the library until after
1797 the library is loaded if the function/data symbols do not have
1800 GDB can now also read debug symbols produced by the HP C compiler on
1801 HPPAs (sorry, no C++, Fortran or 68k support).
1803 * Target byte order now dynamically selectable
1805 You can choose which byte order to use with a target system, via the
1806 commands "set endian big" and "set endian little", and you can see the
1807 current setting by using "show endian". You can also give the command
1808 "set endian auto", in which case GDB will use the byte order
1809 associated with the executable. Currently, only embedded MIPS
1810 configurations support dynamic selection of target byte order.
1812 * New DOS host serial code
1814 This version uses DPMI interrupts to handle buffered I/O, so you
1815 no longer need to run asynctsr when debugging boards connected to
1818 *** Changes in GDB-4.13:
1820 * New "complete" command
1822 This lists all the possible completions for the rest of the line, if it
1823 were to be given as a command itself. This is intended for use by emacs.
1825 * Trailing space optional in prompt
1827 "set prompt" no longer adds a space for you after the prompt you set. This
1828 allows you to set a prompt which ends in a space or one that does not.
1830 * Breakpoint hit counts
1832 "info break" now displays a count of the number of times the breakpoint
1833 has been hit. This is especially useful in conjunction with "ignore"; you
1834 can ignore a large number of breakpoint hits, look at the breakpoint info
1835 to see how many times the breakpoint was hit, then run again, ignoring one
1836 less than that number, and this will get you quickly to the last hit of
1839 * Ability to stop printing at NULL character
1841 "set print null-stop" will cause GDB to stop printing the characters of
1842 an array when the first NULL is encountered. This is useful when large
1843 arrays actually contain only short strings.
1845 * Shared library breakpoints
1847 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1848 breakpoints in shared libraries before the executable is run.
1850 * Hardware watchpoints
1852 There is a new hardware breakpoint for the watch command for sparclite
1853 targets. See gdb/sparclite/hw_breakpoint.note.
1855 Hardware watchpoints are also now supported under GNU/Linux.
1859 Annotations have been added. These are for use with graphical interfaces,
1860 and are still experimental. Currently only gdba.el uses these.
1862 * Improved Irix 5 support
1864 GDB now works properly with Irix 5.2.
1866 * Improved HPPA support
1868 GDB now works properly with the latest GCC and GAS.
1870 * New native configurations
1872 Sequent PTX4 i[34]86-sequent-ptx4
1873 HPPA running OSF/1 hppa*-*-osf*
1874 Atari TT running SVR4 m68*-*-sysv4*
1875 RS/6000 LynxOS rs6000-*-lynxos*
1879 OS/9000 i[34]86-*-os9k
1880 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1883 * Hitachi SH7000 and E7000-PC ICE support
1885 There is now support for communicating with the Hitachi E7000-PC ICE.
1886 This is available automatically when GDB is configured for the SH.
1890 As usual, a variety of small fixes and improvements, both generic
1891 and configuration-specific. See the ChangeLog for more detail.
1893 *** Changes in GDB-4.12:
1895 * Irix 5 is now supported
1899 GDB-4.12 on the HPPA has a number of changes which make it unable
1900 to debug the output from the currently released versions of GCC and
1901 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1902 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1903 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1906 *** Changes in GDB-4.11:
1908 * User visible changes:
1912 The "set remotedebug" option is now consistent between the mips remote
1913 target, remote targets using the gdb-specific protocol, UDI (AMD's
1914 debug protocol for the 29k) and the 88k bug monitor. It is now an
1915 integer specifying a debug level (normally 0 or 1, but 2 means more
1916 debugging info for the mips target).
1918 * DEC Alpha native support
1920 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1921 debug info, but GDB works fairly well with the DEC compiler and should
1922 work with a future GCC release. See the README file for a few
1923 Alpha-specific notes.
1925 * Preliminary thread implementation
1927 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1929 * LynxOS native and target support for 386
1931 This release has been hosted on LynxOS 2.2, and also can be configured
1932 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1935 * Improvements in C++ mangling/demangling.
1937 This release has much better g++ debugging, specifically in name
1938 mangling/demangling, virtual function calls, print virtual table,
1939 call methods, ...etc.
1941 *** Changes in GDB-4.10:
1943 * User visible changes:
1945 Remote debugging using the GDB-specific (`target remote') protocol now
1946 supports the `load' command. This is only useful if you have some
1947 other way of getting the stub to the target system, and you can put it
1948 somewhere in memory where it won't get clobbered by the download.
1950 Filename completion now works.
1952 When run under emacs mode, the "info line" command now causes the
1953 arrow to point to the line specified. Also, "info line" prints
1954 addresses in symbolic form (as well as hex).
1956 All vxworks based targets now support a user settable option, called
1957 vxworks-timeout. This option represents the number of seconds gdb
1958 should wait for responses to rpc's. You might want to use this if
1959 your vxworks target is, perhaps, a slow software simulator or happens
1960 to be on the far side of a thin network line.
1964 This release contains support for using a DEC alpha as a GDB host for
1965 cross debugging. Native alpha debugging is not supported yet.
1968 *** Changes in GDB-4.9:
1972 This is the first GDB release which is accompanied by a matching testsuite.
1973 The testsuite requires installation of dejagnu, which should be available
1974 via ftp from most sites that carry GNU software.
1978 'Cfront' style demangling has had its name changed to 'ARM' style, to
1979 emphasize that it was written from the specifications in the C++ Annotated
1980 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1981 disclaimers, it still generated too much confusion with users attempting to
1982 use gdb with AT&T cfront.
1986 GDB now uses a standard remote interface to a simulator library.
1987 So far, the library contains simulators for the Zilog Z8001/2, the
1988 Hitachi H8/300, H8/500 and Super-H.
1990 * New targets supported
1992 H8/300 simulator h8300-hitachi-hms or h8300hms
1993 H8/500 simulator h8500-hitachi-hms or h8500hms
1994 SH simulator sh-hitachi-hms or sh
1995 Z8000 simulator z8k-zilog-none or z8ksim
1996 IDT MIPS board over serial line mips-idt-ecoff
1998 Cross-debugging to GO32 targets is supported. It requires a custom
1999 version of the i386-stub.c module which is integrated with the
2000 GO32 memory extender.
2002 * New remote protocols
2004 MIPS remote debugging protocol.
2006 * New source languages supported
2008 This version includes preliminary support for Chill, a Pascal like language
2009 used by telecommunications companies. Chill support is also being integrated
2010 into the GNU compiler, but we don't know when it will be publically available.
2013 *** Changes in GDB-4.8:
2015 * HP Precision Architecture supported
2017 GDB now supports HP PA-RISC machines running HPUX. A preliminary
2018 version of this support was available as a set of patches from the
2019 University of Utah. GDB does not support debugging of programs
2020 compiled with the HP compiler, because HP will not document their file
2021 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
2022 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
2024 Many problems in the preliminary version have been fixed.
2026 * Faster and better demangling
2028 We have improved template demangling and fixed numerous bugs in the GNU style
2029 demangler. It can now handle type modifiers such as `static' or `const'. Wide
2030 character types (wchar_t) are now supported. Demangling of each symbol is now
2031 only done once, and is cached when the symbol table for a file is read in.
2032 This results in a small increase in memory usage for C programs, a moderate
2033 increase in memory usage for C++ programs, and a fantastic speedup in
2036 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
2037 from the specifications in the Annotated Reference Manual, which AT&T's
2038 compiler does not actually implement.
2040 * G++ multiple inheritance compiler problem
2042 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
2043 inheritance lattices was reworked to properly discover ambiguities. We
2044 recently found an example which causes this new algorithm to fail in a
2045 very subtle way, producing bad debug information for those classes.
2046 The file 'gcc.patch' (in this directory) can be applied to gcc to
2047 circumvent the problem. A future GCC release will contain a complete
2050 The previous G++ debug info problem (mentioned below for the gdb-4.7
2051 release) is fixed in gcc version 2.3.2.
2053 * Improved configure script
2055 The `configure' script will now attempt to guess your system type if
2056 you don't supply a host system type. The old scheme of supplying a
2057 host system triplet is preferable over using this. All the magic is
2058 done in the new `config.guess' script. Examine it for details.
2060 We have also brought our configure script much more in line with the FSF's
2061 version. It now supports the --with-xxx options. In particular,
2062 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
2063 The resulting GDB will not be able to read arbitrary object file formats --
2064 only the format ``expected'' to be used on the configured target system.
2065 We hope to make this the default in a future release.
2067 * Documentation improvements
2069 There's new internal documentation on how to modify GDB, and how to
2070 produce clean changes to the code. We implore people to read it
2071 before submitting changes.
2073 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
2074 M4 macros. The new texinfo.tex is provided in this release. Pre-built
2075 `info' files are also provided. To build `info' files from scratch,
2076 you will need the latest `makeinfo' release, which will be available in
2077 a future texinfo-X.Y release.
2079 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
2080 We're not sure exactly which versions have this problem, but it has
2081 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
2082 or better. If that isn't possible, there is a patch in
2083 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
2084 around this problem.
2088 GDB now supports array constants that can be used in expressions typed in by
2089 the user. The syntax is `{element, element, ...}'. Ie: you can now type
2090 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
2093 The new directory `gdb/sparclite' contains a program that demonstrates
2094 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
2096 * New native hosts supported
2098 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
2099 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
2101 * New targets supported
2103 AMD 29k family via UDI a29k-amd-udi or udi29k
2105 * New file formats supported
2107 BFD now supports reading HP/PA-RISC executables (SOM file format?),
2108 HPUX core files, and SCO 3.2v2 core files.
2112 Attaching to processes now works again; thanks for the many bug reports.
2114 We have also stomped on a bunch of core dumps caused by
2115 printf_filtered("%s") problems.
2117 We eliminated a copyright problem on the rpc and ptrace header files
2118 for VxWorks, which was discovered at the last minute during the 4.7
2119 release. You should now be able to build a VxWorks GDB.
2121 You can now interrupt gdb while an attached process is running. This
2122 will cause the attached process to stop, and give control back to GDB.
2124 We fixed problems caused by using too many file descriptors
2125 for reading symbols from object files and libraries. This was
2126 especially a problem for programs that used many (~100) shared
2129 The `step' command now only enters a subroutine if there is line number
2130 information for the subroutine. Otherwise it acts like the `next'
2131 command. Previously, `step' would enter subroutines if there was
2132 any debugging information about the routine. This avoids problems
2133 when using `cc -g1' on MIPS machines.
2135 * Internal improvements
2137 GDB's internal interfaces have been improved to make it easier to support
2138 debugging of multiple languages in the future.
2140 GDB now uses a common structure for symbol information internally.
2141 Minimal symbols (derived from linkage symbols in object files), partial
2142 symbols (from a quick scan of debug information), and full symbols
2143 contain a common subset of information, making it easier to write
2144 shared code that handles any of them.
2146 * New command line options
2148 We now accept --silent as an alias for --quiet.
2152 The memory-mapped-malloc library is now licensed under the GNU Library
2153 General Public License.
2155 *** Changes in GDB-4.7:
2157 * Host/native/target split
2159 GDB has had some major internal surgery to untangle the support for
2160 hosts and remote targets. Now, when you configure GDB for a remote
2161 target, it will no longer load in all of the support for debugging
2162 local programs on the host. When fully completed and tested, this will
2163 ensure that arbitrary host/target combinations are possible.
2165 The primary conceptual shift is to separate the non-portable code in
2166 GDB into three categories. Host specific code is required any time GDB
2167 is compiled on that host, regardless of the target. Target specific
2168 code relates to the peculiarities of the target, but can be compiled on
2169 any host. Native specific code is everything else: it can only be
2170 built when the host and target are the same system. Child process
2171 handling and core file support are two common `native' examples.
2173 GDB's use of /proc for controlling Unix child processes is now cleaner.
2174 It has been split out into a single module under the `target_ops' vector,
2175 plus two native-dependent functions for each system that uses /proc.
2177 * New hosts supported
2179 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
2180 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2181 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
2183 * New targets supported
2185 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
2186 68030 and CPU32 m68030-*-*, m68332-*-*
2188 * New native hosts supported
2190 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2191 (386bsd is not well tested yet)
2192 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
2194 * New file formats supported
2196 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
2197 supports reading of `a.out.adobe' object files, which are an a.out
2198 format extended with minimal information about multiple sections.
2202 `show copying' is the same as the old `info copying'.
2203 `show warranty' is the same as `info warrantee'.
2204 These were renamed for consistency. The old commands continue to work.
2206 `info handle' is a new alias for `info signals'.
2208 You can now define pre-command hooks, which attach arbitrary command
2209 scripts to any command. The commands in the hook will be executed
2210 prior to the user's command. You can also create a hook which will be
2211 executed whenever the program stops. See gdb.texinfo.
2215 We now deal with Cfront style name mangling, and can even extract type
2216 info from mangled symbols. GDB can automatically figure out which
2217 symbol mangling style your C++ compiler uses.
2219 Calling of methods and virtual functions has been improved as well.
2223 The crash that occured when debugging Sun Ansi-C compiled binaries is
2224 fixed. This was due to mishandling of the extra N_SO stabs output
2227 We also finally got Ultrix 4.2 running in house, and fixed core file
2228 support, with help from a dozen people on the net.
2230 John M. Farrell discovered that the reason that single-stepping was so
2231 slow on all of the Mips based platforms (primarily SGI and DEC) was
2232 that we were trying to demangle and lookup a symbol used for internal
2233 purposes on every instruction that was being stepped through. Changing
2234 the name of that symbol so that it couldn't be mistaken for a C++
2235 mangled symbol sped things up a great deal.
2237 Rich Pixley sped up symbol lookups in general by getting much smarter
2238 about when C++ symbol mangling is necessary. This should make symbol
2239 completion (TAB on the command line) much faster. It's not as fast as
2240 we'd like, but it's significantly faster than gdb-4.6.
2244 A new user controllable variable 'call_scratch_address' can
2245 specify the location of a scratch area to be used when GDB
2246 calls a function in the target. This is necessary because the
2247 usual method of putting the scratch area on the stack does not work
2248 in systems that have separate instruction and data spaces.
2250 We integrated changes to support the 29k UDI (Universal Debugger
2251 Interface), but discovered at the last minute that we didn't have all
2252 of the appropriate copyright paperwork. We are working with AMD to
2253 resolve this, and hope to have it available soon.
2257 We have sped up the remote serial line protocol, especially for targets
2258 with lots of registers. It now supports a new `expedited status' ('T')
2259 message which can be used in place of the existing 'S' status message.
2260 This allows the remote stub to send only the registers that GDB
2261 needs to make a quick decision about single-stepping or conditional
2262 breakpoints, eliminating the need to fetch the entire register set for
2263 each instruction being stepped through.
2265 The GDB remote serial protocol now implements a write-through cache for
2266 registers, only re-reading the registers if the target has run.
2268 There is also a new remote serial stub for SPARC processors. You can
2269 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
2270 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
2271 processor with a serial port.
2275 Configure.in files have become much easier to read and modify. A new
2276 `table driven' format makes it more obvious what configurations are
2277 supported, and what files each one uses.
2281 There is a new opcodes library which will eventually contain all of the
2282 disassembly routines and opcode tables. At present, it only contains
2283 Sparc and Z8000 routines. This will allow the assembler, debugger, and
2284 disassembler (binutils/objdump) to share these routines.
2286 The libiberty library is now copylefted under the GNU Library General
2287 Public License. This allows more liberal use, and was done so libg++
2288 can use it. This makes no difference to GDB, since the Library License
2289 grants all the rights from the General Public License.
2293 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
2294 reference to the stabs symbol info used by the debugger. It is (as far
2295 as we know) the only published document on this fascinating topic. We
2296 encourage you to read it, compare it to the stabs information on your
2297 system, and send improvements on the document in general (to
2298 bug-gdb@prep.ai.mit.edu).
2300 And, of course, many bugs have been fixed.
2303 *** Changes in GDB-4.6:
2305 * Better support for C++ function names
2307 GDB now accepts as input the "demangled form" of C++ overloaded function
2308 names and member function names, and can do command completion on such names
2309 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
2310 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
2311 Make use of command completion, it is your friend.
2313 GDB also now accepts a variety of C++ mangled symbol formats. They are
2314 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
2315 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
2316 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
2317 for the list of formats.
2319 * G++ symbol mangling problem
2321 Recent versions of gcc have a bug in how they emit debugging information for
2322 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
2323 directory) can be applied to gcc to fix the problem. Alternatively, if you
2324 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
2325 usual symptom is difficulty with setting breakpoints on methods. GDB complains
2326 about the method being non-existent. (We believe that version 2.2.2 of GCC has
2329 * New 'maintenance' command
2331 All of the commands related to hacking GDB internals have been moved out of
2332 the main command set, and now live behind the 'maintenance' command. This
2333 can also be abbreviated as 'mt'. The following changes were made:
2335 dump-me -> maintenance dump-me
2336 info all-breakpoints -> maintenance info breakpoints
2337 printmsyms -> maintenance print msyms
2338 printobjfiles -> maintenance print objfiles
2339 printpsyms -> maintenance print psymbols
2340 printsyms -> maintenance print symbols
2342 The following commands are new:
2344 maintenance demangle Call internal GDB demangler routine to
2345 demangle a C++ link name and prints the result.
2346 maintenance print type Print a type chain for a given symbol
2348 * Change to .gdbinit file processing
2350 We now read the $HOME/.gdbinit file before processing the argv arguments
2351 (e.g. reading symbol files or core files). This allows global parameters to
2352 be set, which will apply during the symbol reading. The ./.gdbinit is still
2353 read after argv processing.
2355 * New hosts supported
2357 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
2359 GNU/Linux support i386-unknown-linux or linux
2361 We are also including code to support the HP/PA running BSD and HPUX. This
2362 is almost guaranteed not to work, as we didn't have time to test or build it
2363 for this release. We are including it so that the more adventurous (or
2364 masochistic) of you can play with it. We also had major problems with the
2365 fact that the compiler that we got from HP doesn't support the -g option.
2368 * New targets supported
2370 Hitachi H8/300 h8300-hitachi-hms or h8300hms
2372 * More smarts about finding #include files
2374 GDB now remembers the compilation directory for all include files, and for
2375 all files from which C is generated (like yacc and lex sources). This
2376 greatly improves GDB's ability to find yacc/lex sources, and include files,
2377 especially if you are debugging your program from a directory different from
2378 the one that contains your sources.
2380 We also fixed a bug which caused difficulty with listing and setting
2381 breakpoints in include files which contain C code. (In the past, you had to
2382 try twice in order to list an include file that you hadn't looked at before.)
2384 * Interesting infernals change
2386 GDB now deals with arbitrary numbers of sections, where the symbols for each
2387 section must be relocated relative to that section's landing place in the
2388 target's address space. This work was needed to support ELF with embedded
2389 stabs used by Solaris-2.0.
2391 * Bug fixes (of course!)
2393 There have been loads of fixes for the following things:
2394 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
2395 i960, stabs, DOS(GO32), procfs, etc...
2397 See the ChangeLog for details.
2399 *** Changes in GDB-4.5:
2401 * New machines supported (host and target)
2403 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
2405 SGI Irix-4.x mips-sgi-irix4 or iris4
2407 * New malloc package
2409 GDB now uses a new memory manager called mmalloc, based on gmalloc.
2410 Mmalloc is capable of handling mutiple heaps of memory. It is also
2411 capable of saving a heap to a file, and then mapping it back in later.
2412 This can be used to greatly speedup the startup of GDB by using a
2413 pre-parsed symbol table which lives in a mmalloc managed heap. For
2414 more details, please read mmalloc/mmalloc.texi.
2418 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
2419 'help info proc' for details.
2421 * MIPS ecoff symbol table format
2423 The code that reads MIPS symbol table format is now supported on all hosts.
2424 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
2427 * File name changes for MS-DOS
2429 Many files in the config directories have been renamed to make it easier to
2430 support GDB on MS-DOSe systems (which have very restrictive file name
2431 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
2432 environment) is close to working but has some remaining problems. Note
2433 that debugging of DOS programs is not supported, due to limitations
2434 in the ``operating system'', but it can be used to host cross-debugging.
2436 * Cross byte order fixes
2438 Many fixes have been made to support cross debugging of Sparc and MIPS
2439 targets from hosts whose byte order differs.
2441 * New -mapped and -readnow options
2443 If memory-mapped files are available on your system through the 'mmap'
2444 system call, you can use the -mapped option on the `file' or
2445 `symbol-file' commands to cause GDB to write the symbols from your
2446 program into a reusable file. If the program you are debugging is
2447 called `/path/fred', the mapped symbol file will be `./fred.syms'.
2448 Future GDB debugging sessions will notice the presence of this file,
2449 and will quickly map in symbol information from it, rather than reading
2450 the symbol table from the executable program. Using the '-mapped'
2451 option in a GDB `file' or `symbol-file' command has the same effect as
2452 starting GDB with the '-mapped' command-line option.
2454 You can cause GDB to read the entire symbol table immediately by using
2455 the '-readnow' option with any of the commands that load symbol table
2456 information (or on the GDB command line). This makes the command
2457 slower, but makes future operations faster.
2459 The -mapped and -readnow options are typically combined in order to
2460 build a `fred.syms' file that contains complete symbol information.
2461 A simple GDB invocation to do nothing but build a `.syms' file for future
2464 gdb -batch -nx -mapped -readnow programname
2466 The `.syms' file is specific to the host machine on which GDB is run.
2467 It holds an exact image of GDB's internal symbol table. It cannot be
2468 shared across multiple host platforms.
2470 * longjmp() handling
2472 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
2473 siglongjmp() without losing control. This feature has not yet been ported to
2474 all systems. It currently works on many 386 platforms, all MIPS-based
2475 platforms (SGI, DECstation, etc), and Sun3/4.
2479 Preliminary work has been put in to support the new Solaris OS from Sun. At
2480 this time, it can control and debug processes, but it is not capable of
2485 As always, many many bug fixes. The major areas were with g++, and mipsread.
2486 People using the MIPS-based platforms should experience fewer mysterious
2487 crashes and trashed symbol tables.
2489 *** Changes in GDB-4.4:
2491 * New machines supported (host and target)
2493 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2495 BSD Reno on Vax vax-dec-bsd
2496 Ultrix on Vax vax-dec-ultrix
2498 * New machines supported (target)
2500 AMD 29000 embedded, using EBMON a29k-none-none
2504 GDB continues to improve its handling of C++. `References' work better.
2505 The demangler has also been improved, and now deals with symbols mangled as
2506 per the Annotated C++ Reference Guide.
2508 GDB also now handles `stabs' symbol information embedded in MIPS
2509 `ecoff' symbol tables. Since the ecoff format was not easily
2510 extensible to handle new languages such as C++, this appeared to be a
2511 good way to put C++ debugging info into MIPS binaries. This option
2512 will be supported in the GNU C compiler, version 2, when it is
2515 * New features for SVR4
2517 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
2518 shared libraries. Debugging dynamically linked programs should present
2519 only minor differences from debugging statically linked programs.
2521 The `info proc' command will print out information about any process
2522 on an SVR4 system (including the one you are debugging). At the moment,
2523 it prints the address mappings of the process.
2525 If you bring up GDB on another SVR4 system, please send mail to
2526 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
2528 * Better dynamic linking support in SunOS
2530 Reading symbols from shared libraries which contain debugging symbols
2531 now works properly. However, there remain issues such as automatic
2532 skipping of `transfer vector' code during function calls, which
2533 make it harder to debug code in a shared library, than to debug the
2534 same code linked statically.
2538 GDB is now using the latest `getopt' routines from the FSF. This
2539 version accepts the -- prefix for options with long names. GDB will
2540 continue to accept the old forms (-option and +option) as well.
2541 Various single letter abbreviations for options have been explicity
2542 added to the option table so that they won't get overshadowed in the
2543 future by other options that begin with the same letter.
2547 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
2548 Many assorted bugs have been handled. Many more remain to be handled.
2549 See the various ChangeLog files (primarily in gdb and bfd) for details.
2552 *** Changes in GDB-4.3:
2554 * New machines supported (host and target)
2556 Amiga 3000 running Amix m68k-cbm-svr4 or amix
2557 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
2558 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
2560 * Almost SCO Unix support
2562 We had hoped to support:
2563 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2564 (except for core file support), but we discovered very late in the release
2565 that it has problems with process groups that render gdb unusable. Sorry
2566 about that. I encourage people to fix it and post the fixes.
2568 * Preliminary ELF and DWARF support
2570 GDB can read ELF object files on System V Release 4, and can handle
2571 debugging records for C, in DWARF format, in ELF files. This support
2572 is preliminary. If you bring up GDB on another SVR4 system, please
2573 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
2578 GDB now uses the latest `readline' library. One user-visible change
2579 is that two tabs will list possible command completions, which previously
2580 required typing M-? (meta-question mark, or ESC ?).
2584 The `stepi' bug that many of you noticed has been squashed.
2585 Many bugs in C++ have been handled. Many more remain to be handled.
2586 See the various ChangeLog files (primarily in gdb and bfd) for details.
2588 * State of the MIPS world (in case you wondered):
2590 GDB can understand the symbol tables emitted by the compilers
2591 supplied by most vendors of MIPS-based machines, including DEC. These
2592 symbol tables are in a format that essentially nobody else uses.
2594 Some versions of gcc come with an assembler post-processor called
2595 mips-tfile. This program is required if you want to do source-level
2596 debugging of gcc-compiled programs. I believe FSF does not ship
2597 mips-tfile with gcc version 1, but it will eventually come with gcc
2600 Debugging of g++ output remains a problem. g++ version 1.xx does not
2601 really support it at all. (If you're lucky, you should be able to get
2602 line numbers and stack traces to work, but no parameters or local
2603 variables.) With some work it should be possible to improve the
2606 When gcc version 2 is released, you will have somewhat better luck.
2607 However, even then you will get confusing results for inheritance and
2610 We will eventually provide full debugging of g++ output on
2611 DECstations. This will probably involve some kind of stabs-in-ecoff
2612 encapulation, but the details have not been worked out yet.
2615 *** Changes in GDB-4.2:
2617 * Improved configuration
2619 Only one copy of `configure' exists now, and it is not self-modifying.
2620 Porting BFD is simpler.
2624 The `step' and `next' commands now only stop at the first instruction
2625 of a source line. This prevents the multiple stops that used to occur
2626 in switch statements, for-loops, etc. `Step' continues to stop if a
2627 function that has debugging information is called within the line.
2631 Lots of small bugs fixed. More remain.
2633 * New host supported (not target)
2635 Intel 386 PC clone running Mach i386-none-mach
2638 *** Changes in GDB-4.1:
2640 * Multiple source language support
2642 GDB now has internal scaffolding to handle several source languages.
2643 It determines the type of each source file from its filename extension,
2644 and will switch expression parsing and number formatting to match the
2645 language of the function in the currently selected stack frame.
2646 You can also specifically set the language to be used, with
2647 `set language c' or `set language modula-2'.
2651 GDB now has preliminary support for the GNU Modula-2 compiler,
2652 currently under development at the State University of New York at
2653 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
2654 continue through the fall of 1991 and into 1992.
2656 Other Modula-2 compilers are currently not supported, and attempting to
2657 debug programs compiled with them will likely result in an error as the
2658 symbol table is read. Feel free to work on it, though!
2660 There are hooks in GDB for strict type checking and range checking,
2661 in the `Modula-2 philosophy', but they do not currently work.
2665 GDB can now write to executable and core files (e.g. patch
2666 a variable's value). You must turn this switch on, specify
2667 the file ("exec foo" or "core foo"), *then* modify it, e.g.
2668 by assigning a new value to a variable. Modifications take
2671 * Automatic SunOS shared library reading
2673 When you run your program, GDB automatically determines where its
2674 shared libraries (if any) have been loaded, and reads their symbols.
2675 The `share' command is no longer needed. This also works when
2676 examining core files.
2680 You can specify the number of lines that the `list' command shows.
2683 * New machines supported (host and target)
2685 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
2686 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
2687 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
2689 * New hosts supported (not targets)
2691 IBM RT/PC: romp-ibm-aix or rtpc
2693 * New targets supported (not hosts)
2695 AMD 29000 embedded with COFF a29k-none-coff
2696 AMD 29000 embedded with a.out a29k-none-aout
2697 Ultracomputer remote kernel debug a29k-nyu-kern
2699 * New remote interfaces
2705 *** Changes in GDB-4.0:
2709 Wide output is wrapped at good places to make the output more readable.
2711 Gdb now supports cross-debugging from a host machine of one type to a
2712 target machine of another type. Communication with the target system
2713 is over serial lines. The ``target'' command handles connecting to the
2714 remote system; the ``load'' command will download a program into the
2715 remote system. Serial stubs for the m68k and i386 are provided. Gdb
2716 also supports debugging of realtime processes running under VxWorks,
2717 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
2718 stub on the target system.
2720 New CPUs supported include the AMD 29000 and Intel 960.
2722 GDB now reads object files and symbol tables via a ``binary file''
2723 library, which allows a single copy of GDB to debug programs of multiple
2724 object file types such as a.out and coff.
2726 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2727 refcard.dvi and refcard.ps are available to format it).
2730 * Control-Variable user interface simplified
2732 All variables that control the operation of the debugger can be set
2733 by the ``set'' command, and displayed by the ``show'' command.
2735 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2736 ``Show prompt'' produces the response:
2737 Gdb's prompt is new-gdb=>.
2739 What follows are the NEW set commands. The command ``help set'' will
2740 print a complete list of old and new set commands. ``help set FOO''
2741 will give a longer description of the variable FOO. ``show'' will show
2742 all of the variable descriptions and their current settings.
2744 confirm on/off: Enables warning questions for operations that are
2745 hard to recover from, e.g. rerunning the program while
2746 it is already running. Default is ON.
2748 editing on/off: Enables EMACS style command line editing
2749 of input. Previous lines can be recalled with
2750 control-P, the current line can be edited with control-B,
2751 you can search for commands with control-R, etc.
2754 history filename NAME: NAME is where the gdb command history
2755 will be stored. The default is .gdb_history,
2756 or the value of the environment variable
2759 history size N: The size, in commands, of the command history. The
2760 default is 256, or the value of the environment variable
2763 history save on/off: If this value is set to ON, the history file will
2764 be saved after exiting gdb. If set to OFF, the
2765 file will not be saved. The default is OFF.
2767 history expansion on/off: If this value is set to ON, then csh-like
2768 history expansion will be performed on
2769 command line input. The default is OFF.
2771 radix N: Sets the default radix for input and output. It can be set
2772 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2773 in the current radix, so "set radix 10" is always a no-op.
2775 height N: This integer value is the number of lines on a page. Default
2776 is 24, the current `stty rows'' setting, or the ``li#''
2777 setting from the termcap entry matching the environment
2780 width N: This integer value is the number of characters on a line.
2781 Default is 80, the current `stty cols'' setting, or the ``co#''
2782 setting from the termcap entry matching the environment
2785 Note: ``set screensize'' is obsolete. Use ``set height'' and
2786 ``set width'' instead.
2788 print address on/off: Print memory addresses in various command displays,
2789 such as stack traces and structure values. Gdb looks
2790 more ``symbolic'' if you turn this off; it looks more
2791 ``machine level'' with it on. Default is ON.
2793 print array on/off: Prettyprint arrays. New convenient format! Default
2796 print demangle on/off: Print C++ symbols in "source" form if on,
2799 print asm-demangle on/off: Same, for assembler level printouts
2802 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2805 * Support for Epoch Environment.
2807 The epoch environment is a version of Emacs v18 with windowing. One
2808 new command, ``inspect'', is identical to ``print'', except that if you
2809 are running in the epoch environment, the value is printed in its own
2813 * Support for Shared Libraries
2815 GDB can now debug programs and core files that use SunOS shared libraries.
2816 Symbols from a shared library cannot be referenced
2817 before the shared library has been linked with the program (this
2818 happens after you type ``run'' and before the function main() is entered).
2819 At any time after this linking (including when examining core files
2820 from dynamically linked programs), gdb reads the symbols from each
2821 shared library when you type the ``sharedlibrary'' command.
2822 It can be abbreviated ``share''.
2824 sharedlibrary REGEXP: Load shared object library symbols for files
2825 matching a unix regular expression. No argument
2826 indicates to load symbols for all shared libraries.
2828 info sharedlibrary: Status of loaded shared libraries.
2833 A watchpoint stops execution of a program whenever the value of an
2834 expression changes. Checking for this slows down execution
2835 tremendously whenever you are in the scope of the expression, but is
2836 quite useful for catching tough ``bit-spreader'' or pointer misuse
2837 problems. Some machines such as the 386 have hardware for doing this
2838 more quickly, and future versions of gdb will use this hardware.
2840 watch EXP: Set a watchpoint (breakpoint) for an expression.
2842 info watchpoints: Information about your watchpoints.
2844 delete N: Deletes watchpoint number N (same as breakpoints).
2845 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2846 enable N: Re-enables watchpoint number N (same as breakpoints).
2849 * C++ multiple inheritance
2851 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2854 * C++ exception handling
2856 Gdb now supports limited C++ exception handling. Besides the existing
2857 ability to breakpoint on an exception handler, gdb can breakpoint on
2858 the raising of an exception (before the stack is peeled back to the
2861 catch FOO: If there is a FOO exception handler in the dynamic scope,
2862 set a breakpoint to catch exceptions which may be raised there.
2863 Multiple exceptions (``catch foo bar baz'') may be caught.
2865 info catch: Lists all exceptions which may be caught in the
2866 current stack frame.
2869 * Minor command changes
2871 The command ``call func (arg, arg, ...)'' now acts like the print
2872 command, except it does not print or save a value if the function's result
2873 is void. This is similar to dbx usage.
2875 The ``up'' and ``down'' commands now always print the frame they end up
2876 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2877 frames without printing.
2879 * New directory command
2881 'dir' now adds directories to the FRONT of the source search path.
2882 The path starts off empty. Source files that contain debug information
2883 about the directory in which they were compiled can be found even
2884 with an empty path; Sun CC and GCC include this information. If GDB can't
2885 find your source file in the current directory, type "dir .".
2887 * Configuring GDB for compilation
2889 For normal use, type ``./configure host''. See README or gdb.texinfo
2892 GDB now handles cross debugging. If you are remotely debugging between
2893 two different machines, type ``./configure host -target=targ''.
2894 Host is the machine where GDB will run; targ is the machine
2895 where the program that you are debugging will run.
projects / deliverable / binutils-gdb.git / blob