1 What has changed in GDB?
2 (Organized release by release)
4 *** Changes since GDB 5.3:
6 * MIPS $fp behavior changed
8 The convenience variable $fp, for the MIPS, now consistently returns
9 the address of the current frame's base. Previously, depending on the
10 context, $fp could refer to either $sp or the current frame's base
11 address. See ``8.10 Registers'' in the manual ``Debugging with GDB:
12 The GNU Source-Level Debugger''.
14 *** Changes in GDB 5.3:
16 * ``gdbserver'' now supports multi-threaded applications on some targets
18 Support for debugging multi-threaded applications which use
19 the GNU/Linux LinuxThreads package has been added for
20 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
21 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
23 * GDB now supports C/C++ preprocessor macros.
25 GDB now expands preprocessor macro invocations in C/C++ expressions,
26 and provides various commands for showing macro definitions and how
29 The new command `macro expand EXPRESSION' expands any macro
30 invocations in expression, and shows the result.
32 The new command `show macro MACRO-NAME' shows the definition of the
33 macro named MACRO-NAME, and where it was defined.
35 Most compilers don't include information about macros in the debugging
36 information by default. In GCC 3.1, for example, you need to compile
37 your program with the options `-gdwarf-2 -g3'. If the macro
38 information is present in the executable, GDB will read it.
40 * Multi-arched targets.
42 DEC Alpha (partial) alpha*-*-*
43 DEC VAX (partial) vax-*-*
45 National Semiconductor NS32000 (partial) ns32k-*-*
46 Motorola 68000 (partial) m68k-*-*
47 Motorola MCORE mcore-*-*
51 Fujitsu FRV architecture added by Red Hat frv*-*-*
54 * New native configurations
56 Alpha NetBSD alpha*-*-netbsd*
57 SH NetBSD sh*-*-netbsdelf*
58 MIPS NetBSD mips*-*-netbsd*
59 UltraSPARC NetBSD sparc64-*-netbsd*
61 * OBSOLETE configurations and files
63 Configurations that have been declared obsolete in this release have
64 been commented out. Unless there is activity to revive these
65 configurations, the next release of GDB will have their sources
68 Mitsubishi D30V d30v-*-*
69 OS/9000 i[34]86-*-os9k
70 IBM AIX PS/2 i[3456]86-*-aix
71 Fujitsu FR30 fr30-*-elf*
72 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
73 Argonaut Risc Chip (ARC) arc-*-*
74 i386 running Mach 3.0 i[3456]86-*-mach3*
75 i386 running Mach i[3456]86-*-mach*
76 i386 running OSF/1 i[3456]86-*osf1mk*
77 HP/Apollo 68k Family m68*-apollo*-sysv*,
79 m68*-hp-bsd*, m68*-hp-hpux*
80 I960 with MON960 i960-*-coff
84 CHILL, a Pascal like language used by telecommunications companies.
86 * REMOVED configurations and files
88 AMD 29k family via UDI a29k-amd-udi, udi29k
89 A29K VxWorks a29k-*-vxworks
90 AMD 29000 embedded, using EBMON a29k-none-none
91 AMD 29000 embedded with COFF a29k-none-coff
92 AMD 29000 embedded with a.out a29k-none-aout
94 testsuite/gdb.hp/gdb.threads-hp/ directory
96 * New command "set max-user-call-depth <nnn>"
98 This command allows the user to limit the call depth of user-defined
99 commands. The default is 1024.
101 * Changes in FreeBSD/i386 native debugging.
103 Support for the "generate-core-file" has been added.
105 * New commands "dump", "append", and "restore".
107 These commands allow data to be copied from target memory
108 to a bfd-format or binary file (dump and append), and back
109 from a file into memory (restore).
111 * Improved "next/step" support on multi-processor Alpha Tru64.
113 The previous single-step mechanism could cause unpredictable problems,
114 including the random appearance of SIGSEGV or SIGTRAP signals. The use
115 of a software single-step mechanism prevents this.
117 *** Changes in GDB 5.2.1:
125 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
126 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
127 Fix, by Joel Brobecker imported from mainline.
129 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
130 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
131 Fix, by Fred Fish, imported from mainline.
133 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
134 Surprisingly enough, it works now.
135 By Michal Ludvig, imported from mainline.
137 i386 hardware watchpoint support:
138 avoid misses on second run for some targets.
139 By Pierre Muller, imported from mainline.
141 *** Changes in GDB 5.2:
143 * New command "set trust-readonly-sections on[off]".
145 This command is a hint that tells gdb that read-only sections
146 really are read-only (ie. that their contents will not change).
147 In this mode, gdb will go to the object file rather than the
148 target to read memory from read-only sections (such as ".text").
149 This can be a significant performance improvement on some
150 (notably embedded) targets.
152 * New command "generate-core-file" (or "gcore").
154 This new gdb command allows the user to drop a core file of the child
155 process state at any time. So far it's been implemented only for
156 GNU/Linux and Solaris, but should be relatively easily ported to other
157 hosts. Argument is core file name (defaults to core.<pid>).
159 * New command line option
161 GDB now accepts --pid or -p followed by a process id.
163 * Change in command line behavior -- corefiles vs. process ids.
165 There is a subtle behavior in the way in which GDB handles
166 command line arguments. The first non-flag argument is always
167 a program to debug, but the second non-flag argument may either
168 be a corefile or a process id. Previously, GDB would attempt to
169 open the second argument as a corefile, and if that failed, would
170 issue a superfluous error message and then attempt to attach it as
171 a process. Now, if the second argument begins with a non-digit,
172 it will be treated as a corefile. If it begins with a digit,
173 GDB will attempt to attach it as a process, and if no such process
174 is found, will then attempt to open it as a corefile.
176 * Changes in ARM configurations.
178 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
179 configuration is fully multi-arch.
181 * New native configurations
183 ARM NetBSD arm*-*-netbsd*
184 x86 OpenBSD i[3456]86-*-openbsd*
185 AMD x86-64 running GNU/Linux x86_64-*-linux-*
186 Sparc64 running FreeBSD sparc64-*-freebsd*
190 Sanyo XStormy16 xstormy16-elf
192 * OBSOLETE configurations and files
194 Configurations that have been declared obsolete in this release have
195 been commented out. Unless there is activity to revive these
196 configurations, the next release of GDB will have their sources
199 AMD 29k family via UDI a29k-amd-udi, udi29k
200 A29K VxWorks a29k-*-vxworks
201 AMD 29000 embedded, using EBMON a29k-none-none
202 AMD 29000 embedded with COFF a29k-none-coff
203 AMD 29000 embedded with a.out a29k-none-aout
205 testsuite/gdb.hp/gdb.threads-hp/ directory
207 * REMOVED configurations and files
209 TI TMS320C80 tic80-*-*
211 PowerPC Solaris powerpcle-*-solaris*
212 PowerPC Windows NT powerpcle-*-cygwin32
213 PowerPC Netware powerpc-*-netware*
214 Harris/CXUX m88k m88*-harris-cxux*
215 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
216 ns32k-utek-sysv* ns32k-utek-*
217 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
218 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
219 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
220 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
221 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
223 * Changes to command line processing
225 The new `--args' feature can be used to specify command-line arguments
226 for the inferior from gdb's command line.
228 * Changes to key bindings
230 There is a new `operate-and-get-next' function bound to `C-o'.
232 *** Changes in GDB 5.1.1
234 Fix compile problem on DJGPP.
236 Fix a problem with floating-point registers on the i386 being
239 Fix to stop GDB crashing on .debug_str debug info.
241 Numerous documentation fixes.
243 Numerous testsuite fixes.
245 *** Changes in GDB 5.1:
247 * New native configurations
249 Alpha FreeBSD alpha*-*-freebsd*
250 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
251 MIPS GNU/Linux mips*-*-linux*
252 MIPS SGI Irix 6.x mips*-sgi-irix6*
254 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
258 Motorola 68HC11 and 68HC12 m68hc11-elf
260 UltraSparc running GNU/Linux sparc64-*-linux*
262 * OBSOLETE configurations and files
264 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
265 Harris/CXUX m88k m88*-harris-cxux*
266 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
267 ns32k-utek-sysv* ns32k-utek-*
268 TI TMS320C80 tic80-*-*
270 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
271 PowerPC Solaris powerpcle-*-solaris*
272 PowerPC Windows NT powerpcle-*-cygwin32
273 PowerPC Netware powerpc-*-netware*
274 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
275 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
276 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
277 Apple Macintosh (MPW) host N/A
279 stuff.c (Program to stuff files into a specially prepared space in kdb)
280 kdb-start.c (Main loop for the standalone kernel debugger)
282 Configurations that have been declared obsolete in this release have
283 been commented out. Unless there is activity to revive these
284 configurations, the next release of GDB will have their sources
287 * REMOVED configurations and files
289 Altos 3068 m68*-altos-*
290 Convex c1-*-*, c2-*-*
292 ARM RISCix arm-*-* (as host)
296 * GDB has been converted to ISO C.
298 GDB's source code has been converted to ISO C. In particular, the
299 sources are fully protoized, and rely on standard headers being
304 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
306 * The MI enabled by default.
308 The new machine oriented interface (MI) introduced in GDB 5.0 has been
309 revised and enabled by default. Packages which use GDB as a debugging
310 engine behind a UI or another front end are encouraged to switch to
311 using the GDB/MI interface, instead of the old annotations interface
312 which is now deprecated.
314 * Support for debugging Pascal programs.
316 GDB now includes support for debugging Pascal programs. The following
317 main features are supported:
319 - Pascal-specific data types such as sets;
321 - automatic recognition of Pascal sources based on file-name
324 - Pascal-style display of data types, variables, and functions;
326 - a Pascal expression parser.
328 However, some important features are not yet supported.
330 - Pascal string operations are not supported at all;
332 - there are some problems with boolean types;
334 - Pascal type hexadecimal constants are not supported
335 because they conflict with the internal variables format;
337 - support for Pascal objects and classes is not full yet;
339 - unlike Pascal, GDB is case-sensitive for symbol names.
341 * Changes in completion.
343 Commands such as `shell', `run' and `set args', which pass arguments
344 to inferior programs, now complete on file names, similar to what
345 users expect at the shell prompt.
347 Commands which accept locations, such as `disassemble', `print',
348 `breakpoint', `until', etc. now complete on filenames as well as
349 program symbols. Thus, if you type "break foob TAB", and the source
350 files linked into the programs include `foobar.c', that file name will
351 be one of the candidates for completion. However, file names are not
352 considered for completion after you typed a colon that delimits a file
353 name from a name of a function in that file, as in "break foo.c:bar".
355 `set demangle-style' completes on available demangling styles.
357 * New platform-independent commands:
359 It is now possible to define a post-hook for a command as well as a
360 hook that runs before the command. For more details, see the
361 documentation of `hookpost' in the GDB manual.
363 * Changes in GNU/Linux native debugging.
365 Support for debugging multi-threaded programs has been completely
366 revised for all platforms except m68k and sparc. You can now debug as
367 many threads as your system allows you to have.
369 Attach/detach is supported for multi-threaded programs.
371 Support for SSE registers was added for x86. This doesn't work for
372 multi-threaded programs though.
374 * Changes in MIPS configurations.
376 Multi-arch support is enabled for all MIPS configurations.
378 GDB can now be built as native debugger on SGI Irix 6.x systems for
379 debugging n32 executables. (Debugging 64-bit executables is not yet
382 * Unified support for hardware watchpoints in all x86 configurations.
384 Most (if not all) native x86 configurations support hardware-assisted
385 breakpoints and watchpoints in a unified manner. This support
386 implements debug register sharing between watchpoints, which allows to
387 put a virtually infinite number of watchpoints on the same address,
388 and also supports watching regions up to 16 bytes with several debug
391 The new maintenance command `maintenance show-debug-regs' toggles
392 debugging print-outs in functions that insert, remove, and test
393 watchpoints and hardware breakpoints.
395 * Changes in the DJGPP native configuration.
397 New command ``info dos sysinfo'' displays assorted information about
398 the CPU, OS, memory, and DPMI server.
400 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
401 display information about segment descriptors stored in GDT, LDT, and
404 New commands ``info dos pde'' and ``info dos pte'' display entries
405 from Page Directory and Page Tables (for now works with CWSDPMI only).
406 New command ``info dos address-pte'' displays the Page Table entry for
407 a given linear address.
409 GDB can now pass command lines longer than 126 characters to the
410 program being debugged (requires an update to the libdbg.a library
411 which is part of the DJGPP development kit).
413 DWARF2 debug info is now supported.
415 It is now possible to `step' and `next' through calls to `longjmp'.
417 * Changes in documentation.
419 All GDB documentation was converted to GFDL, the GNU Free
420 Documentation License.
422 Tracepoints-related commands are now fully documented in the GDB
425 TUI, the Text-mode User Interface, is now documented in the manual.
427 Tracepoints-related commands are now fully documented in the GDB
430 The "GDB Internals" manual now has an index. It also includes
431 documentation of `ui_out' functions, GDB coding standards, x86
432 hardware watchpoints, and memory region attributes.
434 * GDB's version number moved to ``version.in''
436 The Makefile variable VERSION has been replaced by the file
437 ``version.in''. People creating GDB distributions should update the
438 contents of this file.
442 GUD support is now a standard part of the EMACS distribution.
444 *** Changes in GDB 5.0:
446 * Improved support for debugging FP programs on x86 targets
448 Unified and much-improved support for debugging floating-point
449 programs on all x86 targets. In particular, ``info float'' now
450 displays the FP registers in the same format on all x86 targets, with
451 greater level of detail.
453 * Improvements and bugfixes in hardware-assisted watchpoints
455 It is now possible to watch array elements, struct members, and
456 bitfields with hardware-assisted watchpoints. Data-read watchpoints
457 on x86 targets no longer erroneously trigger when the address is
460 * Improvements in the native DJGPP version of GDB
462 The distribution now includes all the scripts and auxiliary files
463 necessary to build the native DJGPP version on MS-DOS/MS-Windows
464 machines ``out of the box''.
466 The DJGPP version can now debug programs that use signals. It is
467 possible to catch signals that happened in the debuggee, deliver
468 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
469 would kill the program being debugged.) Programs that hook hardware
470 interrupts (keyboard, timer, etc.) can also be debugged.
472 It is now possible to debug DJGPP programs that redirect their
473 standard handles or switch them to raw (as opposed to cooked) mode, or
474 even close them. The command ``run < foo > bar'' works as expected,
475 and ``info terminal'' reports useful information about the debuggee's
476 terminal, including raw/cooked mode, redirection, etc.
478 The DJGPP version now uses termios functions for console I/O, which
479 enables debugging graphics programs. Interrupting GDB with Ctrl-C
482 DOS-style file names with drive letters are now fully supported by
485 It is now possible to debug DJGPP programs that switch their working
486 directory. It is also possible to rerun the debuggee any number of
487 times without restarting GDB; thus, you can use the same setup,
488 breakpoints, etc. for many debugging sessions.
490 * New native configurations
492 ARM GNU/Linux arm*-*-linux*
493 PowerPC GNU/Linux powerpc-*-linux*
497 Motorola MCore mcore-*-*
498 x86 VxWorks i[3456]86-*-vxworks*
499 PowerPC VxWorks powerpc-*-vxworks*
500 TI TMS320C80 tic80-*-*
502 * OBSOLETE configurations
504 Altos 3068 m68*-altos-*
505 Convex c1-*-*, c2-*-*
507 ARM RISCix arm-*-* (as host)
510 Configurations that have been declared obsolete will be commented out,
511 but the code will be left in place. If there is no activity to revive
512 these configurations before the next release of GDB, the sources will
513 be permanently REMOVED.
515 * Gould support removed
517 Support for the Gould PowerNode and NP1 has been removed.
519 * New features for SVR4
521 On SVR4 native platforms (such as Solaris), if you attach to a process
522 without first loading a symbol file, GDB will now attempt to locate and
523 load symbols from the running process's executable file.
525 * Many C++ enhancements
527 C++ support has been greatly improved. Overload resolution now works properly
528 in almost all cases. RTTI support is on the way.
530 * Remote targets can connect to a sub-program
532 A popen(3) style serial-device has been added. This device starts a
533 sub-process (such as a stand-alone simulator) and then communicates
534 with that. The sub-program to run is specified using the syntax
535 ``|<program> <args>'' vis:
537 (gdb) set remotedebug 1
538 (gdb) target extended-remote |mn10300-elf-sim program-args
540 * MIPS 64 remote protocol
542 A long standing bug in the mips64 remote protocol where by GDB
543 expected certain 32 bit registers (ex SR) to be transfered as 32
544 instead of 64 bits has been fixed.
546 The command ``set remote-mips64-transfers-32bit-regs on'' has been
547 added to provide backward compatibility with older versions of GDB.
549 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
551 The command ``set remotebinarydownload'' command has been replaced by
552 ``set remote X-packet''. Other commands in ``set remote'' family
553 include ``set remote P-packet''.
555 * Breakpoint commands accept ranges.
557 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
558 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
559 ``tracepoint passcount'' also accepts a range of tracepoints.
561 * ``apropos'' command added.
563 The ``apropos'' command searches through command names and
564 documentation strings, printing out matches, making it much easier to
565 try to find a command that does what you are looking for.
569 A new machine oriented interface (MI) has been added to GDB. This
570 interface is designed for debug environments running GDB as a separate
571 process. This is part of the long term libGDB project. See the
572 "GDB/MI" chapter of the GDB manual for further information. It can be
573 enabled by configuring with:
575 .../configure --enable-gdbmi
577 *** Changes in GDB-4.18:
579 * New native configurations
581 HP-UX 10.20 hppa*-*-hpux10.20
582 HP-UX 11.x hppa*-*-hpux11.0*
583 M68K GNU/Linux m68*-*-linux*
587 Fujitsu FR30 fr30-*-elf*
588 Intel StrongARM strongarm-*-*
589 Mitsubishi D30V d30v-*-*
591 * OBSOLETE configurations
593 Gould PowerNode, NP1 np1-*-*, pn-*-*
595 Configurations that have been declared obsolete will be commented out,
596 but the code will be left in place. If there is no activity to revive
597 these configurations before the next release of GDB, the sources will
598 be permanently REMOVED.
602 As a compatibility experiment, GDB's source files buildsym.h and
603 buildsym.c have been converted to pure standard C, no longer
604 containing any K&R compatibility code. We believe that all systems in
605 use today either come with a standard C compiler, or have a GCC port
606 available. If this is not true, please report the affected
607 configuration to bug-gdb@gnu.org immediately. See the README file for
608 information about getting a standard C compiler if you don't have one
613 GDB now uses readline 2.2.
615 * set extension-language
617 You can now control the mapping between filename extensions and source
618 languages by using the `set extension-language' command. For instance,
619 you can ask GDB to treat .c files as C++ by saying
620 set extension-language .c c++
621 The command `info extensions' lists all of the recognized extensions
622 and their associated languages.
624 * Setting processor type for PowerPC and RS/6000
626 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
627 you can use the `set processor' command to specify what variant of the
628 PowerPC family you are debugging. The command
632 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
633 following PowerPC and RS6000 variants:
635 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
636 rs6000 IBM RS6000 ("POWER") architecture, user-level view
638 403GC IBM PowerPC 403GC
639 505 Motorola PowerPC 505
640 860 Motorola PowerPC 860 or 850
641 601 Motorola PowerPC 601
642 602 Motorola PowerPC 602
643 603 Motorola/IBM PowerPC 603 or 603e
644 604 Motorola PowerPC 604 or 604e
645 750 Motorola/IBM PowerPC 750 or 750
647 At the moment, this command just tells GDB what to name the
648 special-purpose processor registers. Since almost all the affected
649 registers are inaccessible to user-level programs, this command is
650 only useful for remote debugging in its present form.
654 Thanks to a major code donation from Hewlett-Packard, GDB now has much
655 more extensive support for HP-UX. Added features include shared
656 library support, kernel threads and hardware watchpoints for 11.00,
657 support for HP's ANSI C and C++ compilers, and a compatibility mode
658 for xdb and dbx commands.
662 HP's donation includes the new concept of catchpoints, which is a
663 generalization of the old catch command. On HP-UX, it is now possible
664 to catch exec, fork, and vfork, as well as library loading.
666 This means that the existing catch command has changed; its first
667 argument now specifies the type of catch to be set up. See the
668 output of "help catch" for a list of catchpoint types.
670 * Debugging across forks
672 On HP-UX, you can choose which process to debug when a fork() happens
677 HP has donated a curses-based terminal user interface (TUI). To get
678 it, build with --enable-tui. Although this can be enabled for any
679 configuration, at present it only works for native HP debugging.
681 * GDB remote protocol additions
683 A new protocol packet 'X' that writes binary data is now available.
684 Default behavior is to try 'X', then drop back to 'M' if the stub
685 fails to respond. The settable variable `remotebinarydownload'
686 allows explicit control over the use of 'X'.
688 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
689 full 64-bit address. The command
691 set remoteaddresssize 32
693 can be used to revert to the old behaviour. For existing remote stubs
694 the change should not be noticed, as the additional address information
697 In order to assist in debugging stubs, you may use the maintenance
698 command `packet' to send any text string to the stub. For instance,
700 maint packet heythere
702 sends the packet "$heythere#<checksum>". Note that it is very easy to
703 disrupt a debugging session by sending the wrong packet at the wrong
706 The compare-sections command allows you to compare section data on the
707 target to what is in the executable file without uploading or
708 downloading, by comparing CRC checksums.
710 * Tracing can collect general expressions
712 You may now collect general expressions at tracepoints. This requires
713 further additions to the target-side stub; see tracepoint.c and
714 doc/agentexpr.texi for further details.
716 * mask-address variable for Mips
718 For Mips targets, you may control the zeroing of the upper 32 bits of
719 a 64-bit address by entering `set mask-address on'. This is mainly
720 of interest to users of embedded R4xxx and R5xxx processors.
722 * Higher serial baud rates
724 GDB's serial code now allows you to specify baud rates 57600, 115200,
725 230400, and 460800 baud. (Note that your host system may not be able
726 to achieve all of these rates.)
730 The i960 configuration now includes an initial implementation of a
731 builtin simulator, contributed by Jim Wilson.
734 *** Changes in GDB-4.17:
736 * New native configurations
738 Alpha GNU/Linux alpha*-*-linux*
739 Unixware 2.x i[3456]86-unixware2*
740 Irix 6.x mips*-sgi-irix6*
741 PowerPC GNU/Linux powerpc-*-linux*
742 PowerPC Solaris powerpcle-*-solaris*
743 Sparc GNU/Linux sparc-*-linux*
744 Motorola sysV68 R3V7.1 m68k-motorola-sysv
748 Argonaut Risc Chip (ARC) arc-*-*
749 Hitachi H8/300S h8300*-*-*
750 Matsushita MN10200 w/simulator mn10200-*-*
751 Matsushita MN10300 w/simulator mn10300-*-*
752 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
753 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
754 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
755 Mitsubishi D10V w/simulator d10v-*-*
756 Mitsubishi M32R/D w/simulator m32r-*-elf*
757 Tsqware Sparclet sparclet-*-*
758 NEC V850 w/simulator v850-*-*
760 * New debugging protocols
762 ARM with RDI protocol arm*-*-*
763 M68K with dBUG monitor m68*-*-{aout,coff,elf}
764 DDB and LSI variants of PMON protocol mips*-*-*
765 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
766 PowerPC with SDS protocol powerpc{,le}-*-eabi
767 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
771 All configurations can now understand and use the DWARF 2 debugging
772 format. The choice is automatic, if the symbol file contains DWARF 2
777 GDB now includes basic Java language support. This support is
778 only useful with Java compilers that produce native machine code.
780 * solib-absolute-prefix and solib-search-path
782 For SunOS and SVR4 shared libraries, you may now set the prefix for
783 loading absolute shared library symbol files, and the search path for
784 locating non-absolute shared library symbol files.
786 * Live range splitting
788 GDB can now effectively debug code for which GCC has performed live
789 range splitting as part of its optimization. See gdb/doc/LRS for
790 more details on the expected format of the stabs information.
794 GDB's support for the GNU Hurd, including thread debugging, has been
795 updated to work with current versions of the Hurd.
799 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
800 instruction set. ARM GDB automatically detects when Thumb
801 instructions are in use, and adjusts disassembly and backtracing
806 GDB's MIPS target configurations now handle the MIP16 16-bit
811 GDB now includes support for overlays; if an executable has been
812 linked such that multiple sections are based at the same address, GDB
813 will decide which section to use for symbolic info. You can choose to
814 control the decision manually, using overlay commands, or implement
815 additional target-side support and use "overlay load-target" to bring
816 in the overlay mapping. Do "help overlay" for more detail.
820 The command "info symbol <address>" displays information about
821 the symbol at the specified address.
825 The standard remote protocol now includes an extension that allows
826 asynchronous collection and display of trace data. This requires
827 extensive support in the target-side debugging stub. Tracing mode
828 includes a new interaction mode in GDB and new commands: see the
829 file tracepoint.c for more details.
833 Configurations for embedded MIPS now include a simulator contributed
834 by Cygnus Solutions. The simulator supports the instruction sets
835 of most MIPS variants.
839 Sparc configurations may now include the ERC32 simulator contributed
840 by the European Space Agency. The simulator is not built into
841 Sparc targets by default; configure with --enable-sim to include it.
845 For target configurations that may include multiple variants of a
846 basic architecture (such as MIPS and SH), you may now set the
847 architecture explicitly. "set arch" sets, "info arch" lists
848 the possible architectures.
850 *** Changes in GDB-4.16:
852 * New native configurations
854 Windows 95, x86 Windows NT i[345]86-*-cygwin32
855 M68K NetBSD m68k-*-netbsd*
856 PowerPC AIX 4.x powerpc-*-aix*
857 PowerPC MacOS powerpc-*-macos*
858 PowerPC Windows NT powerpcle-*-cygwin32
859 RS/6000 AIX 4.x rs6000-*-aix4*
863 ARM with RDP protocol arm-*-*
864 I960 with MON960 i960-*-coff
865 MIPS VxWorks mips*-*-vxworks*
866 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
867 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
869 Matra Sparclet sparclet-*-*
873 The powerpc-eabi configuration now includes the PSIM simulator,
874 contributed by Andrew Cagney, with assistance from Mike Meissner.
875 PSIM is a very elaborate model of the PowerPC, including not only
876 basic instruction set execution, but also details of execution unit
877 performance and I/O hardware. See sim/ppc/README for more details.
881 GDB now works with Solaris 2.5.
883 * Windows 95/NT native
885 GDB will now work as a native debugger on Windows 95 and Windows NT.
886 To build it from source, you must use the "gnu-win32" environment,
887 which uses a DLL to emulate enough of Unix to run the GNU tools.
888 Further information, binaries, and sources are available at
889 ftp.cygnus.com, under pub/gnu-win32.
891 * dont-repeat command
893 If a user-defined command includes the command `dont-repeat', then the
894 command will not be repeated if the user just types return. This is
895 useful if the command is time-consuming to run, so that accidental
896 extra keystrokes don't run the same command many times.
898 * Send break instead of ^C
900 The standard remote protocol now includes an option to send a break
901 rather than a ^C to the target in order to interrupt it. By default,
902 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
904 * Remote protocol timeout
906 The standard remote protocol includes a new variable `remotetimeout'
907 that allows you to set the number of seconds before GDB gives up trying
908 to read from the target. The default value is 2.
910 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
912 By default GDB will automatically keep track of objects as they are
913 loaded and unloaded by the dynamic linker. By using the command `set
914 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
915 when shared library events occur, thus allowing you to set breakpoints
916 in shared libraries which are explicitly loaded by the inferior.
918 Note this feature does not work on hpux8. On hpux9 you must link
919 /usr/lib/end.o into your program. This feature should work
920 automatically on hpux10.
922 * Irix 5.x hardware watchpoint support
924 Irix 5 configurations now support the use of hardware watchpoints.
926 * Mips protocol "SYN garbage limit"
928 When debugging a Mips target using the `target mips' protocol, you
929 may set the number of characters that GDB will ignore by setting
930 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
931 every character. The default value is 1050.
933 * Recording and replaying remote debug sessions
935 If you set `remotelogfile' to the name of a file, gdb will write to it
936 a recording of a remote debug session. This recording may then be
937 replayed back to gdb using "gdbreplay". See gdbserver/README for
938 details. This is useful when you have a problem with GDB while doing
939 remote debugging; you can make a recording of the session and send it
940 to someone else, who can then recreate the problem.
942 * Speedups for remote debugging
944 GDB includes speedups for downloading and stepping MIPS systems using
945 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
946 and more efficient S-record downloading.
948 * Memory use reductions and statistics collection
950 GDB now uses less memory and reports statistics about memory usage.
951 Try the `maint print statistics' command, for example.
953 *** Changes in GDB-4.15:
957 The symbol reader for AIX GDB now uses partial symbol tables. This
958 can greatly improve startup time, especially for large executables.
960 * Remote targets use caching
962 Remote targets now use a data cache to speed up communication with the
963 remote side. The data cache could lead to incorrect results because
964 it doesn't know about volatile variables, thus making it impossible to
965 debug targets which use memory mapped I/O devices. `set remotecache
966 off' turns the the data cache off.
968 * Remote targets may have threads
970 The standard remote protocol now includes support for multiple threads
971 in the target system, using new protocol commands 'H' and 'T'. See
972 gdb/remote.c for details.
976 If GDB is configured with `--enable-netrom', then it will include
977 support for the NetROM ROM emulator from XLNT Designs. The NetROM
978 acts as though it is a bank of ROM on the target board, but you can
979 write into it over the network. GDB's support consists only of
980 support for fast loading into the emulated ROM; to debug, you must use
981 another protocol, such as standard remote protocol. The usual
982 sequence is something like
984 target nrom <netrom-hostname>
986 target remote <netrom-hostname>:1235
990 GDB now includes support for the Apple Macintosh, as a host only. It
991 may be run as either an MPW tool or as a standalone application, and
992 it can debug through the serial port. All the usual GDB commands are
993 available, but to the target command, you must supply "serial" as the
994 device type instead of "/dev/ttyXX". See mpw-README in the main
995 directory for more information on how to build. The MPW configuration
996 scripts */mpw-config.in support only a few targets, and only the
997 mips-idt-ecoff target has been tested.
1001 GDB configuration now uses autoconf. This is not user-visible,
1002 but does simplify configuration and building.
1006 GDB now supports hpux10.
1008 *** Changes in GDB-4.14:
1010 * New native configurations
1012 x86 FreeBSD i[345]86-*-freebsd
1013 x86 NetBSD i[345]86-*-netbsd
1014 NS32k NetBSD ns32k-*-netbsd
1015 Sparc NetBSD sparc-*-netbsd
1019 A29K VxWorks a29k-*-vxworks
1020 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1021 CPU32 EST-300 emulator m68*-*-est*
1022 PowerPC ELF powerpc-*-elf
1025 * Alpha OSF/1 support for procfs
1027 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1028 possible to attach to running processes. As the mounting of the /proc
1029 filesystem is optional on the Alpha, GDB automatically determines
1030 the availability of /proc during startup. This can lead to problems
1031 if /proc is unmounted after GDB has been started.
1033 * Arguments to user-defined commands
1035 User commands may accept up to 10 arguments separated by whitespace.
1036 Arguments are accessed within the user command via $arg0..$arg9. A
1039 print $arg0 + $arg1 + $arg2
1041 To execute the command use:
1044 Defines the command "adder" which prints the sum of its three arguments.
1045 Note the arguments are text substitutions, so they may reference variables,
1046 use complex expressions, or even perform inferior function calls.
1048 * New `if' and `while' commands
1050 This makes it possible to write more sophisticated user-defined
1051 commands. Both commands take a single argument, which is the
1052 expression to evaluate, and must be followed by the commands to
1053 execute, one per line, if the expression is nonzero, the list being
1054 terminated by the word `end'. The `if' command list may include an
1055 `else' word, which causes the following commands to be executed only
1056 if the expression is zero.
1058 * Fortran source language mode
1060 GDB now includes partial support for Fortran 77. It will recognize
1061 Fortran programs and can evaluate a subset of Fortran expressions, but
1062 variables and functions may not be handled correctly. GDB will work
1063 with G77, but does not yet know much about symbols emitted by other
1066 * Better HPUX support
1068 Most debugging facilities now work on dynamic executables for HPPAs
1069 running hpux9 or later. You can attach to running dynamically linked
1070 processes, but by default the dynamic libraries will be read-only, so
1071 for instance you won't be able to put breakpoints in them. To change
1072 that behavior do the following before running the program:
1078 This will cause the libraries to be mapped private and read-write.
1079 To revert to the normal behavior, do this:
1085 You cannot set breakpoints or examine data in the library until after
1086 the library is loaded if the function/data symbols do not have
1089 GDB can now also read debug symbols produced by the HP C compiler on
1090 HPPAs (sorry, no C++, Fortran or 68k support).
1092 * Target byte order now dynamically selectable
1094 You can choose which byte order to use with a target system, via the
1095 commands "set endian big" and "set endian little", and you can see the
1096 current setting by using "show endian". You can also give the command
1097 "set endian auto", in which case GDB will use the byte order
1098 associated with the executable. Currently, only embedded MIPS
1099 configurations support dynamic selection of target byte order.
1101 * New DOS host serial code
1103 This version uses DPMI interrupts to handle buffered I/O, so you
1104 no longer need to run asynctsr when debugging boards connected to
1107 *** Changes in GDB-4.13:
1109 * New "complete" command
1111 This lists all the possible completions for the rest of the line, if it
1112 were to be given as a command itself. This is intended for use by emacs.
1114 * Trailing space optional in prompt
1116 "set prompt" no longer adds a space for you after the prompt you set. This
1117 allows you to set a prompt which ends in a space or one that does not.
1119 * Breakpoint hit counts
1121 "info break" now displays a count of the number of times the breakpoint
1122 has been hit. This is especially useful in conjunction with "ignore"; you
1123 can ignore a large number of breakpoint hits, look at the breakpoint info
1124 to see how many times the breakpoint was hit, then run again, ignoring one
1125 less than that number, and this will get you quickly to the last hit of
1128 * Ability to stop printing at NULL character
1130 "set print null-stop" will cause GDB to stop printing the characters of
1131 an array when the first NULL is encountered. This is useful when large
1132 arrays actually contain only short strings.
1134 * Shared library breakpoints
1136 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1137 breakpoints in shared libraries before the executable is run.
1139 * Hardware watchpoints
1141 There is a new hardware breakpoint for the watch command for sparclite
1142 targets. See gdb/sparclite/hw_breakpoint.note.
1144 Hardware watchpoints are also now supported under GNU/Linux.
1148 Annotations have been added. These are for use with graphical interfaces,
1149 and are still experimental. Currently only gdba.el uses these.
1151 * Improved Irix 5 support
1153 GDB now works properly with Irix 5.2.
1155 * Improved HPPA support
1157 GDB now works properly with the latest GCC and GAS.
1159 * New native configurations
1161 Sequent PTX4 i[34]86-sequent-ptx4
1162 HPPA running OSF/1 hppa*-*-osf*
1163 Atari TT running SVR4 m68*-*-sysv4*
1164 RS/6000 LynxOS rs6000-*-lynxos*
1168 OS/9000 i[34]86-*-os9k
1169 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1172 * Hitachi SH7000 and E7000-PC ICE support
1174 There is now support for communicating with the Hitachi E7000-PC ICE.
1175 This is available automatically when GDB is configured for the SH.
1179 As usual, a variety of small fixes and improvements, both generic
1180 and configuration-specific. See the ChangeLog for more detail.
1182 *** Changes in GDB-4.12:
1184 * Irix 5 is now supported
1188 GDB-4.12 on the HPPA has a number of changes which make it unable
1189 to debug the output from the currently released versions of GCC and
1190 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1191 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1192 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1195 *** Changes in GDB-4.11:
1197 * User visible changes:
1201 The "set remotedebug" option is now consistent between the mips remote
1202 target, remote targets using the gdb-specific protocol, UDI (AMD's
1203 debug protocol for the 29k) and the 88k bug monitor. It is now an
1204 integer specifying a debug level (normally 0 or 1, but 2 means more
1205 debugging info for the mips target).
1207 * DEC Alpha native support
1209 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1210 debug info, but GDB works fairly well with the DEC compiler and should
1211 work with a future GCC release. See the README file for a few
1212 Alpha-specific notes.
1214 * Preliminary thread implementation
1216 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1218 * LynxOS native and target support for 386
1220 This release has been hosted on LynxOS 2.2, and also can be configured
1221 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1224 * Improvements in C++ mangling/demangling.
1226 This release has much better g++ debugging, specifically in name
1227 mangling/demangling, virtual function calls, print virtual table,
1228 call methods, ...etc.
1230 *** Changes in GDB-4.10:
1232 * User visible changes:
1234 Remote debugging using the GDB-specific (`target remote') protocol now
1235 supports the `load' command. This is only useful if you have some
1236 other way of getting the stub to the target system, and you can put it
1237 somewhere in memory where it won't get clobbered by the download.
1239 Filename completion now works.
1241 When run under emacs mode, the "info line" command now causes the
1242 arrow to point to the line specified. Also, "info line" prints
1243 addresses in symbolic form (as well as hex).
1245 All vxworks based targets now support a user settable option, called
1246 vxworks-timeout. This option represents the number of seconds gdb
1247 should wait for responses to rpc's. You might want to use this if
1248 your vxworks target is, perhaps, a slow software simulator or happens
1249 to be on the far side of a thin network line.
1253 This release contains support for using a DEC alpha as a GDB host for
1254 cross debugging. Native alpha debugging is not supported yet.
1257 *** Changes in GDB-4.9:
1261 This is the first GDB release which is accompanied by a matching testsuite.
1262 The testsuite requires installation of dejagnu, which should be available
1263 via ftp from most sites that carry GNU software.
1267 'Cfront' style demangling has had its name changed to 'ARM' style, to
1268 emphasize that it was written from the specifications in the C++ Annotated
1269 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1270 disclaimers, it still generated too much confusion with users attempting to
1271 use gdb with AT&T cfront.
1275 GDB now uses a standard remote interface to a simulator library.
1276 So far, the library contains simulators for the Zilog Z8001/2, the
1277 Hitachi H8/300, H8/500 and Super-H.
1279 * New targets supported
1281 H8/300 simulator h8300-hitachi-hms or h8300hms
1282 H8/500 simulator h8500-hitachi-hms or h8500hms
1283 SH simulator sh-hitachi-hms or sh
1284 Z8000 simulator z8k-zilog-none or z8ksim
1285 IDT MIPS board over serial line mips-idt-ecoff
1287 Cross-debugging to GO32 targets is supported. It requires a custom
1288 version of the i386-stub.c module which is integrated with the
1289 GO32 memory extender.
1291 * New remote protocols
1293 MIPS remote debugging protocol.
1295 * New source languages supported
1297 This version includes preliminary support for Chill, a Pascal like language
1298 used by telecommunications companies. Chill support is also being integrated
1299 into the GNU compiler, but we don't know when it will be publically available.
1302 *** Changes in GDB-4.8:
1304 * HP Precision Architecture supported
1306 GDB now supports HP PA-RISC machines running HPUX. A preliminary
1307 version of this support was available as a set of patches from the
1308 University of Utah. GDB does not support debugging of programs
1309 compiled with the HP compiler, because HP will not document their file
1310 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
1311 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
1313 Many problems in the preliminary version have been fixed.
1315 * Faster and better demangling
1317 We have improved template demangling and fixed numerous bugs in the GNU style
1318 demangler. It can now handle type modifiers such as `static' or `const'. Wide
1319 character types (wchar_t) are now supported. Demangling of each symbol is now
1320 only done once, and is cached when the symbol table for a file is read in.
1321 This results in a small increase in memory usage for C programs, a moderate
1322 increase in memory usage for C++ programs, and a fantastic speedup in
1325 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
1326 from the specifications in the Annotated Reference Manual, which AT&T's
1327 compiler does not actually implement.
1329 * G++ multiple inheritance compiler problem
1331 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
1332 inheritance lattices was reworked to properly discover ambiguities. We
1333 recently found an example which causes this new algorithm to fail in a
1334 very subtle way, producing bad debug information for those classes.
1335 The file 'gcc.patch' (in this directory) can be applied to gcc to
1336 circumvent the problem. A future GCC release will contain a complete
1339 The previous G++ debug info problem (mentioned below for the gdb-4.7
1340 release) is fixed in gcc version 2.3.2.
1342 * Improved configure script
1344 The `configure' script will now attempt to guess your system type if
1345 you don't supply a host system type. The old scheme of supplying a
1346 host system triplet is preferable over using this. All the magic is
1347 done in the new `config.guess' script. Examine it for details.
1349 We have also brought our configure script much more in line with the FSF's
1350 version. It now supports the --with-xxx options. In particular,
1351 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
1352 The resulting GDB will not be able to read arbitrary object file formats --
1353 only the format ``expected'' to be used on the configured target system.
1354 We hope to make this the default in a future release.
1356 * Documentation improvements
1358 There's new internal documentation on how to modify GDB, and how to
1359 produce clean changes to the code. We implore people to read it
1360 before submitting changes.
1362 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
1363 M4 macros. The new texinfo.tex is provided in this release. Pre-built
1364 `info' files are also provided. To build `info' files from scratch,
1365 you will need the latest `makeinfo' release, which will be available in
1366 a future texinfo-X.Y release.
1368 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
1369 We're not sure exactly which versions have this problem, but it has
1370 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
1371 or better. If that isn't possible, there is a patch in
1372 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
1373 around this problem.
1377 GDB now supports array constants that can be used in expressions typed in by
1378 the user. The syntax is `{element, element, ...}'. Ie: you can now type
1379 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
1382 The new directory `gdb/sparclite' contains a program that demonstrates
1383 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
1385 * New native hosts supported
1387 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
1388 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
1390 * New targets supported
1392 AMD 29k family via UDI a29k-amd-udi or udi29k
1394 * New file formats supported
1396 BFD now supports reading HP/PA-RISC executables (SOM file format?),
1397 HPUX core files, and SCO 3.2v2 core files.
1401 Attaching to processes now works again; thanks for the many bug reports.
1403 We have also stomped on a bunch of core dumps caused by
1404 printf_filtered("%s") problems.
1406 We eliminated a copyright problem on the rpc and ptrace header files
1407 for VxWorks, which was discovered at the last minute during the 4.7
1408 release. You should now be able to build a VxWorks GDB.
1410 You can now interrupt gdb while an attached process is running. This
1411 will cause the attached process to stop, and give control back to GDB.
1413 We fixed problems caused by using too many file descriptors
1414 for reading symbols from object files and libraries. This was
1415 especially a problem for programs that used many (~100) shared
1418 The `step' command now only enters a subroutine if there is line number
1419 information for the subroutine. Otherwise it acts like the `next'
1420 command. Previously, `step' would enter subroutines if there was
1421 any debugging information about the routine. This avoids problems
1422 when using `cc -g1' on MIPS machines.
1424 * Internal improvements
1426 GDB's internal interfaces have been improved to make it easier to support
1427 debugging of multiple languages in the future.
1429 GDB now uses a common structure for symbol information internally.
1430 Minimal symbols (derived from linkage symbols in object files), partial
1431 symbols (from a quick scan of debug information), and full symbols
1432 contain a common subset of information, making it easier to write
1433 shared code that handles any of them.
1435 * New command line options
1437 We now accept --silent as an alias for --quiet.
1441 The memory-mapped-malloc library is now licensed under the GNU Library
1442 General Public License.
1444 *** Changes in GDB-4.7:
1446 * Host/native/target split
1448 GDB has had some major internal surgery to untangle the support for
1449 hosts and remote targets. Now, when you configure GDB for a remote
1450 target, it will no longer load in all of the support for debugging
1451 local programs on the host. When fully completed and tested, this will
1452 ensure that arbitrary host/target combinations are possible.
1454 The primary conceptual shift is to separate the non-portable code in
1455 GDB into three categories. Host specific code is required any time GDB
1456 is compiled on that host, regardless of the target. Target specific
1457 code relates to the peculiarities of the target, but can be compiled on
1458 any host. Native specific code is everything else: it can only be
1459 built when the host and target are the same system. Child process
1460 handling and core file support are two common `native' examples.
1462 GDB's use of /proc for controlling Unix child processes is now cleaner.
1463 It has been split out into a single module under the `target_ops' vector,
1464 plus two native-dependent functions for each system that uses /proc.
1466 * New hosts supported
1468 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
1469 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1470 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
1472 * New targets supported
1474 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
1475 68030 and CPU32 m68030-*-*, m68332-*-*
1477 * New native hosts supported
1479 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1480 (386bsd is not well tested yet)
1481 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
1483 * New file formats supported
1485 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
1486 supports reading of `a.out.adobe' object files, which are an a.out
1487 format extended with minimal information about multiple sections.
1491 `show copying' is the same as the old `info copying'.
1492 `show warranty' is the same as `info warrantee'.
1493 These were renamed for consistency. The old commands continue to work.
1495 `info handle' is a new alias for `info signals'.
1497 You can now define pre-command hooks, which attach arbitrary command
1498 scripts to any command. The commands in the hook will be executed
1499 prior to the user's command. You can also create a hook which will be
1500 executed whenever the program stops. See gdb.texinfo.
1504 We now deal with Cfront style name mangling, and can even extract type
1505 info from mangled symbols. GDB can automatically figure out which
1506 symbol mangling style your C++ compiler uses.
1508 Calling of methods and virtual functions has been improved as well.
1512 The crash that occured when debugging Sun Ansi-C compiled binaries is
1513 fixed. This was due to mishandling of the extra N_SO stabs output
1516 We also finally got Ultrix 4.2 running in house, and fixed core file
1517 support, with help from a dozen people on the net.
1519 John M. Farrell discovered that the reason that single-stepping was so
1520 slow on all of the Mips based platforms (primarily SGI and DEC) was
1521 that we were trying to demangle and lookup a symbol used for internal
1522 purposes on every instruction that was being stepped through. Changing
1523 the name of that symbol so that it couldn't be mistaken for a C++
1524 mangled symbol sped things up a great deal.
1526 Rich Pixley sped up symbol lookups in general by getting much smarter
1527 about when C++ symbol mangling is necessary. This should make symbol
1528 completion (TAB on the command line) much faster. It's not as fast as
1529 we'd like, but it's significantly faster than gdb-4.6.
1533 A new user controllable variable 'call_scratch_address' can
1534 specify the location of a scratch area to be used when GDB
1535 calls a function in the target. This is necessary because the
1536 usual method of putting the scratch area on the stack does not work
1537 in systems that have separate instruction and data spaces.
1539 We integrated changes to support the 29k UDI (Universal Debugger
1540 Interface), but discovered at the last minute that we didn't have all
1541 of the appropriate copyright paperwork. We are working with AMD to
1542 resolve this, and hope to have it available soon.
1546 We have sped up the remote serial line protocol, especially for targets
1547 with lots of registers. It now supports a new `expedited status' ('T')
1548 message which can be used in place of the existing 'S' status message.
1549 This allows the remote stub to send only the registers that GDB
1550 needs to make a quick decision about single-stepping or conditional
1551 breakpoints, eliminating the need to fetch the entire register set for
1552 each instruction being stepped through.
1554 The GDB remote serial protocol now implements a write-through cache for
1555 registers, only re-reading the registers if the target has run.
1557 There is also a new remote serial stub for SPARC processors. You can
1558 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
1559 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
1560 processor with a serial port.
1564 Configure.in files have become much easier to read and modify. A new
1565 `table driven' format makes it more obvious what configurations are
1566 supported, and what files each one uses.
1570 There is a new opcodes library which will eventually contain all of the
1571 disassembly routines and opcode tables. At present, it only contains
1572 Sparc and Z8000 routines. This will allow the assembler, debugger, and
1573 disassembler (binutils/objdump) to share these routines.
1575 The libiberty library is now copylefted under the GNU Library General
1576 Public License. This allows more liberal use, and was done so libg++
1577 can use it. This makes no difference to GDB, since the Library License
1578 grants all the rights from the General Public License.
1582 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
1583 reference to the stabs symbol info used by the debugger. It is (as far
1584 as we know) the only published document on this fascinating topic. We
1585 encourage you to read it, compare it to the stabs information on your
1586 system, and send improvements on the document in general (to
1587 bug-gdb@prep.ai.mit.edu).
1589 And, of course, many bugs have been fixed.
1592 *** Changes in GDB-4.6:
1594 * Better support for C++ function names
1596 GDB now accepts as input the "demangled form" of C++ overloaded function
1597 names and member function names, and can do command completion on such names
1598 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
1599 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
1600 Make use of command completion, it is your friend.
1602 GDB also now accepts a variety of C++ mangled symbol formats. They are
1603 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
1604 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
1605 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
1606 for the list of formats.
1608 * G++ symbol mangling problem
1610 Recent versions of gcc have a bug in how they emit debugging information for
1611 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
1612 directory) can be applied to gcc to fix the problem. Alternatively, if you
1613 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
1614 usual symptom is difficulty with setting breakpoints on methods. GDB complains
1615 about the method being non-existent. (We believe that version 2.2.2 of GCC has
1618 * New 'maintenance' command
1620 All of the commands related to hacking GDB internals have been moved out of
1621 the main command set, and now live behind the 'maintenance' command. This
1622 can also be abbreviated as 'mt'. The following changes were made:
1624 dump-me -> maintenance dump-me
1625 info all-breakpoints -> maintenance info breakpoints
1626 printmsyms -> maintenance print msyms
1627 printobjfiles -> maintenance print objfiles
1628 printpsyms -> maintenance print psymbols
1629 printsyms -> maintenance print symbols
1631 The following commands are new:
1633 maintenance demangle Call internal GDB demangler routine to
1634 demangle a C++ link name and prints the result.
1635 maintenance print type Print a type chain for a given symbol
1637 * Change to .gdbinit file processing
1639 We now read the $HOME/.gdbinit file before processing the argv arguments
1640 (e.g. reading symbol files or core files). This allows global parameters to
1641 be set, which will apply during the symbol reading. The ./.gdbinit is still
1642 read after argv processing.
1644 * New hosts supported
1646 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
1648 GNU/Linux support i386-unknown-linux or linux
1650 We are also including code to support the HP/PA running BSD and HPUX. This
1651 is almost guaranteed not to work, as we didn't have time to test or build it
1652 for this release. We are including it so that the more adventurous (or
1653 masochistic) of you can play with it. We also had major problems with the
1654 fact that the compiler that we got from HP doesn't support the -g option.
1657 * New targets supported
1659 Hitachi H8/300 h8300-hitachi-hms or h8300hms
1661 * More smarts about finding #include files
1663 GDB now remembers the compilation directory for all include files, and for
1664 all files from which C is generated (like yacc and lex sources). This
1665 greatly improves GDB's ability to find yacc/lex sources, and include files,
1666 especially if you are debugging your program from a directory different from
1667 the one that contains your sources.
1669 We also fixed a bug which caused difficulty with listing and setting
1670 breakpoints in include files which contain C code. (In the past, you had to
1671 try twice in order to list an include file that you hadn't looked at before.)
1673 * Interesting infernals change
1675 GDB now deals with arbitrary numbers of sections, where the symbols for each
1676 section must be relocated relative to that section's landing place in the
1677 target's address space. This work was needed to support ELF with embedded
1678 stabs used by Solaris-2.0.
1680 * Bug fixes (of course!)
1682 There have been loads of fixes for the following things:
1683 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
1684 i960, stabs, DOS(GO32), procfs, etc...
1686 See the ChangeLog for details.
1688 *** Changes in GDB-4.5:
1690 * New machines supported (host and target)
1692 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
1694 SGI Irix-4.x mips-sgi-irix4 or iris4
1696 * New malloc package
1698 GDB now uses a new memory manager called mmalloc, based on gmalloc.
1699 Mmalloc is capable of handling mutiple heaps of memory. It is also
1700 capable of saving a heap to a file, and then mapping it back in later.
1701 This can be used to greatly speedup the startup of GDB by using a
1702 pre-parsed symbol table which lives in a mmalloc managed heap. For
1703 more details, please read mmalloc/mmalloc.texi.
1707 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
1708 'help info proc' for details.
1710 * MIPS ecoff symbol table format
1712 The code that reads MIPS symbol table format is now supported on all hosts.
1713 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
1716 * File name changes for MS-DOS
1718 Many files in the config directories have been renamed to make it easier to
1719 support GDB on MS-DOSe systems (which have very restrictive file name
1720 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
1721 environment) is close to working but has some remaining problems. Note
1722 that debugging of DOS programs is not supported, due to limitations
1723 in the ``operating system'', but it can be used to host cross-debugging.
1725 * Cross byte order fixes
1727 Many fixes have been made to support cross debugging of Sparc and MIPS
1728 targets from hosts whose byte order differs.
1730 * New -mapped and -readnow options
1732 If memory-mapped files are available on your system through the 'mmap'
1733 system call, you can use the -mapped option on the `file' or
1734 `symbol-file' commands to cause GDB to write the symbols from your
1735 program into a reusable file. If the program you are debugging is
1736 called `/path/fred', the mapped symbol file will be `./fred.syms'.
1737 Future GDB debugging sessions will notice the presence of this file,
1738 and will quickly map in symbol information from it, rather than reading
1739 the symbol table from the executable program. Using the '-mapped'
1740 option in a GDB `file' or `symbol-file' command has the same effect as
1741 starting GDB with the '-mapped' command-line option.
1743 You can cause GDB to read the entire symbol table immediately by using
1744 the '-readnow' option with any of the commands that load symbol table
1745 information (or on the GDB command line). This makes the command
1746 slower, but makes future operations faster.
1748 The -mapped and -readnow options are typically combined in order to
1749 build a `fred.syms' file that contains complete symbol information.
1750 A simple GDB invocation to do nothing but build a `.syms' file for future
1753 gdb -batch -nx -mapped -readnow programname
1755 The `.syms' file is specific to the host machine on which GDB is run.
1756 It holds an exact image of GDB's internal symbol table. It cannot be
1757 shared across multiple host platforms.
1759 * longjmp() handling
1761 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
1762 siglongjmp() without losing control. This feature has not yet been ported to
1763 all systems. It currently works on many 386 platforms, all MIPS-based
1764 platforms (SGI, DECstation, etc), and Sun3/4.
1768 Preliminary work has been put in to support the new Solaris OS from Sun. At
1769 this time, it can control and debug processes, but it is not capable of
1774 As always, many many bug fixes. The major areas were with g++, and mipsread.
1775 People using the MIPS-based platforms should experience fewer mysterious
1776 crashes and trashed symbol tables.
1778 *** Changes in GDB-4.4:
1780 * New machines supported (host and target)
1782 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1784 BSD Reno on Vax vax-dec-bsd
1785 Ultrix on Vax vax-dec-ultrix
1787 * New machines supported (target)
1789 AMD 29000 embedded, using EBMON a29k-none-none
1793 GDB continues to improve its handling of C++. `References' work better.
1794 The demangler has also been improved, and now deals with symbols mangled as
1795 per the Annotated C++ Reference Guide.
1797 GDB also now handles `stabs' symbol information embedded in MIPS
1798 `ecoff' symbol tables. Since the ecoff format was not easily
1799 extensible to handle new languages such as C++, this appeared to be a
1800 good way to put C++ debugging info into MIPS binaries. This option
1801 will be supported in the GNU C compiler, version 2, when it is
1804 * New features for SVR4
1806 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
1807 shared libraries. Debugging dynamically linked programs should present
1808 only minor differences from debugging statically linked programs.
1810 The `info proc' command will print out information about any process
1811 on an SVR4 system (including the one you are debugging). At the moment,
1812 it prints the address mappings of the process.
1814 If you bring up GDB on another SVR4 system, please send mail to
1815 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
1817 * Better dynamic linking support in SunOS
1819 Reading symbols from shared libraries which contain debugging symbols
1820 now works properly. However, there remain issues such as automatic
1821 skipping of `transfer vector' code during function calls, which
1822 make it harder to debug code in a shared library, than to debug the
1823 same code linked statically.
1827 GDB is now using the latest `getopt' routines from the FSF. This
1828 version accepts the -- prefix for options with long names. GDB will
1829 continue to accept the old forms (-option and +option) as well.
1830 Various single letter abbreviations for options have been explicity
1831 added to the option table so that they won't get overshadowed in the
1832 future by other options that begin with the same letter.
1836 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
1837 Many assorted bugs have been handled. Many more remain to be handled.
1838 See the various ChangeLog files (primarily in gdb and bfd) for details.
1841 *** Changes in GDB-4.3:
1843 * New machines supported (host and target)
1845 Amiga 3000 running Amix m68k-cbm-svr4 or amix
1846 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
1847 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
1849 * Almost SCO Unix support
1851 We had hoped to support:
1852 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1853 (except for core file support), but we discovered very late in the release
1854 that it has problems with process groups that render gdb unusable. Sorry
1855 about that. I encourage people to fix it and post the fixes.
1857 * Preliminary ELF and DWARF support
1859 GDB can read ELF object files on System V Release 4, and can handle
1860 debugging records for C, in DWARF format, in ELF files. This support
1861 is preliminary. If you bring up GDB on another SVR4 system, please
1862 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
1867 GDB now uses the latest `readline' library. One user-visible change
1868 is that two tabs will list possible command completions, which previously
1869 required typing M-? (meta-question mark, or ESC ?).
1873 The `stepi' bug that many of you noticed has been squashed.
1874 Many bugs in C++ have been handled. Many more remain to be handled.
1875 See the various ChangeLog files (primarily in gdb and bfd) for details.
1877 * State of the MIPS world (in case you wondered):
1879 GDB can understand the symbol tables emitted by the compilers
1880 supplied by most vendors of MIPS-based machines, including DEC. These
1881 symbol tables are in a format that essentially nobody else uses.
1883 Some versions of gcc come with an assembler post-processor called
1884 mips-tfile. This program is required if you want to do source-level
1885 debugging of gcc-compiled programs. I believe FSF does not ship
1886 mips-tfile with gcc version 1, but it will eventually come with gcc
1889 Debugging of g++ output remains a problem. g++ version 1.xx does not
1890 really support it at all. (If you're lucky, you should be able to get
1891 line numbers and stack traces to work, but no parameters or local
1892 variables.) With some work it should be possible to improve the
1895 When gcc version 2 is released, you will have somewhat better luck.
1896 However, even then you will get confusing results for inheritance and
1899 We will eventually provide full debugging of g++ output on
1900 DECstations. This will probably involve some kind of stabs-in-ecoff
1901 encapulation, but the details have not been worked out yet.
1904 *** Changes in GDB-4.2:
1906 * Improved configuration
1908 Only one copy of `configure' exists now, and it is not self-modifying.
1909 Porting BFD is simpler.
1913 The `step' and `next' commands now only stop at the first instruction
1914 of a source line. This prevents the multiple stops that used to occur
1915 in switch statements, for-loops, etc. `Step' continues to stop if a
1916 function that has debugging information is called within the line.
1920 Lots of small bugs fixed. More remain.
1922 * New host supported (not target)
1924 Intel 386 PC clone running Mach i386-none-mach
1927 *** Changes in GDB-4.1:
1929 * Multiple source language support
1931 GDB now has internal scaffolding to handle several source languages.
1932 It determines the type of each source file from its filename extension,
1933 and will switch expression parsing and number formatting to match the
1934 language of the function in the currently selected stack frame.
1935 You can also specifically set the language to be used, with
1936 `set language c' or `set language modula-2'.
1940 GDB now has preliminary support for the GNU Modula-2 compiler,
1941 currently under development at the State University of New York at
1942 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
1943 continue through the fall of 1991 and into 1992.
1945 Other Modula-2 compilers are currently not supported, and attempting to
1946 debug programs compiled with them will likely result in an error as the
1947 symbol table is read. Feel free to work on it, though!
1949 There are hooks in GDB for strict type checking and range checking,
1950 in the `Modula-2 philosophy', but they do not currently work.
1954 GDB can now write to executable and core files (e.g. patch
1955 a variable's value). You must turn this switch on, specify
1956 the file ("exec foo" or "core foo"), *then* modify it, e.g.
1957 by assigning a new value to a variable. Modifications take
1960 * Automatic SunOS shared library reading
1962 When you run your program, GDB automatically determines where its
1963 shared libraries (if any) have been loaded, and reads their symbols.
1964 The `share' command is no longer needed. This also works when
1965 examining core files.
1969 You can specify the number of lines that the `list' command shows.
1972 * New machines supported (host and target)
1974 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
1975 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
1976 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
1978 * New hosts supported (not targets)
1980 IBM RT/PC: romp-ibm-aix or rtpc
1982 * New targets supported (not hosts)
1984 AMD 29000 embedded with COFF a29k-none-coff
1985 AMD 29000 embedded with a.out a29k-none-aout
1986 Ultracomputer remote kernel debug a29k-nyu-kern
1988 * New remote interfaces
1994 *** Changes in GDB-4.0:
1998 Wide output is wrapped at good places to make the output more readable.
2000 Gdb now supports cross-debugging from a host machine of one type to a
2001 target machine of another type. Communication with the target system
2002 is over serial lines. The ``target'' command handles connecting to the
2003 remote system; the ``load'' command will download a program into the
2004 remote system. Serial stubs for the m68k and i386 are provided. Gdb
2005 also supports debugging of realtime processes running under VxWorks,
2006 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
2007 stub on the target system.
2009 New CPUs supported include the AMD 29000 and Intel 960.
2011 GDB now reads object files and symbol tables via a ``binary file''
2012 library, which allows a single copy of GDB to debug programs of multiple
2013 object file types such as a.out and coff.
2015 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2016 refcard.dvi and refcard.ps are available to format it).
2019 * Control-Variable user interface simplified
2021 All variables that control the operation of the debugger can be set
2022 by the ``set'' command, and displayed by the ``show'' command.
2024 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2025 ``Show prompt'' produces the response:
2026 Gdb's prompt is new-gdb=>.
2028 What follows are the NEW set commands. The command ``help set'' will
2029 print a complete list of old and new set commands. ``help set FOO''
2030 will give a longer description of the variable FOO. ``show'' will show
2031 all of the variable descriptions and their current settings.
2033 confirm on/off: Enables warning questions for operations that are
2034 hard to recover from, e.g. rerunning the program while
2035 it is already running. Default is ON.
2037 editing on/off: Enables EMACS style command line editing
2038 of input. Previous lines can be recalled with
2039 control-P, the current line can be edited with control-B,
2040 you can search for commands with control-R, etc.
2043 history filename NAME: NAME is where the gdb command history
2044 will be stored. The default is .gdb_history,
2045 or the value of the environment variable
2048 history size N: The size, in commands, of the command history. The
2049 default is 256, or the value of the environment variable
2052 history save on/off: If this value is set to ON, the history file will
2053 be saved after exiting gdb. If set to OFF, the
2054 file will not be saved. The default is OFF.
2056 history expansion on/off: If this value is set to ON, then csh-like
2057 history expansion will be performed on
2058 command line input. The default is OFF.
2060 radix N: Sets the default radix for input and output. It can be set
2061 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2062 in the current radix, so "set radix 10" is always a no-op.
2064 height N: This integer value is the number of lines on a page. Default
2065 is 24, the current `stty rows'' setting, or the ``li#''
2066 setting from the termcap entry matching the environment
2069 width N: This integer value is the number of characters on a line.
2070 Default is 80, the current `stty cols'' setting, or the ``co#''
2071 setting from the termcap entry matching the environment
2074 Note: ``set screensize'' is obsolete. Use ``set height'' and
2075 ``set width'' instead.
2077 print address on/off: Print memory addresses in various command displays,
2078 such as stack traces and structure values. Gdb looks
2079 more ``symbolic'' if you turn this off; it looks more
2080 ``machine level'' with it on. Default is ON.
2082 print array on/off: Prettyprint arrays. New convenient format! Default
2085 print demangle on/off: Print C++ symbols in "source" form if on,
2088 print asm-demangle on/off: Same, for assembler level printouts
2091 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2094 * Support for Epoch Environment.
2096 The epoch environment is a version of Emacs v18 with windowing. One
2097 new command, ``inspect'', is identical to ``print'', except that if you
2098 are running in the epoch environment, the value is printed in its own
2102 * Support for Shared Libraries
2104 GDB can now debug programs and core files that use SunOS shared libraries.
2105 Symbols from a shared library cannot be referenced
2106 before the shared library has been linked with the program (this
2107 happens after you type ``run'' and before the function main() is entered).
2108 At any time after this linking (including when examining core files
2109 from dynamically linked programs), gdb reads the symbols from each
2110 shared library when you type the ``sharedlibrary'' command.
2111 It can be abbreviated ``share''.
2113 sharedlibrary REGEXP: Load shared object library symbols for files
2114 matching a unix regular expression. No argument
2115 indicates to load symbols for all shared libraries.
2117 info sharedlibrary: Status of loaded shared libraries.
2122 A watchpoint stops execution of a program whenever the value of an
2123 expression changes. Checking for this slows down execution
2124 tremendously whenever you are in the scope of the expression, but is
2125 quite useful for catching tough ``bit-spreader'' or pointer misuse
2126 problems. Some machines such as the 386 have hardware for doing this
2127 more quickly, and future versions of gdb will use this hardware.
2129 watch EXP: Set a watchpoint (breakpoint) for an expression.
2131 info watchpoints: Information about your watchpoints.
2133 delete N: Deletes watchpoint number N (same as breakpoints).
2134 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2135 enable N: Re-enables watchpoint number N (same as breakpoints).
2138 * C++ multiple inheritance
2140 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2143 * C++ exception handling
2145 Gdb now supports limited C++ exception handling. Besides the existing
2146 ability to breakpoint on an exception handler, gdb can breakpoint on
2147 the raising of an exception (before the stack is peeled back to the
2150 catch FOO: If there is a FOO exception handler in the dynamic scope,
2151 set a breakpoint to catch exceptions which may be raised there.
2152 Multiple exceptions (``catch foo bar baz'') may be caught.
2154 info catch: Lists all exceptions which may be caught in the
2155 current stack frame.
2158 * Minor command changes
2160 The command ``call func (arg, arg, ...)'' now acts like the print
2161 command, except it does not print or save a value if the function's result
2162 is void. This is similar to dbx usage.
2164 The ``up'' and ``down'' commands now always print the frame they end up
2165 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2166 frames without printing.
2168 * New directory command
2170 'dir' now adds directories to the FRONT of the source search path.
2171 The path starts off empty. Source files that contain debug information
2172 about the directory in which they were compiled can be found even
2173 with an empty path; Sun CC and GCC include this information. If GDB can't
2174 find your source file in the current directory, type "dir .".
2176 * Configuring GDB for compilation
2178 For normal use, type ``./configure host''. See README or gdb.texinfo
2181 GDB now handles cross debugging. If you are remotely debugging between
2182 two different machines, type ``./configure host -target=targ''.
2183 Host is the machine where GDB will run; targ is the machine
2184 where the program that you are debugging will run.
projects / deliverable / binutils-gdb.git / blob