1 What has changed in GDB?
2 (Organized release by release)
4 *** Changes since GDB 6.5
10 * GDB can now be configured as a cross-debugger targeting native Windows
11 (mingw32) or Cygwin. It can communicate with a remote debugging stub
12 running on a Windows system over TCP/IP to debug Windows programs.
14 * The GDB remote stub, gdbserver, has been updated to support Windows and
15 Cygwin debugging. Both single-threaded and multi-threaded programs are
18 * The "set trust-readonly-sections" command works again. This command was
19 broken in GDB 6.3, 6.4, and 6.5.
21 * Support for GNU/Linux Thread Local Storage (TLS, per-thread variables) no
22 longer requires symbolic debug information (e.g. DWARF-2).
24 * The GDB remote stub, gdbserver, now has lower overhead for high
25 frequency signals (e.g. SIGALRM) via the QPassSignals packet.
32 Manage a list of substitution rules that GDB uses to rewrite the name
33 of the directories where the sources are located. This can be useful
34 for instance when the sources were moved to a different location
35 between compilation and debugging.
39 Print each CLI command as it is executed. Each command is prefixed with
40 a number of `+' symbols representing the nesting depth.
41 The source command now has a `-v' option to enable the same feature.
45 The ARM Demon monitor support (RDP protocol, "target rdp").
47 Kernel Object Display, an embedded debugging feature which only worked with
48 an obsolete version of Cisco IOS.
50 The 'set download-write-size' and 'show download-write-size' commands.
55 Tell a stub about GDB client features, and request remote target features.
56 The first feature implemented is PacketSize, which allows the target to
57 specify the size of packets it can handle - to minimize the number of
58 packets required and improve performance when connected to a remote
62 Fetch an OS auxilliary vector from the remote stub. This packet is a
63 more efficient replacement for qPart:auxv:read.
66 Ignore the specified signals; pass them directly to the debugged program
67 without stopping other threads or reporting them to GDB.
69 * Removed remote packets
72 This packet has been replaced by qXfer:auxv:read. Only GDB 6.4 and 6.5
73 used it, and only gdbserver implemented it.
75 *** Changes in GDB 6.5
79 Renesas M32C/M16C m32c-elf
81 Morpho Technologies ms1 ms1-elf
85 init-if-undefined Initialize a convenience variable, but
86 only if it doesn't already have a value.
88 The following commands are presently only implemented for native GNU/Linux:
90 checkpoint Save a snapshot of the program state.
92 restart <n> Return the program state to a
93 previously saved state.
95 info checkpoints List currently saved checkpoints.
97 delete-checkpoint <n> Delete a previously saved checkpoint.
99 set|show detach-on-fork Tell gdb whether to detach from a newly
100 forked process, or to keep debugging it.
102 info forks List forks of the user program that
103 are available to be debugged.
105 fork <n> Switch to debugging one of several
106 forks of the user program that are
107 available to be debugged.
109 delete-fork <n> Delete a fork from the list of forks
110 that are available to be debugged (and
111 kill the forked process).
113 detach-fork <n> Delete a fork from the list of forks
114 that are available to be debugged (and
115 allow the process to continue).
119 Morpho Technologies ms2 ms1-elf
121 * Improved Windows host support
123 GDB now builds as a cross debugger hosted on i686-mingw32, including
124 native console support, and remote communications using either
125 network sockets or serial ports.
127 * Improved Modula-2 language support
129 GDB can now print most types in the Modula-2 syntax. This includes:
130 basic types, set types, record types, enumerated types, range types,
131 pointer types and ARRAY types. Procedure var parameters are correctly
132 printed and hexadecimal addresses and character constants are also
133 written in the Modula-2 syntax. Best results can be obtained by using
134 GNU Modula-2 together with the -gdwarf-2 command line option.
138 The ARM rdi-share module.
140 The Netware NLM debug server.
142 *** Changes in GDB 6.4
144 * New native configurations
146 OpenBSD/arm arm*-*-openbsd*
147 OpenBSD/mips64 mips64-*-openbsd*
151 Morpho Technologies ms1 ms1-elf
153 * New command line options
155 --batch-silent As for --batch, but totally silent.
156 --return-child-result The debugger will exist with the same value
157 the child (debugged) program exited with.
158 --eval-command COMMAND, -ex COMMAND
159 Execute a single GDB CLI command. This may be
160 specified multiple times and in conjunction
161 with the --command (-x) option.
163 * Deprecated commands removed
165 The following commands, that were deprecated in 2000, have been
169 set|show arm disassembly-flavor set|show arm disassembler
170 othernames set arm disassembler
171 set|show remotedebug set|show debug remote
172 set|show archdebug set|show debug arch
173 set|show eventdebug set|show debug event
176 * New BSD user-level threads support
178 It is now possible to debug programs using the user-level threads
179 library on OpenBSD and FreeBSD. Currently supported (target)
182 FreeBSD/amd64 x86_64-*-freebsd*
183 FreeBSD/i386 i386-*-freebsd*
184 OpenBSD/i386 i386-*-openbsd*
186 Note that the new kernel threads libraries introduced in FreeBSD 5.x
187 are not yet supported.
189 * New support for Matsushita MN10300 w/sim added
190 (Work in progress). mn10300-elf.
192 * REMOVED configurations and files
194 VxWorks and the XDR protocol *-*-vxworks
195 Motorola MCORE mcore-*-*
196 National Semiconductor NS32000 ns32k-*-*
198 * New "set print array-indexes" command
200 After turning this setting "on", GDB prints the index of each element
201 when displaying arrays. The default is "off" to preserve the previous
204 * VAX floating point support
206 GDB now supports the not-quite-ieee VAX F and D floating point formats.
208 * User-defined command support
210 In addition to using $arg0..$arg9 for argument passing, it is now possible
211 to use $argc to determine now many arguments have been passed. See the
212 section on user-defined commands in the user manual for more information.
214 *** Changes in GDB 6.3:
216 * New command line option
218 GDB now accepts -l followed by a number to set the timeout for remote
221 * GDB works with GCC -feliminate-dwarf2-dups
223 GDB now supports a more compact representation of DWARF-2 debug
224 information using DW_FORM_ref_addr references. These are produced
225 by GCC with the option -feliminate-dwarf2-dups and also by some
226 proprietary compilers. With GCC, you must use GCC 3.3.4 or later
227 to use -feliminate-dwarf2-dups.
229 * Internationalization
231 When supported by the host system, GDB will be built with
232 internationalization (libintl). The task of marking up the sources is
233 continued, we're looking forward to our first translation.
237 Initial support for debugging programs compiled with the GNAT
238 implementation of the Ada programming language has been integrated
239 into GDB. In this release, support is limited to expression evaluation.
241 * New native configurations
243 GNU/Linux/m32r m32r-*-linux-gnu
247 GDB's remote protocol now includes support for the 'p' packet. This
248 packet is used to fetch individual registers from a remote inferior.
250 * END-OF-LIFE registers[] compatibility module
252 GDB's internal register infrastructure has been completely rewritten.
253 The new infrastructure making possible the implementation of key new
254 features including 32x64 (e.g., 64-bit amd64 GDB debugging a 32-bit
257 GDB 6.3 will be the last release to include the the registers[]
258 compatibility module that allowed out-of-date configurations to
259 continue to work. This change directly impacts the following
271 Unless there is activity to revive these configurations, they will be
272 made OBSOLETE in GDB 6.4, and REMOVED from GDB 6.5.
274 * OBSOLETE configurations and files
276 Configurations that have been declared obsolete in this release have
277 been commented out. Unless there is activity to revive these
278 configurations, the next release of GDB will have their sources
288 *** Changes in GDB 6.2.1:
290 * MIPS `break main; run' gave an heuristic-fence-post warning
292 When attempting to run even a simple program, a warning about
293 heuristic-fence-post being hit would be reported. This problem has
296 * MIPS IRIX 'long double' crashed GDB
298 When examining a long double variable, GDB would get a segmentation
299 fault. The crash has been fixed (but GDB 6.2 cannot correctly examine
300 IRIX long double values).
304 A bug in the VAX stack code was causing problems with the "next"
305 command. This problem has been fixed.
307 *** Changes in GDB 6.2:
309 * Fix for ``many threads''
311 On GNU/Linux systems that use the NPTL threads library, a program
312 rapidly creating and deleting threads would confuse GDB leading to the
315 ptrace: No such process.
316 thread_db_get_info: cannot get thread info: generic error
318 This problem has been fixed.
320 * "-async" and "-noasync" options removed.
322 Support for the broken "-noasync" option has been removed (it caused
325 * New ``start'' command.
327 This command runs the program until the begining of the main procedure.
329 * New BSD Kernel Data Access Library (libkvm) interface
331 Using ``target kvm'' it is now possible to debug kernel core dumps and
332 live kernel memory images on various FreeBSD, NetBSD and OpenBSD
333 platforms. Currently supported (native-only) configurations are:
335 FreeBSD/amd64 x86_64-*-freebsd*
336 FreeBSD/i386 i?86-*-freebsd*
337 NetBSD/i386 i?86-*-netbsd*
338 NetBSD/m68k m68*-*-netbsd*
339 NetBSD/sparc sparc-*-netbsd*
340 OpenBSD/amd64 x86_64-*-openbsd*
341 OpenBSD/i386 i?86-*-openbsd*
342 OpenBSD/m68k m68*-openbsd*
343 OpenBSD/sparc sparc-*-openbsd*
345 * Signal trampoline code overhauled
347 Many generic problems with GDB's signal handling code have been fixed.
348 These include: backtraces through non-contiguous stacks; recognition
349 of sa_sigaction signal trampolines; backtrace from a NULL pointer
350 call; backtrace through a signal trampoline; step into and out of
351 signal handlers; and single-stepping in the signal trampoline.
353 Please note that kernel bugs are a limiting factor here. These
354 features have been shown to work on an s390 GNU/Linux system that
355 include a 2.6.8-rc1 kernel. Ref PR breakpoints/1702.
357 * Cygwin support for DWARF 2 added.
359 * New native configurations
361 GNU/Linux/hppa hppa*-*-linux*
362 OpenBSD/hppa hppa*-*-openbsd*
363 OpenBSD/m68k m68*-*-openbsd*
364 OpenBSD/m88k m88*-*-openbsd*
365 OpenBSD/powerpc powerpc-*-openbsd*
366 NetBSD/vax vax-*-netbsd*
367 OpenBSD/vax vax-*-openbsd*
369 * END-OF-LIFE frame compatibility module
371 GDB's internal frame infrastructure has been completely rewritten.
372 The new infrastructure making it possible to support key new features
373 including DWARF 2 Call Frame Information. To aid in the task of
374 migrating old configurations to this new infrastructure, a
375 compatibility module, that allowed old configurations to continue to
376 work, was also included.
378 GDB 6.2 will be the last release to include this frame compatibility
379 module. This change directly impacts the following configurations:
389 Unless there is activity to revive these configurations, they will be
390 made OBSOLETE in GDB 6.3, and REMOVED from GDB 6.4.
392 * REMOVED configurations and files
394 Sun 3, running SunOS 3 m68*-*-sunos3*
395 Sun 3, running SunOS 4 m68*-*-sunos4*
396 Sun 2, running SunOS 3 m68000-*-sunos3*
397 Sun 2, running SunOS 4 m68000-*-sunos4*
398 Motorola 680x0 running LynxOS m68*-*-lynxos*
399 AT&T 3b1/Unix pc m68*-att-*
400 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
401 decstation mips-dec-* mips-little-*
402 riscos mips-*-riscos* mips-*-sysv*
404 sysv mips*-*-sysv4* (IRIX 5/6 not included)
406 *** Changes in GDB 6.1.1:
408 * TUI (Text-mode User Interface) built-in (also included in GDB 6.1)
410 The TUI (Text-mode User Interface) is now built as part of a default
411 GDB configuration. It is enabled by either selecting the TUI with the
412 command line option "-i=tui" or by running the separate "gdbtui"
413 program. For more information on the TUI, see the manual "Debugging
416 * Pending breakpoint support (also included in GDB 6.1)
418 Support has been added to allow you to specify breakpoints in shared
419 libraries that have not yet been loaded. If a breakpoint location
420 cannot be found, and the "breakpoint pending" option is set to auto,
421 GDB queries you if you wish to make the breakpoint pending on a future
422 shared-library load. If and when GDB resolves the breakpoint symbol,
423 the pending breakpoint is removed as one or more regular breakpoints
426 Pending breakpoints are very useful for GCJ Java debugging.
428 * Fixed ISO-C build problems
430 The files bfd/elf-bfd.h, gdb/dictionary.c and gdb/types.c contained
431 non ISO-C code that stopped them being built using a more strict ISO-C
432 compiler (e.g., IBM's C compiler).
434 * Fixed build problem on IRIX 5
436 Due to header problems with <sys/proc.h>, the file gdb/proc-api.c
437 wasn't able to compile compile on an IRIX 5 system.
439 * Added execute permission to gdb/gdbserver/configure
441 The shell script gdb/testsuite/gdb.stabs/configure lacked execute
442 permission. This bug would cause configure to fail on a number of
443 systems (Solaris, IRIX). Ref: server/519.
445 * Fixed build problem on hpux2.0w-hp-hpux11.00 using the HP ANSI C compiler
447 Older HPUX ANSI C compilers did not accept variable array sizes. somsolib.c
448 has been updated to use constant array sizes.
450 * Fixed a panic in the DWARF Call Frame Info code on Solaris 2.7
452 GCC 3.3.2, on Solaris 2.7, includes the DW_EH_PE_funcrel encoding in
453 its generated DWARF Call Frame Info. This encoding was causing GDB to
454 panic, that panic has been fixed. Ref: gdb/1628.
456 * Fixed a problem when examining parameters in shared library code.
458 When examining parameters in optimized shared library code generated
459 by a mainline GCC, GDB would incorrectly report ``Variable "..." is
460 not available''. GDB now correctly displays the variable's value.
462 *** Changes in GDB 6.1:
464 * Removed --with-mmalloc
466 Support for the mmalloc memory manager has been removed, as it
467 conflicted with the internal gdb byte cache.
469 * Changes in AMD64 configurations
471 The AMD64 target now includes the %cs and %ss registers. As a result
472 the AMD64 remote protocol has changed; this affects the floating-point
473 and SSE registers. If you rely on those registers for your debugging,
474 you should upgrade gdbserver on the remote side.
476 * Revised SPARC target
478 The SPARC target has been completely revised, incorporating the
479 FreeBSD/sparc64 support that was added for GDB 6.0. As a result
480 support for LynxOS and SunOS 4 has been dropped. Calling functions
481 from within GDB on operating systems with a non-executable stack
482 (Solaris, OpenBSD) now works.
486 GDB has a new C++ demangler which does a better job on the mangled
487 names generated by current versions of g++. It also runs faster, so
488 with this and other changes gdb should now start faster on large C++
491 * DWARF 2 Location Expressions
493 GDB support for location expressions has been extended to support function
494 arguments and frame bases. Older versions of GDB could crash when they
497 * C++ nested types and namespaces
499 GDB's support for nested types and namespaces in C++ has been
500 improved, especially if you use the DWARF 2 debugging format. (This
501 is the default for recent versions of GCC on most platforms.)
502 Specifically, if you have a class "Inner" defined within a class or
503 namespace "Outer", then GDB realizes that the class's name is
504 "Outer::Inner", not simply "Inner". This should greatly reduce the
505 frequency of complaints about not finding RTTI symbols. In addition,
506 if you are stopped at inside of a function defined within a namespace,
507 GDB modifies its name lookup accordingly.
509 * New native configurations
511 NetBSD/amd64 x86_64-*-netbsd*
512 OpenBSD/amd64 x86_64-*-openbsd*
513 OpenBSD/alpha alpha*-*-openbsd*
514 OpenBSD/sparc sparc-*-openbsd*
515 OpenBSD/sparc64 sparc64-*-openbsd*
517 * New debugging protocols
519 M32R with SDI protocol m32r-*-elf*
521 * "set prompt-escape-char" command deleted.
523 The command "set prompt-escape-char" has been deleted. This command,
524 and its very obscure effet on GDB's prompt, was never documented,
525 tested, nor mentioned in the NEWS file.
527 * OBSOLETE configurations and files
529 Configurations that have been declared obsolete in this release have
530 been commented out. Unless there is activity to revive these
531 configurations, the next release of GDB will have their sources
534 Sun 3, running SunOS 3 m68*-*-sunos3*
535 Sun 3, running SunOS 4 m68*-*-sunos4*
536 Sun 2, running SunOS 3 m68000-*-sunos3*
537 Sun 2, running SunOS 4 m68000-*-sunos4*
538 Motorola 680x0 running LynxOS m68*-*-lynxos*
539 AT&T 3b1/Unix pc m68*-att-*
540 Bull DPX2 (68k, System V release 3) m68*-bull-sysv*
541 decstation mips-dec-* mips-little-*
542 riscos mips-*-riscos* mips-*-sysv*
544 sysv mips*-*-sysv4* (IRIX 5/6 not included)
546 * REMOVED configurations and files
548 SGI Irix-4.x mips-sgi-irix4 or iris4
549 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
550 Z8000 simulator z8k-zilog-none or z8ksim
551 Matsushita MN10200 w/simulator mn10200-*-*
552 H8/500 simulator h8500-hitachi-hms or h8500hms
553 HP/PA running BSD hppa*-*-bsd*
554 HP/PA running OSF/1 hppa*-*-osf*
555 HP/PA Pro target hppa*-*-pro*
556 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
557 386BSD i[3456]86-*-bsd*
558 Sequent family i[3456]86-sequent-sysv4*
559 i[3456]86-sequent-sysv*
560 i[3456]86-sequent-bsd*
561 SPARC running LynxOS sparc-*-lynxos*
562 SPARC running SunOS 4 sparc-*-sunos4*
563 Tsqware Sparclet sparclet-*-*
564 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
566 *** Changes in GDB 6.0:
570 Support for debugging the Objective-C programming language has been
573 * New backtrace mechanism (includes DWARF 2 Call Frame Information).
575 DWARF 2's Call Frame Information makes available compiler generated
576 information that more exactly describes the program's run-time stack.
577 By using this information, GDB is able to provide more robust stack
580 The i386, amd64 (nee, x86-64), Alpha, m68hc11, ia64, and m32r targets
581 have been updated to use a new backtrace mechanism which includes
586 GDB's remote protocol has been extended to include support for hosted
587 file I/O (where the remote target uses GDB's file system). See GDB's
588 remote protocol documentation for details.
590 * All targets using the new architecture framework.
592 All of GDB's targets have been updated to use the new internal
593 architecture framework. The way is now open for future GDB releases
594 to include cross-architecture native debugging support (i386 on amd64,
597 * GNU/Linux's Thread Local Storage (TLS)
599 GDB now includes support for for the GNU/Linux implementation of
600 per-thread variables.
602 * GNU/Linux's Native POSIX Thread Library (NPTL)
604 GDB's thread code has been updated to work with either the new
605 GNU/Linux NPTL thread library or the older "LinuxThreads" library.
607 * Separate debug info.
609 GDB, in conjunction with BINUTILS, now supports a mechanism for
610 automatically loading debug information from a separate file. Instead
611 of shipping full debug and non-debug versions of system libraries,
612 system integrators can now instead ship just the stripped libraries
613 and optional debug files.
615 * DWARF 2 Location Expressions
617 DWARF 2 Location Expressions allow the compiler to more completely
618 describe the location of variables (even in optimized code) to the
621 GDB now includes preliminary support for location expressions (support
622 for DW_OP_piece is still missing).
626 A number of long standing bugs that caused GDB to die while starting a
627 Java application have been fixed. GDB's Java support is now
628 considered "useable".
630 * GNU/Linux support for fork, vfork, and exec.
632 The "catch fork", "catch exec", "catch vfork", and "set follow-fork-mode"
633 commands are now implemented for GNU/Linux. They require a 2.5.x or later
636 * GDB supports logging output to a file
638 There are two new commands, "set logging" and "show logging", which can be
639 used to capture GDB's output to a file.
641 * The meaning of "detach" has changed for gdbserver
643 The "detach" command will now resume the application, as documented. To
644 disconnect from gdbserver and leave it stopped, use the new "disconnect"
647 * d10v, m68hc11 `regs' command deprecated
649 The `info registers' command has been updated so that it displays the
650 registers using a format identical to the old `regs' command.
654 A new command, "maint set profile on/off", has been added. This command can
655 be used to enable or disable profiling while running GDB, to profile a
656 session or a set of commands. In addition there is a new configure switch,
657 "--enable-profiling", which will cause GDB to be compiled with profiling
658 data, for more informative profiling results.
660 * Default MI syntax changed to "mi2".
662 The default MI (machine interface) syntax, enabled by the command line
663 option "-i=mi", has been changed to "mi2". The previous MI syntax,
664 "mi1", can be enabled by specifying the option "-i=mi1".
666 Support for the original "mi0" syntax (included in GDB 5.0) has been
669 Fix for gdb/192: removed extraneous space when displaying frame level.
670 Fix for gdb/672: update changelist is now output in mi list format.
671 Fix for gdb/702: a -var-assign that updates the value now shows up
672 in a subsequent -var-update.
674 * New native configurations.
676 FreeBSD/amd64 x86_64-*-freebsd*
678 * Multi-arched targets.
680 HP/PA HPUX11 hppa*-*-hpux*
681 Renesas M32R/D w/simulator m32r-*-elf*
683 * OBSOLETE configurations and files
685 Configurations that have been declared obsolete in this release have
686 been commented out. Unless there is activity to revive these
687 configurations, the next release of GDB will have their sources
690 Z8000 simulator z8k-zilog-none or z8ksim
691 Matsushita MN10200 w/simulator mn10200-*-*
692 H8/500 simulator h8500-hitachi-hms or h8500hms
693 HP/PA running BSD hppa*-*-bsd*
694 HP/PA running OSF/1 hppa*-*-osf*
695 HP/PA Pro target hppa*-*-pro*
696 PMAX (MIPS) running Mach 3.0 mips*-*-mach3*
697 Sequent family i[3456]86-sequent-sysv4*
698 i[3456]86-sequent-sysv*
699 i[3456]86-sequent-bsd*
700 Tsqware Sparclet sparclet-*-*
701 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
703 * REMOVED configurations and files
706 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
707 IBM AIX PS/2 i[3456]86-*-aix
708 i386 running Mach 3.0 i[3456]86-*-mach3*
709 i386 running Mach i[3456]86-*-mach*
710 i386 running OSF/1 i[3456]86-*osf1mk*
711 HP/Apollo 68k Family m68*-apollo*-sysv*,
713 m68*-hp-bsd*, m68*-hp-hpux*
714 Argonaut Risc Chip (ARC) arc-*-*
715 Mitsubishi D30V d30v-*-*
716 Fujitsu FR30 fr30-*-elf*
717 OS/9000 i[34]86-*-os9k
718 I960 with MON960 i960-*-coff
720 * MIPS $fp behavior changed
722 The convenience variable $fp, for the MIPS, now consistently returns
723 the address of the current frame's base. Previously, depending on the
724 context, $fp could refer to either $sp or the current frame's base
725 address. See ``8.10 Registers'' in the manual ``Debugging with GDB:
726 The GNU Source-Level Debugger''.
728 *** Changes in GDB 5.3:
730 * GNU/Linux shared library multi-threaded performance improved.
732 When debugging a multi-threaded application on GNU/Linux, GDB now uses
733 `/proc', in preference to `ptrace' for memory reads. This may result
734 in an improvement in the start-up time of multi-threaded, shared
735 library applications when run under GDB. One GDB user writes: ``loads
736 shared libs like mad''.
738 * ``gdbserver'' now supports multi-threaded applications on some targets
740 Support for debugging multi-threaded applications which use
741 the GNU/Linux LinuxThreads package has been added for
742 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
743 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
745 * GDB now supports C/C++ preprocessor macros.
747 GDB now expands preprocessor macro invocations in C/C++ expressions,
748 and provides various commands for showing macro definitions and how
751 The new command `macro expand EXPRESSION' expands any macro
752 invocations in expression, and shows the result.
754 The new command `show macro MACRO-NAME' shows the definition of the
755 macro named MACRO-NAME, and where it was defined.
757 Most compilers don't include information about macros in the debugging
758 information by default. In GCC 3.1, for example, you need to compile
759 your program with the options `-gdwarf-2 -g3'. If the macro
760 information is present in the executable, GDB will read it.
762 * Multi-arched targets.
764 DEC Alpha (partial) alpha*-*-*
765 DEC VAX (partial) vax-*-*
767 National Semiconductor NS32000 (partial) ns32k-*-*
768 Motorola 68000 (partial) m68k-*-*
769 Motorola MCORE mcore-*-*
773 Fujitsu FRV architecture added by Red Hat frv*-*-*
776 * New native configurations
778 Alpha NetBSD alpha*-*-netbsd*
779 SH NetBSD sh*-*-netbsdelf*
780 MIPS NetBSD mips*-*-netbsd*
781 UltraSPARC NetBSD sparc64-*-netbsd*
783 * OBSOLETE configurations and files
785 Configurations that have been declared obsolete in this release have
786 been commented out. Unless there is activity to revive these
787 configurations, the next release of GDB will have their sources
790 Mitsubishi D30V d30v-*-*
791 OS/9000 i[34]86-*-os9k
792 IBM AIX PS/2 i[3456]86-*-aix
793 Fujitsu FR30 fr30-*-elf*
794 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
795 Argonaut Risc Chip (ARC) arc-*-*
796 i386 running Mach 3.0 i[3456]86-*-mach3*
797 i386 running Mach i[3456]86-*-mach*
798 i386 running OSF/1 i[3456]86-*osf1mk*
799 HP/Apollo 68k Family m68*-apollo*-sysv*,
801 m68*-hp-bsd*, m68*-hp-hpux*
802 I960 with MON960 i960-*-coff
806 CHILL, a Pascal like language used by telecommunications companies.
808 * REMOVED configurations and files
810 AMD 29k family via UDI a29k-amd-udi, udi29k
811 A29K VxWorks a29k-*-vxworks
812 AMD 29000 embedded, using EBMON a29k-none-none
813 AMD 29000 embedded with COFF a29k-none-coff
814 AMD 29000 embedded with a.out a29k-none-aout
816 testsuite/gdb.hp/gdb.threads-hp/ directory
818 * New command "set max-user-call-depth <nnn>"
820 This command allows the user to limit the call depth of user-defined
821 commands. The default is 1024.
823 * Changes in FreeBSD/i386 native debugging.
825 Support for the "generate-core-file" has been added.
827 * New commands "dump", "append", and "restore".
829 These commands allow data to be copied from target memory
830 to a bfd-format or binary file (dump and append), and back
831 from a file into memory (restore).
833 * Improved "next/step" support on multi-processor Alpha Tru64.
835 The previous single-step mechanism could cause unpredictable problems,
836 including the random appearance of SIGSEGV or SIGTRAP signals. The use
837 of a software single-step mechanism prevents this.
839 *** Changes in GDB 5.2.1:
847 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
848 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
849 Fix, by Joel Brobecker imported from mainline.
851 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
852 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
853 Fix, by Fred Fish, imported from mainline.
855 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
856 Surprisingly enough, it works now.
857 By Michal Ludvig, imported from mainline.
859 i386 hardware watchpoint support:
860 avoid misses on second run for some targets.
861 By Pierre Muller, imported from mainline.
863 *** Changes in GDB 5.2:
865 * New command "set trust-readonly-sections on[off]".
867 This command is a hint that tells gdb that read-only sections
868 really are read-only (ie. that their contents will not change).
869 In this mode, gdb will go to the object file rather than the
870 target to read memory from read-only sections (such as ".text").
871 This can be a significant performance improvement on some
872 (notably embedded) targets.
874 * New command "generate-core-file" (or "gcore").
876 This new gdb command allows the user to drop a core file of the child
877 process state at any time. So far it's been implemented only for
878 GNU/Linux and Solaris, but should be relatively easily ported to other
879 hosts. Argument is core file name (defaults to core.<pid>).
881 * New command line option
883 GDB now accepts --pid or -p followed by a process id.
885 * Change in command line behavior -- corefiles vs. process ids.
887 There is a subtle behavior in the way in which GDB handles
888 command line arguments. The first non-flag argument is always
889 a program to debug, but the second non-flag argument may either
890 be a corefile or a process id. Previously, GDB would attempt to
891 open the second argument as a corefile, and if that failed, would
892 issue a superfluous error message and then attempt to attach it as
893 a process. Now, if the second argument begins with a non-digit,
894 it will be treated as a corefile. If it begins with a digit,
895 GDB will attempt to attach it as a process, and if no such process
896 is found, will then attempt to open it as a corefile.
898 * Changes in ARM configurations.
900 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
901 configuration is fully multi-arch.
903 * New native configurations
905 ARM NetBSD arm*-*-netbsd*
906 x86 OpenBSD i[3456]86-*-openbsd*
907 AMD x86-64 running GNU/Linux x86_64-*-linux-*
908 Sparc64 running FreeBSD sparc64-*-freebsd*
912 Sanyo XStormy16 xstormy16-elf
914 * OBSOLETE configurations and files
916 Configurations that have been declared obsolete in this release have
917 been commented out. Unless there is activity to revive these
918 configurations, the next release of GDB will have their sources
921 AMD 29k family via UDI a29k-amd-udi, udi29k
922 A29K VxWorks a29k-*-vxworks
923 AMD 29000 embedded, using EBMON a29k-none-none
924 AMD 29000 embedded with COFF a29k-none-coff
925 AMD 29000 embedded with a.out a29k-none-aout
927 testsuite/gdb.hp/gdb.threads-hp/ directory
929 * REMOVED configurations and files
931 TI TMS320C80 tic80-*-*
933 PowerPC Solaris powerpcle-*-solaris*
934 PowerPC Windows NT powerpcle-*-cygwin32
935 PowerPC Netware powerpc-*-netware*
936 Harris/CXUX m88k m88*-harris-cxux*
937 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
938 ns32k-utek-sysv* ns32k-utek-*
939 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
940 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
941 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
942 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
943 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
945 * Changes to command line processing
947 The new `--args' feature can be used to specify command-line arguments
948 for the inferior from gdb's command line.
950 * Changes to key bindings
952 There is a new `operate-and-get-next' function bound to `C-o'.
954 *** Changes in GDB 5.1.1
956 Fix compile problem on DJGPP.
958 Fix a problem with floating-point registers on the i386 being
961 Fix to stop GDB crashing on .debug_str debug info.
963 Numerous documentation fixes.
965 Numerous testsuite fixes.
967 *** Changes in GDB 5.1:
969 * New native configurations
971 Alpha FreeBSD alpha*-*-freebsd*
972 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
973 MIPS GNU/Linux mips*-*-linux*
974 MIPS SGI Irix 6.x mips*-sgi-irix6*
976 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
980 Motorola 68HC11 and 68HC12 m68hc11-elf
982 UltraSparc running GNU/Linux sparc64-*-linux*
984 * OBSOLETE configurations and files
986 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
987 Harris/CXUX m88k m88*-harris-cxux*
988 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
989 ns32k-utek-sysv* ns32k-utek-*
990 TI TMS320C80 tic80-*-*
992 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
993 PowerPC Solaris powerpcle-*-solaris*
994 PowerPC Windows NT powerpcle-*-cygwin32
995 PowerPC Netware powerpc-*-netware*
996 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
997 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
998 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
999 Apple Macintosh (MPW) host N/A
1001 stuff.c (Program to stuff files into a specially prepared space in kdb)
1002 kdb-start.c (Main loop for the standalone kernel debugger)
1004 Configurations that have been declared obsolete in this release have
1005 been commented out. Unless there is activity to revive these
1006 configurations, the next release of GDB will have their sources
1007 permanently REMOVED.
1009 * REMOVED configurations and files
1011 Altos 3068 m68*-altos-*
1012 Convex c1-*-*, c2-*-*
1014 ARM RISCix arm-*-* (as host)
1018 * GDB has been converted to ISO C.
1020 GDB's source code has been converted to ISO C. In particular, the
1021 sources are fully protoized, and rely on standard headers being
1026 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
1028 * The MI enabled by default.
1030 The new machine oriented interface (MI) introduced in GDB 5.0 has been
1031 revised and enabled by default. Packages which use GDB as a debugging
1032 engine behind a UI or another front end are encouraged to switch to
1033 using the GDB/MI interface, instead of the old annotations interface
1034 which is now deprecated.
1036 * Support for debugging Pascal programs.
1038 GDB now includes support for debugging Pascal programs. The following
1039 main features are supported:
1041 - Pascal-specific data types such as sets;
1043 - automatic recognition of Pascal sources based on file-name
1046 - Pascal-style display of data types, variables, and functions;
1048 - a Pascal expression parser.
1050 However, some important features are not yet supported.
1052 - Pascal string operations are not supported at all;
1054 - there are some problems with boolean types;
1056 - Pascal type hexadecimal constants are not supported
1057 because they conflict with the internal variables format;
1059 - support for Pascal objects and classes is not full yet;
1061 - unlike Pascal, GDB is case-sensitive for symbol names.
1063 * Changes in completion.
1065 Commands such as `shell', `run' and `set args', which pass arguments
1066 to inferior programs, now complete on file names, similar to what
1067 users expect at the shell prompt.
1069 Commands which accept locations, such as `disassemble', `print',
1070 `breakpoint', `until', etc. now complete on filenames as well as
1071 program symbols. Thus, if you type "break foob TAB", and the source
1072 files linked into the programs include `foobar.c', that file name will
1073 be one of the candidates for completion. However, file names are not
1074 considered for completion after you typed a colon that delimits a file
1075 name from a name of a function in that file, as in "break foo.c:bar".
1077 `set demangle-style' completes on available demangling styles.
1079 * New platform-independent commands:
1081 It is now possible to define a post-hook for a command as well as a
1082 hook that runs before the command. For more details, see the
1083 documentation of `hookpost' in the GDB manual.
1085 * Changes in GNU/Linux native debugging.
1087 Support for debugging multi-threaded programs has been completely
1088 revised for all platforms except m68k and sparc. You can now debug as
1089 many threads as your system allows you to have.
1091 Attach/detach is supported for multi-threaded programs.
1093 Support for SSE registers was added for x86. This doesn't work for
1094 multi-threaded programs though.
1096 * Changes in MIPS configurations.
1098 Multi-arch support is enabled for all MIPS configurations.
1100 GDB can now be built as native debugger on SGI Irix 6.x systems for
1101 debugging n32 executables. (Debugging 64-bit executables is not yet
1104 * Unified support for hardware watchpoints in all x86 configurations.
1106 Most (if not all) native x86 configurations support hardware-assisted
1107 breakpoints and watchpoints in a unified manner. This support
1108 implements debug register sharing between watchpoints, which allows to
1109 put a virtually infinite number of watchpoints on the same address,
1110 and also supports watching regions up to 16 bytes with several debug
1113 The new maintenance command `maintenance show-debug-regs' toggles
1114 debugging print-outs in functions that insert, remove, and test
1115 watchpoints and hardware breakpoints.
1117 * Changes in the DJGPP native configuration.
1119 New command ``info dos sysinfo'' displays assorted information about
1120 the CPU, OS, memory, and DPMI server.
1122 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
1123 display information about segment descriptors stored in GDT, LDT, and
1126 New commands ``info dos pde'' and ``info dos pte'' display entries
1127 from Page Directory and Page Tables (for now works with CWSDPMI only).
1128 New command ``info dos address-pte'' displays the Page Table entry for
1129 a given linear address.
1131 GDB can now pass command lines longer than 126 characters to the
1132 program being debugged (requires an update to the libdbg.a library
1133 which is part of the DJGPP development kit).
1135 DWARF2 debug info is now supported.
1137 It is now possible to `step' and `next' through calls to `longjmp'.
1139 * Changes in documentation.
1141 All GDB documentation was converted to GFDL, the GNU Free
1142 Documentation License.
1144 Tracepoints-related commands are now fully documented in the GDB
1147 TUI, the Text-mode User Interface, is now documented in the manual.
1149 Tracepoints-related commands are now fully documented in the GDB
1152 The "GDB Internals" manual now has an index. It also includes
1153 documentation of `ui_out' functions, GDB coding standards, x86
1154 hardware watchpoints, and memory region attributes.
1156 * GDB's version number moved to ``version.in''
1158 The Makefile variable VERSION has been replaced by the file
1159 ``version.in''. People creating GDB distributions should update the
1160 contents of this file.
1164 GUD support is now a standard part of the EMACS distribution.
1166 *** Changes in GDB 5.0:
1168 * Improved support for debugging FP programs on x86 targets
1170 Unified and much-improved support for debugging floating-point
1171 programs on all x86 targets. In particular, ``info float'' now
1172 displays the FP registers in the same format on all x86 targets, with
1173 greater level of detail.
1175 * Improvements and bugfixes in hardware-assisted watchpoints
1177 It is now possible to watch array elements, struct members, and
1178 bitfields with hardware-assisted watchpoints. Data-read watchpoints
1179 on x86 targets no longer erroneously trigger when the address is
1182 * Improvements in the native DJGPP version of GDB
1184 The distribution now includes all the scripts and auxiliary files
1185 necessary to build the native DJGPP version on MS-DOS/MS-Windows
1186 machines ``out of the box''.
1188 The DJGPP version can now debug programs that use signals. It is
1189 possible to catch signals that happened in the debuggee, deliver
1190 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
1191 would kill the program being debugged.) Programs that hook hardware
1192 interrupts (keyboard, timer, etc.) can also be debugged.
1194 It is now possible to debug DJGPP programs that redirect their
1195 standard handles or switch them to raw (as opposed to cooked) mode, or
1196 even close them. The command ``run < foo > bar'' works as expected,
1197 and ``info terminal'' reports useful information about the debuggee's
1198 terminal, including raw/cooked mode, redirection, etc.
1200 The DJGPP version now uses termios functions for console I/O, which
1201 enables debugging graphics programs. Interrupting GDB with Ctrl-C
1204 DOS-style file names with drive letters are now fully supported by
1207 It is now possible to debug DJGPP programs that switch their working
1208 directory. It is also possible to rerun the debuggee any number of
1209 times without restarting GDB; thus, you can use the same setup,
1210 breakpoints, etc. for many debugging sessions.
1212 * New native configurations
1214 ARM GNU/Linux arm*-*-linux*
1215 PowerPC GNU/Linux powerpc-*-linux*
1219 Motorola MCore mcore-*-*
1220 x86 VxWorks i[3456]86-*-vxworks*
1221 PowerPC VxWorks powerpc-*-vxworks*
1222 TI TMS320C80 tic80-*-*
1224 * OBSOLETE configurations
1226 Altos 3068 m68*-altos-*
1227 Convex c1-*-*, c2-*-*
1229 ARM RISCix arm-*-* (as host)
1232 Configurations that have been declared obsolete will be commented out,
1233 but the code will be left in place. If there is no activity to revive
1234 these configurations before the next release of GDB, the sources will
1235 be permanently REMOVED.
1237 * Gould support removed
1239 Support for the Gould PowerNode and NP1 has been removed.
1241 * New features for SVR4
1243 On SVR4 native platforms (such as Solaris), if you attach to a process
1244 without first loading a symbol file, GDB will now attempt to locate and
1245 load symbols from the running process's executable file.
1247 * Many C++ enhancements
1249 C++ support has been greatly improved. Overload resolution now works properly
1250 in almost all cases. RTTI support is on the way.
1252 * Remote targets can connect to a sub-program
1254 A popen(3) style serial-device has been added. This device starts a
1255 sub-process (such as a stand-alone simulator) and then communicates
1256 with that. The sub-program to run is specified using the syntax
1257 ``|<program> <args>'' vis:
1259 (gdb) set remotedebug 1
1260 (gdb) target extended-remote |mn10300-elf-sim program-args
1262 * MIPS 64 remote protocol
1264 A long standing bug in the mips64 remote protocol where by GDB
1265 expected certain 32 bit registers (ex SR) to be transfered as 32
1266 instead of 64 bits has been fixed.
1268 The command ``set remote-mips64-transfers-32bit-regs on'' has been
1269 added to provide backward compatibility with older versions of GDB.
1271 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
1273 The command ``set remotebinarydownload'' command has been replaced by
1274 ``set remote X-packet''. Other commands in ``set remote'' family
1275 include ``set remote P-packet''.
1277 * Breakpoint commands accept ranges.
1279 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
1280 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
1281 ``tracepoint passcount'' also accepts a range of tracepoints.
1283 * ``apropos'' command added.
1285 The ``apropos'' command searches through command names and
1286 documentation strings, printing out matches, making it much easier to
1287 try to find a command that does what you are looking for.
1291 A new machine oriented interface (MI) has been added to GDB. This
1292 interface is designed for debug environments running GDB as a separate
1293 process. This is part of the long term libGDB project. See the
1294 "GDB/MI" chapter of the GDB manual for further information. It can be
1295 enabled by configuring with:
1297 .../configure --enable-gdbmi
1299 *** Changes in GDB-4.18:
1301 * New native configurations
1303 HP-UX 10.20 hppa*-*-hpux10.20
1304 HP-UX 11.x hppa*-*-hpux11.0*
1305 M68K GNU/Linux m68*-*-linux*
1309 Fujitsu FR30 fr30-*-elf*
1310 Intel StrongARM strongarm-*-*
1311 Mitsubishi D30V d30v-*-*
1313 * OBSOLETE configurations
1315 Gould PowerNode, NP1 np1-*-*, pn-*-*
1317 Configurations that have been declared obsolete will be commented out,
1318 but the code will be left in place. If there is no activity to revive
1319 these configurations before the next release of GDB, the sources will
1320 be permanently REMOVED.
1324 As a compatibility experiment, GDB's source files buildsym.h and
1325 buildsym.c have been converted to pure standard C, no longer
1326 containing any K&R compatibility code. We believe that all systems in
1327 use today either come with a standard C compiler, or have a GCC port
1328 available. If this is not true, please report the affected
1329 configuration to bug-gdb@gnu.org immediately. See the README file for
1330 information about getting a standard C compiler if you don't have one
1335 GDB now uses readline 2.2.
1337 * set extension-language
1339 You can now control the mapping between filename extensions and source
1340 languages by using the `set extension-language' command. For instance,
1341 you can ask GDB to treat .c files as C++ by saying
1342 set extension-language .c c++
1343 The command `info extensions' lists all of the recognized extensions
1344 and their associated languages.
1346 * Setting processor type for PowerPC and RS/6000
1348 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
1349 you can use the `set processor' command to specify what variant of the
1350 PowerPC family you are debugging. The command
1354 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
1355 following PowerPC and RS6000 variants:
1357 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
1358 rs6000 IBM RS6000 ("POWER") architecture, user-level view
1360 403GC IBM PowerPC 403GC
1361 505 Motorola PowerPC 505
1362 860 Motorola PowerPC 860 or 850
1363 601 Motorola PowerPC 601
1364 602 Motorola PowerPC 602
1365 603 Motorola/IBM PowerPC 603 or 603e
1366 604 Motorola PowerPC 604 or 604e
1367 750 Motorola/IBM PowerPC 750 or 750
1369 At the moment, this command just tells GDB what to name the
1370 special-purpose processor registers. Since almost all the affected
1371 registers are inaccessible to user-level programs, this command is
1372 only useful for remote debugging in its present form.
1376 Thanks to a major code donation from Hewlett-Packard, GDB now has much
1377 more extensive support for HP-UX. Added features include shared
1378 library support, kernel threads and hardware watchpoints for 11.00,
1379 support for HP's ANSI C and C++ compilers, and a compatibility mode
1380 for xdb and dbx commands.
1384 HP's donation includes the new concept of catchpoints, which is a
1385 generalization of the old catch command. On HP-UX, it is now possible
1386 to catch exec, fork, and vfork, as well as library loading.
1388 This means that the existing catch command has changed; its first
1389 argument now specifies the type of catch to be set up. See the
1390 output of "help catch" for a list of catchpoint types.
1392 * Debugging across forks
1394 On HP-UX, you can choose which process to debug when a fork() happens
1399 HP has donated a curses-based terminal user interface (TUI). To get
1400 it, build with --enable-tui. Although this can be enabled for any
1401 configuration, at present it only works for native HP debugging.
1403 * GDB remote protocol additions
1405 A new protocol packet 'X' that writes binary data is now available.
1406 Default behavior is to try 'X', then drop back to 'M' if the stub
1407 fails to respond. The settable variable `remotebinarydownload'
1408 allows explicit control over the use of 'X'.
1410 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
1411 full 64-bit address. The command
1413 set remoteaddresssize 32
1415 can be used to revert to the old behaviour. For existing remote stubs
1416 the change should not be noticed, as the additional address information
1419 In order to assist in debugging stubs, you may use the maintenance
1420 command `packet' to send any text string to the stub. For instance,
1422 maint packet heythere
1424 sends the packet "$heythere#<checksum>". Note that it is very easy to
1425 disrupt a debugging session by sending the wrong packet at the wrong
1428 The compare-sections command allows you to compare section data on the
1429 target to what is in the executable file without uploading or
1430 downloading, by comparing CRC checksums.
1432 * Tracing can collect general expressions
1434 You may now collect general expressions at tracepoints. This requires
1435 further additions to the target-side stub; see tracepoint.c and
1436 doc/agentexpr.texi for further details.
1438 * mask-address variable for Mips
1440 For Mips targets, you may control the zeroing of the upper 32 bits of
1441 a 64-bit address by entering `set mask-address on'. This is mainly
1442 of interest to users of embedded R4xxx and R5xxx processors.
1444 * Higher serial baud rates
1446 GDB's serial code now allows you to specify baud rates 57600, 115200,
1447 230400, and 460800 baud. (Note that your host system may not be able
1448 to achieve all of these rates.)
1452 The i960 configuration now includes an initial implementation of a
1453 builtin simulator, contributed by Jim Wilson.
1456 *** Changes in GDB-4.17:
1458 * New native configurations
1460 Alpha GNU/Linux alpha*-*-linux*
1461 Unixware 2.x i[3456]86-unixware2*
1462 Irix 6.x mips*-sgi-irix6*
1463 PowerPC GNU/Linux powerpc-*-linux*
1464 PowerPC Solaris powerpcle-*-solaris*
1465 Sparc GNU/Linux sparc-*-linux*
1466 Motorola sysV68 R3V7.1 m68k-motorola-sysv
1470 Argonaut Risc Chip (ARC) arc-*-*
1471 Hitachi H8/300S h8300*-*-*
1472 Matsushita MN10200 w/simulator mn10200-*-*
1473 Matsushita MN10300 w/simulator mn10300-*-*
1474 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
1475 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
1476 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
1477 Mitsubishi D10V w/simulator d10v-*-*
1478 Mitsubishi M32R/D w/simulator m32r-*-elf*
1479 Tsqware Sparclet sparclet-*-*
1480 NEC V850 w/simulator v850-*-*
1482 * New debugging protocols
1484 ARM with RDI protocol arm*-*-*
1485 M68K with dBUG monitor m68*-*-{aout,coff,elf}
1486 DDB and LSI variants of PMON protocol mips*-*-*
1487 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
1488 PowerPC with SDS protocol powerpc{,le}-*-eabi
1489 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
1493 All configurations can now understand and use the DWARF 2 debugging
1494 format. The choice is automatic, if the symbol file contains DWARF 2
1499 GDB now includes basic Java language support. This support is
1500 only useful with Java compilers that produce native machine code.
1502 * solib-absolute-prefix and solib-search-path
1504 For SunOS and SVR4 shared libraries, you may now set the prefix for
1505 loading absolute shared library symbol files, and the search path for
1506 locating non-absolute shared library symbol files.
1508 * Live range splitting
1510 GDB can now effectively debug code for which GCC has performed live
1511 range splitting as part of its optimization. See gdb/doc/LRS for
1512 more details on the expected format of the stabs information.
1516 GDB's support for the GNU Hurd, including thread debugging, has been
1517 updated to work with current versions of the Hurd.
1521 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
1522 instruction set. ARM GDB automatically detects when Thumb
1523 instructions are in use, and adjusts disassembly and backtracing
1528 GDB's MIPS target configurations now handle the MIP16 16-bit
1533 GDB now includes support for overlays; if an executable has been
1534 linked such that multiple sections are based at the same address, GDB
1535 will decide which section to use for symbolic info. You can choose to
1536 control the decision manually, using overlay commands, or implement
1537 additional target-side support and use "overlay load-target" to bring
1538 in the overlay mapping. Do "help overlay" for more detail.
1542 The command "info symbol <address>" displays information about
1543 the symbol at the specified address.
1547 The standard remote protocol now includes an extension that allows
1548 asynchronous collection and display of trace data. This requires
1549 extensive support in the target-side debugging stub. Tracing mode
1550 includes a new interaction mode in GDB and new commands: see the
1551 file tracepoint.c for more details.
1555 Configurations for embedded MIPS now include a simulator contributed
1556 by Cygnus Solutions. The simulator supports the instruction sets
1557 of most MIPS variants.
1561 Sparc configurations may now include the ERC32 simulator contributed
1562 by the European Space Agency. The simulator is not built into
1563 Sparc targets by default; configure with --enable-sim to include it.
1567 For target configurations that may include multiple variants of a
1568 basic architecture (such as MIPS and SH), you may now set the
1569 architecture explicitly. "set arch" sets, "info arch" lists
1570 the possible architectures.
1572 *** Changes in GDB-4.16:
1574 * New native configurations
1576 Windows 95, x86 Windows NT i[345]86-*-cygwin32
1577 M68K NetBSD m68k-*-netbsd*
1578 PowerPC AIX 4.x powerpc-*-aix*
1579 PowerPC MacOS powerpc-*-macos*
1580 PowerPC Windows NT powerpcle-*-cygwin32
1581 RS/6000 AIX 4.x rs6000-*-aix4*
1585 ARM with RDP protocol arm-*-*
1586 I960 with MON960 i960-*-coff
1587 MIPS VxWorks mips*-*-vxworks*
1588 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
1589 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
1591 Matra Sparclet sparclet-*-*
1595 The powerpc-eabi configuration now includes the PSIM simulator,
1596 contributed by Andrew Cagney, with assistance from Mike Meissner.
1597 PSIM is a very elaborate model of the PowerPC, including not only
1598 basic instruction set execution, but also details of execution unit
1599 performance and I/O hardware. See sim/ppc/README for more details.
1603 GDB now works with Solaris 2.5.
1605 * Windows 95/NT native
1607 GDB will now work as a native debugger on Windows 95 and Windows NT.
1608 To build it from source, you must use the "gnu-win32" environment,
1609 which uses a DLL to emulate enough of Unix to run the GNU tools.
1610 Further information, binaries, and sources are available at
1611 ftp.cygnus.com, under pub/gnu-win32.
1613 * dont-repeat command
1615 If a user-defined command includes the command `dont-repeat', then the
1616 command will not be repeated if the user just types return. This is
1617 useful if the command is time-consuming to run, so that accidental
1618 extra keystrokes don't run the same command many times.
1620 * Send break instead of ^C
1622 The standard remote protocol now includes an option to send a break
1623 rather than a ^C to the target in order to interrupt it. By default,
1624 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
1626 * Remote protocol timeout
1628 The standard remote protocol includes a new variable `remotetimeout'
1629 that allows you to set the number of seconds before GDB gives up trying
1630 to read from the target. The default value is 2.
1632 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
1634 By default GDB will automatically keep track of objects as they are
1635 loaded and unloaded by the dynamic linker. By using the command `set
1636 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
1637 when shared library events occur, thus allowing you to set breakpoints
1638 in shared libraries which are explicitly loaded by the inferior.
1640 Note this feature does not work on hpux8. On hpux9 you must link
1641 /usr/lib/end.o into your program. This feature should work
1642 automatically on hpux10.
1644 * Irix 5.x hardware watchpoint support
1646 Irix 5 configurations now support the use of hardware watchpoints.
1648 * Mips protocol "SYN garbage limit"
1650 When debugging a Mips target using the `target mips' protocol, you
1651 may set the number of characters that GDB will ignore by setting
1652 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
1653 every character. The default value is 1050.
1655 * Recording and replaying remote debug sessions
1657 If you set `remotelogfile' to the name of a file, gdb will write to it
1658 a recording of a remote debug session. This recording may then be
1659 replayed back to gdb using "gdbreplay". See gdbserver/README for
1660 details. This is useful when you have a problem with GDB while doing
1661 remote debugging; you can make a recording of the session and send it
1662 to someone else, who can then recreate the problem.
1664 * Speedups for remote debugging
1666 GDB includes speedups for downloading and stepping MIPS systems using
1667 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
1668 and more efficient S-record downloading.
1670 * Memory use reductions and statistics collection
1672 GDB now uses less memory and reports statistics about memory usage.
1673 Try the `maint print statistics' command, for example.
1675 *** Changes in GDB-4.15:
1677 * Psymtabs for XCOFF
1679 The symbol reader for AIX GDB now uses partial symbol tables. This
1680 can greatly improve startup time, especially for large executables.
1682 * Remote targets use caching
1684 Remote targets now use a data cache to speed up communication with the
1685 remote side. The data cache could lead to incorrect results because
1686 it doesn't know about volatile variables, thus making it impossible to
1687 debug targets which use memory mapped I/O devices. `set remotecache
1688 off' turns the the data cache off.
1690 * Remote targets may have threads
1692 The standard remote protocol now includes support for multiple threads
1693 in the target system, using new protocol commands 'H' and 'T'. See
1694 gdb/remote.c for details.
1698 If GDB is configured with `--enable-netrom', then it will include
1699 support for the NetROM ROM emulator from XLNT Designs. The NetROM
1700 acts as though it is a bank of ROM on the target board, but you can
1701 write into it over the network. GDB's support consists only of
1702 support for fast loading into the emulated ROM; to debug, you must use
1703 another protocol, such as standard remote protocol. The usual
1704 sequence is something like
1706 target nrom <netrom-hostname>
1708 target remote <netrom-hostname>:1235
1712 GDB now includes support for the Apple Macintosh, as a host only. It
1713 may be run as either an MPW tool or as a standalone application, and
1714 it can debug through the serial port. All the usual GDB commands are
1715 available, but to the target command, you must supply "serial" as the
1716 device type instead of "/dev/ttyXX". See mpw-README in the main
1717 directory for more information on how to build. The MPW configuration
1718 scripts */mpw-config.in support only a few targets, and only the
1719 mips-idt-ecoff target has been tested.
1723 GDB configuration now uses autoconf. This is not user-visible,
1724 but does simplify configuration and building.
1728 GDB now supports hpux10.
1730 *** Changes in GDB-4.14:
1732 * New native configurations
1734 x86 FreeBSD i[345]86-*-freebsd
1735 x86 NetBSD i[345]86-*-netbsd
1736 NS32k NetBSD ns32k-*-netbsd
1737 Sparc NetBSD sparc-*-netbsd
1741 A29K VxWorks a29k-*-vxworks
1742 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1743 CPU32 EST-300 emulator m68*-*-est*
1744 PowerPC ELF powerpc-*-elf
1747 * Alpha OSF/1 support for procfs
1749 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1750 possible to attach to running processes. As the mounting of the /proc
1751 filesystem is optional on the Alpha, GDB automatically determines
1752 the availability of /proc during startup. This can lead to problems
1753 if /proc is unmounted after GDB has been started.
1755 * Arguments to user-defined commands
1757 User commands may accept up to 10 arguments separated by whitespace.
1758 Arguments are accessed within the user command via $arg0..$arg9. A
1761 print $arg0 + $arg1 + $arg2
1763 To execute the command use:
1766 Defines the command "adder" which prints the sum of its three arguments.
1767 Note the arguments are text substitutions, so they may reference variables,
1768 use complex expressions, or even perform inferior function calls.
1770 * New `if' and `while' commands
1772 This makes it possible to write more sophisticated user-defined
1773 commands. Both commands take a single argument, which is the
1774 expression to evaluate, and must be followed by the commands to
1775 execute, one per line, if the expression is nonzero, the list being
1776 terminated by the word `end'. The `if' command list may include an
1777 `else' word, which causes the following commands to be executed only
1778 if the expression is zero.
1780 * Fortran source language mode
1782 GDB now includes partial support for Fortran 77. It will recognize
1783 Fortran programs and can evaluate a subset of Fortran expressions, but
1784 variables and functions may not be handled correctly. GDB will work
1785 with G77, but does not yet know much about symbols emitted by other
1788 * Better HPUX support
1790 Most debugging facilities now work on dynamic executables for HPPAs
1791 running hpux9 or later. You can attach to running dynamically linked
1792 processes, but by default the dynamic libraries will be read-only, so
1793 for instance you won't be able to put breakpoints in them. To change
1794 that behavior do the following before running the program:
1800 This will cause the libraries to be mapped private and read-write.
1801 To revert to the normal behavior, do this:
1807 You cannot set breakpoints or examine data in the library until after
1808 the library is loaded if the function/data symbols do not have
1811 GDB can now also read debug symbols produced by the HP C compiler on
1812 HPPAs (sorry, no C++, Fortran or 68k support).
1814 * Target byte order now dynamically selectable
1816 You can choose which byte order to use with a target system, via the
1817 commands "set endian big" and "set endian little", and you can see the
1818 current setting by using "show endian". You can also give the command
1819 "set endian auto", in which case GDB will use the byte order
1820 associated with the executable. Currently, only embedded MIPS
1821 configurations support dynamic selection of target byte order.
1823 * New DOS host serial code
1825 This version uses DPMI interrupts to handle buffered I/O, so you
1826 no longer need to run asynctsr when debugging boards connected to
1829 *** Changes in GDB-4.13:
1831 * New "complete" command
1833 This lists all the possible completions for the rest of the line, if it
1834 were to be given as a command itself. This is intended for use by emacs.
1836 * Trailing space optional in prompt
1838 "set prompt" no longer adds a space for you after the prompt you set. This
1839 allows you to set a prompt which ends in a space or one that does not.
1841 * Breakpoint hit counts
1843 "info break" now displays a count of the number of times the breakpoint
1844 has been hit. This is especially useful in conjunction with "ignore"; you
1845 can ignore a large number of breakpoint hits, look at the breakpoint info
1846 to see how many times the breakpoint was hit, then run again, ignoring one
1847 less than that number, and this will get you quickly to the last hit of
1850 * Ability to stop printing at NULL character
1852 "set print null-stop" will cause GDB to stop printing the characters of
1853 an array when the first NULL is encountered. This is useful when large
1854 arrays actually contain only short strings.
1856 * Shared library breakpoints
1858 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1859 breakpoints in shared libraries before the executable is run.
1861 * Hardware watchpoints
1863 There is a new hardware breakpoint for the watch command for sparclite
1864 targets. See gdb/sparclite/hw_breakpoint.note.
1866 Hardware watchpoints are also now supported under GNU/Linux.
1870 Annotations have been added. These are for use with graphical interfaces,
1871 and are still experimental. Currently only gdba.el uses these.
1873 * Improved Irix 5 support
1875 GDB now works properly with Irix 5.2.
1877 * Improved HPPA support
1879 GDB now works properly with the latest GCC and GAS.
1881 * New native configurations
1883 Sequent PTX4 i[34]86-sequent-ptx4
1884 HPPA running OSF/1 hppa*-*-osf*
1885 Atari TT running SVR4 m68*-*-sysv4*
1886 RS/6000 LynxOS rs6000-*-lynxos*
1890 OS/9000 i[34]86-*-os9k
1891 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1894 * Hitachi SH7000 and E7000-PC ICE support
1896 There is now support for communicating with the Hitachi E7000-PC ICE.
1897 This is available automatically when GDB is configured for the SH.
1901 As usual, a variety of small fixes and improvements, both generic
1902 and configuration-specific. See the ChangeLog for more detail.
1904 *** Changes in GDB-4.12:
1906 * Irix 5 is now supported
1910 GDB-4.12 on the HPPA has a number of changes which make it unable
1911 to debug the output from the currently released versions of GCC and
1912 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1913 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1914 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1917 *** Changes in GDB-4.11:
1919 * User visible changes:
1923 The "set remotedebug" option is now consistent between the mips remote
1924 target, remote targets using the gdb-specific protocol, UDI (AMD's
1925 debug protocol for the 29k) and the 88k bug monitor. It is now an
1926 integer specifying a debug level (normally 0 or 1, but 2 means more
1927 debugging info for the mips target).
1929 * DEC Alpha native support
1931 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1932 debug info, but GDB works fairly well with the DEC compiler and should
1933 work with a future GCC release. See the README file for a few
1934 Alpha-specific notes.
1936 * Preliminary thread implementation
1938 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1940 * LynxOS native and target support for 386
1942 This release has been hosted on LynxOS 2.2, and also can be configured
1943 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1946 * Improvements in C++ mangling/demangling.
1948 This release has much better g++ debugging, specifically in name
1949 mangling/demangling, virtual function calls, print virtual table,
1950 call methods, ...etc.
1952 *** Changes in GDB-4.10:
1954 * User visible changes:
1956 Remote debugging using the GDB-specific (`target remote') protocol now
1957 supports the `load' command. This is only useful if you have some
1958 other way of getting the stub to the target system, and you can put it
1959 somewhere in memory where it won't get clobbered by the download.
1961 Filename completion now works.
1963 When run under emacs mode, the "info line" command now causes the
1964 arrow to point to the line specified. Also, "info line" prints
1965 addresses in symbolic form (as well as hex).
1967 All vxworks based targets now support a user settable option, called
1968 vxworks-timeout. This option represents the number of seconds gdb
1969 should wait for responses to rpc's. You might want to use this if
1970 your vxworks target is, perhaps, a slow software simulator or happens
1971 to be on the far side of a thin network line.
1975 This release contains support for using a DEC alpha as a GDB host for
1976 cross debugging. Native alpha debugging is not supported yet.
1979 *** Changes in GDB-4.9:
1983 This is the first GDB release which is accompanied by a matching testsuite.
1984 The testsuite requires installation of dejagnu, which should be available
1985 via ftp from most sites that carry GNU software.
1989 'Cfront' style demangling has had its name changed to 'ARM' style, to
1990 emphasize that it was written from the specifications in the C++ Annotated
1991 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1992 disclaimers, it still generated too much confusion with users attempting to
1993 use gdb with AT&T cfront.
1997 GDB now uses a standard remote interface to a simulator library.
1998 So far, the library contains simulators for the Zilog Z8001/2, the
1999 Hitachi H8/300, H8/500 and Super-H.
2001 * New targets supported
2003 H8/300 simulator h8300-hitachi-hms or h8300hms
2004 H8/500 simulator h8500-hitachi-hms or h8500hms
2005 SH simulator sh-hitachi-hms or sh
2006 Z8000 simulator z8k-zilog-none or z8ksim
2007 IDT MIPS board over serial line mips-idt-ecoff
2009 Cross-debugging to GO32 targets is supported. It requires a custom
2010 version of the i386-stub.c module which is integrated with the
2011 GO32 memory extender.
2013 * New remote protocols
2015 MIPS remote debugging protocol.
2017 * New source languages supported
2019 This version includes preliminary support for Chill, a Pascal like language
2020 used by telecommunications companies. Chill support is also being integrated
2021 into the GNU compiler, but we don't know when it will be publically available.
2024 *** Changes in GDB-4.8:
2026 * HP Precision Architecture supported
2028 GDB now supports HP PA-RISC machines running HPUX. A preliminary
2029 version of this support was available as a set of patches from the
2030 University of Utah. GDB does not support debugging of programs
2031 compiled with the HP compiler, because HP will not document their file
2032 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
2033 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
2035 Many problems in the preliminary version have been fixed.
2037 * Faster and better demangling
2039 We have improved template demangling and fixed numerous bugs in the GNU style
2040 demangler. It can now handle type modifiers such as `static' or `const'. Wide
2041 character types (wchar_t) are now supported. Demangling of each symbol is now
2042 only done once, and is cached when the symbol table for a file is read in.
2043 This results in a small increase in memory usage for C programs, a moderate
2044 increase in memory usage for C++ programs, and a fantastic speedup in
2047 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
2048 from the specifications in the Annotated Reference Manual, which AT&T's
2049 compiler does not actually implement.
2051 * G++ multiple inheritance compiler problem
2053 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
2054 inheritance lattices was reworked to properly discover ambiguities. We
2055 recently found an example which causes this new algorithm to fail in a
2056 very subtle way, producing bad debug information for those classes.
2057 The file 'gcc.patch' (in this directory) can be applied to gcc to
2058 circumvent the problem. A future GCC release will contain a complete
2061 The previous G++ debug info problem (mentioned below for the gdb-4.7
2062 release) is fixed in gcc version 2.3.2.
2064 * Improved configure script
2066 The `configure' script will now attempt to guess your system type if
2067 you don't supply a host system type. The old scheme of supplying a
2068 host system triplet is preferable over using this. All the magic is
2069 done in the new `config.guess' script. Examine it for details.
2071 We have also brought our configure script much more in line with the FSF's
2072 version. It now supports the --with-xxx options. In particular,
2073 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
2074 The resulting GDB will not be able to read arbitrary object file formats --
2075 only the format ``expected'' to be used on the configured target system.
2076 We hope to make this the default in a future release.
2078 * Documentation improvements
2080 There's new internal documentation on how to modify GDB, and how to
2081 produce clean changes to the code. We implore people to read it
2082 before submitting changes.
2084 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
2085 M4 macros. The new texinfo.tex is provided in this release. Pre-built
2086 `info' files are also provided. To build `info' files from scratch,
2087 you will need the latest `makeinfo' release, which will be available in
2088 a future texinfo-X.Y release.
2090 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
2091 We're not sure exactly which versions have this problem, but it has
2092 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
2093 or better. If that isn't possible, there is a patch in
2094 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
2095 around this problem.
2099 GDB now supports array constants that can be used in expressions typed in by
2100 the user. The syntax is `{element, element, ...}'. Ie: you can now type
2101 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
2104 The new directory `gdb/sparclite' contains a program that demonstrates
2105 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
2107 * New native hosts supported
2109 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
2110 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
2112 * New targets supported
2114 AMD 29k family via UDI a29k-amd-udi or udi29k
2116 * New file formats supported
2118 BFD now supports reading HP/PA-RISC executables (SOM file format?),
2119 HPUX core files, and SCO 3.2v2 core files.
2123 Attaching to processes now works again; thanks for the many bug reports.
2125 We have also stomped on a bunch of core dumps caused by
2126 printf_filtered("%s") problems.
2128 We eliminated a copyright problem on the rpc and ptrace header files
2129 for VxWorks, which was discovered at the last minute during the 4.7
2130 release. You should now be able to build a VxWorks GDB.
2132 You can now interrupt gdb while an attached process is running. This
2133 will cause the attached process to stop, and give control back to GDB.
2135 We fixed problems caused by using too many file descriptors
2136 for reading symbols from object files and libraries. This was
2137 especially a problem for programs that used many (~100) shared
2140 The `step' command now only enters a subroutine if there is line number
2141 information for the subroutine. Otherwise it acts like the `next'
2142 command. Previously, `step' would enter subroutines if there was
2143 any debugging information about the routine. This avoids problems
2144 when using `cc -g1' on MIPS machines.
2146 * Internal improvements
2148 GDB's internal interfaces have been improved to make it easier to support
2149 debugging of multiple languages in the future.
2151 GDB now uses a common structure for symbol information internally.
2152 Minimal symbols (derived from linkage symbols in object files), partial
2153 symbols (from a quick scan of debug information), and full symbols
2154 contain a common subset of information, making it easier to write
2155 shared code that handles any of them.
2157 * New command line options
2159 We now accept --silent as an alias for --quiet.
2163 The memory-mapped-malloc library is now licensed under the GNU Library
2164 General Public License.
2166 *** Changes in GDB-4.7:
2168 * Host/native/target split
2170 GDB has had some major internal surgery to untangle the support for
2171 hosts and remote targets. Now, when you configure GDB for a remote
2172 target, it will no longer load in all of the support for debugging
2173 local programs on the host. When fully completed and tested, this will
2174 ensure that arbitrary host/target combinations are possible.
2176 The primary conceptual shift is to separate the non-portable code in
2177 GDB into three categories. Host specific code is required any time GDB
2178 is compiled on that host, regardless of the target. Target specific
2179 code relates to the peculiarities of the target, but can be compiled on
2180 any host. Native specific code is everything else: it can only be
2181 built when the host and target are the same system. Child process
2182 handling and core file support are two common `native' examples.
2184 GDB's use of /proc for controlling Unix child processes is now cleaner.
2185 It has been split out into a single module under the `target_ops' vector,
2186 plus two native-dependent functions for each system that uses /proc.
2188 * New hosts supported
2190 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
2191 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2192 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
2194 * New targets supported
2196 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
2197 68030 and CPU32 m68030-*-*, m68332-*-*
2199 * New native hosts supported
2201 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
2202 (386bsd is not well tested yet)
2203 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
2205 * New file formats supported
2207 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
2208 supports reading of `a.out.adobe' object files, which are an a.out
2209 format extended with minimal information about multiple sections.
2213 `show copying' is the same as the old `info copying'.
2214 `show warranty' is the same as `info warrantee'.
2215 These were renamed for consistency. The old commands continue to work.
2217 `info handle' is a new alias for `info signals'.
2219 You can now define pre-command hooks, which attach arbitrary command
2220 scripts to any command. The commands in the hook will be executed
2221 prior to the user's command. You can also create a hook which will be
2222 executed whenever the program stops. See gdb.texinfo.
2226 We now deal with Cfront style name mangling, and can even extract type
2227 info from mangled symbols. GDB can automatically figure out which
2228 symbol mangling style your C++ compiler uses.
2230 Calling of methods and virtual functions has been improved as well.
2234 The crash that occured when debugging Sun Ansi-C compiled binaries is
2235 fixed. This was due to mishandling of the extra N_SO stabs output
2238 We also finally got Ultrix 4.2 running in house, and fixed core file
2239 support, with help from a dozen people on the net.
2241 John M. Farrell discovered that the reason that single-stepping was so
2242 slow on all of the Mips based platforms (primarily SGI and DEC) was
2243 that we were trying to demangle and lookup a symbol used for internal
2244 purposes on every instruction that was being stepped through. Changing
2245 the name of that symbol so that it couldn't be mistaken for a C++
2246 mangled symbol sped things up a great deal.
2248 Rich Pixley sped up symbol lookups in general by getting much smarter
2249 about when C++ symbol mangling is necessary. This should make symbol
2250 completion (TAB on the command line) much faster. It's not as fast as
2251 we'd like, but it's significantly faster than gdb-4.6.
2255 A new user controllable variable 'call_scratch_address' can
2256 specify the location of a scratch area to be used when GDB
2257 calls a function in the target. This is necessary because the
2258 usual method of putting the scratch area on the stack does not work
2259 in systems that have separate instruction and data spaces.
2261 We integrated changes to support the 29k UDI (Universal Debugger
2262 Interface), but discovered at the last minute that we didn't have all
2263 of the appropriate copyright paperwork. We are working with AMD to
2264 resolve this, and hope to have it available soon.
2268 We have sped up the remote serial line protocol, especially for targets
2269 with lots of registers. It now supports a new `expedited status' ('T')
2270 message which can be used in place of the existing 'S' status message.
2271 This allows the remote stub to send only the registers that GDB
2272 needs to make a quick decision about single-stepping or conditional
2273 breakpoints, eliminating the need to fetch the entire register set for
2274 each instruction being stepped through.
2276 The GDB remote serial protocol now implements a write-through cache for
2277 registers, only re-reading the registers if the target has run.
2279 There is also a new remote serial stub for SPARC processors. You can
2280 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
2281 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
2282 processor with a serial port.
2286 Configure.in files have become much easier to read and modify. A new
2287 `table driven' format makes it more obvious what configurations are
2288 supported, and what files each one uses.
2292 There is a new opcodes library which will eventually contain all of the
2293 disassembly routines and opcode tables. At present, it only contains
2294 Sparc and Z8000 routines. This will allow the assembler, debugger, and
2295 disassembler (binutils/objdump) to share these routines.
2297 The libiberty library is now copylefted under the GNU Library General
2298 Public License. This allows more liberal use, and was done so libg++
2299 can use it. This makes no difference to GDB, since the Library License
2300 grants all the rights from the General Public License.
2304 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
2305 reference to the stabs symbol info used by the debugger. It is (as far
2306 as we know) the only published document on this fascinating topic. We
2307 encourage you to read it, compare it to the stabs information on your
2308 system, and send improvements on the document in general (to
2309 bug-gdb@prep.ai.mit.edu).
2311 And, of course, many bugs have been fixed.
2314 *** Changes in GDB-4.6:
2316 * Better support for C++ function names
2318 GDB now accepts as input the "demangled form" of C++ overloaded function
2319 names and member function names, and can do command completion on such names
2320 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
2321 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
2322 Make use of command completion, it is your friend.
2324 GDB also now accepts a variety of C++ mangled symbol formats. They are
2325 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
2326 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
2327 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
2328 for the list of formats.
2330 * G++ symbol mangling problem
2332 Recent versions of gcc have a bug in how they emit debugging information for
2333 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
2334 directory) can be applied to gcc to fix the problem. Alternatively, if you
2335 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
2336 usual symptom is difficulty with setting breakpoints on methods. GDB complains
2337 about the method being non-existent. (We believe that version 2.2.2 of GCC has
2340 * New 'maintenance' command
2342 All of the commands related to hacking GDB internals have been moved out of
2343 the main command set, and now live behind the 'maintenance' command. This
2344 can also be abbreviated as 'mt'. The following changes were made:
2346 dump-me -> maintenance dump-me
2347 info all-breakpoints -> maintenance info breakpoints
2348 printmsyms -> maintenance print msyms
2349 printobjfiles -> maintenance print objfiles
2350 printpsyms -> maintenance print psymbols
2351 printsyms -> maintenance print symbols
2353 The following commands are new:
2355 maintenance demangle Call internal GDB demangler routine to
2356 demangle a C++ link name and prints the result.
2357 maintenance print type Print a type chain for a given symbol
2359 * Change to .gdbinit file processing
2361 We now read the $HOME/.gdbinit file before processing the argv arguments
2362 (e.g. reading symbol files or core files). This allows global parameters to
2363 be set, which will apply during the symbol reading. The ./.gdbinit is still
2364 read after argv processing.
2366 * New hosts supported
2368 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
2370 GNU/Linux support i386-unknown-linux or linux
2372 We are also including code to support the HP/PA running BSD and HPUX. This
2373 is almost guaranteed not to work, as we didn't have time to test or build it
2374 for this release. We are including it so that the more adventurous (or
2375 masochistic) of you can play with it. We also had major problems with the
2376 fact that the compiler that we got from HP doesn't support the -g option.
2379 * New targets supported
2381 Hitachi H8/300 h8300-hitachi-hms or h8300hms
2383 * More smarts about finding #include files
2385 GDB now remembers the compilation directory for all include files, and for
2386 all files from which C is generated (like yacc and lex sources). This
2387 greatly improves GDB's ability to find yacc/lex sources, and include files,
2388 especially if you are debugging your program from a directory different from
2389 the one that contains your sources.
2391 We also fixed a bug which caused difficulty with listing and setting
2392 breakpoints in include files which contain C code. (In the past, you had to
2393 try twice in order to list an include file that you hadn't looked at before.)
2395 * Interesting infernals change
2397 GDB now deals with arbitrary numbers of sections, where the symbols for each
2398 section must be relocated relative to that section's landing place in the
2399 target's address space. This work was needed to support ELF with embedded
2400 stabs used by Solaris-2.0.
2402 * Bug fixes (of course!)
2404 There have been loads of fixes for the following things:
2405 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
2406 i960, stabs, DOS(GO32), procfs, etc...
2408 See the ChangeLog for details.
2410 *** Changes in GDB-4.5:
2412 * New machines supported (host and target)
2414 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
2416 SGI Irix-4.x mips-sgi-irix4 or iris4
2418 * New malloc package
2420 GDB now uses a new memory manager called mmalloc, based on gmalloc.
2421 Mmalloc is capable of handling mutiple heaps of memory. It is also
2422 capable of saving a heap to a file, and then mapping it back in later.
2423 This can be used to greatly speedup the startup of GDB by using a
2424 pre-parsed symbol table which lives in a mmalloc managed heap. For
2425 more details, please read mmalloc/mmalloc.texi.
2429 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
2430 'help info proc' for details.
2432 * MIPS ecoff symbol table format
2434 The code that reads MIPS symbol table format is now supported on all hosts.
2435 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
2438 * File name changes for MS-DOS
2440 Many files in the config directories have been renamed to make it easier to
2441 support GDB on MS-DOSe systems (which have very restrictive file name
2442 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
2443 environment) is close to working but has some remaining problems. Note
2444 that debugging of DOS programs is not supported, due to limitations
2445 in the ``operating system'', but it can be used to host cross-debugging.
2447 * Cross byte order fixes
2449 Many fixes have been made to support cross debugging of Sparc and MIPS
2450 targets from hosts whose byte order differs.
2452 * New -mapped and -readnow options
2454 If memory-mapped files are available on your system through the 'mmap'
2455 system call, you can use the -mapped option on the `file' or
2456 `symbol-file' commands to cause GDB to write the symbols from your
2457 program into a reusable file. If the program you are debugging is
2458 called `/path/fred', the mapped symbol file will be `./fred.syms'.
2459 Future GDB debugging sessions will notice the presence of this file,
2460 and will quickly map in symbol information from it, rather than reading
2461 the symbol table from the executable program. Using the '-mapped'
2462 option in a GDB `file' or `symbol-file' command has the same effect as
2463 starting GDB with the '-mapped' command-line option.
2465 You can cause GDB to read the entire symbol table immediately by using
2466 the '-readnow' option with any of the commands that load symbol table
2467 information (or on the GDB command line). This makes the command
2468 slower, but makes future operations faster.
2470 The -mapped and -readnow options are typically combined in order to
2471 build a `fred.syms' file that contains complete symbol information.
2472 A simple GDB invocation to do nothing but build a `.syms' file for future
2475 gdb -batch -nx -mapped -readnow programname
2477 The `.syms' file is specific to the host machine on which GDB is run.
2478 It holds an exact image of GDB's internal symbol table. It cannot be
2479 shared across multiple host platforms.
2481 * longjmp() handling
2483 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
2484 siglongjmp() without losing control. This feature has not yet been ported to
2485 all systems. It currently works on many 386 platforms, all MIPS-based
2486 platforms (SGI, DECstation, etc), and Sun3/4.
2490 Preliminary work has been put in to support the new Solaris OS from Sun. At
2491 this time, it can control and debug processes, but it is not capable of
2496 As always, many many bug fixes. The major areas were with g++, and mipsread.
2497 People using the MIPS-based platforms should experience fewer mysterious
2498 crashes and trashed symbol tables.
2500 *** Changes in GDB-4.4:
2502 * New machines supported (host and target)
2504 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2506 BSD Reno on Vax vax-dec-bsd
2507 Ultrix on Vax vax-dec-ultrix
2509 * New machines supported (target)
2511 AMD 29000 embedded, using EBMON a29k-none-none
2515 GDB continues to improve its handling of C++. `References' work better.
2516 The demangler has also been improved, and now deals with symbols mangled as
2517 per the Annotated C++ Reference Guide.
2519 GDB also now handles `stabs' symbol information embedded in MIPS
2520 `ecoff' symbol tables. Since the ecoff format was not easily
2521 extensible to handle new languages such as C++, this appeared to be a
2522 good way to put C++ debugging info into MIPS binaries. This option
2523 will be supported in the GNU C compiler, version 2, when it is
2526 * New features for SVR4
2528 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
2529 shared libraries. Debugging dynamically linked programs should present
2530 only minor differences from debugging statically linked programs.
2532 The `info proc' command will print out information about any process
2533 on an SVR4 system (including the one you are debugging). At the moment,
2534 it prints the address mappings of the process.
2536 If you bring up GDB on another SVR4 system, please send mail to
2537 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
2539 * Better dynamic linking support in SunOS
2541 Reading symbols from shared libraries which contain debugging symbols
2542 now works properly. However, there remain issues such as automatic
2543 skipping of `transfer vector' code during function calls, which
2544 make it harder to debug code in a shared library, than to debug the
2545 same code linked statically.
2549 GDB is now using the latest `getopt' routines from the FSF. This
2550 version accepts the -- prefix for options with long names. GDB will
2551 continue to accept the old forms (-option and +option) as well.
2552 Various single letter abbreviations for options have been explicity
2553 added to the option table so that they won't get overshadowed in the
2554 future by other options that begin with the same letter.
2558 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
2559 Many assorted bugs have been handled. Many more remain to be handled.
2560 See the various ChangeLog files (primarily in gdb and bfd) for details.
2563 *** Changes in GDB-4.3:
2565 * New machines supported (host and target)
2567 Amiga 3000 running Amix m68k-cbm-svr4 or amix
2568 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
2569 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
2571 * Almost SCO Unix support
2573 We had hoped to support:
2574 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
2575 (except for core file support), but we discovered very late in the release
2576 that it has problems with process groups that render gdb unusable. Sorry
2577 about that. I encourage people to fix it and post the fixes.
2579 * Preliminary ELF and DWARF support
2581 GDB can read ELF object files on System V Release 4, and can handle
2582 debugging records for C, in DWARF format, in ELF files. This support
2583 is preliminary. If you bring up GDB on another SVR4 system, please
2584 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
2589 GDB now uses the latest `readline' library. One user-visible change
2590 is that two tabs will list possible command completions, which previously
2591 required typing M-? (meta-question mark, or ESC ?).
2595 The `stepi' bug that many of you noticed has been squashed.
2596 Many bugs in C++ have been handled. Many more remain to be handled.
2597 See the various ChangeLog files (primarily in gdb and bfd) for details.
2599 * State of the MIPS world (in case you wondered):
2601 GDB can understand the symbol tables emitted by the compilers
2602 supplied by most vendors of MIPS-based machines, including DEC. These
2603 symbol tables are in a format that essentially nobody else uses.
2605 Some versions of gcc come with an assembler post-processor called
2606 mips-tfile. This program is required if you want to do source-level
2607 debugging of gcc-compiled programs. I believe FSF does not ship
2608 mips-tfile with gcc version 1, but it will eventually come with gcc
2611 Debugging of g++ output remains a problem. g++ version 1.xx does not
2612 really support it at all. (If you're lucky, you should be able to get
2613 line numbers and stack traces to work, but no parameters or local
2614 variables.) With some work it should be possible to improve the
2617 When gcc version 2 is released, you will have somewhat better luck.
2618 However, even then you will get confusing results for inheritance and
2621 We will eventually provide full debugging of g++ output on
2622 DECstations. This will probably involve some kind of stabs-in-ecoff
2623 encapulation, but the details have not been worked out yet.
2626 *** Changes in GDB-4.2:
2628 * Improved configuration
2630 Only one copy of `configure' exists now, and it is not self-modifying.
2631 Porting BFD is simpler.
2635 The `step' and `next' commands now only stop at the first instruction
2636 of a source line. This prevents the multiple stops that used to occur
2637 in switch statements, for-loops, etc. `Step' continues to stop if a
2638 function that has debugging information is called within the line.
2642 Lots of small bugs fixed. More remain.
2644 * New host supported (not target)
2646 Intel 386 PC clone running Mach i386-none-mach
2649 *** Changes in GDB-4.1:
2651 * Multiple source language support
2653 GDB now has internal scaffolding to handle several source languages.
2654 It determines the type of each source file from its filename extension,
2655 and will switch expression parsing and number formatting to match the
2656 language of the function in the currently selected stack frame.
2657 You can also specifically set the language to be used, with
2658 `set language c' or `set language modula-2'.
2662 GDB now has preliminary support for the GNU Modula-2 compiler,
2663 currently under development at the State University of New York at
2664 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
2665 continue through the fall of 1991 and into 1992.
2667 Other Modula-2 compilers are currently not supported, and attempting to
2668 debug programs compiled with them will likely result in an error as the
2669 symbol table is read. Feel free to work on it, though!
2671 There are hooks in GDB for strict type checking and range checking,
2672 in the `Modula-2 philosophy', but they do not currently work.
2676 GDB can now write to executable and core files (e.g. patch
2677 a variable's value). You must turn this switch on, specify
2678 the file ("exec foo" or "core foo"), *then* modify it, e.g.
2679 by assigning a new value to a variable. Modifications take
2682 * Automatic SunOS shared library reading
2684 When you run your program, GDB automatically determines where its
2685 shared libraries (if any) have been loaded, and reads their symbols.
2686 The `share' command is no longer needed. This also works when
2687 examining core files.
2691 You can specify the number of lines that the `list' command shows.
2694 * New machines supported (host and target)
2696 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
2697 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
2698 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
2700 * New hosts supported (not targets)
2702 IBM RT/PC: romp-ibm-aix or rtpc
2704 * New targets supported (not hosts)
2706 AMD 29000 embedded with COFF a29k-none-coff
2707 AMD 29000 embedded with a.out a29k-none-aout
2708 Ultracomputer remote kernel debug a29k-nyu-kern
2710 * New remote interfaces
2716 *** Changes in GDB-4.0:
2720 Wide output is wrapped at good places to make the output more readable.
2722 Gdb now supports cross-debugging from a host machine of one type to a
2723 target machine of another type. Communication with the target system
2724 is over serial lines. The ``target'' command handles connecting to the
2725 remote system; the ``load'' command will download a program into the
2726 remote system. Serial stubs for the m68k and i386 are provided. Gdb
2727 also supports debugging of realtime processes running under VxWorks,
2728 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
2729 stub on the target system.
2731 New CPUs supported include the AMD 29000 and Intel 960.
2733 GDB now reads object files and symbol tables via a ``binary file''
2734 library, which allows a single copy of GDB to debug programs of multiple
2735 object file types such as a.out and coff.
2737 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2738 refcard.dvi and refcard.ps are available to format it).
2741 * Control-Variable user interface simplified
2743 All variables that control the operation of the debugger can be set
2744 by the ``set'' command, and displayed by the ``show'' command.
2746 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2747 ``Show prompt'' produces the response:
2748 Gdb's prompt is new-gdb=>.
2750 What follows are the NEW set commands. The command ``help set'' will
2751 print a complete list of old and new set commands. ``help set FOO''
2752 will give a longer description of the variable FOO. ``show'' will show
2753 all of the variable descriptions and their current settings.
2755 confirm on/off: Enables warning questions for operations that are
2756 hard to recover from, e.g. rerunning the program while
2757 it is already running. Default is ON.
2759 editing on/off: Enables EMACS style command line editing
2760 of input. Previous lines can be recalled with
2761 control-P, the current line can be edited with control-B,
2762 you can search for commands with control-R, etc.
2765 history filename NAME: NAME is where the gdb command history
2766 will be stored. The default is .gdb_history,
2767 or the value of the environment variable
2770 history size N: The size, in commands, of the command history. The
2771 default is 256, or the value of the environment variable
2774 history save on/off: If this value is set to ON, the history file will
2775 be saved after exiting gdb. If set to OFF, the
2776 file will not be saved. The default is OFF.
2778 history expansion on/off: If this value is set to ON, then csh-like
2779 history expansion will be performed on
2780 command line input. The default is OFF.
2782 radix N: Sets the default radix for input and output. It can be set
2783 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2784 in the current radix, so "set radix 10" is always a no-op.
2786 height N: This integer value is the number of lines on a page. Default
2787 is 24, the current `stty rows'' setting, or the ``li#''
2788 setting from the termcap entry matching the environment
2791 width N: This integer value is the number of characters on a line.
2792 Default is 80, the current `stty cols'' setting, or the ``co#''
2793 setting from the termcap entry matching the environment
2796 Note: ``set screensize'' is obsolete. Use ``set height'' and
2797 ``set width'' instead.
2799 print address on/off: Print memory addresses in various command displays,
2800 such as stack traces and structure values. Gdb looks
2801 more ``symbolic'' if you turn this off; it looks more
2802 ``machine level'' with it on. Default is ON.
2804 print array on/off: Prettyprint arrays. New convenient format! Default
2807 print demangle on/off: Print C++ symbols in "source" form if on,
2810 print asm-demangle on/off: Same, for assembler level printouts
2813 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2816 * Support for Epoch Environment.
2818 The epoch environment is a version of Emacs v18 with windowing. One
2819 new command, ``inspect'', is identical to ``print'', except that if you
2820 are running in the epoch environment, the value is printed in its own
2824 * Support for Shared Libraries
2826 GDB can now debug programs and core files that use SunOS shared libraries.
2827 Symbols from a shared library cannot be referenced
2828 before the shared library has been linked with the program (this
2829 happens after you type ``run'' and before the function main() is entered).
2830 At any time after this linking (including when examining core files
2831 from dynamically linked programs), gdb reads the symbols from each
2832 shared library when you type the ``sharedlibrary'' command.
2833 It can be abbreviated ``share''.
2835 sharedlibrary REGEXP: Load shared object library symbols for files
2836 matching a unix regular expression. No argument
2837 indicates to load symbols for all shared libraries.
2839 info sharedlibrary: Status of loaded shared libraries.
2844 A watchpoint stops execution of a program whenever the value of an
2845 expression changes. Checking for this slows down execution
2846 tremendously whenever you are in the scope of the expression, but is
2847 quite useful for catching tough ``bit-spreader'' or pointer misuse
2848 problems. Some machines such as the 386 have hardware for doing this
2849 more quickly, and future versions of gdb will use this hardware.
2851 watch EXP: Set a watchpoint (breakpoint) for an expression.
2853 info watchpoints: Information about your watchpoints.
2855 delete N: Deletes watchpoint number N (same as breakpoints).
2856 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2857 enable N: Re-enables watchpoint number N (same as breakpoints).
2860 * C++ multiple inheritance
2862 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2865 * C++ exception handling
2867 Gdb now supports limited C++ exception handling. Besides the existing
2868 ability to breakpoint on an exception handler, gdb can breakpoint on
2869 the raising of an exception (before the stack is peeled back to the
2872 catch FOO: If there is a FOO exception handler in the dynamic scope,
2873 set a breakpoint to catch exceptions which may be raised there.
2874 Multiple exceptions (``catch foo bar baz'') may be caught.
2876 info catch: Lists all exceptions which may be caught in the
2877 current stack frame.
2880 * Minor command changes
2882 The command ``call func (arg, arg, ...)'' now acts like the print
2883 command, except it does not print or save a value if the function's result
2884 is void. This is similar to dbx usage.
2886 The ``up'' and ``down'' commands now always print the frame they end up
2887 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2888 frames without printing.
2890 * New directory command
2892 'dir' now adds directories to the FRONT of the source search path.
2893 The path starts off empty. Source files that contain debug information
2894 about the directory in which they were compiled can be found even
2895 with an empty path; Sun CC and GCC include this information. If GDB can't
2896 find your source file in the current directory, type "dir .".
2898 * Configuring GDB for compilation
2900 For normal use, type ``./configure host''. See README or gdb.texinfo
2903 GDB now handles cross debugging. If you are remotely debugging between
2904 two different machines, type ``./configure host -target=targ''.
2905 Host is the machine where GDB will run; targ is the machine
2906 where the program that you are debugging will run.
projects / binutils-gdb.git / blob