1 What has changed in GDB?
2 (Organized release by release)
4 *** Changes since GDB 5.2:
6 * ``gdbserver'' now supports multi-threaded applications on some targets
8 Support for debugging multi-threaded applications which use
9 the GNU/Linux LinuxThreads package has been added for
10 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
11 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
13 * GDB now supports C/C++ preprocessor macros.
15 GDB now expands preprocessor macro invocations in C/C++ expressions,
16 and provides various commands for showing macro definitions and how
19 The new command `macro expand EXPRESSION' expands any macro
20 invocations in expression, and shows the result.
22 The new command `show macro MACRO-NAME' shows the definition of the
23 macro named MACRO-NAME, and where it was defined.
25 Most compilers don't include information about macros in the debugging
26 information by default. In GCC 3.1, for example, you need to compile
27 your program with the options `-gdwarf-2 -g3'. If the macro
28 information is present in the executable, GDB will read it.
30 * Multi-arched targets.
32 DEC Alpha (partial) alpha*-*-*
33 DEC VAX (partial) vax-*-*
35 National Semiconductor NS32000 (partial) ns32k-*-*
36 Motorola 68000 (partial) m68k-*-*
37 Motorola MCORE mcore-*-*
41 Fujitsu FRV architecture added by Red Hat frv*-*-*
44 * New native configurations
46 Alpha NetBSD alpha*-*-netbsd*
47 SH NetBSD sh*-*-netbsdelf*
48 MIPS NetBSD mips*-*-netbsd*
49 UltraSPARC NetBSD sparc64-*-netbsd*
51 * OBSOLETE configurations and files
53 Configurations that have been declared obsolete in this release have
54 been commented out. Unless there is activity to revive these
55 configurations, the next release of GDB will have their sources
58 Mitsubishi D30V d30v-*-*
59 OS/9000 i[34]86-*-os9k
60 IBM AIX PS/2 i[3456]86-*-aix
61 Fujitsu FR30 fr30-*-elf*
62 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
63 Argonaut Risc Chip (ARC) arc-*-*
64 i386 running Mach 3.0 i[3456]86-*-mach3*
65 i386 running Mach i[3456]86-*-mach*
66 i386 running OSF/1 i[3456]86-*osf1mk*
67 HP/Apollo 68k Family m68*-apollo*-sysv*,
69 m68*-hp-bsd*, m68*-hp-hpux*
73 CHILL, a Pascal like language used by telecommunications companies.
75 * REMOVED configurations and files
77 AMD 29k family via UDI a29k-amd-udi, udi29k
78 A29K VxWorks a29k-*-vxworks
79 AMD 29000 embedded, using EBMON a29k-none-none
80 AMD 29000 embedded with COFF a29k-none-coff
81 AMD 29000 embedded with a.out a29k-none-aout
83 testsuite/gdb.hp/gdb.threads-hp/ directory
85 * New command "set max-user-call-depth <nnn>"
87 This command allows the user to limit the call depth of user-defined
88 commands. The default is 1024.
90 * Changes in FreeBSD/i386 native debugging.
92 Support for the "generate-core-file" has been added.
94 * New commands "dump", "append", and "restore".
96 These commands allow data to be copied from target memory
97 to a bfd-format or binary file (dump and append), and back
98 from a file into memory (restore).
100 *** Changes in GDB 5.2.1:
108 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
109 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
110 Fix, by Joel Brobecker imported from mainline.
112 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
113 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
114 Fix, by Fred Fish, imported from mainline.
116 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
117 Surprisingly enough, it works now.
118 By Michal Ludvig, imported from mainline.
120 i386 hardware watchpoint support:
121 avoid misses on second run for some targets.
122 By Pierre Muller, imported from mainline.
124 *** Changes in GDB 5.2:
126 * New command "set trust-readonly-sections on[off]".
128 This command is a hint that tells gdb that read-only sections
129 really are read-only (ie. that their contents will not change).
130 In this mode, gdb will go to the object file rather than the
131 target to read memory from read-only sections (such as ".text").
132 This can be a significant performance improvement on some
133 (notably embedded) targets.
135 * New command "generate-core-file" (or "gcore").
137 This new gdb command allows the user to drop a core file of the child
138 process state at any time. So far it's been implemented only for
139 GNU/Linux and Solaris, but should be relatively easily ported to other
140 hosts. Argument is core file name (defaults to core.<pid>).
142 * New command line option
144 GDB now accepts --pid or -p followed by a process id.
146 * Change in command line behavior -- corefiles vs. process ids.
148 There is a subtle behavior in the way in which GDB handles
149 command line arguments. The first non-flag argument is always
150 a program to debug, but the second non-flag argument may either
151 be a corefile or a process id. Previously, GDB would attempt to
152 open the second argument as a corefile, and if that failed, would
153 issue a superfluous error message and then attempt to attach it as
154 a process. Now, if the second argument begins with a non-digit,
155 it will be treated as a corefile. If it begins with a digit,
156 GDB will attempt to attach it as a process, and if no such process
157 is found, will then attempt to open it as a corefile.
159 * Changes in ARM configurations.
161 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
162 configuration is fully multi-arch.
164 * New native configurations
166 ARM NetBSD arm*-*-netbsd*
167 x86 OpenBSD i[3456]86-*-openbsd*
168 AMD x86-64 running GNU/Linux x86_64-*-linux-*
169 Sparc64 running FreeBSD sparc64-*-freebsd*
173 Sanyo XStormy16 xstormy16-elf
175 * OBSOLETE configurations and files
177 Configurations that have been declared obsolete in this release have
178 been commented out. Unless there is activity to revive these
179 configurations, the next release of GDB will have their sources
182 AMD 29k family via UDI a29k-amd-udi, udi29k
183 A29K VxWorks a29k-*-vxworks
184 AMD 29000 embedded, using EBMON a29k-none-none
185 AMD 29000 embedded with COFF a29k-none-coff
186 AMD 29000 embedded with a.out a29k-none-aout
188 testsuite/gdb.hp/gdb.threads-hp/ directory
190 * REMOVED configurations and files
192 TI TMS320C80 tic80-*-*
194 PowerPC Solaris powerpcle-*-solaris*
195 PowerPC Windows NT powerpcle-*-cygwin32
196 PowerPC Netware powerpc-*-netware*
197 Harris/CXUX m88k m88*-harris-cxux*
198 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
199 ns32k-utek-sysv* ns32k-utek-*
200 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
201 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
202 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
203 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
204 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
206 * Changes to command line processing
208 The new `--args' feature can be used to specify command-line arguments
209 for the inferior from gdb's command line.
211 * Changes to key bindings
213 There is a new `operate-and-get-next' function bound to `C-o'.
215 *** Changes in GDB 5.1.1
217 Fix compile problem on DJGPP.
219 Fix a problem with floating-point registers on the i386 being
222 Fix to stop GDB crashing on .debug_str debug info.
224 Numerous documentation fixes.
226 Numerous testsuite fixes.
228 *** Changes in GDB 5.1:
230 * New native configurations
232 Alpha FreeBSD alpha*-*-freebsd*
233 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
234 MIPS GNU/Linux mips*-*-linux*
235 MIPS SGI Irix 6.x mips*-sgi-irix6*
237 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
241 Motorola 68HC11 and 68HC12 m68hc11-elf
243 UltraSparc running GNU/Linux sparc64-*-linux*
245 * OBSOLETE configurations and files
247 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
248 Harris/CXUX m88k m88*-harris-cxux*
249 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
250 ns32k-utek-sysv* ns32k-utek-*
251 TI TMS320C80 tic80-*-*
253 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
254 PowerPC Solaris powerpcle-*-solaris*
255 PowerPC Windows NT powerpcle-*-cygwin32
256 PowerPC Netware powerpc-*-netware*
257 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
258 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
259 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
260 Apple Macintosh (MPW) host N/A
262 stuff.c (Program to stuff files into a specially prepared space in kdb)
263 kdb-start.c (Main loop for the standalone kernel debugger)
265 Configurations that have been declared obsolete in this release have
266 been commented out. Unless there is activity to revive these
267 configurations, the next release of GDB will have their sources
270 * REMOVED configurations and files
272 Altos 3068 m68*-altos-*
273 Convex c1-*-*, c2-*-*
275 ARM RISCix arm-*-* (as host)
279 * GDB has been converted to ISO C.
281 GDB's source code has been converted to ISO C. In particular, the
282 sources are fully protoized, and rely on standard headers being
287 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
289 * The MI enabled by default.
291 The new machine oriented interface (MI) introduced in GDB 5.0 has been
292 revised and enabled by default. Packages which use GDB as a debugging
293 engine behind a UI or another front end are encouraged to switch to
294 using the GDB/MI interface, instead of the old annotations interface
295 which is now deprecated.
297 * Support for debugging Pascal programs.
299 GDB now includes support for debugging Pascal programs. The following
300 main features are supported:
302 - Pascal-specific data types such as sets;
304 - automatic recognition of Pascal sources based on file-name
307 - Pascal-style display of data types, variables, and functions;
309 - a Pascal expression parser.
311 However, some important features are not yet supported.
313 - Pascal string operations are not supported at all;
315 - there are some problems with boolean types;
317 - Pascal type hexadecimal constants are not supported
318 because they conflict with the internal variables format;
320 - support for Pascal objects and classes is not full yet;
322 - unlike Pascal, GDB is case-sensitive for symbol names.
324 * Changes in completion.
326 Commands such as `shell', `run' and `set args', which pass arguments
327 to inferior programs, now complete on file names, similar to what
328 users expect at the shell prompt.
330 Commands which accept locations, such as `disassemble', `print',
331 `breakpoint', `until', etc. now complete on filenames as well as
332 program symbols. Thus, if you type "break foob TAB", and the source
333 files linked into the programs include `foobar.c', that file name will
334 be one of the candidates for completion. However, file names are not
335 considered for completion after you typed a colon that delimits a file
336 name from a name of a function in that file, as in "break foo.c:bar".
338 `set demangle-style' completes on available demangling styles.
340 * New platform-independent commands:
342 It is now possible to define a post-hook for a command as well as a
343 hook that runs before the command. For more details, see the
344 documentation of `hookpost' in the GDB manual.
346 * Changes in GNU/Linux native debugging.
348 Support for debugging multi-threaded programs has been completely
349 revised for all platforms except m68k and sparc. You can now debug as
350 many threads as your system allows you to have.
352 Attach/detach is supported for multi-threaded programs.
354 Support for SSE registers was added for x86. This doesn't work for
355 multi-threaded programs though.
357 * Changes in MIPS configurations.
359 Multi-arch support is enabled for all MIPS configurations.
361 GDB can now be built as native debugger on SGI Irix 6.x systems for
362 debugging n32 executables. (Debugging 64-bit executables is not yet
365 * Unified support for hardware watchpoints in all x86 configurations.
367 Most (if not all) native x86 configurations support hardware-assisted
368 breakpoints and watchpoints in a unified manner. This support
369 implements debug register sharing between watchpoints, which allows to
370 put a virtually infinite number of watchpoints on the same address,
371 and also supports watching regions up to 16 bytes with several debug
374 The new maintenance command `maintenance show-debug-regs' toggles
375 debugging print-outs in functions that insert, remove, and test
376 watchpoints and hardware breakpoints.
378 * Changes in the DJGPP native configuration.
380 New command ``info dos sysinfo'' displays assorted information about
381 the CPU, OS, memory, and DPMI server.
383 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
384 display information about segment descriptors stored in GDT, LDT, and
387 New commands ``info dos pde'' and ``info dos pte'' display entries
388 from Page Directory and Page Tables (for now works with CWSDPMI only).
389 New command ``info dos address-pte'' displays the Page Table entry for
390 a given linear address.
392 GDB can now pass command lines longer than 126 characters to the
393 program being debugged (requires an update to the libdbg.a library
394 which is part of the DJGPP development kit).
396 DWARF2 debug info is now supported.
398 It is now possible to `step' and `next' through calls to `longjmp'.
400 * Changes in documentation.
402 All GDB documentation was converted to GFDL, the GNU Free
403 Documentation License.
405 Tracepoints-related commands are now fully documented in the GDB
408 TUI, the Text-mode User Interface, is now documented in the manual.
410 Tracepoints-related commands are now fully documented in the GDB
413 The "GDB Internals" manual now has an index. It also includes
414 documentation of `ui_out' functions, GDB coding standards, x86
415 hardware watchpoints, and memory region attributes.
417 * GDB's version number moved to ``version.in''
419 The Makefile variable VERSION has been replaced by the file
420 ``version.in''. People creating GDB distributions should update the
421 contents of this file.
425 GUD support is now a standard part of the EMACS distribution.
427 *** Changes in GDB 5.0:
429 * Improved support for debugging FP programs on x86 targets
431 Unified and much-improved support for debugging floating-point
432 programs on all x86 targets. In particular, ``info float'' now
433 displays the FP registers in the same format on all x86 targets, with
434 greater level of detail.
436 * Improvements and bugfixes in hardware-assisted watchpoints
438 It is now possible to watch array elements, struct members, and
439 bitfields with hardware-assisted watchpoints. Data-read watchpoints
440 on x86 targets no longer erroneously trigger when the address is
443 * Improvements in the native DJGPP version of GDB
445 The distribution now includes all the scripts and auxiliary files
446 necessary to build the native DJGPP version on MS-DOS/MS-Windows
447 machines ``out of the box''.
449 The DJGPP version can now debug programs that use signals. It is
450 possible to catch signals that happened in the debuggee, deliver
451 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
452 would kill the program being debugged.) Programs that hook hardware
453 interrupts (keyboard, timer, etc.) can also be debugged.
455 It is now possible to debug DJGPP programs that redirect their
456 standard handles or switch them to raw (as opposed to cooked) mode, or
457 even close them. The command ``run < foo > bar'' works as expected,
458 and ``info terminal'' reports useful information about the debuggee's
459 terminal, including raw/cooked mode, redirection, etc.
461 The DJGPP version now uses termios functions for console I/O, which
462 enables debugging graphics programs. Interrupting GDB with Ctrl-C
465 DOS-style file names with drive letters are now fully supported by
468 It is now possible to debug DJGPP programs that switch their working
469 directory. It is also possible to rerun the debuggee any number of
470 times without restarting GDB; thus, you can use the same setup,
471 breakpoints, etc. for many debugging sessions.
473 * New native configurations
475 ARM GNU/Linux arm*-*-linux*
476 PowerPC GNU/Linux powerpc-*-linux*
480 Motorola MCore mcore-*-*
481 x86 VxWorks i[3456]86-*-vxworks*
482 PowerPC VxWorks powerpc-*-vxworks*
483 TI TMS320C80 tic80-*-*
485 * OBSOLETE configurations
487 Altos 3068 m68*-altos-*
488 Convex c1-*-*, c2-*-*
490 ARM RISCix arm-*-* (as host)
493 Configurations that have been declared obsolete will be commented out,
494 but the code will be left in place. If there is no activity to revive
495 these configurations before the next release of GDB, the sources will
496 be permanently REMOVED.
498 * Gould support removed
500 Support for the Gould PowerNode and NP1 has been removed.
502 * New features for SVR4
504 On SVR4 native platforms (such as Solaris), if you attach to a process
505 without first loading a symbol file, GDB will now attempt to locate and
506 load symbols from the running process's executable file.
508 * Many C++ enhancements
510 C++ support has been greatly improved. Overload resolution now works properly
511 in almost all cases. RTTI support is on the way.
513 * Remote targets can connect to a sub-program
515 A popen(3) style serial-device has been added. This device starts a
516 sub-process (such as a stand-alone simulator) and then communicates
517 with that. The sub-program to run is specified using the syntax
518 ``|<program> <args>'' vis:
520 (gdb) set remotedebug 1
521 (gdb) target extended-remote |mn10300-elf-sim program-args
523 * MIPS 64 remote protocol
525 A long standing bug in the mips64 remote protocol where by GDB
526 expected certain 32 bit registers (ex SR) to be transfered as 32
527 instead of 64 bits has been fixed.
529 The command ``set remote-mips64-transfers-32bit-regs on'' has been
530 added to provide backward compatibility with older versions of GDB.
532 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
534 The command ``set remotebinarydownload'' command has been replaced by
535 ``set remote X-packet''. Other commands in ``set remote'' family
536 include ``set remote P-packet''.
538 * Breakpoint commands accept ranges.
540 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
541 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
542 ``tracepoint passcount'' also accepts a range of tracepoints.
544 * ``apropos'' command added.
546 The ``apropos'' command searches through command names and
547 documentation strings, printing out matches, making it much easier to
548 try to find a command that does what you are looking for.
552 A new machine oriented interface (MI) has been added to GDB. This
553 interface is designed for debug environments running GDB as a separate
554 process. This is part of the long term libGDB project. See the
555 "GDB/MI" chapter of the GDB manual for further information. It can be
556 enabled by configuring with:
558 .../configure --enable-gdbmi
560 *** Changes in GDB-4.18:
562 * New native configurations
564 HP-UX 10.20 hppa*-*-hpux10.20
565 HP-UX 11.x hppa*-*-hpux11.0*
566 M68K GNU/Linux m68*-*-linux*
570 Fujitsu FR30 fr30-*-elf*
571 Intel StrongARM strongarm-*-*
572 Mitsubishi D30V d30v-*-*
574 * OBSOLETE configurations
576 Gould PowerNode, NP1 np1-*-*, pn-*-*
578 Configurations that have been declared obsolete will be commented out,
579 but the code will be left in place. If there is no activity to revive
580 these configurations before the next release of GDB, the sources will
581 be permanently REMOVED.
585 As a compatibility experiment, GDB's source files buildsym.h and
586 buildsym.c have been converted to pure standard C, no longer
587 containing any K&R compatibility code. We believe that all systems in
588 use today either come with a standard C compiler, or have a GCC port
589 available. If this is not true, please report the affected
590 configuration to bug-gdb@gnu.org immediately. See the README file for
591 information about getting a standard C compiler if you don't have one
596 GDB now uses readline 2.2.
598 * set extension-language
600 You can now control the mapping between filename extensions and source
601 languages by using the `set extension-language' command. For instance,
602 you can ask GDB to treat .c files as C++ by saying
603 set extension-language .c c++
604 The command `info extensions' lists all of the recognized extensions
605 and their associated languages.
607 * Setting processor type for PowerPC and RS/6000
609 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
610 you can use the `set processor' command to specify what variant of the
611 PowerPC family you are debugging. The command
615 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
616 following PowerPC and RS6000 variants:
618 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
619 rs6000 IBM RS6000 ("POWER") architecture, user-level view
621 403GC IBM PowerPC 403GC
622 505 Motorola PowerPC 505
623 860 Motorola PowerPC 860 or 850
624 601 Motorola PowerPC 601
625 602 Motorola PowerPC 602
626 603 Motorola/IBM PowerPC 603 or 603e
627 604 Motorola PowerPC 604 or 604e
628 750 Motorola/IBM PowerPC 750 or 750
630 At the moment, this command just tells GDB what to name the
631 special-purpose processor registers. Since almost all the affected
632 registers are inaccessible to user-level programs, this command is
633 only useful for remote debugging in its present form.
637 Thanks to a major code donation from Hewlett-Packard, GDB now has much
638 more extensive support for HP-UX. Added features include shared
639 library support, kernel threads and hardware watchpoints for 11.00,
640 support for HP's ANSI C and C++ compilers, and a compatibility mode
641 for xdb and dbx commands.
645 HP's donation includes the new concept of catchpoints, which is a
646 generalization of the old catch command. On HP-UX, it is now possible
647 to catch exec, fork, and vfork, as well as library loading.
649 This means that the existing catch command has changed; its first
650 argument now specifies the type of catch to be set up. See the
651 output of "help catch" for a list of catchpoint types.
653 * Debugging across forks
655 On HP-UX, you can choose which process to debug when a fork() happens
660 HP has donated a curses-based terminal user interface (TUI). To get
661 it, build with --enable-tui. Although this can be enabled for any
662 configuration, at present it only works for native HP debugging.
664 * GDB remote protocol additions
666 A new protocol packet 'X' that writes binary data is now available.
667 Default behavior is to try 'X', then drop back to 'M' if the stub
668 fails to respond. The settable variable `remotebinarydownload'
669 allows explicit control over the use of 'X'.
671 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
672 full 64-bit address. The command
674 set remoteaddresssize 32
676 can be used to revert to the old behaviour. For existing remote stubs
677 the change should not be noticed, as the additional address information
680 In order to assist in debugging stubs, you may use the maintenance
681 command `packet' to send any text string to the stub. For instance,
683 maint packet heythere
685 sends the packet "$heythere#<checksum>". Note that it is very easy to
686 disrupt a debugging session by sending the wrong packet at the wrong
689 The compare-sections command allows you to compare section data on the
690 target to what is in the executable file without uploading or
691 downloading, by comparing CRC checksums.
693 * Tracing can collect general expressions
695 You may now collect general expressions at tracepoints. This requires
696 further additions to the target-side stub; see tracepoint.c and
697 doc/agentexpr.texi for further details.
699 * mask-address variable for Mips
701 For Mips targets, you may control the zeroing of the upper 32 bits of
702 a 64-bit address by entering `set mask-address on'. This is mainly
703 of interest to users of embedded R4xxx and R5xxx processors.
705 * Higher serial baud rates
707 GDB's serial code now allows you to specify baud rates 57600, 115200,
708 230400, and 460800 baud. (Note that your host system may not be able
709 to achieve all of these rates.)
713 The i960 configuration now includes an initial implementation of a
714 builtin simulator, contributed by Jim Wilson.
717 *** Changes in GDB-4.17:
719 * New native configurations
721 Alpha GNU/Linux alpha*-*-linux*
722 Unixware 2.x i[3456]86-unixware2*
723 Irix 6.x mips*-sgi-irix6*
724 PowerPC GNU/Linux powerpc-*-linux*
725 PowerPC Solaris powerpcle-*-solaris*
726 Sparc GNU/Linux sparc-*-linux*
727 Motorola sysV68 R3V7.1 m68k-motorola-sysv
731 Argonaut Risc Chip (ARC) arc-*-*
732 Hitachi H8/300S h8300*-*-*
733 Matsushita MN10200 w/simulator mn10200-*-*
734 Matsushita MN10300 w/simulator mn10300-*-*
735 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
736 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
737 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
738 Mitsubishi D10V w/simulator d10v-*-*
739 Mitsubishi M32R/D w/simulator m32r-*-elf*
740 Tsqware Sparclet sparclet-*-*
741 NEC V850 w/simulator v850-*-*
743 * New debugging protocols
745 ARM with RDI protocol arm*-*-*
746 M68K with dBUG monitor m68*-*-{aout,coff,elf}
747 DDB and LSI variants of PMON protocol mips*-*-*
748 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
749 PowerPC with SDS protocol powerpc{,le}-*-eabi
750 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
754 All configurations can now understand and use the DWARF 2 debugging
755 format. The choice is automatic, if the symbol file contains DWARF 2
760 GDB now includes basic Java language support. This support is
761 only useful with Java compilers that produce native machine code.
763 * solib-absolute-prefix and solib-search-path
765 For SunOS and SVR4 shared libraries, you may now set the prefix for
766 loading absolute shared library symbol files, and the search path for
767 locating non-absolute shared library symbol files.
769 * Live range splitting
771 GDB can now effectively debug code for which GCC has performed live
772 range splitting as part of its optimization. See gdb/doc/LRS for
773 more details on the expected format of the stabs information.
777 GDB's support for the GNU Hurd, including thread debugging, has been
778 updated to work with current versions of the Hurd.
782 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
783 instruction set. ARM GDB automatically detects when Thumb
784 instructions are in use, and adjusts disassembly and backtracing
789 GDB's MIPS target configurations now handle the MIP16 16-bit
794 GDB now includes support for overlays; if an executable has been
795 linked such that multiple sections are based at the same address, GDB
796 will decide which section to use for symbolic info. You can choose to
797 control the decision manually, using overlay commands, or implement
798 additional target-side support and use "overlay load-target" to bring
799 in the overlay mapping. Do "help overlay" for more detail.
803 The command "info symbol <address>" displays information about
804 the symbol at the specified address.
808 The standard remote protocol now includes an extension that allows
809 asynchronous collection and display of trace data. This requires
810 extensive support in the target-side debugging stub. Tracing mode
811 includes a new interaction mode in GDB and new commands: see the
812 file tracepoint.c for more details.
816 Configurations for embedded MIPS now include a simulator contributed
817 by Cygnus Solutions. The simulator supports the instruction sets
818 of most MIPS variants.
822 Sparc configurations may now include the ERC32 simulator contributed
823 by the European Space Agency. The simulator is not built into
824 Sparc targets by default; configure with --enable-sim to include it.
828 For target configurations that may include multiple variants of a
829 basic architecture (such as MIPS and SH), you may now set the
830 architecture explicitly. "set arch" sets, "info arch" lists
831 the possible architectures.
833 *** Changes in GDB-4.16:
835 * New native configurations
837 Windows 95, x86 Windows NT i[345]86-*-cygwin32
838 M68K NetBSD m68k-*-netbsd*
839 PowerPC AIX 4.x powerpc-*-aix*
840 PowerPC MacOS powerpc-*-macos*
841 PowerPC Windows NT powerpcle-*-cygwin32
842 RS/6000 AIX 4.x rs6000-*-aix4*
846 ARM with RDP protocol arm-*-*
847 I960 with MON960 i960-*-coff
848 MIPS VxWorks mips*-*-vxworks*
849 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
850 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
852 Matra Sparclet sparclet-*-*
856 The powerpc-eabi configuration now includes the PSIM simulator,
857 contributed by Andrew Cagney, with assistance from Mike Meissner.
858 PSIM is a very elaborate model of the PowerPC, including not only
859 basic instruction set execution, but also details of execution unit
860 performance and I/O hardware. See sim/ppc/README for more details.
864 GDB now works with Solaris 2.5.
866 * Windows 95/NT native
868 GDB will now work as a native debugger on Windows 95 and Windows NT.
869 To build it from source, you must use the "gnu-win32" environment,
870 which uses a DLL to emulate enough of Unix to run the GNU tools.
871 Further information, binaries, and sources are available at
872 ftp.cygnus.com, under pub/gnu-win32.
874 * dont-repeat command
876 If a user-defined command includes the command `dont-repeat', then the
877 command will not be repeated if the user just types return. This is
878 useful if the command is time-consuming to run, so that accidental
879 extra keystrokes don't run the same command many times.
881 * Send break instead of ^C
883 The standard remote protocol now includes an option to send a break
884 rather than a ^C to the target in order to interrupt it. By default,
885 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
887 * Remote protocol timeout
889 The standard remote protocol includes a new variable `remotetimeout'
890 that allows you to set the number of seconds before GDB gives up trying
891 to read from the target. The default value is 2.
893 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
895 By default GDB will automatically keep track of objects as they are
896 loaded and unloaded by the dynamic linker. By using the command `set
897 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
898 when shared library events occur, thus allowing you to set breakpoints
899 in shared libraries which are explicitly loaded by the inferior.
901 Note this feature does not work on hpux8. On hpux9 you must link
902 /usr/lib/end.o into your program. This feature should work
903 automatically on hpux10.
905 * Irix 5.x hardware watchpoint support
907 Irix 5 configurations now support the use of hardware watchpoints.
909 * Mips protocol "SYN garbage limit"
911 When debugging a Mips target using the `target mips' protocol, you
912 may set the number of characters that GDB will ignore by setting
913 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
914 every character. The default value is 1050.
916 * Recording and replaying remote debug sessions
918 If you set `remotelogfile' to the name of a file, gdb will write to it
919 a recording of a remote debug session. This recording may then be
920 replayed back to gdb using "gdbreplay". See gdbserver/README for
921 details. This is useful when you have a problem with GDB while doing
922 remote debugging; you can make a recording of the session and send it
923 to someone else, who can then recreate the problem.
925 * Speedups for remote debugging
927 GDB includes speedups for downloading and stepping MIPS systems using
928 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
929 and more efficient S-record downloading.
931 * Memory use reductions and statistics collection
933 GDB now uses less memory and reports statistics about memory usage.
934 Try the `maint print statistics' command, for example.
936 *** Changes in GDB-4.15:
940 The symbol reader for AIX GDB now uses partial symbol tables. This
941 can greatly improve startup time, especially for large executables.
943 * Remote targets use caching
945 Remote targets now use a data cache to speed up communication with the
946 remote side. The data cache could lead to incorrect results because
947 it doesn't know about volatile variables, thus making it impossible to
948 debug targets which use memory mapped I/O devices. `set remotecache
949 off' turns the the data cache off.
951 * Remote targets may have threads
953 The standard remote protocol now includes support for multiple threads
954 in the target system, using new protocol commands 'H' and 'T'. See
955 gdb/remote.c for details.
959 If GDB is configured with `--enable-netrom', then it will include
960 support for the NetROM ROM emulator from XLNT Designs. The NetROM
961 acts as though it is a bank of ROM on the target board, but you can
962 write into it over the network. GDB's support consists only of
963 support for fast loading into the emulated ROM; to debug, you must use
964 another protocol, such as standard remote protocol. The usual
965 sequence is something like
967 target nrom <netrom-hostname>
969 target remote <netrom-hostname>:1235
973 GDB now includes support for the Apple Macintosh, as a host only. It
974 may be run as either an MPW tool or as a standalone application, and
975 it can debug through the serial port. All the usual GDB commands are
976 available, but to the target command, you must supply "serial" as the
977 device type instead of "/dev/ttyXX". See mpw-README in the main
978 directory for more information on how to build. The MPW configuration
979 scripts */mpw-config.in support only a few targets, and only the
980 mips-idt-ecoff target has been tested.
984 GDB configuration now uses autoconf. This is not user-visible,
985 but does simplify configuration and building.
989 GDB now supports hpux10.
991 *** Changes in GDB-4.14:
993 * New native configurations
995 x86 FreeBSD i[345]86-*-freebsd
996 x86 NetBSD i[345]86-*-netbsd
997 NS32k NetBSD ns32k-*-netbsd
998 Sparc NetBSD sparc-*-netbsd
1002 A29K VxWorks a29k-*-vxworks
1003 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1004 CPU32 EST-300 emulator m68*-*-est*
1005 PowerPC ELF powerpc-*-elf
1008 * Alpha OSF/1 support for procfs
1010 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1011 possible to attach to running processes. As the mounting of the /proc
1012 filesystem is optional on the Alpha, GDB automatically determines
1013 the availability of /proc during startup. This can lead to problems
1014 if /proc is unmounted after GDB has been started.
1016 * Arguments to user-defined commands
1018 User commands may accept up to 10 arguments separated by whitespace.
1019 Arguments are accessed within the user command via $arg0..$arg9. A
1022 print $arg0 + $arg1 + $arg2
1024 To execute the command use:
1027 Defines the command "adder" which prints the sum of its three arguments.
1028 Note the arguments are text substitutions, so they may reference variables,
1029 use complex expressions, or even perform inferior function calls.
1031 * New `if' and `while' commands
1033 This makes it possible to write more sophisticated user-defined
1034 commands. Both commands take a single argument, which is the
1035 expression to evaluate, and must be followed by the commands to
1036 execute, one per line, if the expression is nonzero, the list being
1037 terminated by the word `end'. The `if' command list may include an
1038 `else' word, which causes the following commands to be executed only
1039 if the expression is zero.
1041 * Fortran source language mode
1043 GDB now includes partial support for Fortran 77. It will recognize
1044 Fortran programs and can evaluate a subset of Fortran expressions, but
1045 variables and functions may not be handled correctly. GDB will work
1046 with G77, but does not yet know much about symbols emitted by other
1049 * Better HPUX support
1051 Most debugging facilities now work on dynamic executables for HPPAs
1052 running hpux9 or later. You can attach to running dynamically linked
1053 processes, but by default the dynamic libraries will be read-only, so
1054 for instance you won't be able to put breakpoints in them. To change
1055 that behavior do the following before running the program:
1061 This will cause the libraries to be mapped private and read-write.
1062 To revert to the normal behavior, do this:
1068 You cannot set breakpoints or examine data in the library until after
1069 the library is loaded if the function/data symbols do not have
1072 GDB can now also read debug symbols produced by the HP C compiler on
1073 HPPAs (sorry, no C++, Fortran or 68k support).
1075 * Target byte order now dynamically selectable
1077 You can choose which byte order to use with a target system, via the
1078 commands "set endian big" and "set endian little", and you can see the
1079 current setting by using "show endian". You can also give the command
1080 "set endian auto", in which case GDB will use the byte order
1081 associated with the executable. Currently, only embedded MIPS
1082 configurations support dynamic selection of target byte order.
1084 * New DOS host serial code
1086 This version uses DPMI interrupts to handle buffered I/O, so you
1087 no longer need to run asynctsr when debugging boards connected to
1090 *** Changes in GDB-4.13:
1092 * New "complete" command
1094 This lists all the possible completions for the rest of the line, if it
1095 were to be given as a command itself. This is intended for use by emacs.
1097 * Trailing space optional in prompt
1099 "set prompt" no longer adds a space for you after the prompt you set. This
1100 allows you to set a prompt which ends in a space or one that does not.
1102 * Breakpoint hit counts
1104 "info break" now displays a count of the number of times the breakpoint
1105 has been hit. This is especially useful in conjunction with "ignore"; you
1106 can ignore a large number of breakpoint hits, look at the breakpoint info
1107 to see how many times the breakpoint was hit, then run again, ignoring one
1108 less than that number, and this will get you quickly to the last hit of
1111 * Ability to stop printing at NULL character
1113 "set print null-stop" will cause GDB to stop printing the characters of
1114 an array when the first NULL is encountered. This is useful when large
1115 arrays actually contain only short strings.
1117 * Shared library breakpoints
1119 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1120 breakpoints in shared libraries before the executable is run.
1122 * Hardware watchpoints
1124 There is a new hardware breakpoint for the watch command for sparclite
1125 targets. See gdb/sparclite/hw_breakpoint.note.
1127 Hardware watchpoints are also now supported under GNU/Linux.
1131 Annotations have been added. These are for use with graphical interfaces,
1132 and are still experimental. Currently only gdba.el uses these.
1134 * Improved Irix 5 support
1136 GDB now works properly with Irix 5.2.
1138 * Improved HPPA support
1140 GDB now works properly with the latest GCC and GAS.
1142 * New native configurations
1144 Sequent PTX4 i[34]86-sequent-ptx4
1145 HPPA running OSF/1 hppa*-*-osf*
1146 Atari TT running SVR4 m68*-*-sysv4*
1147 RS/6000 LynxOS rs6000-*-lynxos*
1151 OS/9000 i[34]86-*-os9k
1152 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1155 * Hitachi SH7000 and E7000-PC ICE support
1157 There is now support for communicating with the Hitachi E7000-PC ICE.
1158 This is available automatically when GDB is configured for the SH.
1162 As usual, a variety of small fixes and improvements, both generic
1163 and configuration-specific. See the ChangeLog for more detail.
1165 *** Changes in GDB-4.12:
1167 * Irix 5 is now supported
1171 GDB-4.12 on the HPPA has a number of changes which make it unable
1172 to debug the output from the currently released versions of GCC and
1173 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1174 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1175 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1178 *** Changes in GDB-4.11:
1180 * User visible changes:
1184 The "set remotedebug" option is now consistent between the mips remote
1185 target, remote targets using the gdb-specific protocol, UDI (AMD's
1186 debug protocol for the 29k) and the 88k bug monitor. It is now an
1187 integer specifying a debug level (normally 0 or 1, but 2 means more
1188 debugging info for the mips target).
1190 * DEC Alpha native support
1192 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1193 debug info, but GDB works fairly well with the DEC compiler and should
1194 work with a future GCC release. See the README file for a few
1195 Alpha-specific notes.
1197 * Preliminary thread implementation
1199 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1201 * LynxOS native and target support for 386
1203 This release has been hosted on LynxOS 2.2, and also can be configured
1204 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1207 * Improvements in C++ mangling/demangling.
1209 This release has much better g++ debugging, specifically in name
1210 mangling/demangling, virtual function calls, print virtual table,
1211 call methods, ...etc.
1213 *** Changes in GDB-4.10:
1215 * User visible changes:
1217 Remote debugging using the GDB-specific (`target remote') protocol now
1218 supports the `load' command. This is only useful if you have some
1219 other way of getting the stub to the target system, and you can put it
1220 somewhere in memory where it won't get clobbered by the download.
1222 Filename completion now works.
1224 When run under emacs mode, the "info line" command now causes the
1225 arrow to point to the line specified. Also, "info line" prints
1226 addresses in symbolic form (as well as hex).
1228 All vxworks based targets now support a user settable option, called
1229 vxworks-timeout. This option represents the number of seconds gdb
1230 should wait for responses to rpc's. You might want to use this if
1231 your vxworks target is, perhaps, a slow software simulator or happens
1232 to be on the far side of a thin network line.
1236 This release contains support for using a DEC alpha as a GDB host for
1237 cross debugging. Native alpha debugging is not supported yet.
1240 *** Changes in GDB-4.9:
1244 This is the first GDB release which is accompanied by a matching testsuite.
1245 The testsuite requires installation of dejagnu, which should be available
1246 via ftp from most sites that carry GNU software.
1250 'Cfront' style demangling has had its name changed to 'ARM' style, to
1251 emphasize that it was written from the specifications in the C++ Annotated
1252 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1253 disclaimers, it still generated too much confusion with users attempting to
1254 use gdb with AT&T cfront.
1258 GDB now uses a standard remote interface to a simulator library.
1259 So far, the library contains simulators for the Zilog Z8001/2, the
1260 Hitachi H8/300, H8/500 and Super-H.
1262 * New targets supported
1264 H8/300 simulator h8300-hitachi-hms or h8300hms
1265 H8/500 simulator h8500-hitachi-hms or h8500hms
1266 SH simulator sh-hitachi-hms or sh
1267 Z8000 simulator z8k-zilog-none or z8ksim
1268 IDT MIPS board over serial line mips-idt-ecoff
1270 Cross-debugging to GO32 targets is supported. It requires a custom
1271 version of the i386-stub.c module which is integrated with the
1272 GO32 memory extender.
1274 * New remote protocols
1276 MIPS remote debugging protocol.
1278 * New source languages supported
1280 This version includes preliminary support for Chill, a Pascal like language
1281 used by telecommunications companies. Chill support is also being integrated
1282 into the GNU compiler, but we don't know when it will be publically available.
1285 *** Changes in GDB-4.8:
1287 * HP Precision Architecture supported
1289 GDB now supports HP PA-RISC machines running HPUX. A preliminary
1290 version of this support was available as a set of patches from the
1291 University of Utah. GDB does not support debugging of programs
1292 compiled with the HP compiler, because HP will not document their file
1293 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
1294 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
1296 Many problems in the preliminary version have been fixed.
1298 * Faster and better demangling
1300 We have improved template demangling and fixed numerous bugs in the GNU style
1301 demangler. It can now handle type modifiers such as `static' or `const'. Wide
1302 character types (wchar_t) are now supported. Demangling of each symbol is now
1303 only done once, and is cached when the symbol table for a file is read in.
1304 This results in a small increase in memory usage for C programs, a moderate
1305 increase in memory usage for C++ programs, and a fantastic speedup in
1308 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
1309 from the specifications in the Annotated Reference Manual, which AT&T's
1310 compiler does not actually implement.
1312 * G++ multiple inheritance compiler problem
1314 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
1315 inheritance lattices was reworked to properly discover ambiguities. We
1316 recently found an example which causes this new algorithm to fail in a
1317 very subtle way, producing bad debug information for those classes.
1318 The file 'gcc.patch' (in this directory) can be applied to gcc to
1319 circumvent the problem. A future GCC release will contain a complete
1322 The previous G++ debug info problem (mentioned below for the gdb-4.7
1323 release) is fixed in gcc version 2.3.2.
1325 * Improved configure script
1327 The `configure' script will now attempt to guess your system type if
1328 you don't supply a host system type. The old scheme of supplying a
1329 host system triplet is preferable over using this. All the magic is
1330 done in the new `config.guess' script. Examine it for details.
1332 We have also brought our configure script much more in line with the FSF's
1333 version. It now supports the --with-xxx options. In particular,
1334 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
1335 The resulting GDB will not be able to read arbitrary object file formats --
1336 only the format ``expected'' to be used on the configured target system.
1337 We hope to make this the default in a future release.
1339 * Documentation improvements
1341 There's new internal documentation on how to modify GDB, and how to
1342 produce clean changes to the code. We implore people to read it
1343 before submitting changes.
1345 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
1346 M4 macros. The new texinfo.tex is provided in this release. Pre-built
1347 `info' files are also provided. To build `info' files from scratch,
1348 you will need the latest `makeinfo' release, which will be available in
1349 a future texinfo-X.Y release.
1351 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
1352 We're not sure exactly which versions have this problem, but it has
1353 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
1354 or better. If that isn't possible, there is a patch in
1355 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
1356 around this problem.
1360 GDB now supports array constants that can be used in expressions typed in by
1361 the user. The syntax is `{element, element, ...}'. Ie: you can now type
1362 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
1365 The new directory `gdb/sparclite' contains a program that demonstrates
1366 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
1368 * New native hosts supported
1370 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
1371 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
1373 * New targets supported
1375 AMD 29k family via UDI a29k-amd-udi or udi29k
1377 * New file formats supported
1379 BFD now supports reading HP/PA-RISC executables (SOM file format?),
1380 HPUX core files, and SCO 3.2v2 core files.
1384 Attaching to processes now works again; thanks for the many bug reports.
1386 We have also stomped on a bunch of core dumps caused by
1387 printf_filtered("%s") problems.
1389 We eliminated a copyright problem on the rpc and ptrace header files
1390 for VxWorks, which was discovered at the last minute during the 4.7
1391 release. You should now be able to build a VxWorks GDB.
1393 You can now interrupt gdb while an attached process is running. This
1394 will cause the attached process to stop, and give control back to GDB.
1396 We fixed problems caused by using too many file descriptors
1397 for reading symbols from object files and libraries. This was
1398 especially a problem for programs that used many (~100) shared
1401 The `step' command now only enters a subroutine if there is line number
1402 information for the subroutine. Otherwise it acts like the `next'
1403 command. Previously, `step' would enter subroutines if there was
1404 any debugging information about the routine. This avoids problems
1405 when using `cc -g1' on MIPS machines.
1407 * Internal improvements
1409 GDB's internal interfaces have been improved to make it easier to support
1410 debugging of multiple languages in the future.
1412 GDB now uses a common structure for symbol information internally.
1413 Minimal symbols (derived from linkage symbols in object files), partial
1414 symbols (from a quick scan of debug information), and full symbols
1415 contain a common subset of information, making it easier to write
1416 shared code that handles any of them.
1418 * New command line options
1420 We now accept --silent as an alias for --quiet.
1424 The memory-mapped-malloc library is now licensed under the GNU Library
1425 General Public License.
1427 *** Changes in GDB-4.7:
1429 * Host/native/target split
1431 GDB has had some major internal surgery to untangle the support for
1432 hosts and remote targets. Now, when you configure GDB for a remote
1433 target, it will no longer load in all of the support for debugging
1434 local programs on the host. When fully completed and tested, this will
1435 ensure that arbitrary host/target combinations are possible.
1437 The primary conceptual shift is to separate the non-portable code in
1438 GDB into three categories. Host specific code is required any time GDB
1439 is compiled on that host, regardless of the target. Target specific
1440 code relates to the peculiarities of the target, but can be compiled on
1441 any host. Native specific code is everything else: it can only be
1442 built when the host and target are the same system. Child process
1443 handling and core file support are two common `native' examples.
1445 GDB's use of /proc for controlling Unix child processes is now cleaner.
1446 It has been split out into a single module under the `target_ops' vector,
1447 plus two native-dependent functions for each system that uses /proc.
1449 * New hosts supported
1451 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
1452 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1453 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
1455 * New targets supported
1457 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
1458 68030 and CPU32 m68030-*-*, m68332-*-*
1460 * New native hosts supported
1462 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1463 (386bsd is not well tested yet)
1464 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
1466 * New file formats supported
1468 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
1469 supports reading of `a.out.adobe' object files, which are an a.out
1470 format extended with minimal information about multiple sections.
1474 `show copying' is the same as the old `info copying'.
1475 `show warranty' is the same as `info warrantee'.
1476 These were renamed for consistency. The old commands continue to work.
1478 `info handle' is a new alias for `info signals'.
1480 You can now define pre-command hooks, which attach arbitrary command
1481 scripts to any command. The commands in the hook will be executed
1482 prior to the user's command. You can also create a hook which will be
1483 executed whenever the program stops. See gdb.texinfo.
1487 We now deal with Cfront style name mangling, and can even extract type
1488 info from mangled symbols. GDB can automatically figure out which
1489 symbol mangling style your C++ compiler uses.
1491 Calling of methods and virtual functions has been improved as well.
1495 The crash that occured when debugging Sun Ansi-C compiled binaries is
1496 fixed. This was due to mishandling of the extra N_SO stabs output
1499 We also finally got Ultrix 4.2 running in house, and fixed core file
1500 support, with help from a dozen people on the net.
1502 John M. Farrell discovered that the reason that single-stepping was so
1503 slow on all of the Mips based platforms (primarily SGI and DEC) was
1504 that we were trying to demangle and lookup a symbol used for internal
1505 purposes on every instruction that was being stepped through. Changing
1506 the name of that symbol so that it couldn't be mistaken for a C++
1507 mangled symbol sped things up a great deal.
1509 Rich Pixley sped up symbol lookups in general by getting much smarter
1510 about when C++ symbol mangling is necessary. This should make symbol
1511 completion (TAB on the command line) much faster. It's not as fast as
1512 we'd like, but it's significantly faster than gdb-4.6.
1516 A new user controllable variable 'call_scratch_address' can
1517 specify the location of a scratch area to be used when GDB
1518 calls a function in the target. This is necessary because the
1519 usual method of putting the scratch area on the stack does not work
1520 in systems that have separate instruction and data spaces.
1522 We integrated changes to support the 29k UDI (Universal Debugger
1523 Interface), but discovered at the last minute that we didn't have all
1524 of the appropriate copyright paperwork. We are working with AMD to
1525 resolve this, and hope to have it available soon.
1529 We have sped up the remote serial line protocol, especially for targets
1530 with lots of registers. It now supports a new `expedited status' ('T')
1531 message which can be used in place of the existing 'S' status message.
1532 This allows the remote stub to send only the registers that GDB
1533 needs to make a quick decision about single-stepping or conditional
1534 breakpoints, eliminating the need to fetch the entire register set for
1535 each instruction being stepped through.
1537 The GDB remote serial protocol now implements a write-through cache for
1538 registers, only re-reading the registers if the target has run.
1540 There is also a new remote serial stub for SPARC processors. You can
1541 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
1542 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
1543 processor with a serial port.
1547 Configure.in files have become much easier to read and modify. A new
1548 `table driven' format makes it more obvious what configurations are
1549 supported, and what files each one uses.
1553 There is a new opcodes library which will eventually contain all of the
1554 disassembly routines and opcode tables. At present, it only contains
1555 Sparc and Z8000 routines. This will allow the assembler, debugger, and
1556 disassembler (binutils/objdump) to share these routines.
1558 The libiberty library is now copylefted under the GNU Library General
1559 Public License. This allows more liberal use, and was done so libg++
1560 can use it. This makes no difference to GDB, since the Library License
1561 grants all the rights from the General Public License.
1565 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
1566 reference to the stabs symbol info used by the debugger. It is (as far
1567 as we know) the only published document on this fascinating topic. We
1568 encourage you to read it, compare it to the stabs information on your
1569 system, and send improvements on the document in general (to
1570 bug-gdb@prep.ai.mit.edu).
1572 And, of course, many bugs have been fixed.
1575 *** Changes in GDB-4.6:
1577 * Better support for C++ function names
1579 GDB now accepts as input the "demangled form" of C++ overloaded function
1580 names and member function names, and can do command completion on such names
1581 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
1582 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
1583 Make use of command completion, it is your friend.
1585 GDB also now accepts a variety of C++ mangled symbol formats. They are
1586 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
1587 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
1588 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
1589 for the list of formats.
1591 * G++ symbol mangling problem
1593 Recent versions of gcc have a bug in how they emit debugging information for
1594 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
1595 directory) can be applied to gcc to fix the problem. Alternatively, if you
1596 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
1597 usual symptom is difficulty with setting breakpoints on methods. GDB complains
1598 about the method being non-existent. (We believe that version 2.2.2 of GCC has
1601 * New 'maintenance' command
1603 All of the commands related to hacking GDB internals have been moved out of
1604 the main command set, and now live behind the 'maintenance' command. This
1605 can also be abbreviated as 'mt'. The following changes were made:
1607 dump-me -> maintenance dump-me
1608 info all-breakpoints -> maintenance info breakpoints
1609 printmsyms -> maintenance print msyms
1610 printobjfiles -> maintenance print objfiles
1611 printpsyms -> maintenance print psymbols
1612 printsyms -> maintenance print symbols
1614 The following commands are new:
1616 maintenance demangle Call internal GDB demangler routine to
1617 demangle a C++ link name and prints the result.
1618 maintenance print type Print a type chain for a given symbol
1620 * Change to .gdbinit file processing
1622 We now read the $HOME/.gdbinit file before processing the argv arguments
1623 (e.g. reading symbol files or core files). This allows global parameters to
1624 be set, which will apply during the symbol reading. The ./.gdbinit is still
1625 read after argv processing.
1627 * New hosts supported
1629 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
1631 GNU/Linux support i386-unknown-linux or linux
1633 We are also including code to support the HP/PA running BSD and HPUX. This
1634 is almost guaranteed not to work, as we didn't have time to test or build it
1635 for this release. We are including it so that the more adventurous (or
1636 masochistic) of you can play with it. We also had major problems with the
1637 fact that the compiler that we got from HP doesn't support the -g option.
1640 * New targets supported
1642 Hitachi H8/300 h8300-hitachi-hms or h8300hms
1644 * More smarts about finding #include files
1646 GDB now remembers the compilation directory for all include files, and for
1647 all files from which C is generated (like yacc and lex sources). This
1648 greatly improves GDB's ability to find yacc/lex sources, and include files,
1649 especially if you are debugging your program from a directory different from
1650 the one that contains your sources.
1652 We also fixed a bug which caused difficulty with listing and setting
1653 breakpoints in include files which contain C code. (In the past, you had to
1654 try twice in order to list an include file that you hadn't looked at before.)
1656 * Interesting infernals change
1658 GDB now deals with arbitrary numbers of sections, where the symbols for each
1659 section must be relocated relative to that section's landing place in the
1660 target's address space. This work was needed to support ELF with embedded
1661 stabs used by Solaris-2.0.
1663 * Bug fixes (of course!)
1665 There have been loads of fixes for the following things:
1666 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
1667 i960, stabs, DOS(GO32), procfs, etc...
1669 See the ChangeLog for details.
1671 *** Changes in GDB-4.5:
1673 * New machines supported (host and target)
1675 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
1677 SGI Irix-4.x mips-sgi-irix4 or iris4
1679 * New malloc package
1681 GDB now uses a new memory manager called mmalloc, based on gmalloc.
1682 Mmalloc is capable of handling mutiple heaps of memory. It is also
1683 capable of saving a heap to a file, and then mapping it back in later.
1684 This can be used to greatly speedup the startup of GDB by using a
1685 pre-parsed symbol table which lives in a mmalloc managed heap. For
1686 more details, please read mmalloc/mmalloc.texi.
1690 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
1691 'help info proc' for details.
1693 * MIPS ecoff symbol table format
1695 The code that reads MIPS symbol table format is now supported on all hosts.
1696 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
1699 * File name changes for MS-DOS
1701 Many files in the config directories have been renamed to make it easier to
1702 support GDB on MS-DOSe systems (which have very restrictive file name
1703 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
1704 environment) is close to working but has some remaining problems. Note
1705 that debugging of DOS programs is not supported, due to limitations
1706 in the ``operating system'', but it can be used to host cross-debugging.
1708 * Cross byte order fixes
1710 Many fixes have been made to support cross debugging of Sparc and MIPS
1711 targets from hosts whose byte order differs.
1713 * New -mapped and -readnow options
1715 If memory-mapped files are available on your system through the 'mmap'
1716 system call, you can use the -mapped option on the `file' or
1717 `symbol-file' commands to cause GDB to write the symbols from your
1718 program into a reusable file. If the program you are debugging is
1719 called `/path/fred', the mapped symbol file will be `./fred.syms'.
1720 Future GDB debugging sessions will notice the presence of this file,
1721 and will quickly map in symbol information from it, rather than reading
1722 the symbol table from the executable program. Using the '-mapped'
1723 option in a GDB `file' or `symbol-file' command has the same effect as
1724 starting GDB with the '-mapped' command-line option.
1726 You can cause GDB to read the entire symbol table immediately by using
1727 the '-readnow' option with any of the commands that load symbol table
1728 information (or on the GDB command line). This makes the command
1729 slower, but makes future operations faster.
1731 The -mapped and -readnow options are typically combined in order to
1732 build a `fred.syms' file that contains complete symbol information.
1733 A simple GDB invocation to do nothing but build a `.syms' file for future
1736 gdb -batch -nx -mapped -readnow programname
1738 The `.syms' file is specific to the host machine on which GDB is run.
1739 It holds an exact image of GDB's internal symbol table. It cannot be
1740 shared across multiple host platforms.
1742 * longjmp() handling
1744 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
1745 siglongjmp() without losing control. This feature has not yet been ported to
1746 all systems. It currently works on many 386 platforms, all MIPS-based
1747 platforms (SGI, DECstation, etc), and Sun3/4.
1751 Preliminary work has been put in to support the new Solaris OS from Sun. At
1752 this time, it can control and debug processes, but it is not capable of
1757 As always, many many bug fixes. The major areas were with g++, and mipsread.
1758 People using the MIPS-based platforms should experience fewer mysterious
1759 crashes and trashed symbol tables.
1761 *** Changes in GDB-4.4:
1763 * New machines supported (host and target)
1765 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1767 BSD Reno on Vax vax-dec-bsd
1768 Ultrix on Vax vax-dec-ultrix
1770 * New machines supported (target)
1772 AMD 29000 embedded, using EBMON a29k-none-none
1776 GDB continues to improve its handling of C++. `References' work better.
1777 The demangler has also been improved, and now deals with symbols mangled as
1778 per the Annotated C++ Reference Guide.
1780 GDB also now handles `stabs' symbol information embedded in MIPS
1781 `ecoff' symbol tables. Since the ecoff format was not easily
1782 extensible to handle new languages such as C++, this appeared to be a
1783 good way to put C++ debugging info into MIPS binaries. This option
1784 will be supported in the GNU C compiler, version 2, when it is
1787 * New features for SVR4
1789 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
1790 shared libraries. Debugging dynamically linked programs should present
1791 only minor differences from debugging statically linked programs.
1793 The `info proc' command will print out information about any process
1794 on an SVR4 system (including the one you are debugging). At the moment,
1795 it prints the address mappings of the process.
1797 If you bring up GDB on another SVR4 system, please send mail to
1798 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
1800 * Better dynamic linking support in SunOS
1802 Reading symbols from shared libraries which contain debugging symbols
1803 now works properly. However, there remain issues such as automatic
1804 skipping of `transfer vector' code during function calls, which
1805 make it harder to debug code in a shared library, than to debug the
1806 same code linked statically.
1810 GDB is now using the latest `getopt' routines from the FSF. This
1811 version accepts the -- prefix for options with long names. GDB will
1812 continue to accept the old forms (-option and +option) as well.
1813 Various single letter abbreviations for options have been explicity
1814 added to the option table so that they won't get overshadowed in the
1815 future by other options that begin with the same letter.
1819 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
1820 Many assorted bugs have been handled. Many more remain to be handled.
1821 See the various ChangeLog files (primarily in gdb and bfd) for details.
1824 *** Changes in GDB-4.3:
1826 * New machines supported (host and target)
1828 Amiga 3000 running Amix m68k-cbm-svr4 or amix
1829 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
1830 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
1832 * Almost SCO Unix support
1834 We had hoped to support:
1835 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1836 (except for core file support), but we discovered very late in the release
1837 that it has problems with process groups that render gdb unusable. Sorry
1838 about that. I encourage people to fix it and post the fixes.
1840 * Preliminary ELF and DWARF support
1842 GDB can read ELF object files on System V Release 4, and can handle
1843 debugging records for C, in DWARF format, in ELF files. This support
1844 is preliminary. If you bring up GDB on another SVR4 system, please
1845 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
1850 GDB now uses the latest `readline' library. One user-visible change
1851 is that two tabs will list possible command completions, which previously
1852 required typing M-? (meta-question mark, or ESC ?).
1856 The `stepi' bug that many of you noticed has been squashed.
1857 Many bugs in C++ have been handled. Many more remain to be handled.
1858 See the various ChangeLog files (primarily in gdb and bfd) for details.
1860 * State of the MIPS world (in case you wondered):
1862 GDB can understand the symbol tables emitted by the compilers
1863 supplied by most vendors of MIPS-based machines, including DEC. These
1864 symbol tables are in a format that essentially nobody else uses.
1866 Some versions of gcc come with an assembler post-processor called
1867 mips-tfile. This program is required if you want to do source-level
1868 debugging of gcc-compiled programs. I believe FSF does not ship
1869 mips-tfile with gcc version 1, but it will eventually come with gcc
1872 Debugging of g++ output remains a problem. g++ version 1.xx does not
1873 really support it at all. (If you're lucky, you should be able to get
1874 line numbers and stack traces to work, but no parameters or local
1875 variables.) With some work it should be possible to improve the
1878 When gcc version 2 is released, you will have somewhat better luck.
1879 However, even then you will get confusing results for inheritance and
1882 We will eventually provide full debugging of g++ output on
1883 DECstations. This will probably involve some kind of stabs-in-ecoff
1884 encapulation, but the details have not been worked out yet.
1887 *** Changes in GDB-4.2:
1889 * Improved configuration
1891 Only one copy of `configure' exists now, and it is not self-modifying.
1892 Porting BFD is simpler.
1896 The `step' and `next' commands now only stop at the first instruction
1897 of a source line. This prevents the multiple stops that used to occur
1898 in switch statements, for-loops, etc. `Step' continues to stop if a
1899 function that has debugging information is called within the line.
1903 Lots of small bugs fixed. More remain.
1905 * New host supported (not target)
1907 Intel 386 PC clone running Mach i386-none-mach
1910 *** Changes in GDB-4.1:
1912 * Multiple source language support
1914 GDB now has internal scaffolding to handle several source languages.
1915 It determines the type of each source file from its filename extension,
1916 and will switch expression parsing and number formatting to match the
1917 language of the function in the currently selected stack frame.
1918 You can also specifically set the language to be used, with
1919 `set language c' or `set language modula-2'.
1923 GDB now has preliminary support for the GNU Modula-2 compiler,
1924 currently under development at the State University of New York at
1925 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
1926 continue through the fall of 1991 and into 1992.
1928 Other Modula-2 compilers are currently not supported, and attempting to
1929 debug programs compiled with them will likely result in an error as the
1930 symbol table is read. Feel free to work on it, though!
1932 There are hooks in GDB for strict type checking and range checking,
1933 in the `Modula-2 philosophy', but they do not currently work.
1937 GDB can now write to executable and core files (e.g. patch
1938 a variable's value). You must turn this switch on, specify
1939 the file ("exec foo" or "core foo"), *then* modify it, e.g.
1940 by assigning a new value to a variable. Modifications take
1943 * Automatic SunOS shared library reading
1945 When you run your program, GDB automatically determines where its
1946 shared libraries (if any) have been loaded, and reads their symbols.
1947 The `share' command is no longer needed. This also works when
1948 examining core files.
1952 You can specify the number of lines that the `list' command shows.
1955 * New machines supported (host and target)
1957 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
1958 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
1959 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
1961 * New hosts supported (not targets)
1963 IBM RT/PC: romp-ibm-aix or rtpc
1965 * New targets supported (not hosts)
1967 AMD 29000 embedded with COFF a29k-none-coff
1968 AMD 29000 embedded with a.out a29k-none-aout
1969 Ultracomputer remote kernel debug a29k-nyu-kern
1971 * New remote interfaces
1977 *** Changes in GDB-4.0:
1981 Wide output is wrapped at good places to make the output more readable.
1983 Gdb now supports cross-debugging from a host machine of one type to a
1984 target machine of another type. Communication with the target system
1985 is over serial lines. The ``target'' command handles connecting to the
1986 remote system; the ``load'' command will download a program into the
1987 remote system. Serial stubs for the m68k and i386 are provided. Gdb
1988 also supports debugging of realtime processes running under VxWorks,
1989 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
1990 stub on the target system.
1992 New CPUs supported include the AMD 29000 and Intel 960.
1994 GDB now reads object files and symbol tables via a ``binary file''
1995 library, which allows a single copy of GDB to debug programs of multiple
1996 object file types such as a.out and coff.
1998 There is now a GDB reference card in "doc/refcard.tex". (Make targets
1999 refcard.dvi and refcard.ps are available to format it).
2002 * Control-Variable user interface simplified
2004 All variables that control the operation of the debugger can be set
2005 by the ``set'' command, and displayed by the ``show'' command.
2007 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2008 ``Show prompt'' produces the response:
2009 Gdb's prompt is new-gdb=>.
2011 What follows are the NEW set commands. The command ``help set'' will
2012 print a complete list of old and new set commands. ``help set FOO''
2013 will give a longer description of the variable FOO. ``show'' will show
2014 all of the variable descriptions and their current settings.
2016 confirm on/off: Enables warning questions for operations that are
2017 hard to recover from, e.g. rerunning the program while
2018 it is already running. Default is ON.
2020 editing on/off: Enables EMACS style command line editing
2021 of input. Previous lines can be recalled with
2022 control-P, the current line can be edited with control-B,
2023 you can search for commands with control-R, etc.
2026 history filename NAME: NAME is where the gdb command history
2027 will be stored. The default is .gdb_history,
2028 or the value of the environment variable
2031 history size N: The size, in commands, of the command history. The
2032 default is 256, or the value of the environment variable
2035 history save on/off: If this value is set to ON, the history file will
2036 be saved after exiting gdb. If set to OFF, the
2037 file will not be saved. The default is OFF.
2039 history expansion on/off: If this value is set to ON, then csh-like
2040 history expansion will be performed on
2041 command line input. The default is OFF.
2043 radix N: Sets the default radix for input and output. It can be set
2044 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2045 in the current radix, so "set radix 10" is always a no-op.
2047 height N: This integer value is the number of lines on a page. Default
2048 is 24, the current `stty rows'' setting, or the ``li#''
2049 setting from the termcap entry matching the environment
2052 width N: This integer value is the number of characters on a line.
2053 Default is 80, the current `stty cols'' setting, or the ``co#''
2054 setting from the termcap entry matching the environment
2057 Note: ``set screensize'' is obsolete. Use ``set height'' and
2058 ``set width'' instead.
2060 print address on/off: Print memory addresses in various command displays,
2061 such as stack traces and structure values. Gdb looks
2062 more ``symbolic'' if you turn this off; it looks more
2063 ``machine level'' with it on. Default is ON.
2065 print array on/off: Prettyprint arrays. New convenient format! Default
2068 print demangle on/off: Print C++ symbols in "source" form if on,
2071 print asm-demangle on/off: Same, for assembler level printouts
2074 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2077 * Support for Epoch Environment.
2079 The epoch environment is a version of Emacs v18 with windowing. One
2080 new command, ``inspect'', is identical to ``print'', except that if you
2081 are running in the epoch environment, the value is printed in its own
2085 * Support for Shared Libraries
2087 GDB can now debug programs and core files that use SunOS shared libraries.
2088 Symbols from a shared library cannot be referenced
2089 before the shared library has been linked with the program (this
2090 happens after you type ``run'' and before the function main() is entered).
2091 At any time after this linking (including when examining core files
2092 from dynamically linked programs), gdb reads the symbols from each
2093 shared library when you type the ``sharedlibrary'' command.
2094 It can be abbreviated ``share''.
2096 sharedlibrary REGEXP: Load shared object library symbols for files
2097 matching a unix regular expression. No argument
2098 indicates to load symbols for all shared libraries.
2100 info sharedlibrary: Status of loaded shared libraries.
2105 A watchpoint stops execution of a program whenever the value of an
2106 expression changes. Checking for this slows down execution
2107 tremendously whenever you are in the scope of the expression, but is
2108 quite useful for catching tough ``bit-spreader'' or pointer misuse
2109 problems. Some machines such as the 386 have hardware for doing this
2110 more quickly, and future versions of gdb will use this hardware.
2112 watch EXP: Set a watchpoint (breakpoint) for an expression.
2114 info watchpoints: Information about your watchpoints.
2116 delete N: Deletes watchpoint number N (same as breakpoints).
2117 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2118 enable N: Re-enables watchpoint number N (same as breakpoints).
2121 * C++ multiple inheritance
2123 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2126 * C++ exception handling
2128 Gdb now supports limited C++ exception handling. Besides the existing
2129 ability to breakpoint on an exception handler, gdb can breakpoint on
2130 the raising of an exception (before the stack is peeled back to the
2133 catch FOO: If there is a FOO exception handler in the dynamic scope,
2134 set a breakpoint to catch exceptions which may be raised there.
2135 Multiple exceptions (``catch foo bar baz'') may be caught.
2137 info catch: Lists all exceptions which may be caught in the
2138 current stack frame.
2141 * Minor command changes
2143 The command ``call func (arg, arg, ...)'' now acts like the print
2144 command, except it does not print or save a value if the function's result
2145 is void. This is similar to dbx usage.
2147 The ``up'' and ``down'' commands now always print the frame they end up
2148 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2149 frames without printing.
2151 * New directory command
2153 'dir' now adds directories to the FRONT of the source search path.
2154 The path starts off empty. Source files that contain debug information
2155 about the directory in which they were compiled can be found even
2156 with an empty path; Sun CC and GCC include this information. If GDB can't
2157 find your source file in the current directory, type "dir .".
2159 * Configuring GDB for compilation
2161 For normal use, type ``./configure host''. See README or gdb.texinfo
2164 GDB now handles cross debugging. If you are remotely debugging between
2165 two different machines, type ``./configure host -target=targ''.
2166 Host is the machine where GDB will run; targ is the machine
2167 where the program that you are debugging will run.
projects / binutils-gdb.git / blob