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*
70 CHILL, a Pascal like language used by telecommunications companies.
72 * REMOVED configurations and files
74 AMD 29k family via UDI a29k-amd-udi, udi29k
75 A29K VxWorks a29k-*-vxworks
76 AMD 29000 embedded, using EBMON a29k-none-none
77 AMD 29000 embedded with COFF a29k-none-coff
78 AMD 29000 embedded with a.out a29k-none-aout
80 testsuite/gdb.hp/gdb.threads-hp/ directory
82 * New command "set max-user-call-depth <nnn>"
84 This command allows the user to limit the call depth of user-defined
85 commands. The default is 1024.
87 * Changes in FreeBSD/i386 native debugging.
89 Support for the "generate-core-file" has been added.
91 * New commands "dump", "append", and "restore".
93 These commands allow data to be copied from target memory
94 to a bfd-format or binary file (dump and append), and back
95 from a file into memory (restore).
97 *** Changes in GDB 5.2.1:
105 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
106 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
107 Fix, by Joel Brobecker imported from mainline.
109 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
110 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
111 Fix, by Fred Fish, imported from mainline.
113 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
114 Surprisingly enough, it works now.
115 By Michal Ludvig, imported from mainline.
117 i386 hardware watchpoint support:
118 avoid misses on second run for some targets.
119 By Pierre Muller, imported from mainline.
121 *** Changes in GDB 5.2:
123 * New command "set trust-readonly-sections on[off]".
125 This command is a hint that tells gdb that read-only sections
126 really are read-only (ie. that their contents will not change).
127 In this mode, gdb will go to the object file rather than the
128 target to read memory from read-only sections (such as ".text").
129 This can be a significant performance improvement on some
130 (notably embedded) targets.
132 * New command "generate-core-file" (or "gcore").
134 This new gdb command allows the user to drop a core file of the child
135 process state at any time. So far it's been implemented only for
136 GNU/Linux and Solaris, but should be relatively easily ported to other
137 hosts. Argument is core file name (defaults to core.<pid>).
139 * New command line option
141 GDB now accepts --pid or -p followed by a process id.
143 * Change in command line behavior -- corefiles vs. process ids.
145 There is a subtle behavior in the way in which GDB handles
146 command line arguments. The first non-flag argument is always
147 a program to debug, but the second non-flag argument may either
148 be a corefile or a process id. Previously, GDB would attempt to
149 open the second argument as a corefile, and if that failed, would
150 issue a superfluous error message and then attempt to attach it as
151 a process. Now, if the second argument begins with a non-digit,
152 it will be treated as a corefile. If it begins with a digit,
153 GDB will attempt to attach it as a process, and if no such process
154 is found, will then attempt to open it as a corefile.
156 * Changes in ARM configurations.
158 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
159 configuration is fully multi-arch.
161 * New native configurations
163 ARM NetBSD arm*-*-netbsd*
164 x86 OpenBSD i[3456]86-*-openbsd*
165 AMD x86-64 running GNU/Linux x86_64-*-linux-*
166 Sparc64 running FreeBSD sparc64-*-freebsd*
170 Sanyo XStormy16 xstormy16-elf
172 * OBSOLETE configurations and files
174 Configurations that have been declared obsolete in this release have
175 been commented out. Unless there is activity to revive these
176 configurations, the next release of GDB will have their sources
179 AMD 29k family via UDI a29k-amd-udi, udi29k
180 A29K VxWorks a29k-*-vxworks
181 AMD 29000 embedded, using EBMON a29k-none-none
182 AMD 29000 embedded with COFF a29k-none-coff
183 AMD 29000 embedded with a.out a29k-none-aout
185 testsuite/gdb.hp/gdb.threads-hp/ directory
187 * REMOVED configurations and files
189 TI TMS320C80 tic80-*-*
191 PowerPC Solaris powerpcle-*-solaris*
192 PowerPC Windows NT powerpcle-*-cygwin32
193 PowerPC Netware powerpc-*-netware*
194 Harris/CXUX m88k m88*-harris-cxux*
195 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
196 ns32k-utek-sysv* ns32k-utek-*
197 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
198 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
199 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
200 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
201 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
203 * Changes to command line processing
205 The new `--args' feature can be used to specify command-line arguments
206 for the inferior from gdb's command line.
208 * Changes to key bindings
210 There is a new `operate-and-get-next' function bound to `C-o'.
212 *** Changes in GDB 5.1.1
214 Fix compile problem on DJGPP.
216 Fix a problem with floating-point registers on the i386 being
219 Fix to stop GDB crashing on .debug_str debug info.
221 Numerous documentation fixes.
223 Numerous testsuite fixes.
225 *** Changes in GDB 5.1:
227 * New native configurations
229 Alpha FreeBSD alpha*-*-freebsd*
230 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
231 MIPS GNU/Linux mips*-*-linux*
232 MIPS SGI Irix 6.x mips*-sgi-irix6*
234 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
238 Motorola 68HC11 and 68HC12 m68hc11-elf
240 UltraSparc running GNU/Linux sparc64-*-linux*
242 * OBSOLETE configurations and files
244 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
245 Harris/CXUX m88k m88*-harris-cxux*
246 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
247 ns32k-utek-sysv* ns32k-utek-*
248 TI TMS320C80 tic80-*-*
250 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
251 PowerPC Solaris powerpcle-*-solaris*
252 PowerPC Windows NT powerpcle-*-cygwin32
253 PowerPC Netware powerpc-*-netware*
254 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
255 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
256 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
257 Apple Macintosh (MPW) host N/A
259 stuff.c (Program to stuff files into a specially prepared space in kdb)
260 kdb-start.c (Main loop for the standalone kernel debugger)
262 Configurations that have been declared obsolete in this release have
263 been commented out. Unless there is activity to revive these
264 configurations, the next release of GDB will have their sources
267 * REMOVED configurations and files
269 Altos 3068 m68*-altos-*
270 Convex c1-*-*, c2-*-*
272 ARM RISCix arm-*-* (as host)
276 * GDB has been converted to ISO C.
278 GDB's source code has been converted to ISO C. In particular, the
279 sources are fully protoized, and rely on standard headers being
284 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
286 * The MI enabled by default.
288 The new machine oriented interface (MI) introduced in GDB 5.0 has been
289 revised and enabled by default. Packages which use GDB as a debugging
290 engine behind a UI or another front end are encouraged to switch to
291 using the GDB/MI interface, instead of the old annotations interface
292 which is now deprecated.
294 * Support for debugging Pascal programs.
296 GDB now includes support for debugging Pascal programs. The following
297 main features are supported:
299 - Pascal-specific data types such as sets;
301 - automatic recognition of Pascal sources based on file-name
304 - Pascal-style display of data types, variables, and functions;
306 - a Pascal expression parser.
308 However, some important features are not yet supported.
310 - Pascal string operations are not supported at all;
312 - there are some problems with boolean types;
314 - Pascal type hexadecimal constants are not supported
315 because they conflict with the internal variables format;
317 - support for Pascal objects and classes is not full yet;
319 - unlike Pascal, GDB is case-sensitive for symbol names.
321 * Changes in completion.
323 Commands such as `shell', `run' and `set args', which pass arguments
324 to inferior programs, now complete on file names, similar to what
325 users expect at the shell prompt.
327 Commands which accept locations, such as `disassemble', `print',
328 `breakpoint', `until', etc. now complete on filenames as well as
329 program symbols. Thus, if you type "break foob TAB", and the source
330 files linked into the programs include `foobar.c', that file name will
331 be one of the candidates for completion. However, file names are not
332 considered for completion after you typed a colon that delimits a file
333 name from a name of a function in that file, as in "break foo.c:bar".
335 `set demangle-style' completes on available demangling styles.
337 * New platform-independent commands:
339 It is now possible to define a post-hook for a command as well as a
340 hook that runs before the command. For more details, see the
341 documentation of `hookpost' in the GDB manual.
343 * Changes in GNU/Linux native debugging.
345 Support for debugging multi-threaded programs has been completely
346 revised for all platforms except m68k and sparc. You can now debug as
347 many threads as your system allows you to have.
349 Attach/detach is supported for multi-threaded programs.
351 Support for SSE registers was added for x86. This doesn't work for
352 multi-threaded programs though.
354 * Changes in MIPS configurations.
356 Multi-arch support is enabled for all MIPS configurations.
358 GDB can now be built as native debugger on SGI Irix 6.x systems for
359 debugging n32 executables. (Debugging 64-bit executables is not yet
362 * Unified support for hardware watchpoints in all x86 configurations.
364 Most (if not all) native x86 configurations support hardware-assisted
365 breakpoints and watchpoints in a unified manner. This support
366 implements debug register sharing between watchpoints, which allows to
367 put a virtually infinite number of watchpoints on the same address,
368 and also supports watching regions up to 16 bytes with several debug
371 The new maintenance command `maintenance show-debug-regs' toggles
372 debugging print-outs in functions that insert, remove, and test
373 watchpoints and hardware breakpoints.
375 * Changes in the DJGPP native configuration.
377 New command ``info dos sysinfo'' displays assorted information about
378 the CPU, OS, memory, and DPMI server.
380 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
381 display information about segment descriptors stored in GDT, LDT, and
384 New commands ``info dos pde'' and ``info dos pte'' display entries
385 from Page Directory and Page Tables (for now works with CWSDPMI only).
386 New command ``info dos address-pte'' displays the Page Table entry for
387 a given linear address.
389 GDB can now pass command lines longer than 126 characters to the
390 program being debugged (requires an update to the libdbg.a library
391 which is part of the DJGPP development kit).
393 DWARF2 debug info is now supported.
395 It is now possible to `step' and `next' through calls to `longjmp'.
397 * Changes in documentation.
399 All GDB documentation was converted to GFDL, the GNU Free
400 Documentation License.
402 Tracepoints-related commands are now fully documented in the GDB
405 TUI, the Text-mode User Interface, is now documented in the manual.
407 Tracepoints-related commands are now fully documented in the GDB
410 The "GDB Internals" manual now has an index. It also includes
411 documentation of `ui_out' functions, GDB coding standards, x86
412 hardware watchpoints, and memory region attributes.
414 * GDB's version number moved to ``version.in''
416 The Makefile variable VERSION has been replaced by the file
417 ``version.in''. People creating GDB distributions should update the
418 contents of this file.
422 GUD support is now a standard part of the EMACS distribution.
424 *** Changes in GDB 5.0:
426 * Improved support for debugging FP programs on x86 targets
428 Unified and much-improved support for debugging floating-point
429 programs on all x86 targets. In particular, ``info float'' now
430 displays the FP registers in the same format on all x86 targets, with
431 greater level of detail.
433 * Improvements and bugfixes in hardware-assisted watchpoints
435 It is now possible to watch array elements, struct members, and
436 bitfields with hardware-assisted watchpoints. Data-read watchpoints
437 on x86 targets no longer erroneously trigger when the address is
440 * Improvements in the native DJGPP version of GDB
442 The distribution now includes all the scripts and auxiliary files
443 necessary to build the native DJGPP version on MS-DOS/MS-Windows
444 machines ``out of the box''.
446 The DJGPP version can now debug programs that use signals. It is
447 possible to catch signals that happened in the debuggee, deliver
448 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
449 would kill the program being debugged.) Programs that hook hardware
450 interrupts (keyboard, timer, etc.) can also be debugged.
452 It is now possible to debug DJGPP programs that redirect their
453 standard handles or switch them to raw (as opposed to cooked) mode, or
454 even close them. The command ``run < foo > bar'' works as expected,
455 and ``info terminal'' reports useful information about the debuggee's
456 terminal, including raw/cooked mode, redirection, etc.
458 The DJGPP version now uses termios functions for console I/O, which
459 enables debugging graphics programs. Interrupting GDB with Ctrl-C
462 DOS-style file names with drive letters are now fully supported by
465 It is now possible to debug DJGPP programs that switch their working
466 directory. It is also possible to rerun the debuggee any number of
467 times without restarting GDB; thus, you can use the same setup,
468 breakpoints, etc. for many debugging sessions.
470 * New native configurations
472 ARM GNU/Linux arm*-*-linux*
473 PowerPC GNU/Linux powerpc-*-linux*
477 Motorola MCore mcore-*-*
478 x86 VxWorks i[3456]86-*-vxworks*
479 PowerPC VxWorks powerpc-*-vxworks*
480 TI TMS320C80 tic80-*-*
482 * OBSOLETE configurations
484 Altos 3068 m68*-altos-*
485 Convex c1-*-*, c2-*-*
487 ARM RISCix arm-*-* (as host)
490 Configurations that have been declared obsolete will be commented out,
491 but the code will be left in place. If there is no activity to revive
492 these configurations before the next release of GDB, the sources will
493 be permanently REMOVED.
495 * Gould support removed
497 Support for the Gould PowerNode and NP1 has been removed.
499 * New features for SVR4
501 On SVR4 native platforms (such as Solaris), if you attach to a process
502 without first loading a symbol file, GDB will now attempt to locate and
503 load symbols from the running process's executable file.
505 * Many C++ enhancements
507 C++ support has been greatly improved. Overload resolution now works properly
508 in almost all cases. RTTI support is on the way.
510 * Remote targets can connect to a sub-program
512 A popen(3) style serial-device has been added. This device starts a
513 sub-process (such as a stand-alone simulator) and then communicates
514 with that. The sub-program to run is specified using the syntax
515 ``|<program> <args>'' vis:
517 (gdb) set remotedebug 1
518 (gdb) target extended-remote |mn10300-elf-sim program-args
520 * MIPS 64 remote protocol
522 A long standing bug in the mips64 remote protocol where by GDB
523 expected certain 32 bit registers (ex SR) to be transfered as 32
524 instead of 64 bits has been fixed.
526 The command ``set remote-mips64-transfers-32bit-regs on'' has been
527 added to provide backward compatibility with older versions of GDB.
529 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
531 The command ``set remotebinarydownload'' command has been replaced by
532 ``set remote X-packet''. Other commands in ``set remote'' family
533 include ``set remote P-packet''.
535 * Breakpoint commands accept ranges.
537 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
538 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
539 ``tracepoint passcount'' also accepts a range of tracepoints.
541 * ``apropos'' command added.
543 The ``apropos'' command searches through command names and
544 documentation strings, printing out matches, making it much easier to
545 try to find a command that does what you are looking for.
549 A new machine oriented interface (MI) has been added to GDB. This
550 interface is designed for debug environments running GDB as a separate
551 process. This is part of the long term libGDB project. See the
552 "GDB/MI" chapter of the GDB manual for further information. It can be
553 enabled by configuring with:
555 .../configure --enable-gdbmi
557 *** Changes in GDB-4.18:
559 * New native configurations
561 HP-UX 10.20 hppa*-*-hpux10.20
562 HP-UX 11.x hppa*-*-hpux11.0*
563 M68K GNU/Linux m68*-*-linux*
567 Fujitsu FR30 fr30-*-elf*
568 Intel StrongARM strongarm-*-*
569 Mitsubishi D30V d30v-*-*
571 * OBSOLETE configurations
573 Gould PowerNode, NP1 np1-*-*, pn-*-*
575 Configurations that have been declared obsolete will be commented out,
576 but the code will be left in place. If there is no activity to revive
577 these configurations before the next release of GDB, the sources will
578 be permanently REMOVED.
582 As a compatibility experiment, GDB's source files buildsym.h and
583 buildsym.c have been converted to pure standard C, no longer
584 containing any K&R compatibility code. We believe that all systems in
585 use today either come with a standard C compiler, or have a GCC port
586 available. If this is not true, please report the affected
587 configuration to bug-gdb@gnu.org immediately. See the README file for
588 information about getting a standard C compiler if you don't have one
593 GDB now uses readline 2.2.
595 * set extension-language
597 You can now control the mapping between filename extensions and source
598 languages by using the `set extension-language' command. For instance,
599 you can ask GDB to treat .c files as C++ by saying
600 set extension-language .c c++
601 The command `info extensions' lists all of the recognized extensions
602 and their associated languages.
604 * Setting processor type for PowerPC and RS/6000
606 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
607 you can use the `set processor' command to specify what variant of the
608 PowerPC family you are debugging. The command
612 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
613 following PowerPC and RS6000 variants:
615 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
616 rs6000 IBM RS6000 ("POWER") architecture, user-level view
618 403GC IBM PowerPC 403GC
619 505 Motorola PowerPC 505
620 860 Motorola PowerPC 860 or 850
621 601 Motorola PowerPC 601
622 602 Motorola PowerPC 602
623 603 Motorola/IBM PowerPC 603 or 603e
624 604 Motorola PowerPC 604 or 604e
625 750 Motorola/IBM PowerPC 750 or 750
627 At the moment, this command just tells GDB what to name the
628 special-purpose processor registers. Since almost all the affected
629 registers are inaccessible to user-level programs, this command is
630 only useful for remote debugging in its present form.
634 Thanks to a major code donation from Hewlett-Packard, GDB now has much
635 more extensive support for HP-UX. Added features include shared
636 library support, kernel threads and hardware watchpoints for 11.00,
637 support for HP's ANSI C and C++ compilers, and a compatibility mode
638 for xdb and dbx commands.
642 HP's donation includes the new concept of catchpoints, which is a
643 generalization of the old catch command. On HP-UX, it is now possible
644 to catch exec, fork, and vfork, as well as library loading.
646 This means that the existing catch command has changed; its first
647 argument now specifies the type of catch to be set up. See the
648 output of "help catch" for a list of catchpoint types.
650 * Debugging across forks
652 On HP-UX, you can choose which process to debug when a fork() happens
657 HP has donated a curses-based terminal user interface (TUI). To get
658 it, build with --enable-tui. Although this can be enabled for any
659 configuration, at present it only works for native HP debugging.
661 * GDB remote protocol additions
663 A new protocol packet 'X' that writes binary data is now available.
664 Default behavior is to try 'X', then drop back to 'M' if the stub
665 fails to respond. The settable variable `remotebinarydownload'
666 allows explicit control over the use of 'X'.
668 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
669 full 64-bit address. The command
671 set remoteaddresssize 32
673 can be used to revert to the old behaviour. For existing remote stubs
674 the change should not be noticed, as the additional address information
677 In order to assist in debugging stubs, you may use the maintenance
678 command `packet' to send any text string to the stub. For instance,
680 maint packet heythere
682 sends the packet "$heythere#<checksum>". Note that it is very easy to
683 disrupt a debugging session by sending the wrong packet at the wrong
686 The compare-sections command allows you to compare section data on the
687 target to what is in the executable file without uploading or
688 downloading, by comparing CRC checksums.
690 * Tracing can collect general expressions
692 You may now collect general expressions at tracepoints. This requires
693 further additions to the target-side stub; see tracepoint.c and
694 doc/agentexpr.texi for further details.
696 * mask-address variable for Mips
698 For Mips targets, you may control the zeroing of the upper 32 bits of
699 a 64-bit address by entering `set mask-address on'. This is mainly
700 of interest to users of embedded R4xxx and R5xxx processors.
702 * Higher serial baud rates
704 GDB's serial code now allows you to specify baud rates 57600, 115200,
705 230400, and 460800 baud. (Note that your host system may not be able
706 to achieve all of these rates.)
710 The i960 configuration now includes an initial implementation of a
711 builtin simulator, contributed by Jim Wilson.
714 *** Changes in GDB-4.17:
716 * New native configurations
718 Alpha GNU/Linux alpha*-*-linux*
719 Unixware 2.x i[3456]86-unixware2*
720 Irix 6.x mips*-sgi-irix6*
721 PowerPC GNU/Linux powerpc-*-linux*
722 PowerPC Solaris powerpcle-*-solaris*
723 Sparc GNU/Linux sparc-*-linux*
724 Motorola sysV68 R3V7.1 m68k-motorola-sysv
728 Argonaut Risc Chip (ARC) arc-*-*
729 Hitachi H8/300S h8300*-*-*
730 Matsushita MN10200 w/simulator mn10200-*-*
731 Matsushita MN10300 w/simulator mn10300-*-*
732 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
733 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
734 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
735 Mitsubishi D10V w/simulator d10v-*-*
736 Mitsubishi M32R/D w/simulator m32r-*-elf*
737 Tsqware Sparclet sparclet-*-*
738 NEC V850 w/simulator v850-*-*
740 * New debugging protocols
742 ARM with RDI protocol arm*-*-*
743 M68K with dBUG monitor m68*-*-{aout,coff,elf}
744 DDB and LSI variants of PMON protocol mips*-*-*
745 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
746 PowerPC with SDS protocol powerpc{,le}-*-eabi
747 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
751 All configurations can now understand and use the DWARF 2 debugging
752 format. The choice is automatic, if the symbol file contains DWARF 2
757 GDB now includes basic Java language support. This support is
758 only useful with Java compilers that produce native machine code.
760 * solib-absolute-prefix and solib-search-path
762 For SunOS and SVR4 shared libraries, you may now set the prefix for
763 loading absolute shared library symbol files, and the search path for
764 locating non-absolute shared library symbol files.
766 * Live range splitting
768 GDB can now effectively debug code for which GCC has performed live
769 range splitting as part of its optimization. See gdb/doc/LRS for
770 more details on the expected format of the stabs information.
774 GDB's support for the GNU Hurd, including thread debugging, has been
775 updated to work with current versions of the Hurd.
779 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
780 instruction set. ARM GDB automatically detects when Thumb
781 instructions are in use, and adjusts disassembly and backtracing
786 GDB's MIPS target configurations now handle the MIP16 16-bit
791 GDB now includes support for overlays; if an executable has been
792 linked such that multiple sections are based at the same address, GDB
793 will decide which section to use for symbolic info. You can choose to
794 control the decision manually, using overlay commands, or implement
795 additional target-side support and use "overlay load-target" to bring
796 in the overlay mapping. Do "help overlay" for more detail.
800 The command "info symbol <address>" displays information about
801 the symbol at the specified address.
805 The standard remote protocol now includes an extension that allows
806 asynchronous collection and display of trace data. This requires
807 extensive support in the target-side debugging stub. Tracing mode
808 includes a new interaction mode in GDB and new commands: see the
809 file tracepoint.c for more details.
813 Configurations for embedded MIPS now include a simulator contributed
814 by Cygnus Solutions. The simulator supports the instruction sets
815 of most MIPS variants.
819 Sparc configurations may now include the ERC32 simulator contributed
820 by the European Space Agency. The simulator is not built into
821 Sparc targets by default; configure with --enable-sim to include it.
825 For target configurations that may include multiple variants of a
826 basic architecture (such as MIPS and SH), you may now set the
827 architecture explicitly. "set arch" sets, "info arch" lists
828 the possible architectures.
830 *** Changes in GDB-4.16:
832 * New native configurations
834 Windows 95, x86 Windows NT i[345]86-*-cygwin32
835 M68K NetBSD m68k-*-netbsd*
836 PowerPC AIX 4.x powerpc-*-aix*
837 PowerPC MacOS powerpc-*-macos*
838 PowerPC Windows NT powerpcle-*-cygwin32
839 RS/6000 AIX 4.x rs6000-*-aix4*
843 ARM with RDP protocol arm-*-*
844 I960 with MON960 i960-*-coff
845 MIPS VxWorks mips*-*-vxworks*
846 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
847 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
849 Matra Sparclet sparclet-*-*
853 The powerpc-eabi configuration now includes the PSIM simulator,
854 contributed by Andrew Cagney, with assistance from Mike Meissner.
855 PSIM is a very elaborate model of the PowerPC, including not only
856 basic instruction set execution, but also details of execution unit
857 performance and I/O hardware. See sim/ppc/README for more details.
861 GDB now works with Solaris 2.5.
863 * Windows 95/NT native
865 GDB will now work as a native debugger on Windows 95 and Windows NT.
866 To build it from source, you must use the "gnu-win32" environment,
867 which uses a DLL to emulate enough of Unix to run the GNU tools.
868 Further information, binaries, and sources are available at
869 ftp.cygnus.com, under pub/gnu-win32.
871 * dont-repeat command
873 If a user-defined command includes the command `dont-repeat', then the
874 command will not be repeated if the user just types return. This is
875 useful if the command is time-consuming to run, so that accidental
876 extra keystrokes don't run the same command many times.
878 * Send break instead of ^C
880 The standard remote protocol now includes an option to send a break
881 rather than a ^C to the target in order to interrupt it. By default,
882 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
884 * Remote protocol timeout
886 The standard remote protocol includes a new variable `remotetimeout'
887 that allows you to set the number of seconds before GDB gives up trying
888 to read from the target. The default value is 2.
890 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
892 By default GDB will automatically keep track of objects as they are
893 loaded and unloaded by the dynamic linker. By using the command `set
894 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
895 when shared library events occur, thus allowing you to set breakpoints
896 in shared libraries which are explicitly loaded by the inferior.
898 Note this feature does not work on hpux8. On hpux9 you must link
899 /usr/lib/end.o into your program. This feature should work
900 automatically on hpux10.
902 * Irix 5.x hardware watchpoint support
904 Irix 5 configurations now support the use of hardware watchpoints.
906 * Mips protocol "SYN garbage limit"
908 When debugging a Mips target using the `target mips' protocol, you
909 may set the number of characters that GDB will ignore by setting
910 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
911 every character. The default value is 1050.
913 * Recording and replaying remote debug sessions
915 If you set `remotelogfile' to the name of a file, gdb will write to it
916 a recording of a remote debug session. This recording may then be
917 replayed back to gdb using "gdbreplay". See gdbserver/README for
918 details. This is useful when you have a problem with GDB while doing
919 remote debugging; you can make a recording of the session and send it
920 to someone else, who can then recreate the problem.
922 * Speedups for remote debugging
924 GDB includes speedups for downloading and stepping MIPS systems using
925 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
926 and more efficient S-record downloading.
928 * Memory use reductions and statistics collection
930 GDB now uses less memory and reports statistics about memory usage.
931 Try the `maint print statistics' command, for example.
933 *** Changes in GDB-4.15:
937 The symbol reader for AIX GDB now uses partial symbol tables. This
938 can greatly improve startup time, especially for large executables.
940 * Remote targets use caching
942 Remote targets now use a data cache to speed up communication with the
943 remote side. The data cache could lead to incorrect results because
944 it doesn't know about volatile variables, thus making it impossible to
945 debug targets which use memory mapped I/O devices. `set remotecache
946 off' turns the the data cache off.
948 * Remote targets may have threads
950 The standard remote protocol now includes support for multiple threads
951 in the target system, using new protocol commands 'H' and 'T'. See
952 gdb/remote.c for details.
956 If GDB is configured with `--enable-netrom', then it will include
957 support for the NetROM ROM emulator from XLNT Designs. The NetROM
958 acts as though it is a bank of ROM on the target board, but you can
959 write into it over the network. GDB's support consists only of
960 support for fast loading into the emulated ROM; to debug, you must use
961 another protocol, such as standard remote protocol. The usual
962 sequence is something like
964 target nrom <netrom-hostname>
966 target remote <netrom-hostname>:1235
970 GDB now includes support for the Apple Macintosh, as a host only. It
971 may be run as either an MPW tool or as a standalone application, and
972 it can debug through the serial port. All the usual GDB commands are
973 available, but to the target command, you must supply "serial" as the
974 device type instead of "/dev/ttyXX". See mpw-README in the main
975 directory for more information on how to build. The MPW configuration
976 scripts */mpw-config.in support only a few targets, and only the
977 mips-idt-ecoff target has been tested.
981 GDB configuration now uses autoconf. This is not user-visible,
982 but does simplify configuration and building.
986 GDB now supports hpux10.
988 *** Changes in GDB-4.14:
990 * New native configurations
992 x86 FreeBSD i[345]86-*-freebsd
993 x86 NetBSD i[345]86-*-netbsd
994 NS32k NetBSD ns32k-*-netbsd
995 Sparc NetBSD sparc-*-netbsd
999 A29K VxWorks a29k-*-vxworks
1000 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1001 CPU32 EST-300 emulator m68*-*-est*
1002 PowerPC ELF powerpc-*-elf
1005 * Alpha OSF/1 support for procfs
1007 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1008 possible to attach to running processes. As the mounting of the /proc
1009 filesystem is optional on the Alpha, GDB automatically determines
1010 the availability of /proc during startup. This can lead to problems
1011 if /proc is unmounted after GDB has been started.
1013 * Arguments to user-defined commands
1015 User commands may accept up to 10 arguments separated by whitespace.
1016 Arguments are accessed within the user command via $arg0..$arg9. A
1019 print $arg0 + $arg1 + $arg2
1021 To execute the command use:
1024 Defines the command "adder" which prints the sum of its three arguments.
1025 Note the arguments are text substitutions, so they may reference variables,
1026 use complex expressions, or even perform inferior function calls.
1028 * New `if' and `while' commands
1030 This makes it possible to write more sophisticated user-defined
1031 commands. Both commands take a single argument, which is the
1032 expression to evaluate, and must be followed by the commands to
1033 execute, one per line, if the expression is nonzero, the list being
1034 terminated by the word `end'. The `if' command list may include an
1035 `else' word, which causes the following commands to be executed only
1036 if the expression is zero.
1038 * Fortran source language mode
1040 GDB now includes partial support for Fortran 77. It will recognize
1041 Fortran programs and can evaluate a subset of Fortran expressions, but
1042 variables and functions may not be handled correctly. GDB will work
1043 with G77, but does not yet know much about symbols emitted by other
1046 * Better HPUX support
1048 Most debugging facilities now work on dynamic executables for HPPAs
1049 running hpux9 or later. You can attach to running dynamically linked
1050 processes, but by default the dynamic libraries will be read-only, so
1051 for instance you won't be able to put breakpoints in them. To change
1052 that behavior do the following before running the program:
1058 This will cause the libraries to be mapped private and read-write.
1059 To revert to the normal behavior, do this:
1065 You cannot set breakpoints or examine data in the library until after
1066 the library is loaded if the function/data symbols do not have
1069 GDB can now also read debug symbols produced by the HP C compiler on
1070 HPPAs (sorry, no C++, Fortran or 68k support).
1072 * Target byte order now dynamically selectable
1074 You can choose which byte order to use with a target system, via the
1075 commands "set endian big" and "set endian little", and you can see the
1076 current setting by using "show endian". You can also give the command
1077 "set endian auto", in which case GDB will use the byte order
1078 associated with the executable. Currently, only embedded MIPS
1079 configurations support dynamic selection of target byte order.
1081 * New DOS host serial code
1083 This version uses DPMI interrupts to handle buffered I/O, so you
1084 no longer need to run asynctsr when debugging boards connected to
1087 *** Changes in GDB-4.13:
1089 * New "complete" command
1091 This lists all the possible completions for the rest of the line, if it
1092 were to be given as a command itself. This is intended for use by emacs.
1094 * Trailing space optional in prompt
1096 "set prompt" no longer adds a space for you after the prompt you set. This
1097 allows you to set a prompt which ends in a space or one that does not.
1099 * Breakpoint hit counts
1101 "info break" now displays a count of the number of times the breakpoint
1102 has been hit. This is especially useful in conjunction with "ignore"; you
1103 can ignore a large number of breakpoint hits, look at the breakpoint info
1104 to see how many times the breakpoint was hit, then run again, ignoring one
1105 less than that number, and this will get you quickly to the last hit of
1108 * Ability to stop printing at NULL character
1110 "set print null-stop" will cause GDB to stop printing the characters of
1111 an array when the first NULL is encountered. This is useful when large
1112 arrays actually contain only short strings.
1114 * Shared library breakpoints
1116 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1117 breakpoints in shared libraries before the executable is run.
1119 * Hardware watchpoints
1121 There is a new hardware breakpoint for the watch command for sparclite
1122 targets. See gdb/sparclite/hw_breakpoint.note.
1124 Hardware watchpoints are also now supported under GNU/Linux.
1128 Annotations have been added. These are for use with graphical interfaces,
1129 and are still experimental. Currently only gdba.el uses these.
1131 * Improved Irix 5 support
1133 GDB now works properly with Irix 5.2.
1135 * Improved HPPA support
1137 GDB now works properly with the latest GCC and GAS.
1139 * New native configurations
1141 Sequent PTX4 i[34]86-sequent-ptx4
1142 HPPA running OSF/1 hppa*-*-osf*
1143 Atari TT running SVR4 m68*-*-sysv4*
1144 RS/6000 LynxOS rs6000-*-lynxos*
1148 OS/9000 i[34]86-*-os9k
1149 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1152 * Hitachi SH7000 and E7000-PC ICE support
1154 There is now support for communicating with the Hitachi E7000-PC ICE.
1155 This is available automatically when GDB is configured for the SH.
1159 As usual, a variety of small fixes and improvements, both generic
1160 and configuration-specific. See the ChangeLog for more detail.
1162 *** Changes in GDB-4.12:
1164 * Irix 5 is now supported
1168 GDB-4.12 on the HPPA has a number of changes which make it unable
1169 to debug the output from the currently released versions of GCC and
1170 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1171 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1172 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1175 *** Changes in GDB-4.11:
1177 * User visible changes:
1181 The "set remotedebug" option is now consistent between the mips remote
1182 target, remote targets using the gdb-specific protocol, UDI (AMD's
1183 debug protocol for the 29k) and the 88k bug monitor. It is now an
1184 integer specifying a debug level (normally 0 or 1, but 2 means more
1185 debugging info for the mips target).
1187 * DEC Alpha native support
1189 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1190 debug info, but GDB works fairly well with the DEC compiler and should
1191 work with a future GCC release. See the README file for a few
1192 Alpha-specific notes.
1194 * Preliminary thread implementation
1196 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1198 * LynxOS native and target support for 386
1200 This release has been hosted on LynxOS 2.2, and also can be configured
1201 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1204 * Improvements in C++ mangling/demangling.
1206 This release has much better g++ debugging, specifically in name
1207 mangling/demangling, virtual function calls, print virtual table,
1208 call methods, ...etc.
1210 *** Changes in GDB-4.10:
1212 * User visible changes:
1214 Remote debugging using the GDB-specific (`target remote') protocol now
1215 supports the `load' command. This is only useful if you have some
1216 other way of getting the stub to the target system, and you can put it
1217 somewhere in memory where it won't get clobbered by the download.
1219 Filename completion now works.
1221 When run under emacs mode, the "info line" command now causes the
1222 arrow to point to the line specified. Also, "info line" prints
1223 addresses in symbolic form (as well as hex).
1225 All vxworks based targets now support a user settable option, called
1226 vxworks-timeout. This option represents the number of seconds gdb
1227 should wait for responses to rpc's. You might want to use this if
1228 your vxworks target is, perhaps, a slow software simulator or happens
1229 to be on the far side of a thin network line.
1233 This release contains support for using a DEC alpha as a GDB host for
1234 cross debugging. Native alpha debugging is not supported yet.
1237 *** Changes in GDB-4.9:
1241 This is the first GDB release which is accompanied by a matching testsuite.
1242 The testsuite requires installation of dejagnu, which should be available
1243 via ftp from most sites that carry GNU software.
1247 'Cfront' style demangling has had its name changed to 'ARM' style, to
1248 emphasize that it was written from the specifications in the C++ Annotated
1249 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1250 disclaimers, it still generated too much confusion with users attempting to
1251 use gdb with AT&T cfront.
1255 GDB now uses a standard remote interface to a simulator library.
1256 So far, the library contains simulators for the Zilog Z8001/2, the
1257 Hitachi H8/300, H8/500 and Super-H.
1259 * New targets supported
1261 H8/300 simulator h8300-hitachi-hms or h8300hms
1262 H8/500 simulator h8500-hitachi-hms or h8500hms
1263 SH simulator sh-hitachi-hms or sh
1264 Z8000 simulator z8k-zilog-none or z8ksim
1265 IDT MIPS board over serial line mips-idt-ecoff
1267 Cross-debugging to GO32 targets is supported. It requires a custom
1268 version of the i386-stub.c module which is integrated with the
1269 GO32 memory extender.
1271 * New remote protocols
1273 MIPS remote debugging protocol.
1275 * New source languages supported
1277 This version includes preliminary support for Chill, a Pascal like language
1278 used by telecommunications companies. Chill support is also being integrated
1279 into the GNU compiler, but we don't know when it will be publically available.
1282 *** Changes in GDB-4.8:
1284 * HP Precision Architecture supported
1286 GDB now supports HP PA-RISC machines running HPUX. A preliminary
1287 version of this support was available as a set of patches from the
1288 University of Utah. GDB does not support debugging of programs
1289 compiled with the HP compiler, because HP will not document their file
1290 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
1291 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
1293 Many problems in the preliminary version have been fixed.
1295 * Faster and better demangling
1297 We have improved template demangling and fixed numerous bugs in the GNU style
1298 demangler. It can now handle type modifiers such as `static' or `const'. Wide
1299 character types (wchar_t) are now supported. Demangling of each symbol is now
1300 only done once, and is cached when the symbol table for a file is read in.
1301 This results in a small increase in memory usage for C programs, a moderate
1302 increase in memory usage for C++ programs, and a fantastic speedup in
1305 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
1306 from the specifications in the Annotated Reference Manual, which AT&T's
1307 compiler does not actually implement.
1309 * G++ multiple inheritance compiler problem
1311 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
1312 inheritance lattices was reworked to properly discover ambiguities. We
1313 recently found an example which causes this new algorithm to fail in a
1314 very subtle way, producing bad debug information for those classes.
1315 The file 'gcc.patch' (in this directory) can be applied to gcc to
1316 circumvent the problem. A future GCC release will contain a complete
1319 The previous G++ debug info problem (mentioned below for the gdb-4.7
1320 release) is fixed in gcc version 2.3.2.
1322 * Improved configure script
1324 The `configure' script will now attempt to guess your system type if
1325 you don't supply a host system type. The old scheme of supplying a
1326 host system triplet is preferable over using this. All the magic is
1327 done in the new `config.guess' script. Examine it for details.
1329 We have also brought our configure script much more in line with the FSF's
1330 version. It now supports the --with-xxx options. In particular,
1331 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
1332 The resulting GDB will not be able to read arbitrary object file formats --
1333 only the format ``expected'' to be used on the configured target system.
1334 We hope to make this the default in a future release.
1336 * Documentation improvements
1338 There's new internal documentation on how to modify GDB, and how to
1339 produce clean changes to the code. We implore people to read it
1340 before submitting changes.
1342 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
1343 M4 macros. The new texinfo.tex is provided in this release. Pre-built
1344 `info' files are also provided. To build `info' files from scratch,
1345 you will need the latest `makeinfo' release, which will be available in
1346 a future texinfo-X.Y release.
1348 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
1349 We're not sure exactly which versions have this problem, but it has
1350 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
1351 or better. If that isn't possible, there is a patch in
1352 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
1353 around this problem.
1357 GDB now supports array constants that can be used in expressions typed in by
1358 the user. The syntax is `{element, element, ...}'. Ie: you can now type
1359 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
1362 The new directory `gdb/sparclite' contains a program that demonstrates
1363 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
1365 * New native hosts supported
1367 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
1368 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
1370 * New targets supported
1372 AMD 29k family via UDI a29k-amd-udi or udi29k
1374 * New file formats supported
1376 BFD now supports reading HP/PA-RISC executables (SOM file format?),
1377 HPUX core files, and SCO 3.2v2 core files.
1381 Attaching to processes now works again; thanks for the many bug reports.
1383 We have also stomped on a bunch of core dumps caused by
1384 printf_filtered("%s") problems.
1386 We eliminated a copyright problem on the rpc and ptrace header files
1387 for VxWorks, which was discovered at the last minute during the 4.7
1388 release. You should now be able to build a VxWorks GDB.
1390 You can now interrupt gdb while an attached process is running. This
1391 will cause the attached process to stop, and give control back to GDB.
1393 We fixed problems caused by using too many file descriptors
1394 for reading symbols from object files and libraries. This was
1395 especially a problem for programs that used many (~100) shared
1398 The `step' command now only enters a subroutine if there is line number
1399 information for the subroutine. Otherwise it acts like the `next'
1400 command. Previously, `step' would enter subroutines if there was
1401 any debugging information about the routine. This avoids problems
1402 when using `cc -g1' on MIPS machines.
1404 * Internal improvements
1406 GDB's internal interfaces have been improved to make it easier to support
1407 debugging of multiple languages in the future.
1409 GDB now uses a common structure for symbol information internally.
1410 Minimal symbols (derived from linkage symbols in object files), partial
1411 symbols (from a quick scan of debug information), and full symbols
1412 contain a common subset of information, making it easier to write
1413 shared code that handles any of them.
1415 * New command line options
1417 We now accept --silent as an alias for --quiet.
1421 The memory-mapped-malloc library is now licensed under the GNU Library
1422 General Public License.
1424 *** Changes in GDB-4.7:
1426 * Host/native/target split
1428 GDB has had some major internal surgery to untangle the support for
1429 hosts and remote targets. Now, when you configure GDB for a remote
1430 target, it will no longer load in all of the support for debugging
1431 local programs on the host. When fully completed and tested, this will
1432 ensure that arbitrary host/target combinations are possible.
1434 The primary conceptual shift is to separate the non-portable code in
1435 GDB into three categories. Host specific code is required any time GDB
1436 is compiled on that host, regardless of the target. Target specific
1437 code relates to the peculiarities of the target, but can be compiled on
1438 any host. Native specific code is everything else: it can only be
1439 built when the host and target are the same system. Child process
1440 handling and core file support are two common `native' examples.
1442 GDB's use of /proc for controlling Unix child processes is now cleaner.
1443 It has been split out into a single module under the `target_ops' vector,
1444 plus two native-dependent functions for each system that uses /proc.
1446 * New hosts supported
1448 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
1449 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1450 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
1452 * New targets supported
1454 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
1455 68030 and CPU32 m68030-*-*, m68332-*-*
1457 * New native hosts supported
1459 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1460 (386bsd is not well tested yet)
1461 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
1463 * New file formats supported
1465 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
1466 supports reading of `a.out.adobe' object files, which are an a.out
1467 format extended with minimal information about multiple sections.
1471 `show copying' is the same as the old `info copying'.
1472 `show warranty' is the same as `info warrantee'.
1473 These were renamed for consistency. The old commands continue to work.
1475 `info handle' is a new alias for `info signals'.
1477 You can now define pre-command hooks, which attach arbitrary command
1478 scripts to any command. The commands in the hook will be executed
1479 prior to the user's command. You can also create a hook which will be
1480 executed whenever the program stops. See gdb.texinfo.
1484 We now deal with Cfront style name mangling, and can even extract type
1485 info from mangled symbols. GDB can automatically figure out which
1486 symbol mangling style your C++ compiler uses.
1488 Calling of methods and virtual functions has been improved as well.
1492 The crash that occured when debugging Sun Ansi-C compiled binaries is
1493 fixed. This was due to mishandling of the extra N_SO stabs output
1496 We also finally got Ultrix 4.2 running in house, and fixed core file
1497 support, with help from a dozen people on the net.
1499 John M. Farrell discovered that the reason that single-stepping was so
1500 slow on all of the Mips based platforms (primarily SGI and DEC) was
1501 that we were trying to demangle and lookup a symbol used for internal
1502 purposes on every instruction that was being stepped through. Changing
1503 the name of that symbol so that it couldn't be mistaken for a C++
1504 mangled symbol sped things up a great deal.
1506 Rich Pixley sped up symbol lookups in general by getting much smarter
1507 about when C++ symbol mangling is necessary. This should make symbol
1508 completion (TAB on the command line) much faster. It's not as fast as
1509 we'd like, but it's significantly faster than gdb-4.6.
1513 A new user controllable variable 'call_scratch_address' can
1514 specify the location of a scratch area to be used when GDB
1515 calls a function in the target. This is necessary because the
1516 usual method of putting the scratch area on the stack does not work
1517 in systems that have separate instruction and data spaces.
1519 We integrated changes to support the 29k UDI (Universal Debugger
1520 Interface), but discovered at the last minute that we didn't have all
1521 of the appropriate copyright paperwork. We are working with AMD to
1522 resolve this, and hope to have it available soon.
1526 We have sped up the remote serial line protocol, especially for targets
1527 with lots of registers. It now supports a new `expedited status' ('T')
1528 message which can be used in place of the existing 'S' status message.
1529 This allows the remote stub to send only the registers that GDB
1530 needs to make a quick decision about single-stepping or conditional
1531 breakpoints, eliminating the need to fetch the entire register set for
1532 each instruction being stepped through.
1534 The GDB remote serial protocol now implements a write-through cache for
1535 registers, only re-reading the registers if the target has run.
1537 There is also a new remote serial stub for SPARC processors. You can
1538 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
1539 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
1540 processor with a serial port.
1544 Configure.in files have become much easier to read and modify. A new
1545 `table driven' format makes it more obvious what configurations are
1546 supported, and what files each one uses.
1550 There is a new opcodes library which will eventually contain all of the
1551 disassembly routines and opcode tables. At present, it only contains
1552 Sparc and Z8000 routines. This will allow the assembler, debugger, and
1553 disassembler (binutils/objdump) to share these routines.
1555 The libiberty library is now copylefted under the GNU Library General
1556 Public License. This allows more liberal use, and was done so libg++
1557 can use it. This makes no difference to GDB, since the Library License
1558 grants all the rights from the General Public License.
1562 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
1563 reference to the stabs symbol info used by the debugger. It is (as far
1564 as we know) the only published document on this fascinating topic. We
1565 encourage you to read it, compare it to the stabs information on your
1566 system, and send improvements on the document in general (to
1567 bug-gdb@prep.ai.mit.edu).
1569 And, of course, many bugs have been fixed.
1572 *** Changes in GDB-4.6:
1574 * Better support for C++ function names
1576 GDB now accepts as input the "demangled form" of C++ overloaded function
1577 names and member function names, and can do command completion on such names
1578 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
1579 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
1580 Make use of command completion, it is your friend.
1582 GDB also now accepts a variety of C++ mangled symbol formats. They are
1583 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
1584 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
1585 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
1586 for the list of formats.
1588 * G++ symbol mangling problem
1590 Recent versions of gcc have a bug in how they emit debugging information for
1591 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
1592 directory) can be applied to gcc to fix the problem. Alternatively, if you
1593 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
1594 usual symptom is difficulty with setting breakpoints on methods. GDB complains
1595 about the method being non-existent. (We believe that version 2.2.2 of GCC has
1598 * New 'maintenance' command
1600 All of the commands related to hacking GDB internals have been moved out of
1601 the main command set, and now live behind the 'maintenance' command. This
1602 can also be abbreviated as 'mt'. The following changes were made:
1604 dump-me -> maintenance dump-me
1605 info all-breakpoints -> maintenance info breakpoints
1606 printmsyms -> maintenance print msyms
1607 printobjfiles -> maintenance print objfiles
1608 printpsyms -> maintenance print psymbols
1609 printsyms -> maintenance print symbols
1611 The following commands are new:
1613 maintenance demangle Call internal GDB demangler routine to
1614 demangle a C++ link name and prints the result.
1615 maintenance print type Print a type chain for a given symbol
1617 * Change to .gdbinit file processing
1619 We now read the $HOME/.gdbinit file before processing the argv arguments
1620 (e.g. reading symbol files or core files). This allows global parameters to
1621 be set, which will apply during the symbol reading. The ./.gdbinit is still
1622 read after argv processing.
1624 * New hosts supported
1626 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
1628 GNU/Linux support i386-unknown-linux or linux
1630 We are also including code to support the HP/PA running BSD and HPUX. This
1631 is almost guaranteed not to work, as we didn't have time to test or build it
1632 for this release. We are including it so that the more adventurous (or
1633 masochistic) of you can play with it. We also had major problems with the
1634 fact that the compiler that we got from HP doesn't support the -g option.
1637 * New targets supported
1639 Hitachi H8/300 h8300-hitachi-hms or h8300hms
1641 * More smarts about finding #include files
1643 GDB now remembers the compilation directory for all include files, and for
1644 all files from which C is generated (like yacc and lex sources). This
1645 greatly improves GDB's ability to find yacc/lex sources, and include files,
1646 especially if you are debugging your program from a directory different from
1647 the one that contains your sources.
1649 We also fixed a bug which caused difficulty with listing and setting
1650 breakpoints in include files which contain C code. (In the past, you had to
1651 try twice in order to list an include file that you hadn't looked at before.)
1653 * Interesting infernals change
1655 GDB now deals with arbitrary numbers of sections, where the symbols for each
1656 section must be relocated relative to that section's landing place in the
1657 target's address space. This work was needed to support ELF with embedded
1658 stabs used by Solaris-2.0.
1660 * Bug fixes (of course!)
1662 There have been loads of fixes for the following things:
1663 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
1664 i960, stabs, DOS(GO32), procfs, etc...
1666 See the ChangeLog for details.
1668 *** Changes in GDB-4.5:
1670 * New machines supported (host and target)
1672 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
1674 SGI Irix-4.x mips-sgi-irix4 or iris4
1676 * New malloc package
1678 GDB now uses a new memory manager called mmalloc, based on gmalloc.
1679 Mmalloc is capable of handling mutiple heaps of memory. It is also
1680 capable of saving a heap to a file, and then mapping it back in later.
1681 This can be used to greatly speedup the startup of GDB by using a
1682 pre-parsed symbol table which lives in a mmalloc managed heap. For
1683 more details, please read mmalloc/mmalloc.texi.
1687 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
1688 'help info proc' for details.
1690 * MIPS ecoff symbol table format
1692 The code that reads MIPS symbol table format is now supported on all hosts.
1693 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
1696 * File name changes for MS-DOS
1698 Many files in the config directories have been renamed to make it easier to
1699 support GDB on MS-DOSe systems (which have very restrictive file name
1700 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
1701 environment) is close to working but has some remaining problems. Note
1702 that debugging of DOS programs is not supported, due to limitations
1703 in the ``operating system'', but it can be used to host cross-debugging.
1705 * Cross byte order fixes
1707 Many fixes have been made to support cross debugging of Sparc and MIPS
1708 targets from hosts whose byte order differs.
1710 * New -mapped and -readnow options
1712 If memory-mapped files are available on your system through the 'mmap'
1713 system call, you can use the -mapped option on the `file' or
1714 `symbol-file' commands to cause GDB to write the symbols from your
1715 program into a reusable file. If the program you are debugging is
1716 called `/path/fred', the mapped symbol file will be `./fred.syms'.
1717 Future GDB debugging sessions will notice the presence of this file,
1718 and will quickly map in symbol information from it, rather than reading
1719 the symbol table from the executable program. Using the '-mapped'
1720 option in a GDB `file' or `symbol-file' command has the same effect as
1721 starting GDB with the '-mapped' command-line option.
1723 You can cause GDB to read the entire symbol table immediately by using
1724 the '-readnow' option with any of the commands that load symbol table
1725 information (or on the GDB command line). This makes the command
1726 slower, but makes future operations faster.
1728 The -mapped and -readnow options are typically combined in order to
1729 build a `fred.syms' file that contains complete symbol information.
1730 A simple GDB invocation to do nothing but build a `.syms' file for future
1733 gdb -batch -nx -mapped -readnow programname
1735 The `.syms' file is specific to the host machine on which GDB is run.
1736 It holds an exact image of GDB's internal symbol table. It cannot be
1737 shared across multiple host platforms.
1739 * longjmp() handling
1741 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
1742 siglongjmp() without losing control. This feature has not yet been ported to
1743 all systems. It currently works on many 386 platforms, all MIPS-based
1744 platforms (SGI, DECstation, etc), and Sun3/4.
1748 Preliminary work has been put in to support the new Solaris OS from Sun. At
1749 this time, it can control and debug processes, but it is not capable of
1754 As always, many many bug fixes. The major areas were with g++, and mipsread.
1755 People using the MIPS-based platforms should experience fewer mysterious
1756 crashes and trashed symbol tables.
1758 *** Changes in GDB-4.4:
1760 * New machines supported (host and target)
1762 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1764 BSD Reno on Vax vax-dec-bsd
1765 Ultrix on Vax vax-dec-ultrix
1767 * New machines supported (target)
1769 AMD 29000 embedded, using EBMON a29k-none-none
1773 GDB continues to improve its handling of C++. `References' work better.
1774 The demangler has also been improved, and now deals with symbols mangled as
1775 per the Annotated C++ Reference Guide.
1777 GDB also now handles `stabs' symbol information embedded in MIPS
1778 `ecoff' symbol tables. Since the ecoff format was not easily
1779 extensible to handle new languages such as C++, this appeared to be a
1780 good way to put C++ debugging info into MIPS binaries. This option
1781 will be supported in the GNU C compiler, version 2, when it is
1784 * New features for SVR4
1786 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
1787 shared libraries. Debugging dynamically linked programs should present
1788 only minor differences from debugging statically linked programs.
1790 The `info proc' command will print out information about any process
1791 on an SVR4 system (including the one you are debugging). At the moment,
1792 it prints the address mappings of the process.
1794 If you bring up GDB on another SVR4 system, please send mail to
1795 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
1797 * Better dynamic linking support in SunOS
1799 Reading symbols from shared libraries which contain debugging symbols
1800 now works properly. However, there remain issues such as automatic
1801 skipping of `transfer vector' code during function calls, which
1802 make it harder to debug code in a shared library, than to debug the
1803 same code linked statically.
1807 GDB is now using the latest `getopt' routines from the FSF. This
1808 version accepts the -- prefix for options with long names. GDB will
1809 continue to accept the old forms (-option and +option) as well.
1810 Various single letter abbreviations for options have been explicity
1811 added to the option table so that they won't get overshadowed in the
1812 future by other options that begin with the same letter.
1816 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
1817 Many assorted bugs have been handled. Many more remain to be handled.
1818 See the various ChangeLog files (primarily in gdb and bfd) for details.
1821 *** Changes in GDB-4.3:
1823 * New machines supported (host and target)
1825 Amiga 3000 running Amix m68k-cbm-svr4 or amix
1826 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
1827 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
1829 * Almost SCO Unix support
1831 We had hoped to support:
1832 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1833 (except for core file support), but we discovered very late in the release
1834 that it has problems with process groups that render gdb unusable. Sorry
1835 about that. I encourage people to fix it and post the fixes.
1837 * Preliminary ELF and DWARF support
1839 GDB can read ELF object files on System V Release 4, and can handle
1840 debugging records for C, in DWARF format, in ELF files. This support
1841 is preliminary. If you bring up GDB on another SVR4 system, please
1842 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
1847 GDB now uses the latest `readline' library. One user-visible change
1848 is that two tabs will list possible command completions, which previously
1849 required typing M-? (meta-question mark, or ESC ?).
1853 The `stepi' bug that many of you noticed has been squashed.
1854 Many bugs in C++ have been handled. Many more remain to be handled.
1855 See the various ChangeLog files (primarily in gdb and bfd) for details.
1857 * State of the MIPS world (in case you wondered):
1859 GDB can understand the symbol tables emitted by the compilers
1860 supplied by most vendors of MIPS-based machines, including DEC. These
1861 symbol tables are in a format that essentially nobody else uses.
1863 Some versions of gcc come with an assembler post-processor called
1864 mips-tfile. This program is required if you want to do source-level
1865 debugging of gcc-compiled programs. I believe FSF does not ship
1866 mips-tfile with gcc version 1, but it will eventually come with gcc
1869 Debugging of g++ output remains a problem. g++ version 1.xx does not
1870 really support it at all. (If you're lucky, you should be able to get
1871 line numbers and stack traces to work, but no parameters or local
1872 variables.) With some work it should be possible to improve the
1875 When gcc version 2 is released, you will have somewhat better luck.
1876 However, even then you will get confusing results for inheritance and
1879 We will eventually provide full debugging of g++ output on
1880 DECstations. This will probably involve some kind of stabs-in-ecoff
1881 encapulation, but the details have not been worked out yet.
1884 *** Changes in GDB-4.2:
1886 * Improved configuration
1888 Only one copy of `configure' exists now, and it is not self-modifying.
1889 Porting BFD is simpler.
1893 The `step' and `next' commands now only stop at the first instruction
1894 of a source line. This prevents the multiple stops that used to occur
1895 in switch statements, for-loops, etc. `Step' continues to stop if a
1896 function that has debugging information is called within the line.
1900 Lots of small bugs fixed. More remain.
1902 * New host supported (not target)
1904 Intel 386 PC clone running Mach i386-none-mach
1907 *** Changes in GDB-4.1:
1909 * Multiple source language support
1911 GDB now has internal scaffolding to handle several source languages.
1912 It determines the type of each source file from its filename extension,
1913 and will switch expression parsing and number formatting to match the
1914 language of the function in the currently selected stack frame.
1915 You can also specifically set the language to be used, with
1916 `set language c' or `set language modula-2'.
1920 GDB now has preliminary support for the GNU Modula-2 compiler,
1921 currently under development at the State University of New York at
1922 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
1923 continue through the fall of 1991 and into 1992.
1925 Other Modula-2 compilers are currently not supported, and attempting to
1926 debug programs compiled with them will likely result in an error as the
1927 symbol table is read. Feel free to work on it, though!
1929 There are hooks in GDB for strict type checking and range checking,
1930 in the `Modula-2 philosophy', but they do not currently work.
1934 GDB can now write to executable and core files (e.g. patch
1935 a variable's value). You must turn this switch on, specify
1936 the file ("exec foo" or "core foo"), *then* modify it, e.g.
1937 by assigning a new value to a variable. Modifications take
1940 * Automatic SunOS shared library reading
1942 When you run your program, GDB automatically determines where its
1943 shared libraries (if any) have been loaded, and reads their symbols.
1944 The `share' command is no longer needed. This also works when
1945 examining core files.
1949 You can specify the number of lines that the `list' command shows.
1952 * New machines supported (host and target)
1954 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
1955 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
1956 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
1958 * New hosts supported (not targets)
1960 IBM RT/PC: romp-ibm-aix or rtpc
1962 * New targets supported (not hosts)
1964 AMD 29000 embedded with COFF a29k-none-coff
1965 AMD 29000 embedded with a.out a29k-none-aout
1966 Ultracomputer remote kernel debug a29k-nyu-kern
1968 * New remote interfaces
1974 *** Changes in GDB-4.0:
1978 Wide output is wrapped at good places to make the output more readable.
1980 Gdb now supports cross-debugging from a host machine of one type to a
1981 target machine of another type. Communication with the target system
1982 is over serial lines. The ``target'' command handles connecting to the
1983 remote system; the ``load'' command will download a program into the
1984 remote system. Serial stubs for the m68k and i386 are provided. Gdb
1985 also supports debugging of realtime processes running under VxWorks,
1986 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
1987 stub on the target system.
1989 New CPUs supported include the AMD 29000 and Intel 960.
1991 GDB now reads object files and symbol tables via a ``binary file''
1992 library, which allows a single copy of GDB to debug programs of multiple
1993 object file types such as a.out and coff.
1995 There is now a GDB reference card in "doc/refcard.tex". (Make targets
1996 refcard.dvi and refcard.ps are available to format it).
1999 * Control-Variable user interface simplified
2001 All variables that control the operation of the debugger can be set
2002 by the ``set'' command, and displayed by the ``show'' command.
2004 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2005 ``Show prompt'' produces the response:
2006 Gdb's prompt is new-gdb=>.
2008 What follows are the NEW set commands. The command ``help set'' will
2009 print a complete list of old and new set commands. ``help set FOO''
2010 will give a longer description of the variable FOO. ``show'' will show
2011 all of the variable descriptions and their current settings.
2013 confirm on/off: Enables warning questions for operations that are
2014 hard to recover from, e.g. rerunning the program while
2015 it is already running. Default is ON.
2017 editing on/off: Enables EMACS style command line editing
2018 of input. Previous lines can be recalled with
2019 control-P, the current line can be edited with control-B,
2020 you can search for commands with control-R, etc.
2023 history filename NAME: NAME is where the gdb command history
2024 will be stored. The default is .gdb_history,
2025 or the value of the environment variable
2028 history size N: The size, in commands, of the command history. The
2029 default is 256, or the value of the environment variable
2032 history save on/off: If this value is set to ON, the history file will
2033 be saved after exiting gdb. If set to OFF, the
2034 file will not be saved. The default is OFF.
2036 history expansion on/off: If this value is set to ON, then csh-like
2037 history expansion will be performed on
2038 command line input. The default is OFF.
2040 radix N: Sets the default radix for input and output. It can be set
2041 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2042 in the current radix, so "set radix 10" is always a no-op.
2044 height N: This integer value is the number of lines on a page. Default
2045 is 24, the current `stty rows'' setting, or the ``li#''
2046 setting from the termcap entry matching the environment
2049 width N: This integer value is the number of characters on a line.
2050 Default is 80, the current `stty cols'' setting, or the ``co#''
2051 setting from the termcap entry matching the environment
2054 Note: ``set screensize'' is obsolete. Use ``set height'' and
2055 ``set width'' instead.
2057 print address on/off: Print memory addresses in various command displays,
2058 such as stack traces and structure values. Gdb looks
2059 more ``symbolic'' if you turn this off; it looks more
2060 ``machine level'' with it on. Default is ON.
2062 print array on/off: Prettyprint arrays. New convenient format! Default
2065 print demangle on/off: Print C++ symbols in "source" form if on,
2068 print asm-demangle on/off: Same, for assembler level printouts
2071 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2074 * Support for Epoch Environment.
2076 The epoch environment is a version of Emacs v18 with windowing. One
2077 new command, ``inspect'', is identical to ``print'', except that if you
2078 are running in the epoch environment, the value is printed in its own
2082 * Support for Shared Libraries
2084 GDB can now debug programs and core files that use SunOS shared libraries.
2085 Symbols from a shared library cannot be referenced
2086 before the shared library has been linked with the program (this
2087 happens after you type ``run'' and before the function main() is entered).
2088 At any time after this linking (including when examining core files
2089 from dynamically linked programs), gdb reads the symbols from each
2090 shared library when you type the ``sharedlibrary'' command.
2091 It can be abbreviated ``share''.
2093 sharedlibrary REGEXP: Load shared object library symbols for files
2094 matching a unix regular expression. No argument
2095 indicates to load symbols for all shared libraries.
2097 info sharedlibrary: Status of loaded shared libraries.
2102 A watchpoint stops execution of a program whenever the value of an
2103 expression changes. Checking for this slows down execution
2104 tremendously whenever you are in the scope of the expression, but is
2105 quite useful for catching tough ``bit-spreader'' or pointer misuse
2106 problems. Some machines such as the 386 have hardware for doing this
2107 more quickly, and future versions of gdb will use this hardware.
2109 watch EXP: Set a watchpoint (breakpoint) for an expression.
2111 info watchpoints: Information about your watchpoints.
2113 delete N: Deletes watchpoint number N (same as breakpoints).
2114 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2115 enable N: Re-enables watchpoint number N (same as breakpoints).
2118 * C++ multiple inheritance
2120 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2123 * C++ exception handling
2125 Gdb now supports limited C++ exception handling. Besides the existing
2126 ability to breakpoint on an exception handler, gdb can breakpoint on
2127 the raising of an exception (before the stack is peeled back to the
2130 catch FOO: If there is a FOO exception handler in the dynamic scope,
2131 set a breakpoint to catch exceptions which may be raised there.
2132 Multiple exceptions (``catch foo bar baz'') may be caught.
2134 info catch: Lists all exceptions which may be caught in the
2135 current stack frame.
2138 * Minor command changes
2140 The command ``call func (arg, arg, ...)'' now acts like the print
2141 command, except it does not print or save a value if the function's result
2142 is void. This is similar to dbx usage.
2144 The ``up'' and ``down'' commands now always print the frame they end up
2145 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2146 frames without printing.
2148 * New directory command
2150 'dir' now adds directories to the FRONT of the source search path.
2151 The path starts off empty. Source files that contain debug information
2152 about the directory in which they were compiled can be found even
2153 with an empty path; Sun CC and GCC include this information. If GDB can't
2154 find your source file in the current directory, type "dir .".
2156 * Configuring GDB for compilation
2158 For normal use, type ``./configure host''. See README or gdb.texinfo
2161 GDB now handles cross debugging. If you are remotely debugging between
2162 two different machines, type ``./configure host -target=targ''.
2163 Host is the machine where GDB will run; targ is the machine
2164 where the program that you are debugging will run.
projects / external / binutils.git / blob