1 What has changed in GDB?
2 (Organized release by release)
4 *** Changes since GDB 5.3:
6 * REMOVED configurations and files
10 * MIPS $fp behavior changed
12 The convenience variable $fp, for the MIPS, now consistently returns
13 the address of the current frame's base. Previously, depending on the
14 context, $fp could refer to either $sp or the current frame's base
15 address. See ``8.10 Registers'' in the manual ``Debugging with GDB:
16 The GNU Source-Level Debugger''.
18 *** Changes in GDB 5.3:
20 * ``gdbserver'' now supports multi-threaded applications on some targets
22 Support for debugging multi-threaded applications which use
23 the GNU/Linux LinuxThreads package has been added for
24 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
25 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
27 * GDB now supports C/C++ preprocessor macros.
29 GDB now expands preprocessor macro invocations in C/C++ expressions,
30 and provides various commands for showing macro definitions and how
33 The new command `macro expand EXPRESSION' expands any macro
34 invocations in expression, and shows the result.
36 The new command `show macro MACRO-NAME' shows the definition of the
37 macro named MACRO-NAME, and where it was defined.
39 Most compilers don't include information about macros in the debugging
40 information by default. In GCC 3.1, for example, you need to compile
41 your program with the options `-gdwarf-2 -g3'. If the macro
42 information is present in the executable, GDB will read it.
44 * Multi-arched targets.
46 DEC Alpha (partial) alpha*-*-*
47 DEC VAX (partial) vax-*-*
49 National Semiconductor NS32000 (partial) ns32k-*-*
50 Motorola 68000 (partial) m68k-*-*
51 Motorola MCORE mcore-*-*
55 Fujitsu FRV architecture added by Red Hat frv*-*-*
58 * New native configurations
60 Alpha NetBSD alpha*-*-netbsd*
61 SH NetBSD sh*-*-netbsdelf*
62 MIPS NetBSD mips*-*-netbsd*
63 UltraSPARC NetBSD sparc64-*-netbsd*
65 * OBSOLETE configurations and files
67 Configurations that have been declared obsolete in this release have
68 been commented out. Unless there is activity to revive these
69 configurations, the next release of GDB will have their sources
72 Mitsubishi D30V d30v-*-*
73 OS/9000 i[34]86-*-os9k
74 IBM AIX PS/2 i[3456]86-*-aix
75 Fujitsu FR30 fr30-*-elf*
76 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
77 Argonaut Risc Chip (ARC) arc-*-*
78 i386 running Mach 3.0 i[3456]86-*-mach3*
79 i386 running Mach i[3456]86-*-mach*
80 i386 running OSF/1 i[3456]86-*osf1mk*
81 HP/Apollo 68k Family m68*-apollo*-sysv*,
83 m68*-hp-bsd*, m68*-hp-hpux*
84 I960 with MON960 i960-*-coff
88 CHILL, a Pascal like language used by telecommunications companies.
90 * REMOVED configurations and files
92 AMD 29k family via UDI a29k-amd-udi, udi29k
93 A29K VxWorks a29k-*-vxworks
94 AMD 29000 embedded, using EBMON a29k-none-none
95 AMD 29000 embedded with COFF a29k-none-coff
96 AMD 29000 embedded with a.out a29k-none-aout
98 testsuite/gdb.hp/gdb.threads-hp/ directory
100 * New command "set max-user-call-depth <nnn>"
102 This command allows the user to limit the call depth of user-defined
103 commands. The default is 1024.
105 * Changes in FreeBSD/i386 native debugging.
107 Support for the "generate-core-file" has been added.
109 * New commands "dump", "append", and "restore".
111 These commands allow data to be copied from target memory
112 to a bfd-format or binary file (dump and append), and back
113 from a file into memory (restore).
115 * Improved "next/step" support on multi-processor Alpha Tru64.
117 The previous single-step mechanism could cause unpredictable problems,
118 including the random appearance of SIGSEGV or SIGTRAP signals. The use
119 of a software single-step mechanism prevents this.
121 *** Changes in GDB 5.2.1:
129 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
130 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
131 Fix, by Joel Brobecker imported from mainline.
133 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
134 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
135 Fix, by Fred Fish, imported from mainline.
137 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
138 Surprisingly enough, it works now.
139 By Michal Ludvig, imported from mainline.
141 i386 hardware watchpoint support:
142 avoid misses on second run for some targets.
143 By Pierre Muller, imported from mainline.
145 *** Changes in GDB 5.2:
147 * New command "set trust-readonly-sections on[off]".
149 This command is a hint that tells gdb that read-only sections
150 really are read-only (ie. that their contents will not change).
151 In this mode, gdb will go to the object file rather than the
152 target to read memory from read-only sections (such as ".text").
153 This can be a significant performance improvement on some
154 (notably embedded) targets.
156 * New command "generate-core-file" (or "gcore").
158 This new gdb command allows the user to drop a core file of the child
159 process state at any time. So far it's been implemented only for
160 GNU/Linux and Solaris, but should be relatively easily ported to other
161 hosts. Argument is core file name (defaults to core.<pid>).
163 * New command line option
165 GDB now accepts --pid or -p followed by a process id.
167 * Change in command line behavior -- corefiles vs. process ids.
169 There is a subtle behavior in the way in which GDB handles
170 command line arguments. The first non-flag argument is always
171 a program to debug, but the second non-flag argument may either
172 be a corefile or a process id. Previously, GDB would attempt to
173 open the second argument as a corefile, and if that failed, would
174 issue a superfluous error message and then attempt to attach it as
175 a process. Now, if the second argument begins with a non-digit,
176 it will be treated as a corefile. If it begins with a digit,
177 GDB will attempt to attach it as a process, and if no such process
178 is found, will then attempt to open it as a corefile.
180 * Changes in ARM configurations.
182 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
183 configuration is fully multi-arch.
185 * New native configurations
187 ARM NetBSD arm*-*-netbsd*
188 x86 OpenBSD i[3456]86-*-openbsd*
189 AMD x86-64 running GNU/Linux x86_64-*-linux-*
190 Sparc64 running FreeBSD sparc64-*-freebsd*
194 Sanyo XStormy16 xstormy16-elf
196 * OBSOLETE configurations and files
198 Configurations that have been declared obsolete in this release have
199 been commented out. Unless there is activity to revive these
200 configurations, the next release of GDB will have their sources
203 AMD 29k family via UDI a29k-amd-udi, udi29k
204 A29K VxWorks a29k-*-vxworks
205 AMD 29000 embedded, using EBMON a29k-none-none
206 AMD 29000 embedded with COFF a29k-none-coff
207 AMD 29000 embedded with a.out a29k-none-aout
209 testsuite/gdb.hp/gdb.threads-hp/ directory
211 * REMOVED configurations and files
213 TI TMS320C80 tic80-*-*
215 PowerPC Solaris powerpcle-*-solaris*
216 PowerPC Windows NT powerpcle-*-cygwin32
217 PowerPC Netware powerpc-*-netware*
218 Harris/CXUX m88k m88*-harris-cxux*
219 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
220 ns32k-utek-sysv* ns32k-utek-*
221 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
222 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
223 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
224 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
225 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
227 * Changes to command line processing
229 The new `--args' feature can be used to specify command-line arguments
230 for the inferior from gdb's command line.
232 * Changes to key bindings
234 There is a new `operate-and-get-next' function bound to `C-o'.
236 *** Changes in GDB 5.1.1
238 Fix compile problem on DJGPP.
240 Fix a problem with floating-point registers on the i386 being
243 Fix to stop GDB crashing on .debug_str debug info.
245 Numerous documentation fixes.
247 Numerous testsuite fixes.
249 *** Changes in GDB 5.1:
251 * New native configurations
253 Alpha FreeBSD alpha*-*-freebsd*
254 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
255 MIPS GNU/Linux mips*-*-linux*
256 MIPS SGI Irix 6.x mips*-sgi-irix6*
258 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
262 Motorola 68HC11 and 68HC12 m68hc11-elf
264 UltraSparc running GNU/Linux sparc64-*-linux*
266 * OBSOLETE configurations and files
268 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
269 Harris/CXUX m88k m88*-harris-cxux*
270 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
271 ns32k-utek-sysv* ns32k-utek-*
272 TI TMS320C80 tic80-*-*
274 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
275 PowerPC Solaris powerpcle-*-solaris*
276 PowerPC Windows NT powerpcle-*-cygwin32
277 PowerPC Netware powerpc-*-netware*
278 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
279 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
280 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
281 Apple Macintosh (MPW) host N/A
283 stuff.c (Program to stuff files into a specially prepared space in kdb)
284 kdb-start.c (Main loop for the standalone kernel debugger)
286 Configurations that have been declared obsolete in this release have
287 been commented out. Unless there is activity to revive these
288 configurations, the next release of GDB will have their sources
291 * REMOVED configurations and files
293 Altos 3068 m68*-altos-*
294 Convex c1-*-*, c2-*-*
296 ARM RISCix arm-*-* (as host)
300 * GDB has been converted to ISO C.
302 GDB's source code has been converted to ISO C. In particular, the
303 sources are fully protoized, and rely on standard headers being
308 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
310 * The MI enabled by default.
312 The new machine oriented interface (MI) introduced in GDB 5.0 has been
313 revised and enabled by default. Packages which use GDB as a debugging
314 engine behind a UI or another front end are encouraged to switch to
315 using the GDB/MI interface, instead of the old annotations interface
316 which is now deprecated.
318 * Support for debugging Pascal programs.
320 GDB now includes support for debugging Pascal programs. The following
321 main features are supported:
323 - Pascal-specific data types such as sets;
325 - automatic recognition of Pascal sources based on file-name
328 - Pascal-style display of data types, variables, and functions;
330 - a Pascal expression parser.
332 However, some important features are not yet supported.
334 - Pascal string operations are not supported at all;
336 - there are some problems with boolean types;
338 - Pascal type hexadecimal constants are not supported
339 because they conflict with the internal variables format;
341 - support for Pascal objects and classes is not full yet;
343 - unlike Pascal, GDB is case-sensitive for symbol names.
345 * Changes in completion.
347 Commands such as `shell', `run' and `set args', which pass arguments
348 to inferior programs, now complete on file names, similar to what
349 users expect at the shell prompt.
351 Commands which accept locations, such as `disassemble', `print',
352 `breakpoint', `until', etc. now complete on filenames as well as
353 program symbols. Thus, if you type "break foob TAB", and the source
354 files linked into the programs include `foobar.c', that file name will
355 be one of the candidates for completion. However, file names are not
356 considered for completion after you typed a colon that delimits a file
357 name from a name of a function in that file, as in "break foo.c:bar".
359 `set demangle-style' completes on available demangling styles.
361 * New platform-independent commands:
363 It is now possible to define a post-hook for a command as well as a
364 hook that runs before the command. For more details, see the
365 documentation of `hookpost' in the GDB manual.
367 * Changes in GNU/Linux native debugging.
369 Support for debugging multi-threaded programs has been completely
370 revised for all platforms except m68k and sparc. You can now debug as
371 many threads as your system allows you to have.
373 Attach/detach is supported for multi-threaded programs.
375 Support for SSE registers was added for x86. This doesn't work for
376 multi-threaded programs though.
378 * Changes in MIPS configurations.
380 Multi-arch support is enabled for all MIPS configurations.
382 GDB can now be built as native debugger on SGI Irix 6.x systems for
383 debugging n32 executables. (Debugging 64-bit executables is not yet
386 * Unified support for hardware watchpoints in all x86 configurations.
388 Most (if not all) native x86 configurations support hardware-assisted
389 breakpoints and watchpoints in a unified manner. This support
390 implements debug register sharing between watchpoints, which allows to
391 put a virtually infinite number of watchpoints on the same address,
392 and also supports watching regions up to 16 bytes with several debug
395 The new maintenance command `maintenance show-debug-regs' toggles
396 debugging print-outs in functions that insert, remove, and test
397 watchpoints and hardware breakpoints.
399 * Changes in the DJGPP native configuration.
401 New command ``info dos sysinfo'' displays assorted information about
402 the CPU, OS, memory, and DPMI server.
404 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
405 display information about segment descriptors stored in GDT, LDT, and
408 New commands ``info dos pde'' and ``info dos pte'' display entries
409 from Page Directory and Page Tables (for now works with CWSDPMI only).
410 New command ``info dos address-pte'' displays the Page Table entry for
411 a given linear address.
413 GDB can now pass command lines longer than 126 characters to the
414 program being debugged (requires an update to the libdbg.a library
415 which is part of the DJGPP development kit).
417 DWARF2 debug info is now supported.
419 It is now possible to `step' and `next' through calls to `longjmp'.
421 * Changes in documentation.
423 All GDB documentation was converted to GFDL, the GNU Free
424 Documentation License.
426 Tracepoints-related commands are now fully documented in the GDB
429 TUI, the Text-mode User Interface, is now documented in the manual.
431 Tracepoints-related commands are now fully documented in the GDB
434 The "GDB Internals" manual now has an index. It also includes
435 documentation of `ui_out' functions, GDB coding standards, x86
436 hardware watchpoints, and memory region attributes.
438 * GDB's version number moved to ``version.in''
440 The Makefile variable VERSION has been replaced by the file
441 ``version.in''. People creating GDB distributions should update the
442 contents of this file.
446 GUD support is now a standard part of the EMACS distribution.
448 *** Changes in GDB 5.0:
450 * Improved support for debugging FP programs on x86 targets
452 Unified and much-improved support for debugging floating-point
453 programs on all x86 targets. In particular, ``info float'' now
454 displays the FP registers in the same format on all x86 targets, with
455 greater level of detail.
457 * Improvements and bugfixes in hardware-assisted watchpoints
459 It is now possible to watch array elements, struct members, and
460 bitfields with hardware-assisted watchpoints. Data-read watchpoints
461 on x86 targets no longer erroneously trigger when the address is
464 * Improvements in the native DJGPP version of GDB
466 The distribution now includes all the scripts and auxiliary files
467 necessary to build the native DJGPP version on MS-DOS/MS-Windows
468 machines ``out of the box''.
470 The DJGPP version can now debug programs that use signals. It is
471 possible to catch signals that happened in the debuggee, deliver
472 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
473 would kill the program being debugged.) Programs that hook hardware
474 interrupts (keyboard, timer, etc.) can also be debugged.
476 It is now possible to debug DJGPP programs that redirect their
477 standard handles or switch them to raw (as opposed to cooked) mode, or
478 even close them. The command ``run < foo > bar'' works as expected,
479 and ``info terminal'' reports useful information about the debuggee's
480 terminal, including raw/cooked mode, redirection, etc.
482 The DJGPP version now uses termios functions for console I/O, which
483 enables debugging graphics programs. Interrupting GDB with Ctrl-C
486 DOS-style file names with drive letters are now fully supported by
489 It is now possible to debug DJGPP programs that switch their working
490 directory. It is also possible to rerun the debuggee any number of
491 times without restarting GDB; thus, you can use the same setup,
492 breakpoints, etc. for many debugging sessions.
494 * New native configurations
496 ARM GNU/Linux arm*-*-linux*
497 PowerPC GNU/Linux powerpc-*-linux*
501 Motorola MCore mcore-*-*
502 x86 VxWorks i[3456]86-*-vxworks*
503 PowerPC VxWorks powerpc-*-vxworks*
504 TI TMS320C80 tic80-*-*
506 * OBSOLETE configurations
508 Altos 3068 m68*-altos-*
509 Convex c1-*-*, c2-*-*
511 ARM RISCix arm-*-* (as host)
514 Configurations that have been declared obsolete will be commented out,
515 but the code will be left in place. If there is no activity to revive
516 these configurations before the next release of GDB, the sources will
517 be permanently REMOVED.
519 * Gould support removed
521 Support for the Gould PowerNode and NP1 has been removed.
523 * New features for SVR4
525 On SVR4 native platforms (such as Solaris), if you attach to a process
526 without first loading a symbol file, GDB will now attempt to locate and
527 load symbols from the running process's executable file.
529 * Many C++ enhancements
531 C++ support has been greatly improved. Overload resolution now works properly
532 in almost all cases. RTTI support is on the way.
534 * Remote targets can connect to a sub-program
536 A popen(3) style serial-device has been added. This device starts a
537 sub-process (such as a stand-alone simulator) and then communicates
538 with that. The sub-program to run is specified using the syntax
539 ``|<program> <args>'' vis:
541 (gdb) set remotedebug 1
542 (gdb) target extended-remote |mn10300-elf-sim program-args
544 * MIPS 64 remote protocol
546 A long standing bug in the mips64 remote protocol where by GDB
547 expected certain 32 bit registers (ex SR) to be transfered as 32
548 instead of 64 bits has been fixed.
550 The command ``set remote-mips64-transfers-32bit-regs on'' has been
551 added to provide backward compatibility with older versions of GDB.
553 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
555 The command ``set remotebinarydownload'' command has been replaced by
556 ``set remote X-packet''. Other commands in ``set remote'' family
557 include ``set remote P-packet''.
559 * Breakpoint commands accept ranges.
561 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
562 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
563 ``tracepoint passcount'' also accepts a range of tracepoints.
565 * ``apropos'' command added.
567 The ``apropos'' command searches through command names and
568 documentation strings, printing out matches, making it much easier to
569 try to find a command that does what you are looking for.
573 A new machine oriented interface (MI) has been added to GDB. This
574 interface is designed for debug environments running GDB as a separate
575 process. This is part of the long term libGDB project. See the
576 "GDB/MI" chapter of the GDB manual for further information. It can be
577 enabled by configuring with:
579 .../configure --enable-gdbmi
581 *** Changes in GDB-4.18:
583 * New native configurations
585 HP-UX 10.20 hppa*-*-hpux10.20
586 HP-UX 11.x hppa*-*-hpux11.0*
587 M68K GNU/Linux m68*-*-linux*
591 Fujitsu FR30 fr30-*-elf*
592 Intel StrongARM strongarm-*-*
593 Mitsubishi D30V d30v-*-*
595 * OBSOLETE configurations
597 Gould PowerNode, NP1 np1-*-*, pn-*-*
599 Configurations that have been declared obsolete will be commented out,
600 but the code will be left in place. If there is no activity to revive
601 these configurations before the next release of GDB, the sources will
602 be permanently REMOVED.
606 As a compatibility experiment, GDB's source files buildsym.h and
607 buildsym.c have been converted to pure standard C, no longer
608 containing any K&R compatibility code. We believe that all systems in
609 use today either come with a standard C compiler, or have a GCC port
610 available. If this is not true, please report the affected
611 configuration to bug-gdb@gnu.org immediately. See the README file for
612 information about getting a standard C compiler if you don't have one
617 GDB now uses readline 2.2.
619 * set extension-language
621 You can now control the mapping between filename extensions and source
622 languages by using the `set extension-language' command. For instance,
623 you can ask GDB to treat .c files as C++ by saying
624 set extension-language .c c++
625 The command `info extensions' lists all of the recognized extensions
626 and their associated languages.
628 * Setting processor type for PowerPC and RS/6000
630 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
631 you can use the `set processor' command to specify what variant of the
632 PowerPC family you are debugging. The command
636 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
637 following PowerPC and RS6000 variants:
639 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
640 rs6000 IBM RS6000 ("POWER") architecture, user-level view
642 403GC IBM PowerPC 403GC
643 505 Motorola PowerPC 505
644 860 Motorola PowerPC 860 or 850
645 601 Motorola PowerPC 601
646 602 Motorola PowerPC 602
647 603 Motorola/IBM PowerPC 603 or 603e
648 604 Motorola PowerPC 604 or 604e
649 750 Motorola/IBM PowerPC 750 or 750
651 At the moment, this command just tells GDB what to name the
652 special-purpose processor registers. Since almost all the affected
653 registers are inaccessible to user-level programs, this command is
654 only useful for remote debugging in its present form.
658 Thanks to a major code donation from Hewlett-Packard, GDB now has much
659 more extensive support for HP-UX. Added features include shared
660 library support, kernel threads and hardware watchpoints for 11.00,
661 support for HP's ANSI C and C++ compilers, and a compatibility mode
662 for xdb and dbx commands.
666 HP's donation includes the new concept of catchpoints, which is a
667 generalization of the old catch command. On HP-UX, it is now possible
668 to catch exec, fork, and vfork, as well as library loading.
670 This means that the existing catch command has changed; its first
671 argument now specifies the type of catch to be set up. See the
672 output of "help catch" for a list of catchpoint types.
674 * Debugging across forks
676 On HP-UX, you can choose which process to debug when a fork() happens
681 HP has donated a curses-based terminal user interface (TUI). To get
682 it, build with --enable-tui. Although this can be enabled for any
683 configuration, at present it only works for native HP debugging.
685 * GDB remote protocol additions
687 A new protocol packet 'X' that writes binary data is now available.
688 Default behavior is to try 'X', then drop back to 'M' if the stub
689 fails to respond. The settable variable `remotebinarydownload'
690 allows explicit control over the use of 'X'.
692 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
693 full 64-bit address. The command
695 set remoteaddresssize 32
697 can be used to revert to the old behaviour. For existing remote stubs
698 the change should not be noticed, as the additional address information
701 In order to assist in debugging stubs, you may use the maintenance
702 command `packet' to send any text string to the stub. For instance,
704 maint packet heythere
706 sends the packet "$heythere#<checksum>". Note that it is very easy to
707 disrupt a debugging session by sending the wrong packet at the wrong
710 The compare-sections command allows you to compare section data on the
711 target to what is in the executable file without uploading or
712 downloading, by comparing CRC checksums.
714 * Tracing can collect general expressions
716 You may now collect general expressions at tracepoints. This requires
717 further additions to the target-side stub; see tracepoint.c and
718 doc/agentexpr.texi for further details.
720 * mask-address variable for Mips
722 For Mips targets, you may control the zeroing of the upper 32 bits of
723 a 64-bit address by entering `set mask-address on'. This is mainly
724 of interest to users of embedded R4xxx and R5xxx processors.
726 * Higher serial baud rates
728 GDB's serial code now allows you to specify baud rates 57600, 115200,
729 230400, and 460800 baud. (Note that your host system may not be able
730 to achieve all of these rates.)
734 The i960 configuration now includes an initial implementation of a
735 builtin simulator, contributed by Jim Wilson.
738 *** Changes in GDB-4.17:
740 * New native configurations
742 Alpha GNU/Linux alpha*-*-linux*
743 Unixware 2.x i[3456]86-unixware2*
744 Irix 6.x mips*-sgi-irix6*
745 PowerPC GNU/Linux powerpc-*-linux*
746 PowerPC Solaris powerpcle-*-solaris*
747 Sparc GNU/Linux sparc-*-linux*
748 Motorola sysV68 R3V7.1 m68k-motorola-sysv
752 Argonaut Risc Chip (ARC) arc-*-*
753 Hitachi H8/300S h8300*-*-*
754 Matsushita MN10200 w/simulator mn10200-*-*
755 Matsushita MN10300 w/simulator mn10300-*-*
756 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
757 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
758 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
759 Mitsubishi D10V w/simulator d10v-*-*
760 Mitsubishi M32R/D w/simulator m32r-*-elf*
761 Tsqware Sparclet sparclet-*-*
762 NEC V850 w/simulator v850-*-*
764 * New debugging protocols
766 ARM with RDI protocol arm*-*-*
767 M68K with dBUG monitor m68*-*-{aout,coff,elf}
768 DDB and LSI variants of PMON protocol mips*-*-*
769 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
770 PowerPC with SDS protocol powerpc{,le}-*-eabi
771 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
775 All configurations can now understand and use the DWARF 2 debugging
776 format. The choice is automatic, if the symbol file contains DWARF 2
781 GDB now includes basic Java language support. This support is
782 only useful with Java compilers that produce native machine code.
784 * solib-absolute-prefix and solib-search-path
786 For SunOS and SVR4 shared libraries, you may now set the prefix for
787 loading absolute shared library symbol files, and the search path for
788 locating non-absolute shared library symbol files.
790 * Live range splitting
792 GDB can now effectively debug code for which GCC has performed live
793 range splitting as part of its optimization. See gdb/doc/LRS for
794 more details on the expected format of the stabs information.
798 GDB's support for the GNU Hurd, including thread debugging, has been
799 updated to work with current versions of the Hurd.
803 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
804 instruction set. ARM GDB automatically detects when Thumb
805 instructions are in use, and adjusts disassembly and backtracing
810 GDB's MIPS target configurations now handle the MIP16 16-bit
815 GDB now includes support for overlays; if an executable has been
816 linked such that multiple sections are based at the same address, GDB
817 will decide which section to use for symbolic info. You can choose to
818 control the decision manually, using overlay commands, or implement
819 additional target-side support and use "overlay load-target" to bring
820 in the overlay mapping. Do "help overlay" for more detail.
824 The command "info symbol <address>" displays information about
825 the symbol at the specified address.
829 The standard remote protocol now includes an extension that allows
830 asynchronous collection and display of trace data. This requires
831 extensive support in the target-side debugging stub. Tracing mode
832 includes a new interaction mode in GDB and new commands: see the
833 file tracepoint.c for more details.
837 Configurations for embedded MIPS now include a simulator contributed
838 by Cygnus Solutions. The simulator supports the instruction sets
839 of most MIPS variants.
843 Sparc configurations may now include the ERC32 simulator contributed
844 by the European Space Agency. The simulator is not built into
845 Sparc targets by default; configure with --enable-sim to include it.
849 For target configurations that may include multiple variants of a
850 basic architecture (such as MIPS and SH), you may now set the
851 architecture explicitly. "set arch" sets, "info arch" lists
852 the possible architectures.
854 *** Changes in GDB-4.16:
856 * New native configurations
858 Windows 95, x86 Windows NT i[345]86-*-cygwin32
859 M68K NetBSD m68k-*-netbsd*
860 PowerPC AIX 4.x powerpc-*-aix*
861 PowerPC MacOS powerpc-*-macos*
862 PowerPC Windows NT powerpcle-*-cygwin32
863 RS/6000 AIX 4.x rs6000-*-aix4*
867 ARM with RDP protocol arm-*-*
868 I960 with MON960 i960-*-coff
869 MIPS VxWorks mips*-*-vxworks*
870 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
871 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
873 Matra Sparclet sparclet-*-*
877 The powerpc-eabi configuration now includes the PSIM simulator,
878 contributed by Andrew Cagney, with assistance from Mike Meissner.
879 PSIM is a very elaborate model of the PowerPC, including not only
880 basic instruction set execution, but also details of execution unit
881 performance and I/O hardware. See sim/ppc/README for more details.
885 GDB now works with Solaris 2.5.
887 * Windows 95/NT native
889 GDB will now work as a native debugger on Windows 95 and Windows NT.
890 To build it from source, you must use the "gnu-win32" environment,
891 which uses a DLL to emulate enough of Unix to run the GNU tools.
892 Further information, binaries, and sources are available at
893 ftp.cygnus.com, under pub/gnu-win32.
895 * dont-repeat command
897 If a user-defined command includes the command `dont-repeat', then the
898 command will not be repeated if the user just types return. This is
899 useful if the command is time-consuming to run, so that accidental
900 extra keystrokes don't run the same command many times.
902 * Send break instead of ^C
904 The standard remote protocol now includes an option to send a break
905 rather than a ^C to the target in order to interrupt it. By default,
906 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
908 * Remote protocol timeout
910 The standard remote protocol includes a new variable `remotetimeout'
911 that allows you to set the number of seconds before GDB gives up trying
912 to read from the target. The default value is 2.
914 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
916 By default GDB will automatically keep track of objects as they are
917 loaded and unloaded by the dynamic linker. By using the command `set
918 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
919 when shared library events occur, thus allowing you to set breakpoints
920 in shared libraries which are explicitly loaded by the inferior.
922 Note this feature does not work on hpux8. On hpux9 you must link
923 /usr/lib/end.o into your program. This feature should work
924 automatically on hpux10.
926 * Irix 5.x hardware watchpoint support
928 Irix 5 configurations now support the use of hardware watchpoints.
930 * Mips protocol "SYN garbage limit"
932 When debugging a Mips target using the `target mips' protocol, you
933 may set the number of characters that GDB will ignore by setting
934 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
935 every character. The default value is 1050.
937 * Recording and replaying remote debug sessions
939 If you set `remotelogfile' to the name of a file, gdb will write to it
940 a recording of a remote debug session. This recording may then be
941 replayed back to gdb using "gdbreplay". See gdbserver/README for
942 details. This is useful when you have a problem with GDB while doing
943 remote debugging; you can make a recording of the session and send it
944 to someone else, who can then recreate the problem.
946 * Speedups for remote debugging
948 GDB includes speedups for downloading and stepping MIPS systems using
949 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
950 and more efficient S-record downloading.
952 * Memory use reductions and statistics collection
954 GDB now uses less memory and reports statistics about memory usage.
955 Try the `maint print statistics' command, for example.
957 *** Changes in GDB-4.15:
961 The symbol reader for AIX GDB now uses partial symbol tables. This
962 can greatly improve startup time, especially for large executables.
964 * Remote targets use caching
966 Remote targets now use a data cache to speed up communication with the
967 remote side. The data cache could lead to incorrect results because
968 it doesn't know about volatile variables, thus making it impossible to
969 debug targets which use memory mapped I/O devices. `set remotecache
970 off' turns the the data cache off.
972 * Remote targets may have threads
974 The standard remote protocol now includes support for multiple threads
975 in the target system, using new protocol commands 'H' and 'T'. See
976 gdb/remote.c for details.
980 If GDB is configured with `--enable-netrom', then it will include
981 support for the NetROM ROM emulator from XLNT Designs. The NetROM
982 acts as though it is a bank of ROM on the target board, but you can
983 write into it over the network. GDB's support consists only of
984 support for fast loading into the emulated ROM; to debug, you must use
985 another protocol, such as standard remote protocol. The usual
986 sequence is something like
988 target nrom <netrom-hostname>
990 target remote <netrom-hostname>:1235
994 GDB now includes support for the Apple Macintosh, as a host only. It
995 may be run as either an MPW tool or as a standalone application, and
996 it can debug through the serial port. All the usual GDB commands are
997 available, but to the target command, you must supply "serial" as the
998 device type instead of "/dev/ttyXX". See mpw-README in the main
999 directory for more information on how to build. The MPW configuration
1000 scripts */mpw-config.in support only a few targets, and only the
1001 mips-idt-ecoff target has been tested.
1005 GDB configuration now uses autoconf. This is not user-visible,
1006 but does simplify configuration and building.
1010 GDB now supports hpux10.
1012 *** Changes in GDB-4.14:
1014 * New native configurations
1016 x86 FreeBSD i[345]86-*-freebsd
1017 x86 NetBSD i[345]86-*-netbsd
1018 NS32k NetBSD ns32k-*-netbsd
1019 Sparc NetBSD sparc-*-netbsd
1023 A29K VxWorks a29k-*-vxworks
1024 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1025 CPU32 EST-300 emulator m68*-*-est*
1026 PowerPC ELF powerpc-*-elf
1029 * Alpha OSF/1 support for procfs
1031 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1032 possible to attach to running processes. As the mounting of the /proc
1033 filesystem is optional on the Alpha, GDB automatically determines
1034 the availability of /proc during startup. This can lead to problems
1035 if /proc is unmounted after GDB has been started.
1037 * Arguments to user-defined commands
1039 User commands may accept up to 10 arguments separated by whitespace.
1040 Arguments are accessed within the user command via $arg0..$arg9. A
1043 print $arg0 + $arg1 + $arg2
1045 To execute the command use:
1048 Defines the command "adder" which prints the sum of its three arguments.
1049 Note the arguments are text substitutions, so they may reference variables,
1050 use complex expressions, or even perform inferior function calls.
1052 * New `if' and `while' commands
1054 This makes it possible to write more sophisticated user-defined
1055 commands. Both commands take a single argument, which is the
1056 expression to evaluate, and must be followed by the commands to
1057 execute, one per line, if the expression is nonzero, the list being
1058 terminated by the word `end'. The `if' command list may include an
1059 `else' word, which causes the following commands to be executed only
1060 if the expression is zero.
1062 * Fortran source language mode
1064 GDB now includes partial support for Fortran 77. It will recognize
1065 Fortran programs and can evaluate a subset of Fortran expressions, but
1066 variables and functions may not be handled correctly. GDB will work
1067 with G77, but does not yet know much about symbols emitted by other
1070 * Better HPUX support
1072 Most debugging facilities now work on dynamic executables for HPPAs
1073 running hpux9 or later. You can attach to running dynamically linked
1074 processes, but by default the dynamic libraries will be read-only, so
1075 for instance you won't be able to put breakpoints in them. To change
1076 that behavior do the following before running the program:
1082 This will cause the libraries to be mapped private and read-write.
1083 To revert to the normal behavior, do this:
1089 You cannot set breakpoints or examine data in the library until after
1090 the library is loaded if the function/data symbols do not have
1093 GDB can now also read debug symbols produced by the HP C compiler on
1094 HPPAs (sorry, no C++, Fortran or 68k support).
1096 * Target byte order now dynamically selectable
1098 You can choose which byte order to use with a target system, via the
1099 commands "set endian big" and "set endian little", and you can see the
1100 current setting by using "show endian". You can also give the command
1101 "set endian auto", in which case GDB will use the byte order
1102 associated with the executable. Currently, only embedded MIPS
1103 configurations support dynamic selection of target byte order.
1105 * New DOS host serial code
1107 This version uses DPMI interrupts to handle buffered I/O, so you
1108 no longer need to run asynctsr when debugging boards connected to
1111 *** Changes in GDB-4.13:
1113 * New "complete" command
1115 This lists all the possible completions for the rest of the line, if it
1116 were to be given as a command itself. This is intended for use by emacs.
1118 * Trailing space optional in prompt
1120 "set prompt" no longer adds a space for you after the prompt you set. This
1121 allows you to set a prompt which ends in a space or one that does not.
1123 * Breakpoint hit counts
1125 "info break" now displays a count of the number of times the breakpoint
1126 has been hit. This is especially useful in conjunction with "ignore"; you
1127 can ignore a large number of breakpoint hits, look at the breakpoint info
1128 to see how many times the breakpoint was hit, then run again, ignoring one
1129 less than that number, and this will get you quickly to the last hit of
1132 * Ability to stop printing at NULL character
1134 "set print null-stop" will cause GDB to stop printing the characters of
1135 an array when the first NULL is encountered. This is useful when large
1136 arrays actually contain only short strings.
1138 * Shared library breakpoints
1140 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1141 breakpoints in shared libraries before the executable is run.
1143 * Hardware watchpoints
1145 There is a new hardware breakpoint for the watch command for sparclite
1146 targets. See gdb/sparclite/hw_breakpoint.note.
1148 Hardware watchpoints are also now supported under GNU/Linux.
1152 Annotations have been added. These are for use with graphical interfaces,
1153 and are still experimental. Currently only gdba.el uses these.
1155 * Improved Irix 5 support
1157 GDB now works properly with Irix 5.2.
1159 * Improved HPPA support
1161 GDB now works properly with the latest GCC and GAS.
1163 * New native configurations
1165 Sequent PTX4 i[34]86-sequent-ptx4
1166 HPPA running OSF/1 hppa*-*-osf*
1167 Atari TT running SVR4 m68*-*-sysv4*
1168 RS/6000 LynxOS rs6000-*-lynxos*
1172 OS/9000 i[34]86-*-os9k
1173 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1176 * Hitachi SH7000 and E7000-PC ICE support
1178 There is now support for communicating with the Hitachi E7000-PC ICE.
1179 This is available automatically when GDB is configured for the SH.
1183 As usual, a variety of small fixes and improvements, both generic
1184 and configuration-specific. See the ChangeLog for more detail.
1186 *** Changes in GDB-4.12:
1188 * Irix 5 is now supported
1192 GDB-4.12 on the HPPA has a number of changes which make it unable
1193 to debug the output from the currently released versions of GCC and
1194 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1195 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1196 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1199 *** Changes in GDB-4.11:
1201 * User visible changes:
1205 The "set remotedebug" option is now consistent between the mips remote
1206 target, remote targets using the gdb-specific protocol, UDI (AMD's
1207 debug protocol for the 29k) and the 88k bug monitor. It is now an
1208 integer specifying a debug level (normally 0 or 1, but 2 means more
1209 debugging info for the mips target).
1211 * DEC Alpha native support
1213 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1214 debug info, but GDB works fairly well with the DEC compiler and should
1215 work with a future GCC release. See the README file for a few
1216 Alpha-specific notes.
1218 * Preliminary thread implementation
1220 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1222 * LynxOS native and target support for 386
1224 This release has been hosted on LynxOS 2.2, and also can be configured
1225 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1228 * Improvements in C++ mangling/demangling.
1230 This release has much better g++ debugging, specifically in name
1231 mangling/demangling, virtual function calls, print virtual table,
1232 call methods, ...etc.
1234 *** Changes in GDB-4.10:
1236 * User visible changes:
1238 Remote debugging using the GDB-specific (`target remote') protocol now
1239 supports the `load' command. This is only useful if you have some
1240 other way of getting the stub to the target system, and you can put it
1241 somewhere in memory where it won't get clobbered by the download.
1243 Filename completion now works.
1245 When run under emacs mode, the "info line" command now causes the
1246 arrow to point to the line specified. Also, "info line" prints
1247 addresses in symbolic form (as well as hex).
1249 All vxworks based targets now support a user settable option, called
1250 vxworks-timeout. This option represents the number of seconds gdb
1251 should wait for responses to rpc's. You might want to use this if
1252 your vxworks target is, perhaps, a slow software simulator or happens
1253 to be on the far side of a thin network line.
1257 This release contains support for using a DEC alpha as a GDB host for
1258 cross debugging. Native alpha debugging is not supported yet.
1261 *** Changes in GDB-4.9:
1265 This is the first GDB release which is accompanied by a matching testsuite.
1266 The testsuite requires installation of dejagnu, which should be available
1267 via ftp from most sites that carry GNU software.
1271 'Cfront' style demangling has had its name changed to 'ARM' style, to
1272 emphasize that it was written from the specifications in the C++ Annotated
1273 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1274 disclaimers, it still generated too much confusion with users attempting to
1275 use gdb with AT&T cfront.
1279 GDB now uses a standard remote interface to a simulator library.
1280 So far, the library contains simulators for the Zilog Z8001/2, the
1281 Hitachi H8/300, H8/500 and Super-H.
1283 * New targets supported
1285 H8/300 simulator h8300-hitachi-hms or h8300hms
1286 H8/500 simulator h8500-hitachi-hms or h8500hms
1287 SH simulator sh-hitachi-hms or sh
1288 Z8000 simulator z8k-zilog-none or z8ksim
1289 IDT MIPS board over serial line mips-idt-ecoff
1291 Cross-debugging to GO32 targets is supported. It requires a custom
1292 version of the i386-stub.c module which is integrated with the
1293 GO32 memory extender.
1295 * New remote protocols
1297 MIPS remote debugging protocol.
1299 * New source languages supported
1301 This version includes preliminary support for Chill, a Pascal like language
1302 used by telecommunications companies. Chill support is also being integrated
1303 into the GNU compiler, but we don't know when it will be publically available.
1306 *** Changes in GDB-4.8:
1308 * HP Precision Architecture supported
1310 GDB now supports HP PA-RISC machines running HPUX. A preliminary
1311 version of this support was available as a set of patches from the
1312 University of Utah. GDB does not support debugging of programs
1313 compiled with the HP compiler, because HP will not document their file
1314 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
1315 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
1317 Many problems in the preliminary version have been fixed.
1319 * Faster and better demangling
1321 We have improved template demangling and fixed numerous bugs in the GNU style
1322 demangler. It can now handle type modifiers such as `static' or `const'. Wide
1323 character types (wchar_t) are now supported. Demangling of each symbol is now
1324 only done once, and is cached when the symbol table for a file is read in.
1325 This results in a small increase in memory usage for C programs, a moderate
1326 increase in memory usage for C++ programs, and a fantastic speedup in
1329 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
1330 from the specifications in the Annotated Reference Manual, which AT&T's
1331 compiler does not actually implement.
1333 * G++ multiple inheritance compiler problem
1335 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
1336 inheritance lattices was reworked to properly discover ambiguities. We
1337 recently found an example which causes this new algorithm to fail in a
1338 very subtle way, producing bad debug information for those classes.
1339 The file 'gcc.patch' (in this directory) can be applied to gcc to
1340 circumvent the problem. A future GCC release will contain a complete
1343 The previous G++ debug info problem (mentioned below for the gdb-4.7
1344 release) is fixed in gcc version 2.3.2.
1346 * Improved configure script
1348 The `configure' script will now attempt to guess your system type if
1349 you don't supply a host system type. The old scheme of supplying a
1350 host system triplet is preferable over using this. All the magic is
1351 done in the new `config.guess' script. Examine it for details.
1353 We have also brought our configure script much more in line with the FSF's
1354 version. It now supports the --with-xxx options. In particular,
1355 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
1356 The resulting GDB will not be able to read arbitrary object file formats --
1357 only the format ``expected'' to be used on the configured target system.
1358 We hope to make this the default in a future release.
1360 * Documentation improvements
1362 There's new internal documentation on how to modify GDB, and how to
1363 produce clean changes to the code. We implore people to read it
1364 before submitting changes.
1366 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
1367 M4 macros. The new texinfo.tex is provided in this release. Pre-built
1368 `info' files are also provided. To build `info' files from scratch,
1369 you will need the latest `makeinfo' release, which will be available in
1370 a future texinfo-X.Y release.
1372 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
1373 We're not sure exactly which versions have this problem, but it has
1374 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
1375 or better. If that isn't possible, there is a patch in
1376 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
1377 around this problem.
1381 GDB now supports array constants that can be used in expressions typed in by
1382 the user. The syntax is `{element, element, ...}'. Ie: you can now type
1383 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
1386 The new directory `gdb/sparclite' contains a program that demonstrates
1387 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
1389 * New native hosts supported
1391 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
1392 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
1394 * New targets supported
1396 AMD 29k family via UDI a29k-amd-udi or udi29k
1398 * New file formats supported
1400 BFD now supports reading HP/PA-RISC executables (SOM file format?),
1401 HPUX core files, and SCO 3.2v2 core files.
1405 Attaching to processes now works again; thanks for the many bug reports.
1407 We have also stomped on a bunch of core dumps caused by
1408 printf_filtered("%s") problems.
1410 We eliminated a copyright problem on the rpc and ptrace header files
1411 for VxWorks, which was discovered at the last minute during the 4.7
1412 release. You should now be able to build a VxWorks GDB.
1414 You can now interrupt gdb while an attached process is running. This
1415 will cause the attached process to stop, and give control back to GDB.
1417 We fixed problems caused by using too many file descriptors
1418 for reading symbols from object files and libraries. This was
1419 especially a problem for programs that used many (~100) shared
1422 The `step' command now only enters a subroutine if there is line number
1423 information for the subroutine. Otherwise it acts like the `next'
1424 command. Previously, `step' would enter subroutines if there was
1425 any debugging information about the routine. This avoids problems
1426 when using `cc -g1' on MIPS machines.
1428 * Internal improvements
1430 GDB's internal interfaces have been improved to make it easier to support
1431 debugging of multiple languages in the future.
1433 GDB now uses a common structure for symbol information internally.
1434 Minimal symbols (derived from linkage symbols in object files), partial
1435 symbols (from a quick scan of debug information), and full symbols
1436 contain a common subset of information, making it easier to write
1437 shared code that handles any of them.
1439 * New command line options
1441 We now accept --silent as an alias for --quiet.
1445 The memory-mapped-malloc library is now licensed under the GNU Library
1446 General Public License.
1448 *** Changes in GDB-4.7:
1450 * Host/native/target split
1452 GDB has had some major internal surgery to untangle the support for
1453 hosts and remote targets. Now, when you configure GDB for a remote
1454 target, it will no longer load in all of the support for debugging
1455 local programs on the host. When fully completed and tested, this will
1456 ensure that arbitrary host/target combinations are possible.
1458 The primary conceptual shift is to separate the non-portable code in
1459 GDB into three categories. Host specific code is required any time GDB
1460 is compiled on that host, regardless of the target. Target specific
1461 code relates to the peculiarities of the target, but can be compiled on
1462 any host. Native specific code is everything else: it can only be
1463 built when the host and target are the same system. Child process
1464 handling and core file support are two common `native' examples.
1466 GDB's use of /proc for controlling Unix child processes is now cleaner.
1467 It has been split out into a single module under the `target_ops' vector,
1468 plus two native-dependent functions for each system that uses /proc.
1470 * New hosts supported
1472 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
1473 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1474 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
1476 * New targets supported
1478 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
1479 68030 and CPU32 m68030-*-*, m68332-*-*
1481 * New native hosts supported
1483 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1484 (386bsd is not well tested yet)
1485 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
1487 * New file formats supported
1489 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
1490 supports reading of `a.out.adobe' object files, which are an a.out
1491 format extended with minimal information about multiple sections.
1495 `show copying' is the same as the old `info copying'.
1496 `show warranty' is the same as `info warrantee'.
1497 These were renamed for consistency. The old commands continue to work.
1499 `info handle' is a new alias for `info signals'.
1501 You can now define pre-command hooks, which attach arbitrary command
1502 scripts to any command. The commands in the hook will be executed
1503 prior to the user's command. You can also create a hook which will be
1504 executed whenever the program stops. See gdb.texinfo.
1508 We now deal with Cfront style name mangling, and can even extract type
1509 info from mangled symbols. GDB can automatically figure out which
1510 symbol mangling style your C++ compiler uses.
1512 Calling of methods and virtual functions has been improved as well.
1516 The crash that occured when debugging Sun Ansi-C compiled binaries is
1517 fixed. This was due to mishandling of the extra N_SO stabs output
1520 We also finally got Ultrix 4.2 running in house, and fixed core file
1521 support, with help from a dozen people on the net.
1523 John M. Farrell discovered that the reason that single-stepping was so
1524 slow on all of the Mips based platforms (primarily SGI and DEC) was
1525 that we were trying to demangle and lookup a symbol used for internal
1526 purposes on every instruction that was being stepped through. Changing
1527 the name of that symbol so that it couldn't be mistaken for a C++
1528 mangled symbol sped things up a great deal.
1530 Rich Pixley sped up symbol lookups in general by getting much smarter
1531 about when C++ symbol mangling is necessary. This should make symbol
1532 completion (TAB on the command line) much faster. It's not as fast as
1533 we'd like, but it's significantly faster than gdb-4.6.
1537 A new user controllable variable 'call_scratch_address' can
1538 specify the location of a scratch area to be used when GDB
1539 calls a function in the target. This is necessary because the
1540 usual method of putting the scratch area on the stack does not work
1541 in systems that have separate instruction and data spaces.
1543 We integrated changes to support the 29k UDI (Universal Debugger
1544 Interface), but discovered at the last minute that we didn't have all
1545 of the appropriate copyright paperwork. We are working with AMD to
1546 resolve this, and hope to have it available soon.
1550 We have sped up the remote serial line protocol, especially for targets
1551 with lots of registers. It now supports a new `expedited status' ('T')
1552 message which can be used in place of the existing 'S' status message.
1553 This allows the remote stub to send only the registers that GDB
1554 needs to make a quick decision about single-stepping or conditional
1555 breakpoints, eliminating the need to fetch the entire register set for
1556 each instruction being stepped through.
1558 The GDB remote serial protocol now implements a write-through cache for
1559 registers, only re-reading the registers if the target has run.
1561 There is also a new remote serial stub for SPARC processors. You can
1562 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
1563 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
1564 processor with a serial port.
1568 Configure.in files have become much easier to read and modify. A new
1569 `table driven' format makes it more obvious what configurations are
1570 supported, and what files each one uses.
1574 There is a new opcodes library which will eventually contain all of the
1575 disassembly routines and opcode tables. At present, it only contains
1576 Sparc and Z8000 routines. This will allow the assembler, debugger, and
1577 disassembler (binutils/objdump) to share these routines.
1579 The libiberty library is now copylefted under the GNU Library General
1580 Public License. This allows more liberal use, and was done so libg++
1581 can use it. This makes no difference to GDB, since the Library License
1582 grants all the rights from the General Public License.
1586 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
1587 reference to the stabs symbol info used by the debugger. It is (as far
1588 as we know) the only published document on this fascinating topic. We
1589 encourage you to read it, compare it to the stabs information on your
1590 system, and send improvements on the document in general (to
1591 bug-gdb@prep.ai.mit.edu).
1593 And, of course, many bugs have been fixed.
1596 *** Changes in GDB-4.6:
1598 * Better support for C++ function names
1600 GDB now accepts as input the "demangled form" of C++ overloaded function
1601 names and member function names, and can do command completion on such names
1602 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
1603 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
1604 Make use of command completion, it is your friend.
1606 GDB also now accepts a variety of C++ mangled symbol formats. They are
1607 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
1608 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
1609 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
1610 for the list of formats.
1612 * G++ symbol mangling problem
1614 Recent versions of gcc have a bug in how they emit debugging information for
1615 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
1616 directory) can be applied to gcc to fix the problem. Alternatively, if you
1617 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
1618 usual symptom is difficulty with setting breakpoints on methods. GDB complains
1619 about the method being non-existent. (We believe that version 2.2.2 of GCC has
1622 * New 'maintenance' command
1624 All of the commands related to hacking GDB internals have been moved out of
1625 the main command set, and now live behind the 'maintenance' command. This
1626 can also be abbreviated as 'mt'. The following changes were made:
1628 dump-me -> maintenance dump-me
1629 info all-breakpoints -> maintenance info breakpoints
1630 printmsyms -> maintenance print msyms
1631 printobjfiles -> maintenance print objfiles
1632 printpsyms -> maintenance print psymbols
1633 printsyms -> maintenance print symbols
1635 The following commands are new:
1637 maintenance demangle Call internal GDB demangler routine to
1638 demangle a C++ link name and prints the result.
1639 maintenance print type Print a type chain for a given symbol
1641 * Change to .gdbinit file processing
1643 We now read the $HOME/.gdbinit file before processing the argv arguments
1644 (e.g. reading symbol files or core files). This allows global parameters to
1645 be set, which will apply during the symbol reading. The ./.gdbinit is still
1646 read after argv processing.
1648 * New hosts supported
1650 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
1652 GNU/Linux support i386-unknown-linux or linux
1654 We are also including code to support the HP/PA running BSD and HPUX. This
1655 is almost guaranteed not to work, as we didn't have time to test or build it
1656 for this release. We are including it so that the more adventurous (or
1657 masochistic) of you can play with it. We also had major problems with the
1658 fact that the compiler that we got from HP doesn't support the -g option.
1661 * New targets supported
1663 Hitachi H8/300 h8300-hitachi-hms or h8300hms
1665 * More smarts about finding #include files
1667 GDB now remembers the compilation directory for all include files, and for
1668 all files from which C is generated (like yacc and lex sources). This
1669 greatly improves GDB's ability to find yacc/lex sources, and include files,
1670 especially if you are debugging your program from a directory different from
1671 the one that contains your sources.
1673 We also fixed a bug which caused difficulty with listing and setting
1674 breakpoints in include files which contain C code. (In the past, you had to
1675 try twice in order to list an include file that you hadn't looked at before.)
1677 * Interesting infernals change
1679 GDB now deals with arbitrary numbers of sections, where the symbols for each
1680 section must be relocated relative to that section's landing place in the
1681 target's address space. This work was needed to support ELF with embedded
1682 stabs used by Solaris-2.0.
1684 * Bug fixes (of course!)
1686 There have been loads of fixes for the following things:
1687 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
1688 i960, stabs, DOS(GO32), procfs, etc...
1690 See the ChangeLog for details.
1692 *** Changes in GDB-4.5:
1694 * New machines supported (host and target)
1696 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
1698 SGI Irix-4.x mips-sgi-irix4 or iris4
1700 * New malloc package
1702 GDB now uses a new memory manager called mmalloc, based on gmalloc.
1703 Mmalloc is capable of handling mutiple heaps of memory. It is also
1704 capable of saving a heap to a file, and then mapping it back in later.
1705 This can be used to greatly speedup the startup of GDB by using a
1706 pre-parsed symbol table which lives in a mmalloc managed heap. For
1707 more details, please read mmalloc/mmalloc.texi.
1711 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
1712 'help info proc' for details.
1714 * MIPS ecoff symbol table format
1716 The code that reads MIPS symbol table format is now supported on all hosts.
1717 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
1720 * File name changes for MS-DOS
1722 Many files in the config directories have been renamed to make it easier to
1723 support GDB on MS-DOSe systems (which have very restrictive file name
1724 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
1725 environment) is close to working but has some remaining problems. Note
1726 that debugging of DOS programs is not supported, due to limitations
1727 in the ``operating system'', but it can be used to host cross-debugging.
1729 * Cross byte order fixes
1731 Many fixes have been made to support cross debugging of Sparc and MIPS
1732 targets from hosts whose byte order differs.
1734 * New -mapped and -readnow options
1736 If memory-mapped files are available on your system through the 'mmap'
1737 system call, you can use the -mapped option on the `file' or
1738 `symbol-file' commands to cause GDB to write the symbols from your
1739 program into a reusable file. If the program you are debugging is
1740 called `/path/fred', the mapped symbol file will be `./fred.syms'.
1741 Future GDB debugging sessions will notice the presence of this file,
1742 and will quickly map in symbol information from it, rather than reading
1743 the symbol table from the executable program. Using the '-mapped'
1744 option in a GDB `file' or `symbol-file' command has the same effect as
1745 starting GDB with the '-mapped' command-line option.
1747 You can cause GDB to read the entire symbol table immediately by using
1748 the '-readnow' option with any of the commands that load symbol table
1749 information (or on the GDB command line). This makes the command
1750 slower, but makes future operations faster.
1752 The -mapped and -readnow options are typically combined in order to
1753 build a `fred.syms' file that contains complete symbol information.
1754 A simple GDB invocation to do nothing but build a `.syms' file for future
1757 gdb -batch -nx -mapped -readnow programname
1759 The `.syms' file is specific to the host machine on which GDB is run.
1760 It holds an exact image of GDB's internal symbol table. It cannot be
1761 shared across multiple host platforms.
1763 * longjmp() handling
1765 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
1766 siglongjmp() without losing control. This feature has not yet been ported to
1767 all systems. It currently works on many 386 platforms, all MIPS-based
1768 platforms (SGI, DECstation, etc), and Sun3/4.
1772 Preliminary work has been put in to support the new Solaris OS from Sun. At
1773 this time, it can control and debug processes, but it is not capable of
1778 As always, many many bug fixes. The major areas were with g++, and mipsread.
1779 People using the MIPS-based platforms should experience fewer mysterious
1780 crashes and trashed symbol tables.
1782 *** Changes in GDB-4.4:
1784 * New machines supported (host and target)
1786 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1788 BSD Reno on Vax vax-dec-bsd
1789 Ultrix on Vax vax-dec-ultrix
1791 * New machines supported (target)
1793 AMD 29000 embedded, using EBMON a29k-none-none
1797 GDB continues to improve its handling of C++. `References' work better.
1798 The demangler has also been improved, and now deals with symbols mangled as
1799 per the Annotated C++ Reference Guide.
1801 GDB also now handles `stabs' symbol information embedded in MIPS
1802 `ecoff' symbol tables. Since the ecoff format was not easily
1803 extensible to handle new languages such as C++, this appeared to be a
1804 good way to put C++ debugging info into MIPS binaries. This option
1805 will be supported in the GNU C compiler, version 2, when it is
1808 * New features for SVR4
1810 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
1811 shared libraries. Debugging dynamically linked programs should present
1812 only minor differences from debugging statically linked programs.
1814 The `info proc' command will print out information about any process
1815 on an SVR4 system (including the one you are debugging). At the moment,
1816 it prints the address mappings of the process.
1818 If you bring up GDB on another SVR4 system, please send mail to
1819 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
1821 * Better dynamic linking support in SunOS
1823 Reading symbols from shared libraries which contain debugging symbols
1824 now works properly. However, there remain issues such as automatic
1825 skipping of `transfer vector' code during function calls, which
1826 make it harder to debug code in a shared library, than to debug the
1827 same code linked statically.
1831 GDB is now using the latest `getopt' routines from the FSF. This
1832 version accepts the -- prefix for options with long names. GDB will
1833 continue to accept the old forms (-option and +option) as well.
1834 Various single letter abbreviations for options have been explicity
1835 added to the option table so that they won't get overshadowed in the
1836 future by other options that begin with the same letter.
1840 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
1841 Many assorted bugs have been handled. Many more remain to be handled.
1842 See the various ChangeLog files (primarily in gdb and bfd) for details.
1845 *** Changes in GDB-4.3:
1847 * New machines supported (host and target)
1849 Amiga 3000 running Amix m68k-cbm-svr4 or amix
1850 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
1851 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
1853 * Almost SCO Unix support
1855 We had hoped to support:
1856 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1857 (except for core file support), but we discovered very late in the release
1858 that it has problems with process groups that render gdb unusable. Sorry
1859 about that. I encourage people to fix it and post the fixes.
1861 * Preliminary ELF and DWARF support
1863 GDB can read ELF object files on System V Release 4, and can handle
1864 debugging records for C, in DWARF format, in ELF files. This support
1865 is preliminary. If you bring up GDB on another SVR4 system, please
1866 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
1871 GDB now uses the latest `readline' library. One user-visible change
1872 is that two tabs will list possible command completions, which previously
1873 required typing M-? (meta-question mark, or ESC ?).
1877 The `stepi' bug that many of you noticed has been squashed.
1878 Many bugs in C++ have been handled. Many more remain to be handled.
1879 See the various ChangeLog files (primarily in gdb and bfd) for details.
1881 * State of the MIPS world (in case you wondered):
1883 GDB can understand the symbol tables emitted by the compilers
1884 supplied by most vendors of MIPS-based machines, including DEC. These
1885 symbol tables are in a format that essentially nobody else uses.
1887 Some versions of gcc come with an assembler post-processor called
1888 mips-tfile. This program is required if you want to do source-level
1889 debugging of gcc-compiled programs. I believe FSF does not ship
1890 mips-tfile with gcc version 1, but it will eventually come with gcc
1893 Debugging of g++ output remains a problem. g++ version 1.xx does not
1894 really support it at all. (If you're lucky, you should be able to get
1895 line numbers and stack traces to work, but no parameters or local
1896 variables.) With some work it should be possible to improve the
1899 When gcc version 2 is released, you will have somewhat better luck.
1900 However, even then you will get confusing results for inheritance and
1903 We will eventually provide full debugging of g++ output on
1904 DECstations. This will probably involve some kind of stabs-in-ecoff
1905 encapulation, but the details have not been worked out yet.
1908 *** Changes in GDB-4.2:
1910 * Improved configuration
1912 Only one copy of `configure' exists now, and it is not self-modifying.
1913 Porting BFD is simpler.
1917 The `step' and `next' commands now only stop at the first instruction
1918 of a source line. This prevents the multiple stops that used to occur
1919 in switch statements, for-loops, etc. `Step' continues to stop if a
1920 function that has debugging information is called within the line.
1924 Lots of small bugs fixed. More remain.
1926 * New host supported (not target)
1928 Intel 386 PC clone running Mach i386-none-mach
1931 *** Changes in GDB-4.1:
1933 * Multiple source language support
1935 GDB now has internal scaffolding to handle several source languages.
1936 It determines the type of each source file from its filename extension,
1937 and will switch expression parsing and number formatting to match the
1938 language of the function in the currently selected stack frame.
1939 You can also specifically set the language to be used, with
1940 `set language c' or `set language modula-2'.
1944 GDB now has preliminary support for the GNU Modula-2 compiler,
1945 currently under development at the State University of New York at
1946 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
1947 continue through the fall of 1991 and into 1992.
1949 Other Modula-2 compilers are currently not supported, and attempting to
1950 debug programs compiled with them will likely result in an error as the
1951 symbol table is read. Feel free to work on it, though!
1953 There are hooks in GDB for strict type checking and range checking,
1954 in the `Modula-2 philosophy', but they do not currently work.
1958 GDB can now write to executable and core files (e.g. patch
1959 a variable's value). You must turn this switch on, specify
1960 the file ("exec foo" or "core foo"), *then* modify it, e.g.
1961 by assigning a new value to a variable. Modifications take
1964 * Automatic SunOS shared library reading
1966 When you run your program, GDB automatically determines where its
1967 shared libraries (if any) have been loaded, and reads their symbols.
1968 The `share' command is no longer needed. This also works when
1969 examining core files.
1973 You can specify the number of lines that the `list' command shows.
1976 * New machines supported (host and target)
1978 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
1979 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
1980 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
1982 * New hosts supported (not targets)
1984 IBM RT/PC: romp-ibm-aix or rtpc
1986 * New targets supported (not hosts)
1988 AMD 29000 embedded with COFF a29k-none-coff
1989 AMD 29000 embedded with a.out a29k-none-aout
1990 Ultracomputer remote kernel debug a29k-nyu-kern
1992 * New remote interfaces
1998 *** Changes in GDB-4.0:
2002 Wide output is wrapped at good places to make the output more readable.
2004 Gdb now supports cross-debugging from a host machine of one type to a
2005 target machine of another type. Communication with the target system
2006 is over serial lines. The ``target'' command handles connecting to the
2007 remote system; the ``load'' command will download a program into the
2008 remote system. Serial stubs for the m68k and i386 are provided. Gdb
2009 also supports debugging of realtime processes running under VxWorks,
2010 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
2011 stub on the target system.
2013 New CPUs supported include the AMD 29000 and Intel 960.
2015 GDB now reads object files and symbol tables via a ``binary file''
2016 library, which allows a single copy of GDB to debug programs of multiple
2017 object file types such as a.out and coff.
2019 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2020 refcard.dvi and refcard.ps are available to format it).
2023 * Control-Variable user interface simplified
2025 All variables that control the operation of the debugger can be set
2026 by the ``set'' command, and displayed by the ``show'' command.
2028 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2029 ``Show prompt'' produces the response:
2030 Gdb's prompt is new-gdb=>.
2032 What follows are the NEW set commands. The command ``help set'' will
2033 print a complete list of old and new set commands. ``help set FOO''
2034 will give a longer description of the variable FOO. ``show'' will show
2035 all of the variable descriptions and their current settings.
2037 confirm on/off: Enables warning questions for operations that are
2038 hard to recover from, e.g. rerunning the program while
2039 it is already running. Default is ON.
2041 editing on/off: Enables EMACS style command line editing
2042 of input. Previous lines can be recalled with
2043 control-P, the current line can be edited with control-B,
2044 you can search for commands with control-R, etc.
2047 history filename NAME: NAME is where the gdb command history
2048 will be stored. The default is .gdb_history,
2049 or the value of the environment variable
2052 history size N: The size, in commands, of the command history. The
2053 default is 256, or the value of the environment variable
2056 history save on/off: If this value is set to ON, the history file will
2057 be saved after exiting gdb. If set to OFF, the
2058 file will not be saved. The default is OFF.
2060 history expansion on/off: If this value is set to ON, then csh-like
2061 history expansion will be performed on
2062 command line input. The default is OFF.
2064 radix N: Sets the default radix for input and output. It can be set
2065 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2066 in the current radix, so "set radix 10" is always a no-op.
2068 height N: This integer value is the number of lines on a page. Default
2069 is 24, the current `stty rows'' setting, or the ``li#''
2070 setting from the termcap entry matching the environment
2073 width N: This integer value is the number of characters on a line.
2074 Default is 80, the current `stty cols'' setting, or the ``co#''
2075 setting from the termcap entry matching the environment
2078 Note: ``set screensize'' is obsolete. Use ``set height'' and
2079 ``set width'' instead.
2081 print address on/off: Print memory addresses in various command displays,
2082 such as stack traces and structure values. Gdb looks
2083 more ``symbolic'' if you turn this off; it looks more
2084 ``machine level'' with it on. Default is ON.
2086 print array on/off: Prettyprint arrays. New convenient format! Default
2089 print demangle on/off: Print C++ symbols in "source" form if on,
2092 print asm-demangle on/off: Same, for assembler level printouts
2095 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2098 * Support for Epoch Environment.
2100 The epoch environment is a version of Emacs v18 with windowing. One
2101 new command, ``inspect'', is identical to ``print'', except that if you
2102 are running in the epoch environment, the value is printed in its own
2106 * Support for Shared Libraries
2108 GDB can now debug programs and core files that use SunOS shared libraries.
2109 Symbols from a shared library cannot be referenced
2110 before the shared library has been linked with the program (this
2111 happens after you type ``run'' and before the function main() is entered).
2112 At any time after this linking (including when examining core files
2113 from dynamically linked programs), gdb reads the symbols from each
2114 shared library when you type the ``sharedlibrary'' command.
2115 It can be abbreviated ``share''.
2117 sharedlibrary REGEXP: Load shared object library symbols for files
2118 matching a unix regular expression. No argument
2119 indicates to load symbols for all shared libraries.
2121 info sharedlibrary: Status of loaded shared libraries.
2126 A watchpoint stops execution of a program whenever the value of an
2127 expression changes. Checking for this slows down execution
2128 tremendously whenever you are in the scope of the expression, but is
2129 quite useful for catching tough ``bit-spreader'' or pointer misuse
2130 problems. Some machines such as the 386 have hardware for doing this
2131 more quickly, and future versions of gdb will use this hardware.
2133 watch EXP: Set a watchpoint (breakpoint) for an expression.
2135 info watchpoints: Information about your watchpoints.
2137 delete N: Deletes watchpoint number N (same as breakpoints).
2138 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2139 enable N: Re-enables watchpoint number N (same as breakpoints).
2142 * C++ multiple inheritance
2144 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2147 * C++ exception handling
2149 Gdb now supports limited C++ exception handling. Besides the existing
2150 ability to breakpoint on an exception handler, gdb can breakpoint on
2151 the raising of an exception (before the stack is peeled back to the
2154 catch FOO: If there is a FOO exception handler in the dynamic scope,
2155 set a breakpoint to catch exceptions which may be raised there.
2156 Multiple exceptions (``catch foo bar baz'') may be caught.
2158 info catch: Lists all exceptions which may be caught in the
2159 current stack frame.
2162 * Minor command changes
2164 The command ``call func (arg, arg, ...)'' now acts like the print
2165 command, except it does not print or save a value if the function's result
2166 is void. This is similar to dbx usage.
2168 The ``up'' and ``down'' commands now always print the frame they end up
2169 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2170 frames without printing.
2172 * New directory command
2174 'dir' now adds directories to the FRONT of the source search path.
2175 The path starts off empty. Source files that contain debug information
2176 about the directory in which they were compiled can be found even
2177 with an empty path; Sun CC and GCC include this information. If GDB can't
2178 find your source file in the current directory, type "dir .".
2180 * Configuring GDB for compilation
2182 For normal use, type ``./configure host''. See README or gdb.texinfo
2185 GDB now handles cross debugging. If you are remotely debugging between
2186 two different machines, type ``./configure host -target=targ''.
2187 Host is the machine where GDB will run; targ is the machine
2188 where the program that you are debugging will run.
projects / deliverable / binutils-gdb.git / blob