1 What has changed in GDB?
2 (Organized release by release)
4 *** Changes since GDB 6.6
6 * The GDB remote stub, gdbserver, now has lower overhead for high
7 frequency signals (e.g. SIGALRM) via the QPassSignals packet.
12 Ignore the specified signals; pass them directly to the debugged program
13 without stopping other threads or reporting them to GDB.
16 *** Changes in GDB 6.6
22 * GDB can now be configured as a cross-debugger targeting native Windows
23 (mingw32) or Cygwin. It can communicate with a remote debugging stub
24 running on a Windows system over TCP/IP to debug Windows programs.
26 * The GDB remote stub, gdbserver, has been updated to support Windows and
27 Cygwin debugging. Both single-threaded and multi-threaded programs are
30 * The "set trust-readonly-sections" command works again. This command was
31 broken in GDB 6.3, 6.4, and 6.5.
33 * Support for GNU/Linux Thread Local Storage (TLS, per-thread variables) no
34 longer requires symbolic debug information (e.g. DWARF-2).
41 Manage a list of substitution rules that GDB uses to rewrite the name
42 of the directories where the sources are located. This can be useful
43 for instance when the sources were moved to a different location
44 between compilation and debugging.
48 Print each CLI command as it is executed. Each command is prefixed with
49 a number of `+' symbols representing the nesting depth.
50 The source command now has a `-v' option to enable the same feature.
54 The ARM Demon monitor support (RDP protocol, "target rdp").
56 Kernel Object Display, an embedded debugging feature which only worked with
57 an obsolete version of Cisco IOS.
59 The 'set download-write-size' and 'show download-write-size' commands.
64 Tell a stub about GDB client features, and request remote target features.
65 The first feature implemented is PacketSize, which allows the target to
66 specify the size of packets it can handle - to minimize the number of
67 packets required and improve performance when connected to a remote
71 Fetch an OS auxilliary vector from the remote stub. This packet is a
72 more efficient replacement for qPart:auxv:read.
74 * Removed remote packets
77 This packet has been replaced by qXfer:auxv:read. Only GDB 6.4 and 6.5
78 used it, and only gdbserver implemented it.
80 *** Changes in GDB 6.5
84 Renesas M32C/M16C m32c-elf
86 Morpho Technologies ms1 ms1-elf
90 init-if-undefined Initialize a convenience variable, but
91 only if it doesn't already have a value.
93 The following commands are presently only implemented for native GNU/Linux:
95 checkpoint Save a snapshot of the program state.
97 restart <n> Return the program state to a
98 previously saved state.
100 info checkpoints List currently saved checkpoints.
102 delete-checkpoint <n> Delete a previously saved checkpoint.
104 set|show detach-on-fork Tell gdb whether to detach from a newly
105 forked process, or to keep debugging it.
107 info forks List forks of the user program that
108 are available to be debugged.
110 fork <n> Switch to debugging one of several
111 forks of the user program that are
112 available to be debugged.
114 delete-fork <n> Delete a fork from the list of forks
115 that are available to be debugged (and
116 kill the forked process).
118 detach-fork <n> Delete a fork from the list of forks
119 that are available to be debugged (and
120 allow the process to continue).
124 Morpho Technologies ms2 ms1-elf
126 * Improved Windows host support
128 GDB now builds as a cross debugger hosted on i686-mingw32, including
129 native console support, and remote communications using either
130 network sockets or serial ports.
132 * Improved Modula-2 language support
134 GDB can now print most types in the Modula-2 syntax. This includes:
135 basic types, set types, record types, enumerated types, range types,
136 pointer types and ARRAY types. Procedure var parameters are correctly
137 printed and hexadecimal addresses and character constants are also
138 written in the Modula-2 syntax. Best results can be obtained by using
139 GNU Modula-2 together with the -gdwarf-2 command line option.
143 The ARM rdi-share module.
145 The Netware NLM debug server.
147 *** Changes in GDB 6.4
149 * New native configurations
151 OpenBSD/arm arm*-*-openbsd*
152 OpenBSD/mips64 mips64-*-openbsd*
156 Morpho Technologies ms1 ms1-elf
158 * New command line options
160 --batch-silent As for --batch, but totally silent.
161 --return-child-result The debugger will exist with the same value
162 the child (debugged) program exited with.
163 --eval-command COMMAND, -ex COMMAND
164 Execute a single GDB CLI command. This may be
165 specified multiple times and in conjunction
166 with the --command (-x) option.
168 * Deprecated commands removed
170 The following commands, that were deprecated in 2000, have been
174 set|show arm disassembly-flavor set|show arm disassembler
175 othernames set arm disassembler
176 set|show remotedebug set|show debug remote
177 set|show archdebug set|show debug arch
178 set|show eventdebug set|show debug event
181 * New BSD user-level threads support
183 It is now possible to debug programs using the user-level threads
184 library on OpenBSD and FreeBSD. Currently supported (target)
187 FreeBSD/amd64 x86_64-*-freebsd*
188 FreeBSD/i386 i386-*-freebsd*
189 OpenBSD/i386 i386-*-openbsd*
191 Note that the new kernel threads libraries introduced in FreeBSD 5.x
192 are not yet supported.
194 * New support for Matsushita MN10300 w/sim added
195 (Work in progress). mn10300-elf.
197 * REMOVED configurations and files
199 VxWorks and the XDR protocol *-*-vxworks
200 Motorola MCORE mcore-*-*
201 National Semiconductor NS32000 ns32k-*-*
203 * New "set print array-indexes" command
205 After turning this setting "on", GDB prints the index of each element
206 when displaying arrays. The default is "off" to preserve the previous
209 * VAX floating point support
211 GDB now supports the not-quite-ieee VAX F and D floating point formats.
213 * User-defined command support
215 In addition to using $arg0..$arg9 for argument passing, it is now possible
216 to use $argc to determine now many arguments have been passed. See the
217 section on user-defined commands in the user manual for more information.
219 *** Changes in GDB 6.3:
221 * New command line option
223 GDB now accepts -l followed by a number to set the timeout for remote
226 * GDB works with GCC -feliminate-dwarf2-dups
228 GDB now supports a more compact representation of DWARF-2 debug
229 information using DW_FORM_ref_addr references. These are produced
230 by GCC with the option -feliminate-dwarf2-dups and also by some
231 proprietary compilers. With GCC, you must use GCC 3.3.4 or later
232 to use -feliminate-dwarf2-dups.
234 * Internationalization
236 When supported by the host system, GDB will be built with
237 internationalization (libintl). The task of marking up the sources is
238 continued, we're looking forward to our first translation.
242 Initial support for debugging programs compiled with the GNAT
243 implementation of the Ada programming language has been integrated
244 into GDB. In this release, support is limited to expression evaluation.
246 * New native configurations
248 GNU/Linux/m32r m32r-*-linux-gnu
252 GDB's remote protocol now includes support for the 'p' packet. This
253 packet is used to fetch individual registers from a remote inferior.
255 * END-OF-LIFE registers[] compatibility module
257 GDB's internal register infrastructure has been completely rewritten.
258 The new infrastructure making possible the implementation of key new
259 features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit
262 GDB 6.3 will be the last release to include the the registers[]
263 compatibility module that allowed out-of-date configurations to
264 continue to work. This change directly impacts the following
276 Unless there is activity to revive these configurations, they will be
277 made OBSOLETE in GDB 6.4, and REMOVED from GDB 6.5.
279 * OBSOLETE configurations and files
281 Configurations that have been declared obsolete in this release have
282 been commented out. Unless there is activity to revive these
283 configurations, the next release of GDB will have their sources
293 *** Changes in GDB 6.2.1:
295 * MIPS `break main; run' gave an heuristic-fence-post warning
297 When attempting to run even a simple program, a warning about
298 heuristic-fence-post being hit would be reported. This problem has
301 * MIPS IRIX 'long double' crashed GDB
303 When examining a long double variable, GDB would get a segmentation
304 fault. The crash has been fixed (but GDB 6.2 cannot correctly examine
305 IRIX long double values).
309 A bug in the VAX stack code was causing problems with the "next"
310 command. This problem has been fixed.
312 *** Changes in GDB 6.2:
314 * Fix for ``many threads''
316 On GNU/Linux systems that use the NPTL threads library, a program
317 rapidly creating and deleting threads would confuse GDB leading to the
320 ptrace: No such process.
321 thread_db_get_info: cannot get thread info: generic error
323 This problem has been fixed.
325 * "-async" and "-noasync" options removed.
327 Support for the broken "-noasync" option has been removed (it caused
330 * New ``start'' command.
332 This command runs the program until the begining of the main procedure.
334 * New BSD Kernel Data Access Library (libkvm) interface
336 Using ``target kvm'' it is now possible to debug kernel core dumps and
337 live kernel memory images on various FreeBSD, NetBSD and OpenBSD
338 platforms. Currently supported (native-only) configurations are:
340 FreeBSD/amd64 x86_64-*-freebsd*
341 FreeBSD/i386 i?86-*-freebsd*
342 NetBSD/i386 i?86-*-netbsd*
343 NetBSD/m68k m68*-*-netbsd*
344 NetBSD/sparc sparc-*-netbsd*
345 OpenBSD/amd64 x86_64-*-openbsd*
346 OpenBSD/i386 i?86-*-openbsd*
347 OpenBSD/m68k m68*-openbsd*
348 OpenBSD/sparc sparc-*-openbsd*
350 * Signal trampoline code overhauled
352 Many generic problems with GDB's signal handling code have been fixed.
353 These include: backtraces through non-contiguous stacks; recognition
354 of sa_sigaction signal trampolines; backtrace from a NULL pointer
355 call; backtrace through a signal trampoline; step into and out of
356 signal handlers; and single-stepping in the signal trampoline.
358 Please note that kernel bugs are a limiting factor here. These
359 features have been shown to work on an s390 GNU/Linux system that
360 include a 2.6.8-rc1 kernel. Ref PR breakpoints/1702.
362 * Cygwin support for DWARF 2 added.
364 * New native configurations
366 GNU/Linux/hppa hppa*-*-linux*
367 OpenBSD/hppa hppa*-*-openbsd*
368 OpenBSD/m68k m68*-*-openbsd*
369 OpenBSD/m88k m88*-*-openbsd*
370 OpenBSD/powerpc powerpc-*-openbsd*
371 NetBSD/vax vax-*-netbsd*
372 OpenBSD/vax vax-*-openbsd*
374 * END-OF-LIFE frame compatibility module
376 GDB's internal frame infrastructure has been completely rewritten.
377 The new infrastructure making it possible to support key new features
378 including DWARF 2 Call Frame Information. To aid in the task of
379 migrating old configurations to this new infrastructure, a
380 compatibility module, that allowed old configurations to continue to
381 work, was also included.
383 GDB 6.2 will be the last release to include this frame compatibility
384 module. This change directly impacts the following configurations:
394 Unless there is activity to revive these configurations, they will be
395 made OBSOLETE in GDB 6.3, and REMOVED from GDB 6.4.
397 * REMOVED configurations and files
399 Sun 3, running SunOS 3 m68*-*-sunos3*
400 Sun 3, running SunOS 4 m68*-*-sunos4*
401 Sun 2, running SunOS 3 m68000-*-sunos3*
402 Sun 2, running SunOS 4 m68000-*-sunos4*
403 Motorola 680x0 running LynxOS m68*-*-lynxos*
404 AT&T 3b1/Unix pc m68*-att-*
405 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
406 decstation mips-dec-* mips-little-*
407 riscos mips-*-riscos* mips-*-sysv*
409 sysv mips*-*-sysv4* (IRIX 5/6 not included)
411 *** Changes in GDB 6.1.1:
413 * TUI (Text-mode User Interface) built-in (also included in GDB 6.1)
415 The TUI (Text-mode User Interface) is now built as part of a default
416 GDB configuration. It is enabled by either selecting the TUI with the
417 command line option "-i=tui" or by running the separate "gdbtui"
418 program. For more information on the TUI, see the manual "Debugging
421 * Pending breakpoint support (also included in GDB 6.1)
423 Support has been added to allow you to specify breakpoints in shared
424 libraries that have not yet been loaded. If a breakpoint location
425 cannot be found, and the "breakpoint pending" option is set to auto,
426 GDB queries you if you wish to make the breakpoint pending on a future
427 shared-library load. If and when GDB resolves the breakpoint symbol,
428 the pending breakpoint is removed as one or more regular breakpoints
431 Pending breakpoints are very useful for GCJ Java debugging.
433 * Fixed ISO-C build problems
435 The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained
436 non ISO-C code that stopped them being built using a more strict ISO-C
437 compiler (e.g., IBM's C compiler).
439 * Fixed build problem on IRIX 5
441 Due to header problems with <sys/proc.h>, the file gdb/proc-api.c
442 wasn't able to compile compile on an IRIX 5 system.
444 * Added execute permission to gdb/gdbserver/configure
446 The shell script gdb/testsuite/gdb.stabs/configure lacked execute
447 permission. This bug would cause configure to fail on a number of
448 systems (Solaris, IRIX). Ref: server/519.
450 * Fixed build problem on hpux2.0w-hp-hpux11.00 using the HP ANSI C compiler
452 Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c
453 has been updated to use constant array sizes.
455 * Fixed a panic in the DWARF Call Frame Info code on Solaris 2.7
457 GCC 3.3.2, on Solaris 2.7, includes the DW_EH_PE_funcrel encoding in
458 its generated DWARF Call Frame Info. This encoding was causing GDB to
459 panic, that panic has been fixed. Ref: gdb/1628.
461 * Fixed a problem when examining parameters in shared library code.
463 When examining parameters in optimized shared library code generated
464 by a mainline GCC, GDB would incorrectly report ``Variable "..." is
465 not available''. GDB now correctly displays the variable's value.
467 *** Changes in GDB 6.1:
469 * Removed --with-mmalloc
471 Support for the mmalloc memory manager has been removed, as it
472 conflicted with the internal gdb byte cache.
474 * Changes in AMD64 configurations
476 The AMD64 target now includes the %cs and %ss registers. As a result
477 the AMD64 remote protocol has changed; this affects the floating-point
478 and SSE registers. If you rely on those registers for your debugging,
479 you should upgrade gdbserver on the remote side.
481 * Revised SPARC target
483 The SPARC target has been completely revised, incorporating the
484 FreeBSD/sparc64 support that was added for GDB 6.0. As a result
485 support for LynxOS and SunOS 4 has been dropped. Calling functions
486 from within GDB on operating systems with a non-executable stack
487 (Solaris, OpenBSD) now works.
491 GDB has a new C++ demangler which does a better job on the mangled
492 names generated by current versions of g++. It also runs faster, so
493 with this and other changes gdb should now start faster on large C++
496 * DWARF 2 Location Expressions
498 GDB support for location expressions has been extended to support function
499 arguments and frame bases. Older versions of GDB could crash when they
502 * C++ nested types and namespaces
504 GDB's support for nested types and namespaces in C++ has been
505 improved, especially if you use the DWARF 2 debugging format. (This
506 is the default for recent versions of GCC on most platforms.)
507 Specifically, if you have a class "Inner" defined within a class or
508 namespace "Outer", then GDB realizes that the class's name is
509 "Outer::Inner", not simply "Inner". This should greatly reduce the
510 frequency of complaints about not finding RTTI symbols. In addition,
511 if you are stopped at inside of a function defined within a namespace,
512 GDB modifies its name lookup accordingly.
514 * New native configurations
516 NetBSD/amd64 x86_64-*-netbsd*
517 OpenBSD/amd64 x86_64-*-openbsd*
518 OpenBSD/alpha alpha*-*-openbsd*
519 OpenBSD/sparc sparc-*-openbsd*
520 OpenBSD/sparc64 sparc64-*-openbsd*
522 * New debugging protocols
524 M32R with SDI protocol m32r-*-elf*
526 * "set prompt-escape-char" command deleted.
528 The command "set prompt-escape-char" has been deleted. This command,
529 and its very obscure effet on GDB's prompt, was never documented,
530 tested, nor mentioned in the NEWS file.
532 * OBSOLETE configurations and files
534 Configurations that have been declared obsolete in this release have
535 been commented out. Unless there is activity to revive these
536 configurations, the next release of GDB will have their sources
539 Sun 3, running SunOS 3 m68*-*-sunos3*
540 Sun 3, running SunOS 4 m68*-*-sunos4*
541 Sun 2, running SunOS 3 m68000-*-sunos3*
542 Sun 2, running SunOS 4 m68000-*-sunos4*
543 Motorola 680x0 running LynxOS m68*-*-lynxos*
544 AT&T 3b1/Unix pc m68*-att-*
545 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
546 decstation mips-dec-* mips-little-*
547 riscos mips-*-riscos* mips-*-sysv*
549 sysv mips*-*-sysv4* (IRIX 5/6 not included)
551 * REMOVED configurations and files
553 SGI Irix-4.x mips-sgi-irix4 or iris4
554 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
555 Z8000 simulator z8k-zilog-none or z8ksim
556 Matsushita MN10200 w/simulator mn10200-*-*
557 H8/500 simulator h8500-hitachi-hms or h8500hms
558 HP/PA running BSD hppa*-*-bsd*
559 HP/PA running OSF/1 hppa*-*-osf*
560 HP/PA Pro target hppa*-*-pro*
561 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
562 386BSD i[3456]86-*-bsd*
563 Sequent family i[3456]86-sequent-sysv4*
564 i[3456]86-sequent-sysv*
565 i[3456]86-sequent-bsd*
566 SPARC running LynxOS sparc-*-lynxos*
567 SPARC running SunOS 4 sparc-*-sunos4*
568 Tsqware Sparclet sparclet-*-*
569 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
571 *** Changes in GDB 6.0:
575 Support for debugging the Objective-C programming language has been
578 * New backtrace mechanism (includes DWARF 2 Call Frame Information).
580 DWARF 2's Call Frame Information makes available compiler generated
581 information that more exactly describes the program's run-time stack.
582 By using this information, GDB is able to provide more robust stack
585 The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets
586 have been updated to use a new backtrace mechanism which includes
591 GDB's remote protocol has been extended to include support for hosted
592 file I/O (where the remote target uses GDB's file system). See GDB's
593 remote protocol documentation for details.
595 * All targets using the new architecture framework.
597 All of GDB's targets have been updated to use the new internal
598 architecture framework. The way is now open for future GDB releases
599 to include cross-architecture native debugging support (i386 on amd64,
602 * GNU/Linux's Thread Local Storage (TLS)
604 GDB now includes support for for the GNU/Linux implementation of
605 per-thread variables.
607 * GNU/Linux's Native POSIX Thread Library (NPTL)
609 GDB's thread code has been updated to work with either the new
610 GNU/Linux NPTL thread library or the older "LinuxThreads" library.
612 * Separate debug info.
614 GDB, in conjunction with BINUTILS, now supports a mechanism for
615 automatically loading debug information from a separate file. Instead
616 of shipping full debug and non-debug versions of system libraries,
617 system integrators can now instead ship just the stripped libraries
618 and optional debug files.
620 * DWARF 2 Location Expressions
622 DWARF 2 Location Expressions allow the compiler to more completely
623 describe the location of variables (even in optimized code) to the
626 GDB now includes preliminary support for location expressions (support
627 for DW_OP_piece is still missing).
631 A number of long standing bugs that caused GDB to die while starting a
632 Java application have been fixed. GDB's Java support is now
633 considered "useable".
635 * GNU/Linux support for fork, vfork, and exec.
637 The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode"
638 commands are now implemented for GNU/Linux. They require a 2.5.x or later
641 * GDB supports logging output to a file
643 There are two new commands, "set logging" and "show logging", which can be
644 used to capture GDB's output to a file.
646 * The meaning of "detach" has changed for gdbserver
648 The "detach" command will now resume the application, as documented. To
649 disconnect from gdbserver and leave it stopped, use the new "disconnect"
652 * d10v, m68hc11 `regs' command deprecated
654 The `info registers' command has been updated so that it displays the
655 registers using a format identical to the old `regs' command.
659 A new command, "maint set profile on/off", has been added. This command can
660 be used to enable or disable profiling while running GDB, to profile a
661 session or a set of commands. In addition there is a new configure switch,
662 "--enable-profiling", which will cause GDB to be compiled with profiling
663 data, for more informative profiling results.
665 * Default MI syntax changed to "mi2".
667 The default MI (machine interface) syntax, enabled by the command line
668 option "-i=mi", has been changed to "mi2". The previous MI syntax,
669 "mi1", can be enabled by specifying the option "-i=mi1".
671 Support for the original "mi0" syntax (included in GDB 5.0) has been
674 Fix for gdb/192: removed extraneous space when displaying frame level.
675 Fix for gdb/672: update changelist is now output in mi list format.
676 Fix for gdb/702: a -var-assign that updates the value now shows up
677 in a subsequent -var-update.
679 * New native configurations.
681 FreeBSD/amd64 x86_64-*-freebsd*
683 * Multi-arched targets.
685 HP/PA HPUX11 hppa*-*-hpux*
686 Renesas M32R/D w/simulator m32r-*-elf*
688 * OBSOLETE configurations and files
690 Configurations that have been declared obsolete in this release have
691 been commented out. Unless there is activity to revive these
692 configurations, the next release of GDB will have their sources
695 Z8000 simulator z8k-zilog-none or z8ksim
696 Matsushita MN10200 w/simulator mn10200-*-*
697 H8/500 simulator h8500-hitachi-hms or h8500hms
698 HP/PA running BSD hppa*-*-bsd*
699 HP/PA running OSF/1 hppa*-*-osf*
700 HP/PA Pro target hppa*-*-pro*
701 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
702 Sequent family i[3456]86-sequent-sysv4*
703 i[3456]86-sequent-sysv*
704 i[3456]86-sequent-bsd*
705 Tsqware Sparclet sparclet-*-*
706 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
708 * REMOVED configurations and files
711 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
712 IBM AIX PS/2 i[3456]86-*-aix
713 i386 running Mach 3.0 i[3456]86-*-mach3*
714 i386 running Mach i[3456]86-*-mach*
715 i386 running OSF/1 i[3456]86-*osf1mk*
716 HP/Apollo 68k Family m68*-apollo*-sysv*,
718 m68*-hp-bsd*, m68*-hp-hpux*
719 Argonaut Risc Chip (ARC) arc-*-*
720 Mitsubishi D30V d30v-*-*
721 Fujitsu FR30 fr30-*-elf*
722 OS/9000 i[34]86-*-os9k
723 I960 with MON960 i960-*-coff
725 * MIPS $fp behavior changed
727 The convenience variable $fp, for the MIPS, now consistently returns
728 the address of the current frame's base. Previously, depending on the
729 context, $fp could refer to either $sp or the current frame's base
730 address. See ``8.10 Registers'' in the manual ``Debugging with GDB:
731 The GNU Source-Level Debugger''.
733 *** Changes in GDB 5.3:
735 * GNU/Linux shared library multi-threaded performance improved.
737 When debugging a multi-threaded application on GNU/Linux, GDB now uses
738 `/proc', in preference to `ptrace' for memory reads. This may result
739 in an improvement in the start-up time of multi-threaded, shared
740 library applications when run under GDB. One GDB user writes: ``loads
741 shared libs like mad''.
743 * ``gdbserver'' now supports multi-threaded applications on some targets
745 Support for debugging multi-threaded applications which use
746 the GNU/Linux LinuxThreads package has been added for
747 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
748 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
750 * GDB now supports C/C++ preprocessor macros.
752 GDB now expands preprocessor macro invocations in C/C++ expressions,
753 and provides various commands for showing macro definitions and how
756 The new command `macro expand EXPRESSION' expands any macro
757 invocations in expression, and shows the result.
759 The new command `show macro MACRO-NAME' shows the definition of the
760 macro named MACRO-NAME, and where it was defined.
762 Most compilers don't include information about macros in the debugging
763 information by default. In GCC 3.1, for example, you need to compile
764 your program with the options `-gdwarf-2 -g3'. If the macro
765 information is present in the executable, GDB will read it.
767 * Multi-arched targets.
769 DEC Alpha (partial) alpha*-*-*
770 DEC VAX (partial) vax-*-*
772 National Semiconductor NS32000 (partial) ns32k-*-*
773 Motorola 68000 (partial) m68k-*-*
774 Motorola MCORE mcore-*-*
778 Fujitsu FRV architecture added by Red Hat frv*-*-*
781 * New native configurations
783 Alpha NetBSD alpha*-*-netbsd*
784 SH NetBSD sh*-*-netbsdelf*
785 MIPS NetBSD mips*-*-netbsd*
786 UltraSPARC NetBSD sparc64-*-netbsd*
788 * OBSOLETE configurations and files
790 Configurations that have been declared obsolete in this release have
791 been commented out. Unless there is activity to revive these
792 configurations, the next release of GDB will have their sources
795 Mitsubishi D30V d30v-*-*
796 OS/9000 i[34]86-*-os9k
797 IBM AIX PS/2 i[3456]86-*-aix
798 Fujitsu FR30 fr30-*-elf*
799 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
800 Argonaut Risc Chip (ARC) arc-*-*
801 i386 running Mach 3.0 i[3456]86-*-mach3*
802 i386 running Mach i[3456]86-*-mach*
803 i386 running OSF/1 i[3456]86-*osf1mk*
804 HP/Apollo 68k Family m68*-apollo*-sysv*,
806 m68*-hp-bsd*, m68*-hp-hpux*
807 I960 with MON960 i960-*-coff
811 CHILL, a Pascal like language used by telecommunications companies.
813 * REMOVED configurations and files
815 AMD 29k family via UDI a29k-amd-udi, udi29k
816 A29K VxWorks a29k-*-vxworks
817 AMD 29000 embedded, using EBMON a29k-none-none
818 AMD 29000 embedded with COFF a29k-none-coff
819 AMD 29000 embedded with a.out a29k-none-aout
821 testsuite/gdb.hp/gdb.threads-hp/ directory
823 * New command "set max-user-call-depth <nnn>"
825 This command allows the user to limit the call depth of user-defined
826 commands. The default is 1024.
828 * Changes in FreeBSD/i386 native debugging.
830 Support for the "generate-core-file" has been added.
832 * New commands "dump", "append", and "restore".
834 These commands allow data to be copied from target memory
835 to a bfd-format or binary file (dump and append), and back
836 from a file into memory (restore).
838 * Improved "next/step" support on multi-processor Alpha Tru64.
840 The previous single-step mechanism could cause unpredictable problems,
841 including the random appearance of SIGSEGV or SIGTRAP signals. The use
842 of a software single-step mechanism prevents this.
844 *** Changes in GDB 5.2.1:
852 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
853 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
854 Fix, by Joel Brobecker imported from mainline.
856 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
857 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
858 Fix, by Fred Fish, imported from mainline.
860 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
861 Surprisingly enough, it works now.
862 By Michal Ludvig, imported from mainline.
864 i386 hardware watchpoint support:
865 avoid misses on second run for some targets.
866 By Pierre Muller, imported from mainline.
868 *** Changes in GDB 5.2:
870 * New command "set trust-readonly-sections on[off]".
872 This command is a hint that tells gdb that read-only sections
873 really are read-only (ie. that their contents will not change).
874 In this mode, gdb will go to the object file rather than the
875 target to read memory from read-only sections (such as ".text").
876 This can be a significant performance improvement on some
877 (notably embedded) targets.
879 * New command "generate-core-file" (or "gcore").
881 This new gdb command allows the user to drop a core file of the child
882 process state at any time. So far it's been implemented only for
883 GNU/Linux and Solaris, but should be relatively easily ported to other
884 hosts. Argument is core file name (defaults to core.<pid>).
886 * New command line option
888 GDB now accepts --pid or -p followed by a process id.
890 * Change in command line behavior -- corefiles vs. process ids.
892 There is a subtle behavior in the way in which GDB handles
893 command line arguments. The first non-flag argument is always
894 a program to debug, but the second non-flag argument may either
895 be a corefile or a process id. Previously, GDB would attempt to
896 open the second argument as a corefile, and if that failed, would
897 issue a superfluous error message and then attempt to attach it as
898 a process. Now, if the second argument begins with a non-digit,
899 it will be treated as a corefile. If it begins with a digit,
900 GDB will attempt to attach it as a process, and if no such process
901 is found, will then attempt to open it as a corefile.
903 * Changes in ARM configurations.
905 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
906 configuration is fully multi-arch.
908 * New native configurations
910 ARM NetBSD arm*-*-netbsd*
911 x86 OpenBSD i[3456]86-*-openbsd*
912 AMD x86-64 running GNU/Linux x86_64-*-linux-*
913 Sparc64 running FreeBSD sparc64-*-freebsd*
917 Sanyo XStormy16 xstormy16-elf
919 * OBSOLETE configurations and files
921 Configurations that have been declared obsolete in this release have
922 been commented out. Unless there is activity to revive these
923 configurations, the next release of GDB will have their sources
926 AMD 29k family via UDI a29k-amd-udi, udi29k
927 A29K VxWorks a29k-*-vxworks
928 AMD 29000 embedded, using EBMON a29k-none-none
929 AMD 29000 embedded with COFF a29k-none-coff
930 AMD 29000 embedded with a.out a29k-none-aout
932 testsuite/gdb.hp/gdb.threads-hp/ directory
934 * REMOVED configurations and files
936 TI TMS320C80 tic80-*-*
938 PowerPC Solaris powerpcle-*-solaris*
939 PowerPC Windows NT powerpcle-*-cygwin32
940 PowerPC Netware powerpc-*-netware*
941 Harris/CXUX m88k m88*-harris-cxux*
942 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
943 ns32k-utek-sysv* ns32k-utek-*
944 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
945 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
946 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
947 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
948 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
950 * Changes to command line processing
952 The new `--args' feature can be used to specify command-line arguments
953 for the inferior from gdb's command line.
955 * Changes to key bindings
957 There is a new `operate-and-get-next' function bound to `C-o'.
959 *** Changes in GDB 5.1.1
961 Fix compile problem on DJGPP.
963 Fix a problem with floating-point registers on the i386 being
966 Fix to stop GDB crashing on .debug_str debug info.
968 Numerous documentation fixes.
970 Numerous testsuite fixes.
972 *** Changes in GDB 5.1:
974 * New native configurations
976 Alpha FreeBSD alpha*-*-freebsd*
977 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
978 MIPS GNU/Linux mips*-*-linux*
979 MIPS SGI Irix 6.x mips*-sgi-irix6*
981 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
985 Motorola 68HC11 and 68HC12 m68hc11-elf
987 UltraSparc running GNU/Linux sparc64-*-linux*
989 * OBSOLETE configurations and files
991 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
992 Harris/CXUX m88k m88*-harris-cxux*
993 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
994 ns32k-utek-sysv* ns32k-utek-*
995 TI TMS320C80 tic80-*-*
997 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
998 PowerPC Solaris powerpcle-*-solaris*
999 PowerPC Windows NT powerpcle-*-cygwin32
1000 PowerPC Netware powerpc-*-netware*
1001 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
1002 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
1003 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
1004 Apple Macintosh (MPW) host N/A
1006 stuff.c (Program to stuff files into a specially prepared space in kdb)
1007 kdb-start.c (Main loop for the standalone kernel debugger)
1009 Configurations that have been declared obsolete in this release have
1010 been commented out. Unless there is activity to revive these
1011 configurations, the next release of GDB will have their sources
1012 permanently REMOVED.
1014 * REMOVED configurations and files
1016 Altos 3068 m68*-altos-*
1017 Convex c1-*-*, c2-*-*
1019 ARM RISCix arm-*-* (as host)
1023 * GDB has been converted to ISO C.
1025 GDB's source code has been converted to ISO C. In particular, the
1026 sources are fully protoized, and rely on standard headers being
1031 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
1033 * The MI enabled by default.
1035 The new machine oriented interface (MI) introduced in GDB 5.0 has been
1036 revised and enabled by default. Packages which use GDB as a debugging
1037 engine behind a UI or another front end are encouraged to switch to
1038 using the GDB/MI interface, instead of the old annotations interface
1039 which is now deprecated.
1041 * Support for debugging Pascal programs.
1043 GDB now includes support for debugging Pascal programs. The following
1044 main features are supported:
1046 - Pascal-specific data types such as sets;
1048 - automatic recognition of Pascal sources based on file-name
1051 - Pascal-style display of data types, variables, and functions;
1053 - a Pascal expression parser.
1055 However, some important features are not yet supported.
1057 - Pascal string operations are not supported at all;
1059 - there are some problems with boolean types;
1061 - Pascal type hexadecimal constants are not supported
1062 because they conflict with the internal variables format;
1064 - support for Pascal objects and classes is not full yet;
1066 - unlike Pascal, GDB is case-sensitive for symbol names.
1068 * Changes in completion.
1070 Commands such as `shell', `run' and `set args', which pass arguments
1071 to inferior programs, now complete on file names, similar to what
1072 users expect at the shell prompt.
1074 Commands which accept locations, such as `disassemble', `print',
1075 `breakpoint', `until', etc. now complete on filenames as well as
1076 program symbols. Thus, if you type "break foob TAB", and the source
1077 files linked into the programs include `foobar.c', that file name will
1078 be one of the candidates for completion. However, file names are not
1079 considered for completion after you typed a colon that delimits a file
1080 name from a name of a function in that file, as in "break foo.c:bar".
1082 `set demangle-style' completes on available demangling styles.
1084 * New platform-independent commands:
1086 It is now possible to define a post-hook for a command as well as a
1087 hook that runs before the command. For more details, see the
1088 documentation of `hookpost' in the GDB manual.
1090 * Changes in GNU/Linux native debugging.
1092 Support for debugging multi-threaded programs has been completely
1093 revised for all platforms except m68k and sparc. You can now debug as
1094 many threads as your system allows you to have.
1096 Attach/detach is supported for multi-threaded programs.
1098 Support for SSE registers was added for x86. This doesn't work for
1099 multi-threaded programs though.
1101 * Changes in MIPS configurations.
1103 Multi-arch support is enabled for all MIPS configurations.
1105 GDB can now be built as native debugger on SGI Irix 6.x systems for
1106 debugging n32 executables. (Debugging 64-bit executables is not yet
1109 * Unified support for hardware watchpoints in all x86 configurations.
1111 Most (if not all) native x86 configurations support hardware-assisted
1112 breakpoints and watchpoints in a unified manner. This support
1113 implements debug register sharing between watchpoints, which allows to
1114 put a virtually infinite number of watchpoints on the same address,
1115 and also supports watching regions up to 16 bytes with several debug
1118 The new maintenance command `maintenance show-debug-regs' toggles
1119 debugging print-outs in functions that insert, remove, and test
1120 watchpoints and hardware breakpoints.
1122 * Changes in the DJGPP native configuration.
1124 New command ``info dos sysinfo'' displays assorted information about
1125 the CPU, OS, memory, and DPMI server.
1127 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
1128 display information about segment descriptors stored in GDT, LDT, and
1131 New commands ``info dos pde'' and ``info dos pte'' display entries
1132 from Page Directory and Page Tables (for now works with CWSDPMI only).
1133 New command ``info dos address-pte'' displays the Page Table entry for
1134 a given linear address.
1136 GDB can now pass command lines longer than 126 characters to the
1137 program being debugged (requires an update to the libdbg.a library
1138 which is part of the DJGPP development kit).
1140 DWARF2 debug info is now supported.
1142 It is now possible to `step' and `next' through calls to `longjmp'.
1144 * Changes in documentation.
1146 All GDB documentation was converted to GFDL, the GNU Free
1147 Documentation License.
1149 Tracepoints-related commands are now fully documented in the GDB
1152 TUI, the Text-mode User Interface, is now documented in the manual.
1154 Tracepoints-related commands are now fully documented in the GDB
1157 The "GDB Internals" manual now has an index. It also includes
1158 documentation of `ui_out' functions, GDB coding standards, x86
1159 hardware watchpoints, and memory region attributes.
1161 * GDB's version number moved to ``version.in''
1163 The Makefile variable VERSION has been replaced by the file
1164 ``version.in''. People creating GDB distributions should update the
1165 contents of this file.
1169 GUD support is now a standard part of the EMACS distribution.
1171 *** Changes in GDB 5.0:
1173 * Improved support for debugging FP programs on x86 targets
1175 Unified and much-improved support for debugging floating-point
1176 programs on all x86 targets. In particular, ``info float'' now
1177 displays the FP registers in the same format on all x86 targets, with
1178 greater level of detail.
1180 * Improvements and bugfixes in hardware-assisted watchpoints
1182 It is now possible to watch array elements, struct members, and
1183 bitfields with hardware-assisted watchpoints. Data-read watchpoints
1184 on x86 targets no longer erroneously trigger when the address is
1187 * Improvements in the native DJGPP version of GDB
1189 The distribution now includes all the scripts and auxiliary files
1190 necessary to build the native DJGPP version on MS-DOS/MS-Windows
1191 machines ``out of the box''.
1193 The DJGPP version can now debug programs that use signals. It is
1194 possible to catch signals that happened in the debuggee, deliver
1195 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
1196 would kill the program being debugged.) Programs that hook hardware
1197 interrupts (keyboard, timer, etc.) can also be debugged.
1199 It is now possible to debug DJGPP programs that redirect their
1200 standard handles or switch them to raw (as opposed to cooked) mode, or
1201 even close them. The command ``run < foo > bar'' works as expected,
1202 and ``info terminal'' reports useful information about the debuggee's
1203 terminal, including raw/cooked mode, redirection, etc.
1205 The DJGPP version now uses termios functions for console I/O, which
1206 enables debugging graphics programs. Interrupting GDB with Ctrl-C
1209 DOS-style file names with drive letters are now fully supported by
1212 It is now possible to debug DJGPP programs that switch their working
1213 directory. It is also possible to rerun the debuggee any number of
1214 times without restarting GDB; thus, you can use the same setup,
1215 breakpoints, etc. for many debugging sessions.
1217 * New native configurations
1219 ARM GNU/Linux arm*-*-linux*
1220 PowerPC GNU/Linux powerpc-*-linux*
1224 Motorola MCore mcore-*-*
1225 x86 VxWorks i[3456]86-*-vxworks*
1226 PowerPC VxWorks powerpc-*-vxworks*
1227 TI TMS320C80 tic80-*-*
1229 * OBSOLETE configurations
1231 Altos 3068 m68*-altos-*
1232 Convex c1-*-*, c2-*-*
1234 ARM RISCix arm-*-* (as host)
1237 Configurations that have been declared obsolete will be commented out,
1238 but the code will be left in place. If there is no activity to revive
1239 these configurations before the next release of GDB, the sources will
1240 be permanently REMOVED.
1242 * Gould support removed
1244 Support for the Gould PowerNode and NP1 has been removed.
1246 * New features for SVR4
1248 On SVR4 native platforms (such as Solaris), if you attach to a process
1249 without first loading a symbol file, GDB will now attempt to locate and
1250 load symbols from the running process's executable file.
1252 * Many C++ enhancements
1254 C++ support has been greatly improved. Overload resolution now works properly
1255 in almost all cases. RTTI support is on the way.
1257 * Remote targets can connect to a sub-program
1259 A popen(3) style serial-device has been added. This device starts a
1260 sub-process (such as a stand-alone simulator) and then communicates
1261 with that. The sub-program to run is specified using the syntax
1262 ``|<program> <args>'' vis:
1264 (gdb) set remotedebug 1
1265 (gdb) target extended-remote |mn10300-elf-sim program-args
1267 * MIPS 64 remote protocol
1269 A long standing bug in the mips64 remote protocol where by GDB
1270 expected certain 32 bit registers (ex SR) to be transfered as 32
1271 instead of 64 bits has been fixed.
1273 The command ``set remote-mips64-transfers-32bit-regs on'' has been
1274 added to provide backward compatibility with older versions of GDB.
1276 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
1278 The command ``set remotebinarydownload'' command has been replaced by
1279 ``set remote X-packet''. Other commands in ``set remote'' family
1280 include ``set remote P-packet''.
1282 * Breakpoint commands accept ranges.
1284 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
1285 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
1286 ``tracepoint passcount'' also accepts a range of tracepoints.
1288 * ``apropos'' command added.
1290 The ``apropos'' command searches through command names and
1291 documentation strings, printing out matches, making it much easier to
1292 try to find a command that does what you are looking for.
1296 A new machine oriented interface (MI) has been added to GDB. This
1297 interface is designed for debug environments running GDB as a separate
1298 process. This is part of the long term libGDB project. See the
1299 "GDB/MI" chapter of the GDB manual for further information. It can be
1300 enabled by configuring with:
1302 .../configure --enable-gdbmi
1304 *** Changes in GDB-4.18:
1306 * New native configurations
1308 HP-UX 10.20 hppa*-*-hpux10.20
1309 HP-UX 11.x hppa*-*-hpux11.0*
1310 M68K GNU/Linux m68*-*-linux*
1314 Fujitsu FR30 fr30-*-elf*
1315 Intel StrongARM strongarm-*-*
1316 Mitsubishi D30V d30v-*-*
1318 * OBSOLETE configurations
1320 Gould PowerNode, NP1 np1-*-*, pn-*-*
1322 Configurations that have been declared obsolete will be commented out,
1323 but the code will be left in place. If there is no activity to revive
1324 these configurations before the next release of GDB, the sources will
1325 be permanently REMOVED.
1329 As a compatibility experiment, GDB's source files buildsym.h and
1330 buildsym.c have been converted to pure standard C, no longer
1331 containing any K&R compatibility code. We believe that all systems in
1332 use today either come with a standard C compiler, or have a GCC port
1333 available. If this is not true, please report the affected
1334 configuration to bug-gdb@gnu.org immediately. See the README file for
1335 information about getting a standard C compiler if you don't have one
1340 GDB now uses readline 2.2.
1342 * set extension-language
1344 You can now control the mapping between filename extensions and source
1345 languages by using the `set extension-language' command. For instance,
1346 you can ask GDB to treat .c files as C++ by saying
1347 set extension-language .c c++
1348 The command `info extensions' lists all of the recognized extensions
1349 and their associated languages.
1351 * Setting processor type for PowerPC and RS/6000
1353 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
1354 you can use the `set processor' command to specify what variant of the
1355 PowerPC family you are debugging. The command
1359 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
1360 following PowerPC and RS6000 variants:
1362 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
1363 rs6000 IBM RS6000 ("POWER") architecture, user-level view
1365 403GC IBM PowerPC 403GC
1366 505 Motorola PowerPC 505
1367 860 Motorola PowerPC 860 or 850
1368 601 Motorola PowerPC 601
1369 602 Motorola PowerPC 602
1370 603 Motorola/IBM PowerPC 603 or 603e
1371 604 Motorola PowerPC 604 or 604e
1372 750 Motorola/IBM PowerPC 750 or 750
1374 At the moment, this command just tells GDB what to name the
1375 special-purpose processor registers. Since almost all the affected
1376 registers are inaccessible to user-level programs, this command is
1377 only useful for remote debugging in its present form.
1381 Thanks to a major code donation from Hewlett-Packard, GDB now has much
1382 more extensive support for HP-UX. Added features include shared
1383 library support, kernel threads and hardware watchpoints for 11.00,
1384 support for HP's ANSI C and C++ compilers, and a compatibility mode
1385 for xdb and dbx commands.
1389 HP's donation includes the new concept of catchpoints, which is a
1390 generalization of the old catch command. On HP-UX, it is now possible
1391 to catch exec, fork, and vfork, as well as library loading.
1393 This means that the existing catch command has changed; its first
1394 argument now specifies the type of catch to be set up. See the
1395 output of "help catch" for a list of catchpoint types.
1397 * Debugging across forks
1399 On HP-UX, you can choose which process to debug when a fork() happens
1404 HP has donated a curses-based terminal user interface (TUI). To get
1405 it, build with --enable-tui. Although this can be enabled for any
1406 configuration, at present it only works for native HP debugging.
1408 * GDB remote protocol additions
1410 A new protocol packet 'X' that writes binary data is now available.
1411 Default behavior is to try 'X', then drop back to 'M' if the stub
1412 fails to respond. The settable variable `remotebinarydownload'
1413 allows explicit control over the use of 'X'.
1415 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
1416 full 64-bit address. The command
1418 set remoteaddresssize 32
1420 can be used to revert to the old behaviour. For existing remote stubs
1421 the change should not be noticed, as the additional address information
1424 In order to assist in debugging stubs, you may use the maintenance
1425 command `packet' to send any text string to the stub. For instance,
1427 maint packet heythere
1429 sends the packet "$heythere#<checksum>". Note that it is very easy to
1430 disrupt a debugging session by sending the wrong packet at the wrong
1433 The compare-sections command allows you to compare section data on the
1434 target to what is in the executable file without uploading or
1435 downloading, by comparing CRC checksums.
1437 * Tracing can collect general expressions
1439 You may now collect general expressions at tracepoints. This requires
1440 further additions to the target-side stub; see tracepoint.c and
1441 doc/agentexpr.texi for further details.
1443 * mask-address variable for Mips
1445 For Mips targets, you may control the zeroing of the upper 32 bits of
1446 a 64-bit address by entering `set mask-address on'. This is mainly
1447 of interest to users of embedded R4xxx and R5xxx processors.
1449 * Higher serial baud rates
1451 GDB's serial code now allows you to specify baud rates 57600, 115200,
1452 230400, and 460800 baud. (Note that your host system may not be able
1453 to achieve all of these rates.)
1457 The i960 configuration now includes an initial implementation of a
1458 builtin simulator, contributed by Jim Wilson.
1461 *** Changes in GDB-4.17:
1463 * New native configurations
1465 Alpha GNU/Linux alpha*-*-linux*
1466 Unixware 2.x i[3456]86-unixware2*
1467 Irix 6.x mips*-sgi-irix6*
1468 PowerPC GNU/Linux powerpc-*-linux*
1469 PowerPC Solaris powerpcle-*-solaris*
1470 Sparc GNU/Linux sparc-*-linux*
1471 Motorola sysV68 R3V7.1 m68k-motorola-sysv
1475 Argonaut Risc Chip (ARC) arc-*-*
1476 Hitachi H8/300S h8300*-*-*
1477 Matsushita MN10200 w/simulator mn10200-*-*
1478 Matsushita MN10300 w/simulator mn10300-*-*
1479 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
1480 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
1481 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
1482 Mitsubishi D10V w/simulator d10v-*-*
1483 Mitsubishi M32R/D w/simulator m32r-*-elf*
1484 Tsqware Sparclet sparclet-*-*
1485 NEC V850 w/simulator v850-*-*
1487 * New debugging protocols
1489 ARM with RDI protocol arm*-*-*
1490 M68K with dBUG monitor m68*-*-{aout,coff,elf}
1491 DDB and LSI variants of PMON protocol mips*-*-*
1492 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
1493 PowerPC with SDS protocol powerpc{,le}-*-eabi
1494 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
1498 All configurations can now understand and use the DWARF 2 debugging
1499 format. The choice is automatic, if the symbol file contains DWARF 2
1504 GDB now includes basic Java language support. This support is
1505 only useful with Java compilers that produce native machine code.
1507 * solib-absolute-prefix and solib-search-path
1509 For SunOS and SVR4 shared libraries, you may now set the prefix for
1510 loading absolute shared library symbol files, and the search path for
1511 locating non-absolute shared library symbol files.
1513 * Live range splitting
1515 GDB can now effectively debug code for which GCC has performed live
1516 range splitting as part of its optimization. See gdb/doc/LRS for
1517 more details on the expected format of the stabs information.
1521 GDB's support for the GNU Hurd, including thread debugging, has been
1522 updated to work with current versions of the Hurd.
1526 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
1527 instruction set. ARM GDB automatically detects when Thumb
1528 instructions are in use, and adjusts disassembly and backtracing
1533 GDB's MIPS target configurations now handle the MIP16 16-bit
1538 GDB now includes support for overlays; if an executable has been
1539 linked such that multiple sections are based at the same address, GDB
1540 will decide which section to use for symbolic info. You can choose to
1541 control the decision manually, using overlay commands, or implement
1542 additional target-side support and use "overlay load-target" to bring
1543 in the overlay mapping. Do "help overlay" for more detail.
1547 The command "info symbol <address>" displays information about
1548 the symbol at the specified address.
1552 The standard remote protocol now includes an extension that allows
1553 asynchronous collection and display of trace data. This requires
1554 extensive support in the target-side debugging stub. Tracing mode
1555 includes a new interaction mode in GDB and new commands: see the
1556 file tracepoint.c for more details.
1560 Configurations for embedded MIPS now include a simulator contributed
1561 by Cygnus Solutions. The simulator supports the instruction sets
1562 of most MIPS variants.
1566 Sparc configurations may now include the ERC32 simulator contributed
1567 by the European Space Agency. The simulator is not built into
1568 Sparc targets by default; configure with --enable-sim to include it.
1572 For target configurations that may include multiple variants of a
1573 basic architecture (such as MIPS and SH), you may now set the
1574 architecture explicitly. "set arch" sets, "info arch" lists
1575 the possible architectures.
1577 *** Changes in GDB-4.16:
1579 * New native configurations
1581 Windows 95, x86 Windows NT i[345]86-*-cygwin32
1582 M68K NetBSD m68k-*-netbsd*
1583 PowerPC AIX 4.x powerpc-*-aix*
1584 PowerPC MacOS powerpc-*-macos*
1585 PowerPC Windows NT powerpcle-*-cygwin32
1586 RS/6000 AIX 4.x rs6000-*-aix4*
1590 ARM with RDP protocol arm-*-*
1591 I960 with MON960 i960-*-coff
1592 MIPS VxWorks mips*-*-vxworks*
1593 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
1594 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
1596 Matra Sparclet sparclet-*-*
1600 The powerpc-eabi configuration now includes the PSIM simulator,
1601 contributed by Andrew Cagney, with assistance from Mike Meissner.
1602 PSIM is a very elaborate model of the PowerPC, including not only
1603 basic instruction set execution, but also details of execution unit
1604 performance and I/O hardware. See sim/ppc/README for more details.
1608 GDB now works with Solaris 2.5.
1610 * Windows 95/NT native
1612 GDB will now work as a native debugger on Windows 95 and Windows NT.
1613 To build it from source, you must use the "gnu-win32" environment,
1614 which uses a DLL to emulate enough of Unix to run the GNU tools.
1615 Further information, binaries, and sources are available at
1616 ftp.cygnus.com, under pub/gnu-win32.
1618 * dont-repeat command
1620 If a user-defined command includes the command `dont-repeat', then the
1621 command will not be repeated if the user just types return. This is
1622 useful if the command is time-consuming to run, so that accidental
1623 extra keystrokes don't run the same command many times.
1625 * Send break instead of ^C
1627 The standard remote protocol now includes an option to send a break
1628 rather than a ^C to the target in order to interrupt it. By default,
1629 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
1631 * Remote protocol timeout
1633 The standard remote protocol includes a new variable `remotetimeout'
1634 that allows you to set the number of seconds before GDB gives up trying
1635 to read from the target. The default value is 2.
1637 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
1639 By default GDB will automatically keep track of objects as they are
1640 loaded and unloaded by the dynamic linker. By using the command `set
1641 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
1642 when shared library events occur, thus allowing you to set breakpoints
1643 in shared libraries which are explicitly loaded by the inferior.
1645 Note this feature does not work on hpux8. On hpux9 you must link
1646 /usr/lib/end.o into your program. This feature should work
1647 automatically on hpux10.
1649 * Irix 5.x hardware watchpoint support
1651 Irix 5 configurations now support the use of hardware watchpoints.
1653 * Mips protocol "SYN garbage limit"
1655 When debugging a Mips target using the `target mips' protocol, you
1656 may set the number of characters that GDB will ignore by setting
1657 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
1658 every character. The default value is 1050.
1660 * Recording and replaying remote debug sessions
1662 If you set `remotelogfile' to the name of a file, gdb will write to it
1663 a recording of a remote debug session. This recording may then be
1664 replayed back to gdb using "gdbreplay". See gdbserver/README for
1665 details. This is useful when you have a problem with GDB while doing
1666 remote debugging; you can make a recording of the session and send it
1667 to someone else, who can then recreate the problem.
1669 * Speedups for remote debugging
1671 GDB includes speedups for downloading and stepping MIPS systems using
1672 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
1673 and more efficient S-record downloading.
1675 * Memory use reductions and statistics collection
1677 GDB now uses less memory and reports statistics about memory usage.
1678 Try the `maint print statistics' command, for example.
1680 *** Changes in GDB-4.15:
1682 * Psymtabs for XCOFF
1684 The symbol reader for AIX GDB now uses partial symbol tables. This
1685 can greatly improve startup time, especially for large executables.
1687 * Remote targets use caching
1689 Remote targets now use a data cache to speed up communication with the
1690 remote side. The data cache could lead to incorrect results because
1691 it doesn't know about volatile variables, thus making it impossible to
1692 debug targets which use memory mapped I/O devices. `set remotecache
1693 off' turns the the data cache off.
1695 * Remote targets may have threads
1697 The standard remote protocol now includes support for multiple threads
1698 in the target system, using new protocol commands 'H' and 'T'. See
1699 gdb/remote.c for details.
1703 If GDB is configured with `--enable-netrom', then it will include
1704 support for the NetROM ROM emulator from XLNT Designs. The NetROM
1705 acts as though it is a bank of ROM on the target board, but you can
1706 write into it over the network. GDB's support consists only of
1707 support for fast loading into the emulated ROM; to debug, you must use
1708 another protocol, such as standard remote protocol. The usual
1709 sequence is something like
1711 target nrom <netrom-hostname>
1713 target remote <netrom-hostname>:1235
1717 GDB now includes support for the Apple Macintosh, as a host only. It
1718 may be run as either an MPW tool or as a standalone application, and
1719 it can debug through the serial port. All the usual GDB commands are
1720 available, but to the target command, you must supply "serial" as the
1721 device type instead of "/dev/ttyXX". See mpw-README in the main
1722 directory for more information on how to build. The MPW configuration
1723 scripts */mpw-config.in support only a few targets, and only the
1724 mips-idt-ecoff target has been tested.
1728 GDB configuration now uses autoconf. This is not user-visible,
1729 but does simplify configuration and building.
1733 GDB now supports hpux10.
1735 *** Changes in GDB-4.14:
1737 * New native configurations
1739 x86 FreeBSD i[345]86-*-freebsd
1740 x86 NetBSD i[345]86-*-netbsd
1741 NS32k NetBSD ns32k-*-netbsd
1742 Sparc NetBSD sparc-*-netbsd
1746 A29K VxWorks a29k-*-vxworks
1747 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1748 CPU32 EST-300 emulator m68*-*-est*
1749 PowerPC ELF powerpc-*-elf
1752 * Alpha OSF/1 support for procfs
1754 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1755 possible to attach to running processes. As the mounting of the /proc
1756 filesystem is optional on the Alpha, GDB automatically determines
1757 the availability of /proc during startup. This can lead to problems
1758 if /proc is unmounted after GDB has been started.
1760 * Arguments to user-defined commands
1762 User commands may accept up to 10 arguments separated by whitespace.
1763 Arguments are accessed within the user command via $arg0..$arg9. A
1766 print $arg0 + $arg1 + $arg2
1768 To execute the command use:
1771 Defines the command "adder" which prints the sum of its three arguments.
1772 Note the arguments are text substitutions, so they may reference variables,
1773 use complex expressions, or even perform inferior function calls.
1775 * New `if' and `while' commands
1777 This makes it possible to write more sophisticated user-defined
1778 commands. Both commands take a single argument, which is the
1779 expression to evaluate, and must be followed by the commands to
1780 execute, one per line, if the expression is nonzero, the list being
1781 terminated by the word `end'. The `if' command list may include an
1782 `else' word, which causes the following commands to be executed only
1783 if the expression is zero.
1785 * Fortran source language mode
1787 GDB now includes partial support for Fortran 77. It will recognize
1788 Fortran programs and can evaluate a subset of Fortran expressions, but
1789 variables and functions may not be handled correctly. GDB will work
1790 with G77, but does not yet know much about symbols emitted by other
1793 * Better HPUX support
1795 Most debugging facilities now work on dynamic executables for HPPAs
1796 running hpux9 or later. You can attach to running dynamically linked
1797 processes, but by default the dynamic libraries will be read-only, so
1798 for instance you won't be able to put breakpoints in them. To change
1799 that behavior do the following before running the program:
1805 This will cause the libraries to be mapped private and read-write.
1806 To revert to the normal behavior, do this:
1812 You cannot set breakpoints or examine data in the library until after
1813 the library is loaded if the function/data symbols do not have
1816 GDB can now also read debug symbols produced by the HP C compiler on
1817 HPPAs (sorry, no C++, Fortran or 68k support).
1819 * Target byte order now dynamically selectable
1821 You can choose which byte order to use with a target system, via the
1822 commands "set endian big" and "set endian little", and you can see the
1823 current setting by using "show endian". You can also give the command
1824 "set endian auto", in which case GDB will use the byte order
1825 associated with the executable. Currently, only embedded MIPS
1826 configurations support dynamic selection of target byte order.
1828 * New DOS host serial code
1830 This version uses DPMI interrupts to handle buffered I/O, so you
1831 no longer need to run asynctsr when debugging boards connected to
1834 *** Changes in GDB-4.13:
1836 * New "complete" command
1838 This lists all the possible completions for the rest of the line, if it
1839 were to be given as a command itself. This is intended for use by emacs.
1841 * Trailing space optional in prompt
1843 "set prompt" no longer adds a space for you after the prompt you set. This
1844 allows you to set a prompt which ends in a space or one that does not.
1846 * Breakpoint hit counts
1848 "info break" now displays a count of the number of times the breakpoint
1849 has been hit. This is especially useful in conjunction with "ignore"; you
1850 can ignore a large number of breakpoint hits, look at the breakpoint info
1851 to see how many times the breakpoint was hit, then run again, ignoring one
1852 less than that number, and this will get you quickly to the last hit of
1855 * Ability to stop printing at NULL character
1857 "set print null-stop" will cause GDB to stop printing the characters of
1858 an array when the first NULL is encountered. This is useful when large
1859 arrays actually contain only short strings.
1861 * Shared library breakpoints
1863 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1864 breakpoints in shared libraries before the executable is run.
1866 * Hardware watchpoints
1868 There is a new hardware breakpoint for the watch command for sparclite
1869 targets. See gdb/sparclite/hw_breakpoint.note.
1871 Hardware watchpoints are also now supported under GNU/Linux.
1875 Annotations have been added. These are for use with graphical interfaces,
1876 and are still experimental. Currently only gdba.el uses these.
1878 * Improved Irix 5 support
1880 GDB now works properly with Irix 5.2.
1882 * Improved HPPA support
1884 GDB now works properly with the latest GCC and GAS.
1886 * New native configurations
1888 Sequent PTX4 i[34]86-sequent-ptx4
1889 HPPA running OSF/1 hppa*-*-osf*
1890 Atari TT running SVR4 m68*-*-sysv4*
1891 RS/6000 LynxOS rs6000-*-lynxos*
1895 OS/9000 i[34]86-*-os9k
1896 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1899 * Hitachi SH7000 and E7000-PC ICE support
1901 There is now support for communicating with the Hitachi E7000-PC ICE.
1902 This is available automatically when GDB is configured for the SH.
1906 As usual, a variety of small fixes and improvements, both generic
1907 and configuration-specific. See the ChangeLog for more detail.
1909 *** Changes in GDB-4.12:
1911 * Irix 5 is now supported
1915 GDB-4.12 on the HPPA has a number of changes which make it unable
1916 to debug the output from the currently released versions of GCC and
1917 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1918 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1919 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1922 *** Changes in GDB-4.11:
1924 * User visible changes:
1928 The "set remotedebug" option is now consistent between the mips remote
1929 target, remote targets using the gdb-specific protocol, UDI (AMD's
1930 debug protocol for the 29k) and the 88k bug monitor. It is now an
1931 integer specifying a debug level (normally 0 or 1, but 2 means more
1932 debugging info for the mips target).
1934 * DEC Alpha native support
1936 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1937 debug info, but GDB works fairly well with the DEC compiler and should
1938 work with a future GCC release. See the README file for a few
1939 Alpha-specific notes.
1941 * Preliminary thread implementation
1943 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1945 * LynxOS native and target support for 386
1947 This release has been hosted on LynxOS 2.2, and also can be configured
1948 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1951 * Improvements in C++ mangling/demangling.
1953 This release has much better g++ debugging, specifically in name
1954 mangling/demangling, virtual function calls, print virtual table,
1955 call methods, ...etc.
1957 *** Changes in GDB-4.10:
1959 * User visible changes:
1961 Remote debugging using the GDB-specific (`target remote') protocol now
1962 supports the `load' command. This is only useful if you have some
1963 other way of getting the stub to the target system, and you can put it
1964 somewhere in memory where it won't get clobbered by the download.
1966 Filename completion now works.
1968 When run under emacs mode, the "info line" command now causes the
1969 arrow to point to the line specified. Also, "info line" prints
1970 addresses in symbolic form (as well as hex).
1972 All vxworks based targets now support a user settable option, called
1973 vxworks-timeout. This option represents the number of seconds gdb
1974 should wait for responses to rpc's. You might want to use this if
1975 your vxworks target is, perhaps, a slow software simulator or happens
1976 to be on the far side of a thin network line.
1980 This release contains support for using a DEC alpha as a GDB host for
1981 cross debugging. Native alpha debugging is not supported yet.
1984 *** Changes in GDB-4.9:
1988 This is the first GDB release which is accompanied by a matching testsuite.
1989 The testsuite requires installation of dejagnu, which should be available
1990 via ftp from most sites that carry GNU software.
1994 'Cfront' style demangling has had its name changed to 'ARM' style, to
1995 emphasize that it was written from the specifications in the C++ Annotated
1996 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1997 disclaimers, it still generated too much confusion with users attempting to
1998 use gdb with AT&T cfront.
2002 GDB now uses a standard remote interface to a simulator library.
2003 So far, the library contains simulators for the Zilog Z8001/2, the
2004 Hitachi H8/300, H8/500 and Super-H.
2006 * New targets supported
2008 H8/300 simulator h8300-hitachi-hms or h8300hms
2009 H8/500 simulator h8500-hitachi-hms or h8500hms
2010 SH simulator sh-hitachi-hms or sh
2011 Z8000 simulator z8k-zilog-none or z8ksim
2012 IDT MIPS board over serial line mips-idt-ecoff
2014 Cross-debugging to GO32 targets is supported. It requires a custom
2015 version of the i386-stub.c module which is integrated with the
2016 GO32 memory extender.
2018 * New remote protocols
2020 MIPS remote debugging protocol.
2022 * New source languages supported
2024 This version includes preliminary support for Chill, a Pascal like language
2025 used by telecommunications companies. Chill support is also being integrated
2026 into the GNU compiler, but we don't know when it will be publically available.
2029 *** Changes in GDB-4.8:
2031 * HP Precision Architecture supported
2033 GDB now supports HP PA-RISC machines running HPUX. A preliminary
2034 version of this support was available as a set of patches from the
2035 University of Utah. GDB does not support debugging of programs
2036 compiled with the HP compiler, because HP will not document their file
2037 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
2038 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
2040 Many problems in the preliminary version have been fixed.
2042 * Faster and better demangling
2044 We have improved template demangling and fixed numerous bugs in the GNU style
2045 demangler. It can now handle type modifiers such as `static' or `const'. Wide
2046 character types (wchar_t) are now supported. Demangling of each symbol is now
2047 only done once, and is cached when the symbol table for a file is read in.
2048 This results in a small increase in memory usage for C programs, a moderate
2049 increase in memory usage for C++ programs, and a fantastic speedup in
2052 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
2053 from the specifications in the Annotated Reference Manual, which AT&T's
2054 compiler does not actually implement.
2056 * G++ multiple inheritance compiler problem
2058 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
2059 inheritance lattices was reworked to properly discover ambiguities. We
2060 recently found an example which causes this new algorithm to fail in a
2061 very subtle way, producing bad debug information for those classes.
2062 The file 'gcc.patch' (in this directory) can be applied to gcc to
2063 circumvent the problem. A future GCC release will contain a complete
2066 The previous G++ debug info problem (mentioned below for the gdb-4.7
2067 release) is fixed in gcc version 2.3.2.
2069 * Improved configure script
2071 The `configure' script will now attempt to guess your system type if
2072 you don't supply a host system type. The old scheme of supplying a
2073 host system triplet is preferable over using this. All the magic is
2074 done in the new `config.guess' script. Examine it for details.
2076 We have also brought our configure script much more in line with the FSF's
2077 version. It now supports the --with-xxx options. In particular,
2078 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
2079 The resulting GDB will not be able to read arbitrary object file formats --
2080 only the format ``expected'' to be used on the configured target system.
2081 We hope to make this the default in a future release.
2083 * Documentation improvements
2085 There's new internal documentation on how to modify GDB, and how to
2086 produce clean changes to the code. We implore people to read it
2087 before submitting changes.
2089 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
2090 M4 macros. The new texinfo.tex is provided in this release. Pre-built
2091 `info' files are also provided. To build `info' files from scratch,
2092 you will need the latest `makeinfo' release, which will be available in
2093 a future texinfo-X.Y release.
2095 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
2096 We're not sure exactly which versions have this problem, but it has
2097 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
2098 or better. If that isn't possible, there is a patch in
2099 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
2100 around this problem.
2104 GDB now supports array constants that can be used in expressions typed in by
2105 the user. The syntax is `{element, element, ...}'. Ie: you can now type
2106 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
2109 The new directory `gdb/sparclite' contains a program that demonstrates
2110 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
2112 * New native hosts supported
2114 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
2115 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
2117 * New targets supported
2119 AMD 29k family via UDI a29k-amd-udi or udi29k
2121 * New file formats supported
2123 BFD now supports reading HP/PA-RISC executables (SOM file format?),
2124 HPUX core files, and SCO 3.2v2 core files.
2128 Attaching to processes now works again; thanks for the many bug reports.
2130 We have also stomped on a bunch of core dumps caused by
2131 printf_filtered("%s") problems.
2133 We eliminated a copyright problem on the rpc and ptrace header files
2134 for VxWorks, which was discovered at the last minute during the 4.7
2135 release. You should now be able to build a VxWorks GDB.
2137 You can now interrupt gdb while an attached process is running. This
2138 will cause the attached process to stop, and give control back to GDB.
2140 We fixed problems caused by using too many file descriptors
2141 for reading symbols from object files and libraries. This was
2142 especially a problem for programs that used many (~100) shared
2145 The `step' command now only enters a subroutine if there is line number
2146 information for the subroutine. Otherwise it acts like the `next'
2147 command. Previously, `step' would enter subroutines if there was
2148 any debugging information about the routine. This avoids problems
2149 when using `cc -g1' on MIPS machines.
2151 * Internal improvements
2153 GDB's internal interfaces have been improved to make it easier to support
2154 debugging of multiple languages in the future.
2156 GDB now uses a common structure for symbol information internally.
2157 Minimal symbols (derived from linkage symbols in object files), partial
2158 symbols (from a quick scan of debug information), and full symbols
2159 contain a common subset of information, making it easier to write
2160 shared code that handles any of them.
2162 * New command line options
2164 We now accept --silent as an alias for --quiet.
2168 The memory-mapped-malloc library is now licensed under the GNU Library
2169 General Public License.
2171 *** Changes in GDB-4.7:
2173 * Host/native/target split
2175 GDB has had some major internal surgery to untangle the support for
2176 hosts and remote targets. Now, when you configure GDB for a remote
2177 target, it will no longer load in all of the support for debugging
2178 local programs on the host. When fully completed and tested, this will
2179 ensure that arbitrary host/target combinations are possible.
2181 The primary conceptual shift is to separate the non-portable code in
2182 GDB into three categories. Host specific code is required any time GDB
2183 is compiled on that host, regardless of the target. Target specific
2184 code relates to the peculiarities of the target, but can be compiled on
2185 any host. Native specific code is everything else: it can only be
2186 built when the host and target are the same system. Child process
2187 handling and core file support are two common `native' examples.
2189 GDB's use of /proc for controlling Unix child processes is now cleaner.
2190 It has been split out into a single module under the `target_ops' vector,
2191 plus two native-dependent functions for each system that uses /proc.
2193 * New hosts supported
2195 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
2196 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2197 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
2199 * New targets supported
2201 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
2202 68030 and CPU32 m68030-*-*, m68332-*-*
2204 * New native hosts supported
2206 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2207 (386bsd is not well tested yet)
2208 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
2210 * New file formats supported
2212 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
2213 supports reading of `a.out.adobe' object files, which are an a.out
2214 format extended with minimal information about multiple sections.
2218 `show copying' is the same as the old `info copying'.
2219 `show warranty' is the same as `info warrantee'.
2220 These were renamed for consistency. The old commands continue to work.
2222 `info handle' is a new alias for `info signals'.
2224 You can now define pre-command hooks, which attach arbitrary command
2225 scripts to any command. The commands in the hook will be executed
2226 prior to the user's command. You can also create a hook which will be
2227 executed whenever the program stops. See gdb.texinfo.
2231 We now deal with Cfront style name mangling, and can even extract type
2232 info from mangled symbols. GDB can automatically figure out which
2233 symbol mangling style your C++ compiler uses.
2235 Calling of methods and virtual functions has been improved as well.
2239 The crash that occured when debugging Sun Ansi-C compiled binaries is
2240 fixed. This was due to mishandling of the extra N_SO stabs output
2243 We also finally got Ultrix 4.2 running in house, and fixed core file
2244 support, with help from a dozen people on the net.
2246 John M. Farrell discovered that the reason that single-stepping was so
2247 slow on all of the Mips based platforms (primarily SGI and DEC) was
2248 that we were trying to demangle and lookup a symbol used for internal
2249 purposes on every instruction that was being stepped through. Changing
2250 the name of that symbol so that it couldn't be mistaken for a C++
2251 mangled symbol sped things up a great deal.
2253 Rich Pixley sped up symbol lookups in general by getting much smarter
2254 about when C++ symbol mangling is necessary. This should make symbol
2255 completion (TAB on the command line) much faster. It's not as fast as
2256 we'd like, but it's significantly faster than gdb-4.6.
2260 A new user controllable variable 'call_scratch_address' can
2261 specify the location of a scratch area to be used when GDB
2262 calls a function in the target. This is necessary because the
2263 usual method of putting the scratch area on the stack does not work
2264 in systems that have separate instruction and data spaces.
2266 We integrated changes to support the 29k UDI (Universal Debugger
2267 Interface), but discovered at the last minute that we didn't have all
2268 of the appropriate copyright paperwork. We are working with AMD to
2269 resolve this, and hope to have it available soon.
2273 We have sped up the remote serial line protocol, especially for targets
2274 with lots of registers. It now supports a new `expedited status' ('T')
2275 message which can be used in place of the existing 'S' status message.
2276 This allows the remote stub to send only the registers that GDB
2277 needs to make a quick decision about single-stepping or conditional
2278 breakpoints, eliminating the need to fetch the entire register set for
2279 each instruction being stepped through.
2281 The GDB remote serial protocol now implements a write-through cache for
2282 registers, only re-reading the registers if the target has run.
2284 There is also a new remote serial stub for SPARC processors. You can
2285 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
2286 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
2287 processor with a serial port.
2291 Configure.in files have become much easier to read and modify. A new
2292 `table driven' format makes it more obvious what configurations are
2293 supported, and what files each one uses.
2297 There is a new opcodes library which will eventually contain all of the
2298 disassembly routines and opcode tables. At present, it only contains
2299 Sparc and Z8000 routines. This will allow the assembler, debugger, and
2300 disassembler (binutils/objdump) to share these routines.
2302 The libiberty library is now copylefted under the GNU Library General
2303 Public License. This allows more liberal use, and was done so libg++
2304 can use it. This makes no difference to GDB, since the Library License
2305 grants all the rights from the General Public License.
2309 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
2310 reference to the stabs symbol info used by the debugger. It is (as far
2311 as we know) the only published document on this fascinating topic. We
2312 encourage you to read it, compare it to the stabs information on your
2313 system, and send improvements on the document in general (to
2314 bug-gdb@prep.ai.mit.edu).
2316 And, of course, many bugs have been fixed.
2319 *** Changes in GDB-4.6:
2321 * Better support for C++ function names
2323 GDB now accepts as input the "demangled form" of C++ overloaded function
2324 names and member function names, and can do command completion on such names
2325 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
2326 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
2327 Make use of command completion, it is your friend.
2329 GDB also now accepts a variety of C++ mangled symbol formats. They are
2330 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
2331 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
2332 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
2333 for the list of formats.
2335 * G++ symbol mangling problem
2337 Recent versions of gcc have a bug in how they emit debugging information for
2338 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
2339 directory) can be applied to gcc to fix the problem. Alternatively, if you
2340 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
2341 usual symptom is difficulty with setting breakpoints on methods. GDB complains
2342 about the method being non-existent. (We believe that version 2.2.2 of GCC has
2345 * New 'maintenance' command
2347 All of the commands related to hacking GDB internals have been moved out of
2348 the main command set, and now live behind the 'maintenance' command. This
2349 can also be abbreviated as 'mt'. The following changes were made:
2351 dump-me -> maintenance dump-me
2352 info all-breakpoints -> maintenance info breakpoints
2353 printmsyms -> maintenance print msyms
2354 printobjfiles -> maintenance print objfiles
2355 printpsyms -> maintenance print psymbols
2356 printsyms -> maintenance print symbols
2358 The following commands are new:
2360 maintenance demangle Call internal GDB demangler routine to
2361 demangle a C++ link name and prints the result.
2362 maintenance print type Print a type chain for a given symbol
2364 * Change to .gdbinit file processing
2366 We now read the $HOME/.gdbinit file before processing the argv arguments
2367 (e.g. reading symbol files or core files). This allows global parameters to
2368 be set, which will apply during the symbol reading. The ./.gdbinit is still
2369 read after argv processing.
2371 * New hosts supported
2373 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
2375 GNU/Linux support i386-unknown-linux or linux
2377 We are also including code to support the HP/PA running BSD and HPUX. This
2378 is almost guaranteed not to work, as we didn't have time to test or build it
2379 for this release. We are including it so that the more adventurous (or
2380 masochistic) of you can play with it. We also had major problems with the
2381 fact that the compiler that we got from HP doesn't support the -g option.
2384 * New targets supported
2386 Hitachi H8/300 h8300-hitachi-hms or h8300hms
2388 * More smarts about finding #include files
2390 GDB now remembers the compilation directory for all include files, and for
2391 all files from which C is generated (like yacc and lex sources). This
2392 greatly improves GDB's ability to find yacc/lex sources, and include files,
2393 especially if you are debugging your program from a directory different from
2394 the one that contains your sources.
2396 We also fixed a bug which caused difficulty with listing and setting
2397 breakpoints in include files which contain C code. (In the past, you had to
2398 try twice in order to list an include file that you hadn't looked at before.)
2400 * Interesting infernals change
2402 GDB now deals with arbitrary numbers of sections, where the symbols for each
2403 section must be relocated relative to that section's landing place in the
2404 target's address space. This work was needed to support ELF with embedded
2405 stabs used by Solaris-2.0.
2407 * Bug fixes (of course!)
2409 There have been loads of fixes for the following things:
2410 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
2411 i960, stabs, DOS(GO32), procfs, etc...
2413 See the ChangeLog for details.
2415 *** Changes in GDB-4.5:
2417 * New machines supported (host and target)
2419 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
2421 SGI Irix-4.x mips-sgi-irix4 or iris4
2423 * New malloc package
2425 GDB now uses a new memory manager called mmalloc, based on gmalloc.
2426 Mmalloc is capable of handling mutiple heaps of memory. It is also
2427 capable of saving a heap to a file, and then mapping it back in later.
2428 This can be used to greatly speedup the startup of GDB by using a
2429 pre-parsed symbol table which lives in a mmalloc managed heap. For
2430 more details, please read mmalloc/mmalloc.texi.
2434 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
2435 'help info proc' for details.
2437 * MIPS ecoff symbol table format
2439 The code that reads MIPS symbol table format is now supported on all hosts.
2440 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
2443 * File name changes for MS-DOS
2445 Many files in the config directories have been renamed to make it easier to
2446 support GDB on MS-DOSe systems (which have very restrictive file name
2447 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
2448 environment) is close to working but has some remaining problems. Note
2449 that debugging of DOS programs is not supported, due to limitations
2450 in the ``operating system'', but it can be used to host cross-debugging.
2452 * Cross byte order fixes
2454 Many fixes have been made to support cross debugging of Sparc and MIPS
2455 targets from hosts whose byte order differs.
2457 * New -mapped and -readnow options
2459 If memory-mapped files are available on your system through the 'mmap'
2460 system call, you can use the -mapped option on the `file' or
2461 `symbol-file' commands to cause GDB to write the symbols from your
2462 program into a reusable file. If the program you are debugging is
2463 called `/path/fred', the mapped symbol file will be `./fred.syms'.
2464 Future GDB debugging sessions will notice the presence of this file,
2465 and will quickly map in symbol information from it, rather than reading
2466 the symbol table from the executable program. Using the '-mapped'
2467 option in a GDB `file' or `symbol-file' command has the same effect as
2468 starting GDB with the '-mapped' command-line option.
2470 You can cause GDB to read the entire symbol table immediately by using
2471 the '-readnow' option with any of the commands that load symbol table
2472 information (or on the GDB command line). This makes the command
2473 slower, but makes future operations faster.
2475 The -mapped and -readnow options are typically combined in order to
2476 build a `fred.syms' file that contains complete symbol information.
2477 A simple GDB invocation to do nothing but build a `.syms' file for future
2480 gdb -batch -nx -mapped -readnow programname
2482 The `.syms' file is specific to the host machine on which GDB is run.
2483 It holds an exact image of GDB's internal symbol table. It cannot be
2484 shared across multiple host platforms.
2486 * longjmp() handling
2488 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
2489 siglongjmp() without losing control. This feature has not yet been ported to
2490 all systems. It currently works on many 386 platforms, all MIPS-based
2491 platforms (SGI, DECstation, etc), and Sun3/4.
2495 Preliminary work has been put in to support the new Solaris OS from Sun. At
2496 this time, it can control and debug processes, but it is not capable of
2501 As always, many many bug fixes. The major areas were with g++, and mipsread.
2502 People using the MIPS-based platforms should experience fewer mysterious
2503 crashes and trashed symbol tables.
2505 *** Changes in GDB-4.4:
2507 * New machines supported (host and target)
2509 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2511 BSD Reno on Vax vax-dec-bsd
2512 Ultrix on Vax vax-dec-ultrix
2514 * New machines supported (target)
2516 AMD 29000 embedded, using EBMON a29k-none-none
2520 GDB continues to improve its handling of C++. `References' work better.
2521 The demangler has also been improved, and now deals with symbols mangled as
2522 per the Annotated C++ Reference Guide.
2524 GDB also now handles `stabs' symbol information embedded in MIPS
2525 `ecoff' symbol tables. Since the ecoff format was not easily
2526 extensible to handle new languages such as C++, this appeared to be a
2527 good way to put C++ debugging info into MIPS binaries. This option
2528 will be supported in the GNU C compiler, version 2, when it is
2531 * New features for SVR4
2533 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
2534 shared libraries. Debugging dynamically linked programs should present
2535 only minor differences from debugging statically linked programs.
2537 The `info proc' command will print out information about any process
2538 on an SVR4 system (including the one you are debugging). At the moment,
2539 it prints the address mappings of the process.
2541 If you bring up GDB on another SVR4 system, please send mail to
2542 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
2544 * Better dynamic linking support in SunOS
2546 Reading symbols from shared libraries which contain debugging symbols
2547 now works properly. However, there remain issues such as automatic
2548 skipping of `transfer vector' code during function calls, which
2549 make it harder to debug code in a shared library, than to debug the
2550 same code linked statically.
2554 GDB is now using the latest `getopt' routines from the FSF. This
2555 version accepts the -- prefix for options with long names. GDB will
2556 continue to accept the old forms (-option and +option) as well.
2557 Various single letter abbreviations for options have been explicity
2558 added to the option table so that they won't get overshadowed in the
2559 future by other options that begin with the same letter.
2563 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
2564 Many assorted bugs have been handled. Many more remain to be handled.
2565 See the various ChangeLog files (primarily in gdb and bfd) for details.
2568 *** Changes in GDB-4.3:
2570 * New machines supported (host and target)
2572 Amiga 3000 running Amix m68k-cbm-svr4 or amix
2573 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
2574 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
2576 * Almost SCO Unix support
2578 We had hoped to support:
2579 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2580 (except for core file support), but we discovered very late in the release
2581 that it has problems with process groups that render gdb unusable. Sorry
2582 about that. I encourage people to fix it and post the fixes.
2584 * Preliminary ELF and DWARF support
2586 GDB can read ELF object files on System V Release 4, and can handle
2587 debugging records for C, in DWARF format, in ELF files. This support
2588 is preliminary. If you bring up GDB on another SVR4 system, please
2589 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
2594 GDB now uses the latest `readline' library. One user-visible change
2595 is that two tabs will list possible command completions, which previously
2596 required typing M-? (meta-question mark, or ESC ?).
2600 The `stepi' bug that many of you noticed has been squashed.
2601 Many bugs in C++ have been handled. Many more remain to be handled.
2602 See the various ChangeLog files (primarily in gdb and bfd) for details.
2604 * State of the MIPS world (in case you wondered):
2606 GDB can understand the symbol tables emitted by the compilers
2607 supplied by most vendors of MIPS-based machines, including DEC. These
2608 symbol tables are in a format that essentially nobody else uses.
2610 Some versions of gcc come with an assembler post-processor called
2611 mips-tfile. This program is required if you want to do source-level
2612 debugging of gcc-compiled programs. I believe FSF does not ship
2613 mips-tfile with gcc version 1, but it will eventually come with gcc
2616 Debugging of g++ output remains a problem. g++ version 1.xx does not
2617 really support it at all. (If you're lucky, you should be able to get
2618 line numbers and stack traces to work, but no parameters or local
2619 variables.) With some work it should be possible to improve the
2622 When gcc version 2 is released, you will have somewhat better luck.
2623 However, even then you will get confusing results for inheritance and
2626 We will eventually provide full debugging of g++ output on
2627 DECstations. This will probably involve some kind of stabs-in-ecoff
2628 encapulation, but the details have not been worked out yet.
2631 *** Changes in GDB-4.2:
2633 * Improved configuration
2635 Only one copy of `configure' exists now, and it is not self-modifying.
2636 Porting BFD is simpler.
2640 The `step' and `next' commands now only stop at the first instruction
2641 of a source line. This prevents the multiple stops that used to occur
2642 in switch statements, for-loops, etc. `Step' continues to stop if a
2643 function that has debugging information is called within the line.
2647 Lots of small bugs fixed. More remain.
2649 * New host supported (not target)
2651 Intel 386 PC clone running Mach i386-none-mach
2654 *** Changes in GDB-4.1:
2656 * Multiple source language support
2658 GDB now has internal scaffolding to handle several source languages.
2659 It determines the type of each source file from its filename extension,
2660 and will switch expression parsing and number formatting to match the
2661 language of the function in the currently selected stack frame.
2662 You can also specifically set the language to be used, with
2663 `set language c' or `set language modula-2'.
2667 GDB now has preliminary support for the GNU Modula-2 compiler,
2668 currently under development at the State University of New York at
2669 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
2670 continue through the fall of 1991 and into 1992.
2672 Other Modula-2 compilers are currently not supported, and attempting to
2673 debug programs compiled with them will likely result in an error as the
2674 symbol table is read. Feel free to work on it, though!
2676 There are hooks in GDB for strict type checking and range checking,
2677 in the `Modula-2 philosophy', but they do not currently work.
2681 GDB can now write to executable and core files (e.g. patch
2682 a variable's value). You must turn this switch on, specify
2683 the file ("exec foo" or "core foo"), *then* modify it, e.g.
2684 by assigning a new value to a variable. Modifications take
2687 * Automatic SunOS shared library reading
2689 When you run your program, GDB automatically determines where its
2690 shared libraries (if any) have been loaded, and reads their symbols.
2691 The `share' command is no longer needed. This also works when
2692 examining core files.
2696 You can specify the number of lines that the `list' command shows.
2699 * New machines supported (host and target)
2701 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
2702 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
2703 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
2705 * New hosts supported (not targets)
2707 IBM RT/PC: romp-ibm-aix or rtpc
2709 * New targets supported (not hosts)
2711 AMD 29000 embedded with COFF a29k-none-coff
2712 AMD 29000 embedded with a.out a29k-none-aout
2713 Ultracomputer remote kernel debug a29k-nyu-kern
2715 * New remote interfaces
2721 *** Changes in GDB-4.0:
2725 Wide output is wrapped at good places to make the output more readable.
2727 Gdb now supports cross-debugging from a host machine of one type to a
2728 target machine of another type. Communication with the target system
2729 is over serial lines. The ``target'' command handles connecting to the
2730 remote system; the ``load'' command will download a program into the
2731 remote system. Serial stubs for the m68k and i386 are provided. Gdb
2732 also supports debugging of realtime processes running under VxWorks,
2733 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
2734 stub on the target system.
2736 New CPUs supported include the AMD 29000 and Intel 960.
2738 GDB now reads object files and symbol tables via a ``binary file''
2739 library, which allows a single copy of GDB to debug programs of multiple
2740 object file types such as a.out and coff.
2742 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2743 refcard.dvi and refcard.ps are available to format it).
2746 * Control-Variable user interface simplified
2748 All variables that control the operation of the debugger can be set
2749 by the ``set'' command, and displayed by the ``show'' command.
2751 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2752 ``Show prompt'' produces the response:
2753 Gdb's prompt is new-gdb=>.
2755 What follows are the NEW set commands. The command ``help set'' will
2756 print a complete list of old and new set commands. ``help set FOO''
2757 will give a longer description of the variable FOO. ``show'' will show
2758 all of the variable descriptions and their current settings.
2760 confirm on/off: Enables warning questions for operations that are
2761 hard to recover from, e.g. rerunning the program while
2762 it is already running. Default is ON.
2764 editing on/off: Enables EMACS style command line editing
2765 of input. Previous lines can be recalled with
2766 control-P, the current line can be edited with control-B,
2767 you can search for commands with control-R, etc.
2770 history filename NAME: NAME is where the gdb command history
2771 will be stored. The default is .gdb_history,
2772 or the value of the environment variable
2775 history size N: The size, in commands, of the command history. The
2776 default is 256, or the value of the environment variable
2779 history save on/off: If this value is set to ON, the history file will
2780 be saved after exiting gdb. If set to OFF, the
2781 file will not be saved. The default is OFF.
2783 history expansion on/off: If this value is set to ON, then csh-like
2784 history expansion will be performed on
2785 command line input. The default is OFF.
2787 radix N: Sets the default radix for input and output. It can be set
2788 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2789 in the current radix, so "set radix 10" is always a no-op.
2791 height N: This integer value is the number of lines on a page. Default
2792 is 24, the current `stty rows'' setting, or the ``li#''
2793 setting from the termcap entry matching the environment
2796 width N: This integer value is the number of characters on a line.
2797 Default is 80, the current `stty cols'' setting, or the ``co#''
2798 setting from the termcap entry matching the environment
2801 Note: ``set screensize'' is obsolete. Use ``set height'' and
2802 ``set width'' instead.
2804 print address on/off: Print memory addresses in various command displays,
2805 such as stack traces and structure values. Gdb looks
2806 more ``symbolic'' if you turn this off; it looks more
2807 ``machine level'' with it on. Default is ON.
2809 print array on/off: Prettyprint arrays. New convenient format! Default
2812 print demangle on/off: Print C++ symbols in "source" form if on,
2815 print asm-demangle on/off: Same, for assembler level printouts
2818 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2821 * Support for Epoch Environment.
2823 The epoch environment is a version of Emacs v18 with windowing. One
2824 new command, ``inspect'', is identical to ``print'', except that if you
2825 are running in the epoch environment, the value is printed in its own
2829 * Support for Shared Libraries
2831 GDB can now debug programs and core files that use SunOS shared libraries.
2832 Symbols from a shared library cannot be referenced
2833 before the shared library has been linked with the program (this
2834 happens after you type ``run'' and before the function main() is entered).
2835 At any time after this linking (including when examining core files
2836 from dynamically linked programs), gdb reads the symbols from each
2837 shared library when you type the ``sharedlibrary'' command.
2838 It can be abbreviated ``share''.
2840 sharedlibrary REGEXP: Load shared object library symbols for files
2841 matching a unix regular expression. No argument
2842 indicates to load symbols for all shared libraries.
2844 info sharedlibrary: Status of loaded shared libraries.
2849 A watchpoint stops execution of a program whenever the value of an
2850 expression changes. Checking for this slows down execution
2851 tremendously whenever you are in the scope of the expression, but is
2852 quite useful for catching tough ``bit-spreader'' or pointer misuse
2853 problems. Some machines such as the 386 have hardware for doing this
2854 more quickly, and future versions of gdb will use this hardware.
2856 watch EXP: Set a watchpoint (breakpoint) for an expression.
2858 info watchpoints: Information about your watchpoints.
2860 delete N: Deletes watchpoint number N (same as breakpoints).
2861 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2862 enable N: Re-enables watchpoint number N (same as breakpoints).
2865 * C++ multiple inheritance
2867 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2870 * C++ exception handling
2872 Gdb now supports limited C++ exception handling. Besides the existing
2873 ability to breakpoint on an exception handler, gdb can breakpoint on
2874 the raising of an exception (before the stack is peeled back to the
2877 catch FOO: If there is a FOO exception handler in the dynamic scope,
2878 set a breakpoint to catch exceptions which may be raised there.
2879 Multiple exceptions (``catch foo bar baz'') may be caught.
2881 info catch: Lists all exceptions which may be caught in the
2882 current stack frame.
2885 * Minor command changes
2887 The command ``call func (arg, arg, ...)'' now acts like the print
2888 command, except it does not print or save a value if the function's result
2889 is void. This is similar to dbx usage.
2891 The ``up'' and ``down'' commands now always print the frame they end up
2892 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2893 frames without printing.
2895 * New directory command
2897 'dir' now adds directories to the FRONT of the source search path.
2898 The path starts off empty. Source files that contain debug information
2899 about the directory in which they were compiled can be found even
2900 with an empty path; Sun CC and GCC include this information. If GDB can't
2901 find your source file in the current directory, type "dir .".
2903 * Configuring GDB for compilation
2905 For normal use, type ``./configure host''. See README or gdb.texinfo
2908 GDB now handles cross debugging. If you are remotely debugging between
2909 two different machines, type ``./configure host -target=targ''.
2910 Host is the machine where GDB will run; targ is the machine
2911 where the program that you are debugging will run.
projects / deliverable / binutils-gdb.git / blob