1 What has changed in GDB?
2 (Organized release by release)
4 *** Changes since GDB 6.6
8 Cell Broadband Engine SPU spu-elf
10 * The GDB remote stub, gdbserver, now has lower overhead for high
11 frequency signals (e.g. SIGALRM) via the QPassSignals packet.
16 Ignore the specified signals; pass them directly to the debugged program
17 without stopping other threads or reporting them to GDB.
20 *** Changes in GDB 6.6
26 * GDB can now be configured as a cross-debugger targeting native Windows
27 (mingw32) or Cygwin. It can communicate with a remote debugging stub
28 running on a Windows system over TCP/IP to debug Windows programs.
30 * The GDB remote stub, gdbserver, has been updated to support Windows and
31 Cygwin debugging. Both single-threaded and multi-threaded programs are
34 * The "set trust-readonly-sections" command works again. This command was
35 broken in GDB 6.3, 6.4, and 6.5.
37 * Support for GNU/Linux Thread Local Storage (TLS, per-thread variables) no
38 longer requires symbolic debug information (e.g. DWARF-2).
45 Manage a list of substitution rules that GDB uses to rewrite the name
46 of the directories where the sources are located. This can be useful
47 for instance when the sources were moved to a different location
48 between compilation and debugging.
52 Print each CLI command as it is executed. Each command is prefixed with
53 a number of `+' symbols representing the nesting depth.
54 The source command now has a `-v' option to enable the same feature.
58 The ARM Demon monitor support (RDP protocol, "target rdp").
60 Kernel Object Display, an embedded debugging feature which only worked with
61 an obsolete version of Cisco IOS.
63 The 'set download-write-size' and 'show download-write-size' commands.
68 Tell a stub about GDB client features, and request remote target features.
69 The first feature implemented is PacketSize, which allows the target to
70 specify the size of packets it can handle - to minimize the number of
71 packets required and improve performance when connected to a remote
75 Fetch an OS auxilliary vector from the remote stub. This packet is a
76 more efficient replacement for qPart:auxv:read.
78 * Removed remote packets
81 This packet has been replaced by qXfer:auxv:read. Only GDB 6.4 and 6.5
82 used it, and only gdbserver implemented it.
84 *** Changes in GDB 6.5
88 Renesas M32C/M16C m32c-elf
90 Morpho Technologies ms1 ms1-elf
94 init-if-undefined Initialize a convenience variable, but
95 only if it doesn't already have a value.
97 The following commands are presently only implemented for native GNU/Linux:
99 checkpoint Save a snapshot of the program state.
101 restart <n> Return the program state to a
102 previously saved state.
104 info checkpoints List currently saved checkpoints.
106 delete-checkpoint <n> Delete a previously saved checkpoint.
108 set|show detach-on-fork Tell gdb whether to detach from a newly
109 forked process, or to keep debugging it.
111 info forks List forks of the user program that
112 are available to be debugged.
114 fork <n> Switch to debugging one of several
115 forks of the user program that are
116 available to be debugged.
118 delete-fork <n> Delete a fork from the list of forks
119 that are available to be debugged (and
120 kill the forked process).
122 detach-fork <n> Delete a fork from the list of forks
123 that are available to be debugged (and
124 allow the process to continue).
128 Morpho Technologies ms2 ms1-elf
130 * Improved Windows host support
132 GDB now builds as a cross debugger hosted on i686-mingw32, including
133 native console support, and remote communications using either
134 network sockets or serial ports.
136 * Improved Modula-2 language support
138 GDB can now print most types in the Modula-2 syntax. This includes:
139 basic types, set types, record types, enumerated types, range types,
140 pointer types and ARRAY types. Procedure var parameters are correctly
141 printed and hexadecimal addresses and character constants are also
142 written in the Modula-2 syntax. Best results can be obtained by using
143 GNU Modula-2 together with the -gdwarf-2 command line option.
147 The ARM rdi-share module.
149 The Netware NLM debug server.
151 *** Changes in GDB 6.4
153 * New native configurations
155 OpenBSD/arm arm*-*-openbsd*
156 OpenBSD/mips64 mips64-*-openbsd*
160 Morpho Technologies ms1 ms1-elf
162 * New command line options
164 --batch-silent As for --batch, but totally silent.
165 --return-child-result The debugger will exist with the same value
166 the child (debugged) program exited with.
167 --eval-command COMMAND, -ex COMMAND
168 Execute a single GDB CLI command. This may be
169 specified multiple times and in conjunction
170 with the --command (-x) option.
172 * Deprecated commands removed
174 The following commands, that were deprecated in 2000, have been
178 set|show arm disassembly-flavor set|show arm disassembler
179 othernames set arm disassembler
180 set|show remotedebug set|show debug remote
181 set|show archdebug set|show debug arch
182 set|show eventdebug set|show debug event
185 * New BSD user-level threads support
187 It is now possible to debug programs using the user-level threads
188 library on OpenBSD and FreeBSD. Currently supported (target)
191 FreeBSD/amd64 x86_64-*-freebsd*
192 FreeBSD/i386 i386-*-freebsd*
193 OpenBSD/i386 i386-*-openbsd*
195 Note that the new kernel threads libraries introduced in FreeBSD 5.x
196 are not yet supported.
198 * New support for Matsushita MN10300 w/sim added
199 (Work in progress). mn10300-elf.
201 * REMOVED configurations and files
203 VxWorks and the XDR protocol *-*-vxworks
204 Motorola MCORE mcore-*-*
205 National Semiconductor NS32000 ns32k-*-*
207 * New "set print array-indexes" command
209 After turning this setting "on", GDB prints the index of each element
210 when displaying arrays. The default is "off" to preserve the previous
213 * VAX floating point support
215 GDB now supports the not-quite-ieee VAX F and D floating point formats.
217 * User-defined command support
219 In addition to using $arg0..$arg9 for argument passing, it is now possible
220 to use $argc to determine now many arguments have been passed. See the
221 section on user-defined commands in the user manual for more information.
223 *** Changes in GDB 6.3:
225 * New command line option
227 GDB now accepts -l followed by a number to set the timeout for remote
230 * GDB works with GCC -feliminate-dwarf2-dups
232 GDB now supports a more compact representation of DWARF-2 debug
233 information using DW_FORM_ref_addr references. These are produced
234 by GCC with the option -feliminate-dwarf2-dups and also by some
235 proprietary compilers. With GCC, you must use GCC 3.3.4 or later
236 to use -feliminate-dwarf2-dups.
238 * Internationalization
240 When supported by the host system, GDB will be built with
241 internationalization (libintl). The task of marking up the sources is
242 continued, we're looking forward to our first translation.
246 Initial support for debugging programs compiled with the GNAT
247 implementation of the Ada programming language has been integrated
248 into GDB. In this release, support is limited to expression evaluation.
250 * New native configurations
252 GNU/Linux/m32r m32r-*-linux-gnu
256 GDB's remote protocol now includes support for the 'p' packet. This
257 packet is used to fetch individual registers from a remote inferior.
259 * END-OF-LIFE registers[] compatibility module
261 GDB's internal register infrastructure has been completely rewritten.
262 The new infrastructure making possible the implementation of key new
263 features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit
266 GDB 6.3 will be the last release to include the the registers[]
267 compatibility module that allowed out-of-date configurations to
268 continue to work. This change directly impacts the following
280 Unless there is activity to revive these configurations, they will be
281 made OBSOLETE in GDB 6.4, and REMOVED from GDB 6.5.
283 * OBSOLETE configurations and files
285 Configurations that have been declared obsolete in this release have
286 been commented out. Unless there is activity to revive these
287 configurations, the next release of GDB will have their sources
297 *** Changes in GDB 6.2.1:
299 * MIPS `break main; run' gave an heuristic-fence-post warning
301 When attempting to run even a simple program, a warning about
302 heuristic-fence-post being hit would be reported. This problem has
305 * MIPS IRIX 'long double' crashed GDB
307 When examining a long double variable, GDB would get a segmentation
308 fault. The crash has been fixed (but GDB 6.2 cannot correctly examine
309 IRIX long double values).
313 A bug in the VAX stack code was causing problems with the "next"
314 command. This problem has been fixed.
316 *** Changes in GDB 6.2:
318 * Fix for ``many threads''
320 On GNU/Linux systems that use the NPTL threads library, a program
321 rapidly creating and deleting threads would confuse GDB leading to the
324 ptrace: No such process.
325 thread_db_get_info: cannot get thread info: generic error
327 This problem has been fixed.
329 * "-async" and "-noasync" options removed.
331 Support for the broken "-noasync" option has been removed (it caused
334 * New ``start'' command.
336 This command runs the program until the begining of the main procedure.
338 * New BSD Kernel Data Access Library (libkvm) interface
340 Using ``target kvm'' it is now possible to debug kernel core dumps and
341 live kernel memory images on various FreeBSD, NetBSD and OpenBSD
342 platforms. Currently supported (native-only) configurations are:
344 FreeBSD/amd64 x86_64-*-freebsd*
345 FreeBSD/i386 i?86-*-freebsd*
346 NetBSD/i386 i?86-*-netbsd*
347 NetBSD/m68k m68*-*-netbsd*
348 NetBSD/sparc sparc-*-netbsd*
349 OpenBSD/amd64 x86_64-*-openbsd*
350 OpenBSD/i386 i?86-*-openbsd*
351 OpenBSD/m68k m68*-openbsd*
352 OpenBSD/sparc sparc-*-openbsd*
354 * Signal trampoline code overhauled
356 Many generic problems with GDB's signal handling code have been fixed.
357 These include: backtraces through non-contiguous stacks; recognition
358 of sa_sigaction signal trampolines; backtrace from a NULL pointer
359 call; backtrace through a signal trampoline; step into and out of
360 signal handlers; and single-stepping in the signal trampoline.
362 Please note that kernel bugs are a limiting factor here. These
363 features have been shown to work on an s390 GNU/Linux system that
364 include a 2.6.8-rc1 kernel. Ref PR breakpoints/1702.
366 * Cygwin support for DWARF 2 added.
368 * New native configurations
370 GNU/Linux/hppa hppa*-*-linux*
371 OpenBSD/hppa hppa*-*-openbsd*
372 OpenBSD/m68k m68*-*-openbsd*
373 OpenBSD/m88k m88*-*-openbsd*
374 OpenBSD/powerpc powerpc-*-openbsd*
375 NetBSD/vax vax-*-netbsd*
376 OpenBSD/vax vax-*-openbsd*
378 * END-OF-LIFE frame compatibility module
380 GDB's internal frame infrastructure has been completely rewritten.
381 The new infrastructure making it possible to support key new features
382 including DWARF 2 Call Frame Information. To aid in the task of
383 migrating old configurations to this new infrastructure, a
384 compatibility module, that allowed old configurations to continue to
385 work, was also included.
387 GDB 6.2 will be the last release to include this frame compatibility
388 module. This change directly impacts the following configurations:
398 Unless there is activity to revive these configurations, they will be
399 made OBSOLETE in GDB 6.3, and REMOVED from GDB 6.4.
401 * REMOVED configurations and files
403 Sun 3, running SunOS 3 m68*-*-sunos3*
404 Sun 3, running SunOS 4 m68*-*-sunos4*
405 Sun 2, running SunOS 3 m68000-*-sunos3*
406 Sun 2, running SunOS 4 m68000-*-sunos4*
407 Motorola 680x0 running LynxOS m68*-*-lynxos*
408 AT&T 3b1/Unix pc m68*-att-*
409 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
410 decstation mips-dec-* mips-little-*
411 riscos mips-*-riscos* mips-*-sysv*
413 sysv mips*-*-sysv4* (IRIX 5/6 not included)
415 *** Changes in GDB 6.1.1:
417 * TUI (Text-mode User Interface) built-in (also included in GDB 6.1)
419 The TUI (Text-mode User Interface) is now built as part of a default
420 GDB configuration. It is enabled by either selecting the TUI with the
421 command line option "-i=tui" or by running the separate "gdbtui"
422 program. For more information on the TUI, see the manual "Debugging
425 * Pending breakpoint support (also included in GDB 6.1)
427 Support has been added to allow you to specify breakpoints in shared
428 libraries that have not yet been loaded. If a breakpoint location
429 cannot be found, and the "breakpoint pending" option is set to auto,
430 GDB queries you if you wish to make the breakpoint pending on a future
431 shared-library load. If and when GDB resolves the breakpoint symbol,
432 the pending breakpoint is removed as one or more regular breakpoints
435 Pending breakpoints are very useful for GCJ Java debugging.
437 * Fixed ISO-C build problems
439 The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained
440 non ISO-C code that stopped them being built using a more strict ISO-C
441 compiler (e.g., IBM's C compiler).
443 * Fixed build problem on IRIX 5
445 Due to header problems with <sys/proc.h>, the file gdb/proc-api.c
446 wasn't able to compile compile on an IRIX 5 system.
448 * Added execute permission to gdb/gdbserver/configure
450 The shell script gdb/testsuite/gdb.stabs/configure lacked execute
451 permission. This bug would cause configure to fail on a number of
452 systems (Solaris, IRIX). Ref: server/519.
454 * Fixed build problem on hpux2.0w-hp-hpux11.00 using the HP ANSI C compiler
456 Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c
457 has been updated to use constant array sizes.
459 * Fixed a panic in the DWARF Call Frame Info code on Solaris 2.7
461 GCC 3.3.2, on Solaris 2.7, includes the DW_EH_PE_funcrel encoding in
462 its generated DWARF Call Frame Info. This encoding was causing GDB to
463 panic, that panic has been fixed. Ref: gdb/1628.
465 * Fixed a problem when examining parameters in shared library code.
467 When examining parameters in optimized shared library code generated
468 by a mainline GCC, GDB would incorrectly report ``Variable "..." is
469 not available''. GDB now correctly displays the variable's value.
471 *** Changes in GDB 6.1:
473 * Removed --with-mmalloc
475 Support for the mmalloc memory manager has been removed, as it
476 conflicted with the internal gdb byte cache.
478 * Changes in AMD64 configurations
480 The AMD64 target now includes the %cs and %ss registers. As a result
481 the AMD64 remote protocol has changed; this affects the floating-point
482 and SSE registers. If you rely on those registers for your debugging,
483 you should upgrade gdbserver on the remote side.
485 * Revised SPARC target
487 The SPARC target has been completely revised, incorporating the
488 FreeBSD/sparc64 support that was added for GDB 6.0. As a result
489 support for LynxOS and SunOS 4 has been dropped. Calling functions
490 from within GDB on operating systems with a non-executable stack
491 (Solaris, OpenBSD) now works.
495 GDB has a new C++ demangler which does a better job on the mangled
496 names generated by current versions of g++. It also runs faster, so
497 with this and other changes gdb should now start faster on large C++
500 * DWARF 2 Location Expressions
502 GDB support for location expressions has been extended to support function
503 arguments and frame bases. Older versions of GDB could crash when they
506 * C++ nested types and namespaces
508 GDB's support for nested types and namespaces in C++ has been
509 improved, especially if you use the DWARF 2 debugging format. (This
510 is the default for recent versions of GCC on most platforms.)
511 Specifically, if you have a class "Inner" defined within a class or
512 namespace "Outer", then GDB realizes that the class's name is
513 "Outer::Inner", not simply "Inner". This should greatly reduce the
514 frequency of complaints about not finding RTTI symbols. In addition,
515 if you are stopped at inside of a function defined within a namespace,
516 GDB modifies its name lookup accordingly.
518 * New native configurations
520 NetBSD/amd64 x86_64-*-netbsd*
521 OpenBSD/amd64 x86_64-*-openbsd*
522 OpenBSD/alpha alpha*-*-openbsd*
523 OpenBSD/sparc sparc-*-openbsd*
524 OpenBSD/sparc64 sparc64-*-openbsd*
526 * New debugging protocols
528 M32R with SDI protocol m32r-*-elf*
530 * "set prompt-escape-char" command deleted.
532 The command "set prompt-escape-char" has been deleted. This command,
533 and its very obscure effet on GDB's prompt, was never documented,
534 tested, nor mentioned in the NEWS file.
536 * OBSOLETE configurations and files
538 Configurations that have been declared obsolete in this release have
539 been commented out. Unless there is activity to revive these
540 configurations, the next release of GDB will have their sources
543 Sun 3, running SunOS 3 m68*-*-sunos3*
544 Sun 3, running SunOS 4 m68*-*-sunos4*
545 Sun 2, running SunOS 3 m68000-*-sunos3*
546 Sun 2, running SunOS 4 m68000-*-sunos4*
547 Motorola 680x0 running LynxOS m68*-*-lynxos*
548 AT&T 3b1/Unix pc m68*-att-*
549 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
550 decstation mips-dec-* mips-little-*
551 riscos mips-*-riscos* mips-*-sysv*
553 sysv mips*-*-sysv4* (IRIX 5/6 not included)
555 * REMOVED configurations and files
557 SGI Irix-4.x mips-sgi-irix4 or iris4
558 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
559 Z8000 simulator z8k-zilog-none or z8ksim
560 Matsushita MN10200 w/simulator mn10200-*-*
561 H8/500 simulator h8500-hitachi-hms or h8500hms
562 HP/PA running BSD hppa*-*-bsd*
563 HP/PA running OSF/1 hppa*-*-osf*
564 HP/PA Pro target hppa*-*-pro*
565 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
566 386BSD i[3456]86-*-bsd*
567 Sequent family i[3456]86-sequent-sysv4*
568 i[3456]86-sequent-sysv*
569 i[3456]86-sequent-bsd*
570 SPARC running LynxOS sparc-*-lynxos*
571 SPARC running SunOS 4 sparc-*-sunos4*
572 Tsqware Sparclet sparclet-*-*
573 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
575 *** Changes in GDB 6.0:
579 Support for debugging the Objective-C programming language has been
582 * New backtrace mechanism (includes DWARF 2 Call Frame Information).
584 DWARF 2's Call Frame Information makes available compiler generated
585 information that more exactly describes the program's run-time stack.
586 By using this information, GDB is able to provide more robust stack
589 The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets
590 have been updated to use a new backtrace mechanism which includes
595 GDB's remote protocol has been extended to include support for hosted
596 file I/O (where the remote target uses GDB's file system). See GDB's
597 remote protocol documentation for details.
599 * All targets using the new architecture framework.
601 All of GDB's targets have been updated to use the new internal
602 architecture framework. The way is now open for future GDB releases
603 to include cross-architecture native debugging support (i386 on amd64,
606 * GNU/Linux's Thread Local Storage (TLS)
608 GDB now includes support for for the GNU/Linux implementation of
609 per-thread variables.
611 * GNU/Linux's Native POSIX Thread Library (NPTL)
613 GDB's thread code has been updated to work with either the new
614 GNU/Linux NPTL thread library or the older "LinuxThreads" library.
616 * Separate debug info.
618 GDB, in conjunction with BINUTILS, now supports a mechanism for
619 automatically loading debug information from a separate file. Instead
620 of shipping full debug and non-debug versions of system libraries,
621 system integrators can now instead ship just the stripped libraries
622 and optional debug files.
624 * DWARF 2 Location Expressions
626 DWARF 2 Location Expressions allow the compiler to more completely
627 describe the location of variables (even in optimized code) to the
630 GDB now includes preliminary support for location expressions (support
631 for DW_OP_piece is still missing).
635 A number of long standing bugs that caused GDB to die while starting a
636 Java application have been fixed. GDB's Java support is now
637 considered "useable".
639 * GNU/Linux support for fork, vfork, and exec.
641 The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode"
642 commands are now implemented for GNU/Linux. They require a 2.5.x or later
645 * GDB supports logging output to a file
647 There are two new commands, "set logging" and "show logging", which can be
648 used to capture GDB's output to a file.
650 * The meaning of "detach" has changed for gdbserver
652 The "detach" command will now resume the application, as documented. To
653 disconnect from gdbserver and leave it stopped, use the new "disconnect"
656 * d10v, m68hc11 `regs' command deprecated
658 The `info registers' command has been updated so that it displays the
659 registers using a format identical to the old `regs' command.
663 A new command, "maint set profile on/off", has been added. This command can
664 be used to enable or disable profiling while running GDB, to profile a
665 session or a set of commands. In addition there is a new configure switch,
666 "--enable-profiling", which will cause GDB to be compiled with profiling
667 data, for more informative profiling results.
669 * Default MI syntax changed to "mi2".
671 The default MI (machine interface) syntax, enabled by the command line
672 option "-i=mi", has been changed to "mi2". The previous MI syntax,
673 "mi1", can be enabled by specifying the option "-i=mi1".
675 Support for the original "mi0" syntax (included in GDB 5.0) has been
678 Fix for gdb/192: removed extraneous space when displaying frame level.
679 Fix for gdb/672: update changelist is now output in mi list format.
680 Fix for gdb/702: a -var-assign that updates the value now shows up
681 in a subsequent -var-update.
683 * New native configurations.
685 FreeBSD/amd64 x86_64-*-freebsd*
687 * Multi-arched targets.
689 HP/PA HPUX11 hppa*-*-hpux*
690 Renesas M32R/D w/simulator m32r-*-elf*
692 * OBSOLETE configurations and files
694 Configurations that have been declared obsolete in this release have
695 been commented out. Unless there is activity to revive these
696 configurations, the next release of GDB will have their sources
699 Z8000 simulator z8k-zilog-none or z8ksim
700 Matsushita MN10200 w/simulator mn10200-*-*
701 H8/500 simulator h8500-hitachi-hms or h8500hms
702 HP/PA running BSD hppa*-*-bsd*
703 HP/PA running OSF/1 hppa*-*-osf*
704 HP/PA Pro target hppa*-*-pro*
705 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
706 Sequent family i[3456]86-sequent-sysv4*
707 i[3456]86-sequent-sysv*
708 i[3456]86-sequent-bsd*
709 Tsqware Sparclet sparclet-*-*
710 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
712 * REMOVED configurations and files
715 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
716 IBM AIX PS/2 i[3456]86-*-aix
717 i386 running Mach 3.0 i[3456]86-*-mach3*
718 i386 running Mach i[3456]86-*-mach*
719 i386 running OSF/1 i[3456]86-*osf1mk*
720 HP/Apollo 68k Family m68*-apollo*-sysv*,
722 m68*-hp-bsd*, m68*-hp-hpux*
723 Argonaut Risc Chip (ARC) arc-*-*
724 Mitsubishi D30V d30v-*-*
725 Fujitsu FR30 fr30-*-elf*
726 OS/9000 i[34]86-*-os9k
727 I960 with MON960 i960-*-coff
729 * MIPS $fp behavior changed
731 The convenience variable $fp, for the MIPS, now consistently returns
732 the address of the current frame's base. Previously, depending on the
733 context, $fp could refer to either $sp or the current frame's base
734 address. See ``8.10 Registers'' in the manual ``Debugging with GDB:
735 The GNU Source-Level Debugger''.
737 *** Changes in GDB 5.3:
739 * GNU/Linux shared library multi-threaded performance improved.
741 When debugging a multi-threaded application on GNU/Linux, GDB now uses
742 `/proc', in preference to `ptrace' for memory reads. This may result
743 in an improvement in the start-up time of multi-threaded, shared
744 library applications when run under GDB. One GDB user writes: ``loads
745 shared libs like mad''.
747 * ``gdbserver'' now supports multi-threaded applications on some targets
749 Support for debugging multi-threaded applications which use
750 the GNU/Linux LinuxThreads package has been added for
751 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
752 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
754 * GDB now supports C/C++ preprocessor macros.
756 GDB now expands preprocessor macro invocations in C/C++ expressions,
757 and provides various commands for showing macro definitions and how
760 The new command `macro expand EXPRESSION' expands any macro
761 invocations in expression, and shows the result.
763 The new command `show macro MACRO-NAME' shows the definition of the
764 macro named MACRO-NAME, and where it was defined.
766 Most compilers don't include information about macros in the debugging
767 information by default. In GCC 3.1, for example, you need to compile
768 your program with the options `-gdwarf-2 -g3'. If the macro
769 information is present in the executable, GDB will read it.
771 * Multi-arched targets.
773 DEC Alpha (partial) alpha*-*-*
774 DEC VAX (partial) vax-*-*
776 National Semiconductor NS32000 (partial) ns32k-*-*
777 Motorola 68000 (partial) m68k-*-*
778 Motorola MCORE mcore-*-*
782 Fujitsu FRV architecture added by Red Hat frv*-*-*
785 * New native configurations
787 Alpha NetBSD alpha*-*-netbsd*
788 SH NetBSD sh*-*-netbsdelf*
789 MIPS NetBSD mips*-*-netbsd*
790 UltraSPARC NetBSD sparc64-*-netbsd*
792 * OBSOLETE configurations and files
794 Configurations that have been declared obsolete in this release have
795 been commented out. Unless there is activity to revive these
796 configurations, the next release of GDB will have their sources
799 Mitsubishi D30V d30v-*-*
800 OS/9000 i[34]86-*-os9k
801 IBM AIX PS/2 i[3456]86-*-aix
802 Fujitsu FR30 fr30-*-elf*
803 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
804 Argonaut Risc Chip (ARC) arc-*-*
805 i386 running Mach 3.0 i[3456]86-*-mach3*
806 i386 running Mach i[3456]86-*-mach*
807 i386 running OSF/1 i[3456]86-*osf1mk*
808 HP/Apollo 68k Family m68*-apollo*-sysv*,
810 m68*-hp-bsd*, m68*-hp-hpux*
811 I960 with MON960 i960-*-coff
815 CHILL, a Pascal like language used by telecommunications companies.
817 * REMOVED configurations and files
819 AMD 29k family via UDI a29k-amd-udi, udi29k
820 A29K VxWorks a29k-*-vxworks
821 AMD 29000 embedded, using EBMON a29k-none-none
822 AMD 29000 embedded with COFF a29k-none-coff
823 AMD 29000 embedded with a.out a29k-none-aout
825 testsuite/gdb.hp/gdb.threads-hp/ directory
827 * New command "set max-user-call-depth <nnn>"
829 This command allows the user to limit the call depth of user-defined
830 commands. The default is 1024.
832 * Changes in FreeBSD/i386 native debugging.
834 Support for the "generate-core-file" has been added.
836 * New commands "dump", "append", and "restore".
838 These commands allow data to be copied from target memory
839 to a bfd-format or binary file (dump and append), and back
840 from a file into memory (restore).
842 * Improved "next/step" support on multi-processor Alpha Tru64.
844 The previous single-step mechanism could cause unpredictable problems,
845 including the random appearance of SIGSEGV or SIGTRAP signals. The use
846 of a software single-step mechanism prevents this.
848 *** Changes in GDB 5.2.1:
856 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
857 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
858 Fix, by Joel Brobecker imported from mainline.
860 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
861 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
862 Fix, by Fred Fish, imported from mainline.
864 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
865 Surprisingly enough, it works now.
866 By Michal Ludvig, imported from mainline.
868 i386 hardware watchpoint support:
869 avoid misses on second run for some targets.
870 By Pierre Muller, imported from mainline.
872 *** Changes in GDB 5.2:
874 * New command "set trust-readonly-sections on[off]".
876 This command is a hint that tells gdb that read-only sections
877 really are read-only (ie. that their contents will not change).
878 In this mode, gdb will go to the object file rather than the
879 target to read memory from read-only sections (such as ".text").
880 This can be a significant performance improvement on some
881 (notably embedded) targets.
883 * New command "generate-core-file" (or "gcore").
885 This new gdb command allows the user to drop a core file of the child
886 process state at any time. So far it's been implemented only for
887 GNU/Linux and Solaris, but should be relatively easily ported to other
888 hosts. Argument is core file name (defaults to core.<pid>).
890 * New command line option
892 GDB now accepts --pid or -p followed by a process id.
894 * Change in command line behavior -- corefiles vs. process ids.
896 There is a subtle behavior in the way in which GDB handles
897 command line arguments. The first non-flag argument is always
898 a program to debug, but the second non-flag argument may either
899 be a corefile or a process id. Previously, GDB would attempt to
900 open the second argument as a corefile, and if that failed, would
901 issue a superfluous error message and then attempt to attach it as
902 a process. Now, if the second argument begins with a non-digit,
903 it will be treated as a corefile. If it begins with a digit,
904 GDB will attempt to attach it as a process, and if no such process
905 is found, will then attempt to open it as a corefile.
907 * Changes in ARM configurations.
909 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
910 configuration is fully multi-arch.
912 * New native configurations
914 ARM NetBSD arm*-*-netbsd*
915 x86 OpenBSD i[3456]86-*-openbsd*
916 AMD x86-64 running GNU/Linux x86_64-*-linux-*
917 Sparc64 running FreeBSD sparc64-*-freebsd*
921 Sanyo XStormy16 xstormy16-elf
923 * OBSOLETE configurations and files
925 Configurations that have been declared obsolete in this release have
926 been commented out. Unless there is activity to revive these
927 configurations, the next release of GDB will have their sources
930 AMD 29k family via UDI a29k-amd-udi, udi29k
931 A29K VxWorks a29k-*-vxworks
932 AMD 29000 embedded, using EBMON a29k-none-none
933 AMD 29000 embedded with COFF a29k-none-coff
934 AMD 29000 embedded with a.out a29k-none-aout
936 testsuite/gdb.hp/gdb.threads-hp/ directory
938 * REMOVED configurations and files
940 TI TMS320C80 tic80-*-*
942 PowerPC Solaris powerpcle-*-solaris*
943 PowerPC Windows NT powerpcle-*-cygwin32
944 PowerPC Netware powerpc-*-netware*
945 Harris/CXUX m88k m88*-harris-cxux*
946 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
947 ns32k-utek-sysv* ns32k-utek-*
948 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
949 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
950 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
951 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
952 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
954 * Changes to command line processing
956 The new `--args' feature can be used to specify command-line arguments
957 for the inferior from gdb's command line.
959 * Changes to key bindings
961 There is a new `operate-and-get-next' function bound to `C-o'.
963 *** Changes in GDB 5.1.1
965 Fix compile problem on DJGPP.
967 Fix a problem with floating-point registers on the i386 being
970 Fix to stop GDB crashing on .debug_str debug info.
972 Numerous documentation fixes.
974 Numerous testsuite fixes.
976 *** Changes in GDB 5.1:
978 * New native configurations
980 Alpha FreeBSD alpha*-*-freebsd*
981 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
982 MIPS GNU/Linux mips*-*-linux*
983 MIPS SGI Irix 6.x mips*-sgi-irix6*
985 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
989 Motorola 68HC11 and 68HC12 m68hc11-elf
991 UltraSparc running GNU/Linux sparc64-*-linux*
993 * OBSOLETE configurations and files
995 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
996 Harris/CXUX m88k m88*-harris-cxux*
997 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
998 ns32k-utek-sysv* ns32k-utek-*
999 TI TMS320C80 tic80-*-*
1001 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
1002 PowerPC Solaris powerpcle-*-solaris*
1003 PowerPC Windows NT powerpcle-*-cygwin32
1004 PowerPC Netware powerpc-*-netware*
1005 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
1006 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
1007 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
1008 Apple Macintosh (MPW) host N/A
1010 stuff.c (Program to stuff files into a specially prepared space in kdb)
1011 kdb-start.c (Main loop for the standalone kernel debugger)
1013 Configurations that have been declared obsolete in this release have
1014 been commented out. Unless there is activity to revive these
1015 configurations, the next release of GDB will have their sources
1016 permanently REMOVED.
1018 * REMOVED configurations and files
1020 Altos 3068 m68*-altos-*
1021 Convex c1-*-*, c2-*-*
1023 ARM RISCix arm-*-* (as host)
1027 * GDB has been converted to ISO C.
1029 GDB's source code has been converted to ISO C. In particular, the
1030 sources are fully protoized, and rely on standard headers being
1035 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
1037 * The MI enabled by default.
1039 The new machine oriented interface (MI) introduced in GDB 5.0 has been
1040 revised and enabled by default. Packages which use GDB as a debugging
1041 engine behind a UI or another front end are encouraged to switch to
1042 using the GDB/MI interface, instead of the old annotations interface
1043 which is now deprecated.
1045 * Support for debugging Pascal programs.
1047 GDB now includes support for debugging Pascal programs. The following
1048 main features are supported:
1050 - Pascal-specific data types such as sets;
1052 - automatic recognition of Pascal sources based on file-name
1055 - Pascal-style display of data types, variables, and functions;
1057 - a Pascal expression parser.
1059 However, some important features are not yet supported.
1061 - Pascal string operations are not supported at all;
1063 - there are some problems with boolean types;
1065 - Pascal type hexadecimal constants are not supported
1066 because they conflict with the internal variables format;
1068 - support for Pascal objects and classes is not full yet;
1070 - unlike Pascal, GDB is case-sensitive for symbol names.
1072 * Changes in completion.
1074 Commands such as `shell', `run' and `set args', which pass arguments
1075 to inferior programs, now complete on file names, similar to what
1076 users expect at the shell prompt.
1078 Commands which accept locations, such as `disassemble', `print',
1079 `breakpoint', `until', etc. now complete on filenames as well as
1080 program symbols. Thus, if you type "break foob TAB", and the source
1081 files linked into the programs include `foobar.c', that file name will
1082 be one of the candidates for completion. However, file names are not
1083 considered for completion after you typed a colon that delimits a file
1084 name from a name of a function in that file, as in "break foo.c:bar".
1086 `set demangle-style' completes on available demangling styles.
1088 * New platform-independent commands:
1090 It is now possible to define a post-hook for a command as well as a
1091 hook that runs before the command. For more details, see the
1092 documentation of `hookpost' in the GDB manual.
1094 * Changes in GNU/Linux native debugging.
1096 Support for debugging multi-threaded programs has been completely
1097 revised for all platforms except m68k and sparc. You can now debug as
1098 many threads as your system allows you to have.
1100 Attach/detach is supported for multi-threaded programs.
1102 Support for SSE registers was added for x86. This doesn't work for
1103 multi-threaded programs though.
1105 * Changes in MIPS configurations.
1107 Multi-arch support is enabled for all MIPS configurations.
1109 GDB can now be built as native debugger on SGI Irix 6.x systems for
1110 debugging n32 executables. (Debugging 64-bit executables is not yet
1113 * Unified support for hardware watchpoints in all x86 configurations.
1115 Most (if not all) native x86 configurations support hardware-assisted
1116 breakpoints and watchpoints in a unified manner. This support
1117 implements debug register sharing between watchpoints, which allows to
1118 put a virtually infinite number of watchpoints on the same address,
1119 and also supports watching regions up to 16 bytes with several debug
1122 The new maintenance command `maintenance show-debug-regs' toggles
1123 debugging print-outs in functions that insert, remove, and test
1124 watchpoints and hardware breakpoints.
1126 * Changes in the DJGPP native configuration.
1128 New command ``info dos sysinfo'' displays assorted information about
1129 the CPU, OS, memory, and DPMI server.
1131 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
1132 display information about segment descriptors stored in GDT, LDT, and
1135 New commands ``info dos pde'' and ``info dos pte'' display entries
1136 from Page Directory and Page Tables (for now works with CWSDPMI only).
1137 New command ``info dos address-pte'' displays the Page Table entry for
1138 a given linear address.
1140 GDB can now pass command lines longer than 126 characters to the
1141 program being debugged (requires an update to the libdbg.a library
1142 which is part of the DJGPP development kit).
1144 DWARF2 debug info is now supported.
1146 It is now possible to `step' and `next' through calls to `longjmp'.
1148 * Changes in documentation.
1150 All GDB documentation was converted to GFDL, the GNU Free
1151 Documentation License.
1153 Tracepoints-related commands are now fully documented in the GDB
1156 TUI, the Text-mode User Interface, is now documented in the manual.
1158 Tracepoints-related commands are now fully documented in the GDB
1161 The "GDB Internals" manual now has an index. It also includes
1162 documentation of `ui_out' functions, GDB coding standards, x86
1163 hardware watchpoints, and memory region attributes.
1165 * GDB's version number moved to ``version.in''
1167 The Makefile variable VERSION has been replaced by the file
1168 ``version.in''. People creating GDB distributions should update the
1169 contents of this file.
1173 GUD support is now a standard part of the EMACS distribution.
1175 *** Changes in GDB 5.0:
1177 * Improved support for debugging FP programs on x86 targets
1179 Unified and much-improved support for debugging floating-point
1180 programs on all x86 targets. In particular, ``info float'' now
1181 displays the FP registers in the same format on all x86 targets, with
1182 greater level of detail.
1184 * Improvements and bugfixes in hardware-assisted watchpoints
1186 It is now possible to watch array elements, struct members, and
1187 bitfields with hardware-assisted watchpoints. Data-read watchpoints
1188 on x86 targets no longer erroneously trigger when the address is
1191 * Improvements in the native DJGPP version of GDB
1193 The distribution now includes all the scripts and auxiliary files
1194 necessary to build the native DJGPP version on MS-DOS/MS-Windows
1195 machines ``out of the box''.
1197 The DJGPP version can now debug programs that use signals. It is
1198 possible to catch signals that happened in the debuggee, deliver
1199 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
1200 would kill the program being debugged.) Programs that hook hardware
1201 interrupts (keyboard, timer, etc.) can also be debugged.
1203 It is now possible to debug DJGPP programs that redirect their
1204 standard handles or switch them to raw (as opposed to cooked) mode, or
1205 even close them. The command ``run < foo > bar'' works as expected,
1206 and ``info terminal'' reports useful information about the debuggee's
1207 terminal, including raw/cooked mode, redirection, etc.
1209 The DJGPP version now uses termios functions for console I/O, which
1210 enables debugging graphics programs. Interrupting GDB with Ctrl-C
1213 DOS-style file names with drive letters are now fully supported by
1216 It is now possible to debug DJGPP programs that switch their working
1217 directory. It is also possible to rerun the debuggee any number of
1218 times without restarting GDB; thus, you can use the same setup,
1219 breakpoints, etc. for many debugging sessions.
1221 * New native configurations
1223 ARM GNU/Linux arm*-*-linux*
1224 PowerPC GNU/Linux powerpc-*-linux*
1228 Motorola MCore mcore-*-*
1229 x86 VxWorks i[3456]86-*-vxworks*
1230 PowerPC VxWorks powerpc-*-vxworks*
1231 TI TMS320C80 tic80-*-*
1233 * OBSOLETE configurations
1235 Altos 3068 m68*-altos-*
1236 Convex c1-*-*, c2-*-*
1238 ARM RISCix arm-*-* (as host)
1241 Configurations that have been declared obsolete will be commented out,
1242 but the code will be left in place. If there is no activity to revive
1243 these configurations before the next release of GDB, the sources will
1244 be permanently REMOVED.
1246 * Gould support removed
1248 Support for the Gould PowerNode and NP1 has been removed.
1250 * New features for SVR4
1252 On SVR4 native platforms (such as Solaris), if you attach to a process
1253 without first loading a symbol file, GDB will now attempt to locate and
1254 load symbols from the running process's executable file.
1256 * Many C++ enhancements
1258 C++ support has been greatly improved. Overload resolution now works properly
1259 in almost all cases. RTTI support is on the way.
1261 * Remote targets can connect to a sub-program
1263 A popen(3) style serial-device has been added. This device starts a
1264 sub-process (such as a stand-alone simulator) and then communicates
1265 with that. The sub-program to run is specified using the syntax
1266 ``|<program> <args>'' vis:
1268 (gdb) set remotedebug 1
1269 (gdb) target extended-remote |mn10300-elf-sim program-args
1271 * MIPS 64 remote protocol
1273 A long standing bug in the mips64 remote protocol where by GDB
1274 expected certain 32 bit registers (ex SR) to be transfered as 32
1275 instead of 64 bits has been fixed.
1277 The command ``set remote-mips64-transfers-32bit-regs on'' has been
1278 added to provide backward compatibility with older versions of GDB.
1280 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
1282 The command ``set remotebinarydownload'' command has been replaced by
1283 ``set remote X-packet''. Other commands in ``set remote'' family
1284 include ``set remote P-packet''.
1286 * Breakpoint commands accept ranges.
1288 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
1289 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
1290 ``tracepoint passcount'' also accepts a range of tracepoints.
1292 * ``apropos'' command added.
1294 The ``apropos'' command searches through command names and
1295 documentation strings, printing out matches, making it much easier to
1296 try to find a command that does what you are looking for.
1300 A new machine oriented interface (MI) has been added to GDB. This
1301 interface is designed for debug environments running GDB as a separate
1302 process. This is part of the long term libGDB project. See the
1303 "GDB/MI" chapter of the GDB manual for further information. It can be
1304 enabled by configuring with:
1306 .../configure --enable-gdbmi
1308 *** Changes in GDB-4.18:
1310 * New native configurations
1312 HP-UX 10.20 hppa*-*-hpux10.20
1313 HP-UX 11.x hppa*-*-hpux11.0*
1314 M68K GNU/Linux m68*-*-linux*
1318 Fujitsu FR30 fr30-*-elf*
1319 Intel StrongARM strongarm-*-*
1320 Mitsubishi D30V d30v-*-*
1322 * OBSOLETE configurations
1324 Gould PowerNode, NP1 np1-*-*, pn-*-*
1326 Configurations that have been declared obsolete will be commented out,
1327 but the code will be left in place. If there is no activity to revive
1328 these configurations before the next release of GDB, the sources will
1329 be permanently REMOVED.
1333 As a compatibility experiment, GDB's source files buildsym.h and
1334 buildsym.c have been converted to pure standard C, no longer
1335 containing any K&R compatibility code. We believe that all systems in
1336 use today either come with a standard C compiler, or have a GCC port
1337 available. If this is not true, please report the affected
1338 configuration to bug-gdb@gnu.org immediately. See the README file for
1339 information about getting a standard C compiler if you don't have one
1344 GDB now uses readline 2.2.
1346 * set extension-language
1348 You can now control the mapping between filename extensions and source
1349 languages by using the `set extension-language' command. For instance,
1350 you can ask GDB to treat .c files as C++ by saying
1351 set extension-language .c c++
1352 The command `info extensions' lists all of the recognized extensions
1353 and their associated languages.
1355 * Setting processor type for PowerPC and RS/6000
1357 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
1358 you can use the `set processor' command to specify what variant of the
1359 PowerPC family you are debugging. The command
1363 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
1364 following PowerPC and RS6000 variants:
1366 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
1367 rs6000 IBM RS6000 ("POWER") architecture, user-level view
1369 403GC IBM PowerPC 403GC
1370 505 Motorola PowerPC 505
1371 860 Motorola PowerPC 860 or 850
1372 601 Motorola PowerPC 601
1373 602 Motorola PowerPC 602
1374 603 Motorola/IBM PowerPC 603 or 603e
1375 604 Motorola PowerPC 604 or 604e
1376 750 Motorola/IBM PowerPC 750 or 750
1378 At the moment, this command just tells GDB what to name the
1379 special-purpose processor registers. Since almost all the affected
1380 registers are inaccessible to user-level programs, this command is
1381 only useful for remote debugging in its present form.
1385 Thanks to a major code donation from Hewlett-Packard, GDB now has much
1386 more extensive support for HP-UX. Added features include shared
1387 library support, kernel threads and hardware watchpoints for 11.00,
1388 support for HP's ANSI C and C++ compilers, and a compatibility mode
1389 for xdb and dbx commands.
1393 HP's donation includes the new concept of catchpoints, which is a
1394 generalization of the old catch command. On HP-UX, it is now possible
1395 to catch exec, fork, and vfork, as well as library loading.
1397 This means that the existing catch command has changed; its first
1398 argument now specifies the type of catch to be set up. See the
1399 output of "help catch" for a list of catchpoint types.
1401 * Debugging across forks
1403 On HP-UX, you can choose which process to debug when a fork() happens
1408 HP has donated a curses-based terminal user interface (TUI). To get
1409 it, build with --enable-tui. Although this can be enabled for any
1410 configuration, at present it only works for native HP debugging.
1412 * GDB remote protocol additions
1414 A new protocol packet 'X' that writes binary data is now available.
1415 Default behavior is to try 'X', then drop back to 'M' if the stub
1416 fails to respond. The settable variable `remotebinarydownload'
1417 allows explicit control over the use of 'X'.
1419 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
1420 full 64-bit address. The command
1422 set remoteaddresssize 32
1424 can be used to revert to the old behaviour. For existing remote stubs
1425 the change should not be noticed, as the additional address information
1428 In order to assist in debugging stubs, you may use the maintenance
1429 command `packet' to send any text string to the stub. For instance,
1431 maint packet heythere
1433 sends the packet "$heythere#<checksum>". Note that it is very easy to
1434 disrupt a debugging session by sending the wrong packet at the wrong
1437 The compare-sections command allows you to compare section data on the
1438 target to what is in the executable file without uploading or
1439 downloading, by comparing CRC checksums.
1441 * Tracing can collect general expressions
1443 You may now collect general expressions at tracepoints. This requires
1444 further additions to the target-side stub; see tracepoint.c and
1445 doc/agentexpr.texi for further details.
1447 * mask-address variable for Mips
1449 For Mips targets, you may control the zeroing of the upper 32 bits of
1450 a 64-bit address by entering `set mask-address on'. This is mainly
1451 of interest to users of embedded R4xxx and R5xxx processors.
1453 * Higher serial baud rates
1455 GDB's serial code now allows you to specify baud rates 57600, 115200,
1456 230400, and 460800 baud. (Note that your host system may not be able
1457 to achieve all of these rates.)
1461 The i960 configuration now includes an initial implementation of a
1462 builtin simulator, contributed by Jim Wilson.
1465 *** Changes in GDB-4.17:
1467 * New native configurations
1469 Alpha GNU/Linux alpha*-*-linux*
1470 Unixware 2.x i[3456]86-unixware2*
1471 Irix 6.x mips*-sgi-irix6*
1472 PowerPC GNU/Linux powerpc-*-linux*
1473 PowerPC Solaris powerpcle-*-solaris*
1474 Sparc GNU/Linux sparc-*-linux*
1475 Motorola sysV68 R3V7.1 m68k-motorola-sysv
1479 Argonaut Risc Chip (ARC) arc-*-*
1480 Hitachi H8/300S h8300*-*-*
1481 Matsushita MN10200 w/simulator mn10200-*-*
1482 Matsushita MN10300 w/simulator mn10300-*-*
1483 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
1484 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
1485 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
1486 Mitsubishi D10V w/simulator d10v-*-*
1487 Mitsubishi M32R/D w/simulator m32r-*-elf*
1488 Tsqware Sparclet sparclet-*-*
1489 NEC V850 w/simulator v850-*-*
1491 * New debugging protocols
1493 ARM with RDI protocol arm*-*-*
1494 M68K with dBUG monitor m68*-*-{aout,coff,elf}
1495 DDB and LSI variants of PMON protocol mips*-*-*
1496 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
1497 PowerPC with SDS protocol powerpc{,le}-*-eabi
1498 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
1502 All configurations can now understand and use the DWARF 2 debugging
1503 format. The choice is automatic, if the symbol file contains DWARF 2
1508 GDB now includes basic Java language support. This support is
1509 only useful with Java compilers that produce native machine code.
1511 * solib-absolute-prefix and solib-search-path
1513 For SunOS and SVR4 shared libraries, you may now set the prefix for
1514 loading absolute shared library symbol files, and the search path for
1515 locating non-absolute shared library symbol files.
1517 * Live range splitting
1519 GDB can now effectively debug code for which GCC has performed live
1520 range splitting as part of its optimization. See gdb/doc/LRS for
1521 more details on the expected format of the stabs information.
1525 GDB's support for the GNU Hurd, including thread debugging, has been
1526 updated to work with current versions of the Hurd.
1530 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
1531 instruction set. ARM GDB automatically detects when Thumb
1532 instructions are in use, and adjusts disassembly and backtracing
1537 GDB's MIPS target configurations now handle the MIP16 16-bit
1542 GDB now includes support for overlays; if an executable has been
1543 linked such that multiple sections are based at the same address, GDB
1544 will decide which section to use for symbolic info. You can choose to
1545 control the decision manually, using overlay commands, or implement
1546 additional target-side support and use "overlay load-target" to bring
1547 in the overlay mapping. Do "help overlay" for more detail.
1551 The command "info symbol <address>" displays information about
1552 the symbol at the specified address.
1556 The standard remote protocol now includes an extension that allows
1557 asynchronous collection and display of trace data. This requires
1558 extensive support in the target-side debugging stub. Tracing mode
1559 includes a new interaction mode in GDB and new commands: see the
1560 file tracepoint.c for more details.
1564 Configurations for embedded MIPS now include a simulator contributed
1565 by Cygnus Solutions. The simulator supports the instruction sets
1566 of most MIPS variants.
1570 Sparc configurations may now include the ERC32 simulator contributed
1571 by the European Space Agency. The simulator is not built into
1572 Sparc targets by default; configure with --enable-sim to include it.
1576 For target configurations that may include multiple variants of a
1577 basic architecture (such as MIPS and SH), you may now set the
1578 architecture explicitly. "set arch" sets, "info arch" lists
1579 the possible architectures.
1581 *** Changes in GDB-4.16:
1583 * New native configurations
1585 Windows 95, x86 Windows NT i[345]86-*-cygwin32
1586 M68K NetBSD m68k-*-netbsd*
1587 PowerPC AIX 4.x powerpc-*-aix*
1588 PowerPC MacOS powerpc-*-macos*
1589 PowerPC Windows NT powerpcle-*-cygwin32
1590 RS/6000 AIX 4.x rs6000-*-aix4*
1594 ARM with RDP protocol arm-*-*
1595 I960 with MON960 i960-*-coff
1596 MIPS VxWorks mips*-*-vxworks*
1597 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
1598 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
1600 Matra Sparclet sparclet-*-*
1604 The powerpc-eabi configuration now includes the PSIM simulator,
1605 contributed by Andrew Cagney, with assistance from Mike Meissner.
1606 PSIM is a very elaborate model of the PowerPC, including not only
1607 basic instruction set execution, but also details of execution unit
1608 performance and I/O hardware. See sim/ppc/README for more details.
1612 GDB now works with Solaris 2.5.
1614 * Windows 95/NT native
1616 GDB will now work as a native debugger on Windows 95 and Windows NT.
1617 To build it from source, you must use the "gnu-win32" environment,
1618 which uses a DLL to emulate enough of Unix to run the GNU tools.
1619 Further information, binaries, and sources are available at
1620 ftp.cygnus.com, under pub/gnu-win32.
1622 * dont-repeat command
1624 If a user-defined command includes the command `dont-repeat', then the
1625 command will not be repeated if the user just types return. This is
1626 useful if the command is time-consuming to run, so that accidental
1627 extra keystrokes don't run the same command many times.
1629 * Send break instead of ^C
1631 The standard remote protocol now includes an option to send a break
1632 rather than a ^C to the target in order to interrupt it. By default,
1633 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
1635 * Remote protocol timeout
1637 The standard remote protocol includes a new variable `remotetimeout'
1638 that allows you to set the number of seconds before GDB gives up trying
1639 to read from the target. The default value is 2.
1641 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
1643 By default GDB will automatically keep track of objects as they are
1644 loaded and unloaded by the dynamic linker. By using the command `set
1645 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
1646 when shared library events occur, thus allowing you to set breakpoints
1647 in shared libraries which are explicitly loaded by the inferior.
1649 Note this feature does not work on hpux8. On hpux9 you must link
1650 /usr/lib/end.o into your program. This feature should work
1651 automatically on hpux10.
1653 * Irix 5.x hardware watchpoint support
1655 Irix 5 configurations now support the use of hardware watchpoints.
1657 * Mips protocol "SYN garbage limit"
1659 When debugging a Mips target using the `target mips' protocol, you
1660 may set the number of characters that GDB will ignore by setting
1661 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
1662 every character. The default value is 1050.
1664 * Recording and replaying remote debug sessions
1666 If you set `remotelogfile' to the name of a file, gdb will write to it
1667 a recording of a remote debug session. This recording may then be
1668 replayed back to gdb using "gdbreplay". See gdbserver/README for
1669 details. This is useful when you have a problem with GDB while doing
1670 remote debugging; you can make a recording of the session and send it
1671 to someone else, who can then recreate the problem.
1673 * Speedups for remote debugging
1675 GDB includes speedups for downloading and stepping MIPS systems using
1676 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
1677 and more efficient S-record downloading.
1679 * Memory use reductions and statistics collection
1681 GDB now uses less memory and reports statistics about memory usage.
1682 Try the `maint print statistics' command, for example.
1684 *** Changes in GDB-4.15:
1686 * Psymtabs for XCOFF
1688 The symbol reader for AIX GDB now uses partial symbol tables. This
1689 can greatly improve startup time, especially for large executables.
1691 * Remote targets use caching
1693 Remote targets now use a data cache to speed up communication with the
1694 remote side. The data cache could lead to incorrect results because
1695 it doesn't know about volatile variables, thus making it impossible to
1696 debug targets which use memory mapped I/O devices. `set remotecache
1697 off' turns the the data cache off.
1699 * Remote targets may have threads
1701 The standard remote protocol now includes support for multiple threads
1702 in the target system, using new protocol commands 'H' and 'T'. See
1703 gdb/remote.c for details.
1707 If GDB is configured with `--enable-netrom', then it will include
1708 support for the NetROM ROM emulator from XLNT Designs. The NetROM
1709 acts as though it is a bank of ROM on the target board, but you can
1710 write into it over the network. GDB's support consists only of
1711 support for fast loading into the emulated ROM; to debug, you must use
1712 another protocol, such as standard remote protocol. The usual
1713 sequence is something like
1715 target nrom <netrom-hostname>
1717 target remote <netrom-hostname>:1235
1721 GDB now includes support for the Apple Macintosh, as a host only. It
1722 may be run as either an MPW tool or as a standalone application, and
1723 it can debug through the serial port. All the usual GDB commands are
1724 available, but to the target command, you must supply "serial" as the
1725 device type instead of "/dev/ttyXX". See mpw-README in the main
1726 directory for more information on how to build. The MPW configuration
1727 scripts */mpw-config.in support only a few targets, and only the
1728 mips-idt-ecoff target has been tested.
1732 GDB configuration now uses autoconf. This is not user-visible,
1733 but does simplify configuration and building.
1737 GDB now supports hpux10.
1739 *** Changes in GDB-4.14:
1741 * New native configurations
1743 x86 FreeBSD i[345]86-*-freebsd
1744 x86 NetBSD i[345]86-*-netbsd
1745 NS32k NetBSD ns32k-*-netbsd
1746 Sparc NetBSD sparc-*-netbsd
1750 A29K VxWorks a29k-*-vxworks
1751 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1752 CPU32 EST-300 emulator m68*-*-est*
1753 PowerPC ELF powerpc-*-elf
1756 * Alpha OSF/1 support for procfs
1758 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1759 possible to attach to running processes. As the mounting of the /proc
1760 filesystem is optional on the Alpha, GDB automatically determines
1761 the availability of /proc during startup. This can lead to problems
1762 if /proc is unmounted after GDB has been started.
1764 * Arguments to user-defined commands
1766 User commands may accept up to 10 arguments separated by whitespace.
1767 Arguments are accessed within the user command via $arg0..$arg9. A
1770 print $arg0 + $arg1 + $arg2
1772 To execute the command use:
1775 Defines the command "adder" which prints the sum of its three arguments.
1776 Note the arguments are text substitutions, so they may reference variables,
1777 use complex expressions, or even perform inferior function calls.
1779 * New `if' and `while' commands
1781 This makes it possible to write more sophisticated user-defined
1782 commands. Both commands take a single argument, which is the
1783 expression to evaluate, and must be followed by the commands to
1784 execute, one per line, if the expression is nonzero, the list being
1785 terminated by the word `end'. The `if' command list may include an
1786 `else' word, which causes the following commands to be executed only
1787 if the expression is zero.
1789 * Fortran source language mode
1791 GDB now includes partial support for Fortran 77. It will recognize
1792 Fortran programs and can evaluate a subset of Fortran expressions, but
1793 variables and functions may not be handled correctly. GDB will work
1794 with G77, but does not yet know much about symbols emitted by other
1797 * Better HPUX support
1799 Most debugging facilities now work on dynamic executables for HPPAs
1800 running hpux9 or later. You can attach to running dynamically linked
1801 processes, but by default the dynamic libraries will be read-only, so
1802 for instance you won't be able to put breakpoints in them. To change
1803 that behavior do the following before running the program:
1809 This will cause the libraries to be mapped private and read-write.
1810 To revert to the normal behavior, do this:
1816 You cannot set breakpoints or examine data in the library until after
1817 the library is loaded if the function/data symbols do not have
1820 GDB can now also read debug symbols produced by the HP C compiler on
1821 HPPAs (sorry, no C++, Fortran or 68k support).
1823 * Target byte order now dynamically selectable
1825 You can choose which byte order to use with a target system, via the
1826 commands "set endian big" and "set endian little", and you can see the
1827 current setting by using "show endian". You can also give the command
1828 "set endian auto", in which case GDB will use the byte order
1829 associated with the executable. Currently, only embedded MIPS
1830 configurations support dynamic selection of target byte order.
1832 * New DOS host serial code
1834 This version uses DPMI interrupts to handle buffered I/O, so you
1835 no longer need to run asynctsr when debugging boards connected to
1838 *** Changes in GDB-4.13:
1840 * New "complete" command
1842 This lists all the possible completions for the rest of the line, if it
1843 were to be given as a command itself. This is intended for use by emacs.
1845 * Trailing space optional in prompt
1847 "set prompt" no longer adds a space for you after the prompt you set. This
1848 allows you to set a prompt which ends in a space or one that does not.
1850 * Breakpoint hit counts
1852 "info break" now displays a count of the number of times the breakpoint
1853 has been hit. This is especially useful in conjunction with "ignore"; you
1854 can ignore a large number of breakpoint hits, look at the breakpoint info
1855 to see how many times the breakpoint was hit, then run again, ignoring one
1856 less than that number, and this will get you quickly to the last hit of
1859 * Ability to stop printing at NULL character
1861 "set print null-stop" will cause GDB to stop printing the characters of
1862 an array when the first NULL is encountered. This is useful when large
1863 arrays actually contain only short strings.
1865 * Shared library breakpoints
1867 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1868 breakpoints in shared libraries before the executable is run.
1870 * Hardware watchpoints
1872 There is a new hardware breakpoint for the watch command for sparclite
1873 targets. See gdb/sparclite/hw_breakpoint.note.
1875 Hardware watchpoints are also now supported under GNU/Linux.
1879 Annotations have been added. These are for use with graphical interfaces,
1880 and are still experimental. Currently only gdba.el uses these.
1882 * Improved Irix 5 support
1884 GDB now works properly with Irix 5.2.
1886 * Improved HPPA support
1888 GDB now works properly with the latest GCC and GAS.
1890 * New native configurations
1892 Sequent PTX4 i[34]86-sequent-ptx4
1893 HPPA running OSF/1 hppa*-*-osf*
1894 Atari TT running SVR4 m68*-*-sysv4*
1895 RS/6000 LynxOS rs6000-*-lynxos*
1899 OS/9000 i[34]86-*-os9k
1900 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1903 * Hitachi SH7000 and E7000-PC ICE support
1905 There is now support for communicating with the Hitachi E7000-PC ICE.
1906 This is available automatically when GDB is configured for the SH.
1910 As usual, a variety of small fixes and improvements, both generic
1911 and configuration-specific. See the ChangeLog for more detail.
1913 *** Changes in GDB-4.12:
1915 * Irix 5 is now supported
1919 GDB-4.12 on the HPPA has a number of changes which make it unable
1920 to debug the output from the currently released versions of GCC and
1921 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1922 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1923 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1926 *** Changes in GDB-4.11:
1928 * User visible changes:
1932 The "set remotedebug" option is now consistent between the mips remote
1933 target, remote targets using the gdb-specific protocol, UDI (AMD's
1934 debug protocol for the 29k) and the 88k bug monitor. It is now an
1935 integer specifying a debug level (normally 0 or 1, but 2 means more
1936 debugging info for the mips target).
1938 * DEC Alpha native support
1940 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1941 debug info, but GDB works fairly well with the DEC compiler and should
1942 work with a future GCC release. See the README file for a few
1943 Alpha-specific notes.
1945 * Preliminary thread implementation
1947 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1949 * LynxOS native and target support for 386
1951 This release has been hosted on LynxOS 2.2, and also can be configured
1952 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1955 * Improvements in C++ mangling/demangling.
1957 This release has much better g++ debugging, specifically in name
1958 mangling/demangling, virtual function calls, print virtual table,
1959 call methods, ...etc.
1961 *** Changes in GDB-4.10:
1963 * User visible changes:
1965 Remote debugging using the GDB-specific (`target remote') protocol now
1966 supports the `load' command. This is only useful if you have some
1967 other way of getting the stub to the target system, and you can put it
1968 somewhere in memory where it won't get clobbered by the download.
1970 Filename completion now works.
1972 When run under emacs mode, the "info line" command now causes the
1973 arrow to point to the line specified. Also, "info line" prints
1974 addresses in symbolic form (as well as hex).
1976 All vxworks based targets now support a user settable option, called
1977 vxworks-timeout. This option represents the number of seconds gdb
1978 should wait for responses to rpc's. You might want to use this if
1979 your vxworks target is, perhaps, a slow software simulator or happens
1980 to be on the far side of a thin network line.
1984 This release contains support for using a DEC alpha as a GDB host for
1985 cross debugging. Native alpha debugging is not supported yet.
1988 *** Changes in GDB-4.9:
1992 This is the first GDB release which is accompanied by a matching testsuite.
1993 The testsuite requires installation of dejagnu, which should be available
1994 via ftp from most sites that carry GNU software.
1998 'Cfront' style demangling has had its name changed to 'ARM' style, to
1999 emphasize that it was written from the specifications in the C++ Annotated
2000 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
2001 disclaimers, it still generated too much confusion with users attempting to
2002 use gdb with AT&T cfront.
2006 GDB now uses a standard remote interface to a simulator library.
2007 So far, the library contains simulators for the Zilog Z8001/2, the
2008 Hitachi H8/300, H8/500 and Super-H.
2010 * New targets supported
2012 H8/300 simulator h8300-hitachi-hms or h8300hms
2013 H8/500 simulator h8500-hitachi-hms or h8500hms
2014 SH simulator sh-hitachi-hms or sh
2015 Z8000 simulator z8k-zilog-none or z8ksim
2016 IDT MIPS board over serial line mips-idt-ecoff
2018 Cross-debugging to GO32 targets is supported. It requires a custom
2019 version of the i386-stub.c module which is integrated with the
2020 GO32 memory extender.
2022 * New remote protocols
2024 MIPS remote debugging protocol.
2026 * New source languages supported
2028 This version includes preliminary support for Chill, a Pascal like language
2029 used by telecommunications companies. Chill support is also being integrated
2030 into the GNU compiler, but we don't know when it will be publically available.
2033 *** Changes in GDB-4.8:
2035 * HP Precision Architecture supported
2037 GDB now supports HP PA-RISC machines running HPUX. A preliminary
2038 version of this support was available as a set of patches from the
2039 University of Utah. GDB does not support debugging of programs
2040 compiled with the HP compiler, because HP will not document their file
2041 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
2042 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
2044 Many problems in the preliminary version have been fixed.
2046 * Faster and better demangling
2048 We have improved template demangling and fixed numerous bugs in the GNU style
2049 demangler. It can now handle type modifiers such as `static' or `const'. Wide
2050 character types (wchar_t) are now supported. Demangling of each symbol is now
2051 only done once, and is cached when the symbol table for a file is read in.
2052 This results in a small increase in memory usage for C programs, a moderate
2053 increase in memory usage for C++ programs, and a fantastic speedup in
2056 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
2057 from the specifications in the Annotated Reference Manual, which AT&T's
2058 compiler does not actually implement.
2060 * G++ multiple inheritance compiler problem
2062 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
2063 inheritance lattices was reworked to properly discover ambiguities. We
2064 recently found an example which causes this new algorithm to fail in a
2065 very subtle way, producing bad debug information for those classes.
2066 The file 'gcc.patch' (in this directory) can be applied to gcc to
2067 circumvent the problem. A future GCC release will contain a complete
2070 The previous G++ debug info problem (mentioned below for the gdb-4.7
2071 release) is fixed in gcc version 2.3.2.
2073 * Improved configure script
2075 The `configure' script will now attempt to guess your system type if
2076 you don't supply a host system type. The old scheme of supplying a
2077 host system triplet is preferable over using this. All the magic is
2078 done in the new `config.guess' script. Examine it for details.
2080 We have also brought our configure script much more in line with the FSF's
2081 version. It now supports the --with-xxx options. In particular,
2082 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
2083 The resulting GDB will not be able to read arbitrary object file formats --
2084 only the format ``expected'' to be used on the configured target system.
2085 We hope to make this the default in a future release.
2087 * Documentation improvements
2089 There's new internal documentation on how to modify GDB, and how to
2090 produce clean changes to the code. We implore people to read it
2091 before submitting changes.
2093 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
2094 M4 macros. The new texinfo.tex is provided in this release. Pre-built
2095 `info' files are also provided. To build `info' files from scratch,
2096 you will need the latest `makeinfo' release, which will be available in
2097 a future texinfo-X.Y release.
2099 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
2100 We're not sure exactly which versions have this problem, but it has
2101 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
2102 or better. If that isn't possible, there is a patch in
2103 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
2104 around this problem.
2108 GDB now supports array constants that can be used in expressions typed in by
2109 the user. The syntax is `{element, element, ...}'. Ie: you can now type
2110 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
2113 The new directory `gdb/sparclite' contains a program that demonstrates
2114 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
2116 * New native hosts supported
2118 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
2119 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
2121 * New targets supported
2123 AMD 29k family via UDI a29k-amd-udi or udi29k
2125 * New file formats supported
2127 BFD now supports reading HP/PA-RISC executables (SOM file format?),
2128 HPUX core files, and SCO 3.2v2 core files.
2132 Attaching to processes now works again; thanks for the many bug reports.
2134 We have also stomped on a bunch of core dumps caused by
2135 printf_filtered("%s") problems.
2137 We eliminated a copyright problem on the rpc and ptrace header files
2138 for VxWorks, which was discovered at the last minute during the 4.7
2139 release. You should now be able to build a VxWorks GDB.
2141 You can now interrupt gdb while an attached process is running. This
2142 will cause the attached process to stop, and give control back to GDB.
2144 We fixed problems caused by using too many file descriptors
2145 for reading symbols from object files and libraries. This was
2146 especially a problem for programs that used many (~100) shared
2149 The `step' command now only enters a subroutine if there is line number
2150 information for the subroutine. Otherwise it acts like the `next'
2151 command. Previously, `step' would enter subroutines if there was
2152 any debugging information about the routine. This avoids problems
2153 when using `cc -g1' on MIPS machines.
2155 * Internal improvements
2157 GDB's internal interfaces have been improved to make it easier to support
2158 debugging of multiple languages in the future.
2160 GDB now uses a common structure for symbol information internally.
2161 Minimal symbols (derived from linkage symbols in object files), partial
2162 symbols (from a quick scan of debug information), and full symbols
2163 contain a common subset of information, making it easier to write
2164 shared code that handles any of them.
2166 * New command line options
2168 We now accept --silent as an alias for --quiet.
2172 The memory-mapped-malloc library is now licensed under the GNU Library
2173 General Public License.
2175 *** Changes in GDB-4.7:
2177 * Host/native/target split
2179 GDB has had some major internal surgery to untangle the support for
2180 hosts and remote targets. Now, when you configure GDB for a remote
2181 target, it will no longer load in all of the support for debugging
2182 local programs on the host. When fully completed and tested, this will
2183 ensure that arbitrary host/target combinations are possible.
2185 The primary conceptual shift is to separate the non-portable code in
2186 GDB into three categories. Host specific code is required any time GDB
2187 is compiled on that host, regardless of the target. Target specific
2188 code relates to the peculiarities of the target, but can be compiled on
2189 any host. Native specific code is everything else: it can only be
2190 built when the host and target are the same system. Child process
2191 handling and core file support are two common `native' examples.
2193 GDB's use of /proc for controlling Unix child processes is now cleaner.
2194 It has been split out into a single module under the `target_ops' vector,
2195 plus two native-dependent functions for each system that uses /proc.
2197 * New hosts supported
2199 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
2200 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2201 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
2203 * New targets supported
2205 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
2206 68030 and CPU32 m68030-*-*, m68332-*-*
2208 * New native hosts supported
2210 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2211 (386bsd is not well tested yet)
2212 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
2214 * New file formats supported
2216 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
2217 supports reading of `a.out.adobe' object files, which are an a.out
2218 format extended with minimal information about multiple sections.
2222 `show copying' is the same as the old `info copying'.
2223 `show warranty' is the same as `info warrantee'.
2224 These were renamed for consistency. The old commands continue to work.
2226 `info handle' is a new alias for `info signals'.
2228 You can now define pre-command hooks, which attach arbitrary command
2229 scripts to any command. The commands in the hook will be executed
2230 prior to the user's command. You can also create a hook which will be
2231 executed whenever the program stops. See gdb.texinfo.
2235 We now deal with Cfront style name mangling, and can even extract type
2236 info from mangled symbols. GDB can automatically figure out which
2237 symbol mangling style your C++ compiler uses.
2239 Calling of methods and virtual functions has been improved as well.
2243 The crash that occured when debugging Sun Ansi-C compiled binaries is
2244 fixed. This was due to mishandling of the extra N_SO stabs output
2247 We also finally got Ultrix 4.2 running in house, and fixed core file
2248 support, with help from a dozen people on the net.
2250 John M. Farrell discovered that the reason that single-stepping was so
2251 slow on all of the Mips based platforms (primarily SGI and DEC) was
2252 that we were trying to demangle and lookup a symbol used for internal
2253 purposes on every instruction that was being stepped through. Changing
2254 the name of that symbol so that it couldn't be mistaken for a C++
2255 mangled symbol sped things up a great deal.
2257 Rich Pixley sped up symbol lookups in general by getting much smarter
2258 about when C++ symbol mangling is necessary. This should make symbol
2259 completion (TAB on the command line) much faster. It's not as fast as
2260 we'd like, but it's significantly faster than gdb-4.6.
2264 A new user controllable variable 'call_scratch_address' can
2265 specify the location of a scratch area to be used when GDB
2266 calls a function in the target. This is necessary because the
2267 usual method of putting the scratch area on the stack does not work
2268 in systems that have separate instruction and data spaces.
2270 We integrated changes to support the 29k UDI (Universal Debugger
2271 Interface), but discovered at the last minute that we didn't have all
2272 of the appropriate copyright paperwork. We are working with AMD to
2273 resolve this, and hope to have it available soon.
2277 We have sped up the remote serial line protocol, especially for targets
2278 with lots of registers. It now supports a new `expedited status' ('T')
2279 message which can be used in place of the existing 'S' status message.
2280 This allows the remote stub to send only the registers that GDB
2281 needs to make a quick decision about single-stepping or conditional
2282 breakpoints, eliminating the need to fetch the entire register set for
2283 each instruction being stepped through.
2285 The GDB remote serial protocol now implements a write-through cache for
2286 registers, only re-reading the registers if the target has run.
2288 There is also a new remote serial stub for SPARC processors. You can
2289 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
2290 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
2291 processor with a serial port.
2295 Configure.in files have become much easier to read and modify. A new
2296 `table driven' format makes it more obvious what configurations are
2297 supported, and what files each one uses.
2301 There is a new opcodes library which will eventually contain all of the
2302 disassembly routines and opcode tables. At present, it only contains
2303 Sparc and Z8000 routines. This will allow the assembler, debugger, and
2304 disassembler (binutils/objdump) to share these routines.
2306 The libiberty library is now copylefted under the GNU Library General
2307 Public License. This allows more liberal use, and was done so libg++
2308 can use it. This makes no difference to GDB, since the Library License
2309 grants all the rights from the General Public License.
2313 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
2314 reference to the stabs symbol info used by the debugger. It is (as far
2315 as we know) the only published document on this fascinating topic. We
2316 encourage you to read it, compare it to the stabs information on your
2317 system, and send improvements on the document in general (to
2318 bug-gdb@prep.ai.mit.edu).
2320 And, of course, many bugs have been fixed.
2323 *** Changes in GDB-4.6:
2325 * Better support for C++ function names
2327 GDB now accepts as input the "demangled form" of C++ overloaded function
2328 names and member function names, and can do command completion on such names
2329 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
2330 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
2331 Make use of command completion, it is your friend.
2333 GDB also now accepts a variety of C++ mangled symbol formats. They are
2334 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
2335 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
2336 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
2337 for the list of formats.
2339 * G++ symbol mangling problem
2341 Recent versions of gcc have a bug in how they emit debugging information for
2342 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
2343 directory) can be applied to gcc to fix the problem. Alternatively, if you
2344 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
2345 usual symptom is difficulty with setting breakpoints on methods. GDB complains
2346 about the method being non-existent. (We believe that version 2.2.2 of GCC has
2349 * New 'maintenance' command
2351 All of the commands related to hacking GDB internals have been moved out of
2352 the main command set, and now live behind the 'maintenance' command. This
2353 can also be abbreviated as 'mt'. The following changes were made:
2355 dump-me -> maintenance dump-me
2356 info all-breakpoints -> maintenance info breakpoints
2357 printmsyms -> maintenance print msyms
2358 printobjfiles -> maintenance print objfiles
2359 printpsyms -> maintenance print psymbols
2360 printsyms -> maintenance print symbols
2362 The following commands are new:
2364 maintenance demangle Call internal GDB demangler routine to
2365 demangle a C++ link name and prints the result.
2366 maintenance print type Print a type chain for a given symbol
2368 * Change to .gdbinit file processing
2370 We now read the $HOME/.gdbinit file before processing the argv arguments
2371 (e.g. reading symbol files or core files). This allows global parameters to
2372 be set, which will apply during the symbol reading. The ./.gdbinit is still
2373 read after argv processing.
2375 * New hosts supported
2377 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
2379 GNU/Linux support i386-unknown-linux or linux
2381 We are also including code to support the HP/PA running BSD and HPUX. This
2382 is almost guaranteed not to work, as we didn't have time to test or build it
2383 for this release. We are including it so that the more adventurous (or
2384 masochistic) of you can play with it. We also had major problems with the
2385 fact that the compiler that we got from HP doesn't support the -g option.
2388 * New targets supported
2390 Hitachi H8/300 h8300-hitachi-hms or h8300hms
2392 * More smarts about finding #include files
2394 GDB now remembers the compilation directory for all include files, and for
2395 all files from which C is generated (like yacc and lex sources). This
2396 greatly improves GDB's ability to find yacc/lex sources, and include files,
2397 especially if you are debugging your program from a directory different from
2398 the one that contains your sources.
2400 We also fixed a bug which caused difficulty with listing and setting
2401 breakpoints in include files which contain C code. (In the past, you had to
2402 try twice in order to list an include file that you hadn't looked at before.)
2404 * Interesting infernals change
2406 GDB now deals with arbitrary numbers of sections, where the symbols for each
2407 section must be relocated relative to that section's landing place in the
2408 target's address space. This work was needed to support ELF with embedded
2409 stabs used by Solaris-2.0.
2411 * Bug fixes (of course!)
2413 There have been loads of fixes for the following things:
2414 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
2415 i960, stabs, DOS(GO32), procfs, etc...
2417 See the ChangeLog for details.
2419 *** Changes in GDB-4.5:
2421 * New machines supported (host and target)
2423 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
2425 SGI Irix-4.x mips-sgi-irix4 or iris4
2427 * New malloc package
2429 GDB now uses a new memory manager called mmalloc, based on gmalloc.
2430 Mmalloc is capable of handling mutiple heaps of memory. It is also
2431 capable of saving a heap to a file, and then mapping it back in later.
2432 This can be used to greatly speedup the startup of GDB by using a
2433 pre-parsed symbol table which lives in a mmalloc managed heap. For
2434 more details, please read mmalloc/mmalloc.texi.
2438 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
2439 'help info proc' for details.
2441 * MIPS ecoff symbol table format
2443 The code that reads MIPS symbol table format is now supported on all hosts.
2444 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
2447 * File name changes for MS-DOS
2449 Many files in the config directories have been renamed to make it easier to
2450 support GDB on MS-DOSe systems (which have very restrictive file name
2451 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
2452 environment) is close to working but has some remaining problems. Note
2453 that debugging of DOS programs is not supported, due to limitations
2454 in the ``operating system'', but it can be used to host cross-debugging.
2456 * Cross byte order fixes
2458 Many fixes have been made to support cross debugging of Sparc and MIPS
2459 targets from hosts whose byte order differs.
2461 * New -mapped and -readnow options
2463 If memory-mapped files are available on your system through the 'mmap'
2464 system call, you can use the -mapped option on the `file' or
2465 `symbol-file' commands to cause GDB to write the symbols from your
2466 program into a reusable file. If the program you are debugging is
2467 called `/path/fred', the mapped symbol file will be `./fred.syms'.
2468 Future GDB debugging sessions will notice the presence of this file,
2469 and will quickly map in symbol information from it, rather than reading
2470 the symbol table from the executable program. Using the '-mapped'
2471 option in a GDB `file' or `symbol-file' command has the same effect as
2472 starting GDB with the '-mapped' command-line option.
2474 You can cause GDB to read the entire symbol table immediately by using
2475 the '-readnow' option with any of the commands that load symbol table
2476 information (or on the GDB command line). This makes the command
2477 slower, but makes future operations faster.
2479 The -mapped and -readnow options are typically combined in order to
2480 build a `fred.syms' file that contains complete symbol information.
2481 A simple GDB invocation to do nothing but build a `.syms' file for future
2484 gdb -batch -nx -mapped -readnow programname
2486 The `.syms' file is specific to the host machine on which GDB is run.
2487 It holds an exact image of GDB's internal symbol table. It cannot be
2488 shared across multiple host platforms.
2490 * longjmp() handling
2492 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
2493 siglongjmp() without losing control. This feature has not yet been ported to
2494 all systems. It currently works on many 386 platforms, all MIPS-based
2495 platforms (SGI, DECstation, etc), and Sun3/4.
2499 Preliminary work has been put in to support the new Solaris OS from Sun. At
2500 this time, it can control and debug processes, but it is not capable of
2505 As always, many many bug fixes. The major areas were with g++, and mipsread.
2506 People using the MIPS-based platforms should experience fewer mysterious
2507 crashes and trashed symbol tables.
2509 *** Changes in GDB-4.4:
2511 * New machines supported (host and target)
2513 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2515 BSD Reno on Vax vax-dec-bsd
2516 Ultrix on Vax vax-dec-ultrix
2518 * New machines supported (target)
2520 AMD 29000 embedded, using EBMON a29k-none-none
2524 GDB continues to improve its handling of C++. `References' work better.
2525 The demangler has also been improved, and now deals with symbols mangled as
2526 per the Annotated C++ Reference Guide.
2528 GDB also now handles `stabs' symbol information embedded in MIPS
2529 `ecoff' symbol tables. Since the ecoff format was not easily
2530 extensible to handle new languages such as C++, this appeared to be a
2531 good way to put C++ debugging info into MIPS binaries. This option
2532 will be supported in the GNU C compiler, version 2, when it is
2535 * New features for SVR4
2537 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
2538 shared libraries. Debugging dynamically linked programs should present
2539 only minor differences from debugging statically linked programs.
2541 The `info proc' command will print out information about any process
2542 on an SVR4 system (including the one you are debugging). At the moment,
2543 it prints the address mappings of the process.
2545 If you bring up GDB on another SVR4 system, please send mail to
2546 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
2548 * Better dynamic linking support in SunOS
2550 Reading symbols from shared libraries which contain debugging symbols
2551 now works properly. However, there remain issues such as automatic
2552 skipping of `transfer vector' code during function calls, which
2553 make it harder to debug code in a shared library, than to debug the
2554 same code linked statically.
2558 GDB is now using the latest `getopt' routines from the FSF. This
2559 version accepts the -- prefix for options with long names. GDB will
2560 continue to accept the old forms (-option and +option) as well.
2561 Various single letter abbreviations for options have been explicity
2562 added to the option table so that they won't get overshadowed in the
2563 future by other options that begin with the same letter.
2567 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
2568 Many assorted bugs have been handled. Many more remain to be handled.
2569 See the various ChangeLog files (primarily in gdb and bfd) for details.
2572 *** Changes in GDB-4.3:
2574 * New machines supported (host and target)
2576 Amiga 3000 running Amix m68k-cbm-svr4 or amix
2577 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
2578 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
2580 * Almost SCO Unix support
2582 We had hoped to support:
2583 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2584 (except for core file support), but we discovered very late in the release
2585 that it has problems with process groups that render gdb unusable. Sorry
2586 about that. I encourage people to fix it and post the fixes.
2588 * Preliminary ELF and DWARF support
2590 GDB can read ELF object files on System V Release 4, and can handle
2591 debugging records for C, in DWARF format, in ELF files. This support
2592 is preliminary. If you bring up GDB on another SVR4 system, please
2593 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
2598 GDB now uses the latest `readline' library. One user-visible change
2599 is that two tabs will list possible command completions, which previously
2600 required typing M-? (meta-question mark, or ESC ?).
2604 The `stepi' bug that many of you noticed has been squashed.
2605 Many bugs in C++ have been handled. Many more remain to be handled.
2606 See the various ChangeLog files (primarily in gdb and bfd) for details.
2608 * State of the MIPS world (in case you wondered):
2610 GDB can understand the symbol tables emitted by the compilers
2611 supplied by most vendors of MIPS-based machines, including DEC. These
2612 symbol tables are in a format that essentially nobody else uses.
2614 Some versions of gcc come with an assembler post-processor called
2615 mips-tfile. This program is required if you want to do source-level
2616 debugging of gcc-compiled programs. I believe FSF does not ship
2617 mips-tfile with gcc version 1, but it will eventually come with gcc
2620 Debugging of g++ output remains a problem. g++ version 1.xx does not
2621 really support it at all. (If you're lucky, you should be able to get
2622 line numbers and stack traces to work, but no parameters or local
2623 variables.) With some work it should be possible to improve the
2626 When gcc version 2 is released, you will have somewhat better luck.
2627 However, even then you will get confusing results for inheritance and
2630 We will eventually provide full debugging of g++ output on
2631 DECstations. This will probably involve some kind of stabs-in-ecoff
2632 encapulation, but the details have not been worked out yet.
2635 *** Changes in GDB-4.2:
2637 * Improved configuration
2639 Only one copy of `configure' exists now, and it is not self-modifying.
2640 Porting BFD is simpler.
2644 The `step' and `next' commands now only stop at the first instruction
2645 of a source line. This prevents the multiple stops that used to occur
2646 in switch statements, for-loops, etc. `Step' continues to stop if a
2647 function that has debugging information is called within the line.
2651 Lots of small bugs fixed. More remain.
2653 * New host supported (not target)
2655 Intel 386 PC clone running Mach i386-none-mach
2658 *** Changes in GDB-4.1:
2660 * Multiple source language support
2662 GDB now has internal scaffolding to handle several source languages.
2663 It determines the type of each source file from its filename extension,
2664 and will switch expression parsing and number formatting to match the
2665 language of the function in the currently selected stack frame.
2666 You can also specifically set the language to be used, with
2667 `set language c' or `set language modula-2'.
2671 GDB now has preliminary support for the GNU Modula-2 compiler,
2672 currently under development at the State University of New York at
2673 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
2674 continue through the fall of 1991 and into 1992.
2676 Other Modula-2 compilers are currently not supported, and attempting to
2677 debug programs compiled with them will likely result in an error as the
2678 symbol table is read. Feel free to work on it, though!
2680 There are hooks in GDB for strict type checking and range checking,
2681 in the `Modula-2 philosophy', but they do not currently work.
2685 GDB can now write to executable and core files (e.g. patch
2686 a variable's value). You must turn this switch on, specify
2687 the file ("exec foo" or "core foo"), *then* modify it, e.g.
2688 by assigning a new value to a variable. Modifications take
2691 * Automatic SunOS shared library reading
2693 When you run your program, GDB automatically determines where its
2694 shared libraries (if any) have been loaded, and reads their symbols.
2695 The `share' command is no longer needed. This also works when
2696 examining core files.
2700 You can specify the number of lines that the `list' command shows.
2703 * New machines supported (host and target)
2705 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
2706 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
2707 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
2709 * New hosts supported (not targets)
2711 IBM RT/PC: romp-ibm-aix or rtpc
2713 * New targets supported (not hosts)
2715 AMD 29000 embedded with COFF a29k-none-coff
2716 AMD 29000 embedded with a.out a29k-none-aout
2717 Ultracomputer remote kernel debug a29k-nyu-kern
2719 * New remote interfaces
2725 *** Changes in GDB-4.0:
2729 Wide output is wrapped at good places to make the output more readable.
2731 Gdb now supports cross-debugging from a host machine of one type to a
2732 target machine of another type. Communication with the target system
2733 is over serial lines. The ``target'' command handles connecting to the
2734 remote system; the ``load'' command will download a program into the
2735 remote system. Serial stubs for the m68k and i386 are provided. Gdb
2736 also supports debugging of realtime processes running under VxWorks,
2737 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
2738 stub on the target system.
2740 New CPUs supported include the AMD 29000 and Intel 960.
2742 GDB now reads object files and symbol tables via a ``binary file''
2743 library, which allows a single copy of GDB to debug programs of multiple
2744 object file types such as a.out and coff.
2746 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2747 refcard.dvi and refcard.ps are available to format it).
2750 * Control-Variable user interface simplified
2752 All variables that control the operation of the debugger can be set
2753 by the ``set'' command, and displayed by the ``show'' command.
2755 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2756 ``Show prompt'' produces the response:
2757 Gdb's prompt is new-gdb=>.
2759 What follows are the NEW set commands. The command ``help set'' will
2760 print a complete list of old and new set commands. ``help set FOO''
2761 will give a longer description of the variable FOO. ``show'' will show
2762 all of the variable descriptions and their current settings.
2764 confirm on/off: Enables warning questions for operations that are
2765 hard to recover from, e.g. rerunning the program while
2766 it is already running. Default is ON.
2768 editing on/off: Enables EMACS style command line editing
2769 of input. Previous lines can be recalled with
2770 control-P, the current line can be edited with control-B,
2771 you can search for commands with control-R, etc.
2774 history filename NAME: NAME is where the gdb command history
2775 will be stored. The default is .gdb_history,
2776 or the value of the environment variable
2779 history size N: The size, in commands, of the command history. The
2780 default is 256, or the value of the environment variable
2783 history save on/off: If this value is set to ON, the history file will
2784 be saved after exiting gdb. If set to OFF, the
2785 file will not be saved. The default is OFF.
2787 history expansion on/off: If this value is set to ON, then csh-like
2788 history expansion will be performed on
2789 command line input. The default is OFF.
2791 radix N: Sets the default radix for input and output. It can be set
2792 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2793 in the current radix, so "set radix 10" is always a no-op.
2795 height N: This integer value is the number of lines on a page. Default
2796 is 24, the current `stty rows'' setting, or the ``li#''
2797 setting from the termcap entry matching the environment
2800 width N: This integer value is the number of characters on a line.
2801 Default is 80, the current `stty cols'' setting, or the ``co#''
2802 setting from the termcap entry matching the environment
2805 Note: ``set screensize'' is obsolete. Use ``set height'' and
2806 ``set width'' instead.
2808 print address on/off: Print memory addresses in various command displays,
2809 such as stack traces and structure values. Gdb looks
2810 more ``symbolic'' if you turn this off; it looks more
2811 ``machine level'' with it on. Default is ON.
2813 print array on/off: Prettyprint arrays. New convenient format! Default
2816 print demangle on/off: Print C++ symbols in "source" form if on,
2819 print asm-demangle on/off: Same, for assembler level printouts
2822 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2825 * Support for Epoch Environment.
2827 The epoch environment is a version of Emacs v18 with windowing. One
2828 new command, ``inspect'', is identical to ``print'', except that if you
2829 are running in the epoch environment, the value is printed in its own
2833 * Support for Shared Libraries
2835 GDB can now debug programs and core files that use SunOS shared libraries.
2836 Symbols from a shared library cannot be referenced
2837 before the shared library has been linked with the program (this
2838 happens after you type ``run'' and before the function main() is entered).
2839 At any time after this linking (including when examining core files
2840 from dynamically linked programs), gdb reads the symbols from each
2841 shared library when you type the ``sharedlibrary'' command.
2842 It can be abbreviated ``share''.
2844 sharedlibrary REGEXP: Load shared object library symbols for files
2845 matching a unix regular expression. No argument
2846 indicates to load symbols for all shared libraries.
2848 info sharedlibrary: Status of loaded shared libraries.
2853 A watchpoint stops execution of a program whenever the value of an
2854 expression changes. Checking for this slows down execution
2855 tremendously whenever you are in the scope of the expression, but is
2856 quite useful for catching tough ``bit-spreader'' or pointer misuse
2857 problems. Some machines such as the 386 have hardware for doing this
2858 more quickly, and future versions of gdb will use this hardware.
2860 watch EXP: Set a watchpoint (breakpoint) for an expression.
2862 info watchpoints: Information about your watchpoints.
2864 delete N: Deletes watchpoint number N (same as breakpoints).
2865 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2866 enable N: Re-enables watchpoint number N (same as breakpoints).
2869 * C++ multiple inheritance
2871 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2874 * C++ exception handling
2876 Gdb now supports limited C++ exception handling. Besides the existing
2877 ability to breakpoint on an exception handler, gdb can breakpoint on
2878 the raising of an exception (before the stack is peeled back to the
2881 catch FOO: If there is a FOO exception handler in the dynamic scope,
2882 set a breakpoint to catch exceptions which may be raised there.
2883 Multiple exceptions (``catch foo bar baz'') may be caught.
2885 info catch: Lists all exceptions which may be caught in the
2886 current stack frame.
2889 * Minor command changes
2891 The command ``call func (arg, arg, ...)'' now acts like the print
2892 command, except it does not print or save a value if the function's result
2893 is void. This is similar to dbx usage.
2895 The ``up'' and ``down'' commands now always print the frame they end up
2896 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2897 frames without printing.
2899 * New directory command
2901 'dir' now adds directories to the FRONT of the source search path.
2902 The path starts off empty. Source files that contain debug information
2903 about the directory in which they were compiled can be found even
2904 with an empty path; Sun CC and GCC include this information. If GDB can't
2905 find your source file in the current directory, type "dir .".
2907 * Configuring GDB for compilation
2909 For normal use, type ``./configure host''. See README or gdb.texinfo
2912 GDB now handles cross debugging. If you are remotely debugging between
2913 two different machines, type ``./configure host -target=targ''.
2914 Host is the machine where GDB will run; targ is the machine
2915 where the program that you are debugging will run.
projects / deliverable / binutils-gdb.git / blob