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*
70 I960 with MON960 i960-*-coff
74 CHILL, a Pascal like language used by telecommunications companies.
76 * REMOVED configurations and files
78 AMD 29k family via UDI a29k-amd-udi, udi29k
79 A29K VxWorks a29k-*-vxworks
80 AMD 29000 embedded, using EBMON a29k-none-none
81 AMD 29000 embedded with COFF a29k-none-coff
82 AMD 29000 embedded with a.out a29k-none-aout
84 testsuite/gdb.hp/gdb.threads-hp/ directory
86 * New command "set max-user-call-depth <nnn>"
88 This command allows the user to limit the call depth of user-defined
89 commands. The default is 1024.
91 * Changes in FreeBSD/i386 native debugging.
93 Support for the "generate-core-file" has been added.
95 * New commands "dump", "append", and "restore".
97 These commands allow data to be copied from target memory
98 to a bfd-format or binary file (dump and append), and back
99 from a file into memory (restore).
101 * Improved "next/step" support on multi-processor Alpha Tru64.
103 The previous single-step mechanism could cause unpredictable problems,
104 including the random appearance of SIGSEGV or SIGTRAP signals. The use
105 of a software single-step mechanism prevents this.
107 *** Changes in GDB 5.2.1:
115 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
116 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
117 Fix, by Joel Brobecker imported from mainline.
119 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
120 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
121 Fix, by Fred Fish, imported from mainline.
123 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
124 Surprisingly enough, it works now.
125 By Michal Ludvig, imported from mainline.
127 i386 hardware watchpoint support:
128 avoid misses on second run for some targets.
129 By Pierre Muller, imported from mainline.
131 *** Changes in GDB 5.2:
133 * New command "set trust-readonly-sections on[off]".
135 This command is a hint that tells gdb that read-only sections
136 really are read-only (ie. that their contents will not change).
137 In this mode, gdb will go to the object file rather than the
138 target to read memory from read-only sections (such as ".text").
139 This can be a significant performance improvement on some
140 (notably embedded) targets.
142 * New command "generate-core-file" (or "gcore").
144 This new gdb command allows the user to drop a core file of the child
145 process state at any time. So far it's been implemented only for
146 GNU/Linux and Solaris, but should be relatively easily ported to other
147 hosts. Argument is core file name (defaults to core.<pid>).
149 * New command line option
151 GDB now accepts --pid or -p followed by a process id.
153 * Change in command line behavior -- corefiles vs. process ids.
155 There is a subtle behavior in the way in which GDB handles
156 command line arguments. The first non-flag argument is always
157 a program to debug, but the second non-flag argument may either
158 be a corefile or a process id. Previously, GDB would attempt to
159 open the second argument as a corefile, and if that failed, would
160 issue a superfluous error message and then attempt to attach it as
161 a process. Now, if the second argument begins with a non-digit,
162 it will be treated as a corefile. If it begins with a digit,
163 GDB will attempt to attach it as a process, and if no such process
164 is found, will then attempt to open it as a corefile.
166 * Changes in ARM configurations.
168 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
169 configuration is fully multi-arch.
171 * New native configurations
173 ARM NetBSD arm*-*-netbsd*
174 x86 OpenBSD i[3456]86-*-openbsd*
175 AMD x86-64 running GNU/Linux x86_64-*-linux-*
176 Sparc64 running FreeBSD sparc64-*-freebsd*
180 Sanyo XStormy16 xstormy16-elf
182 * OBSOLETE configurations and files
184 Configurations that have been declared obsolete in this release have
185 been commented out. Unless there is activity to revive these
186 configurations, the next release of GDB will have their sources
189 AMD 29k family via UDI a29k-amd-udi, udi29k
190 A29K VxWorks a29k-*-vxworks
191 AMD 29000 embedded, using EBMON a29k-none-none
192 AMD 29000 embedded with COFF a29k-none-coff
193 AMD 29000 embedded with a.out a29k-none-aout
195 testsuite/gdb.hp/gdb.threads-hp/ directory
197 * REMOVED configurations and files
199 TI TMS320C80 tic80-*-*
201 PowerPC Solaris powerpcle-*-solaris*
202 PowerPC Windows NT powerpcle-*-cygwin32
203 PowerPC Netware powerpc-*-netware*
204 Harris/CXUX m88k m88*-harris-cxux*
205 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
206 ns32k-utek-sysv* ns32k-utek-*
207 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
208 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
209 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
210 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
211 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
213 * Changes to command line processing
215 The new `--args' feature can be used to specify command-line arguments
216 for the inferior from gdb's command line.
218 * Changes to key bindings
220 There is a new `operate-and-get-next' function bound to `C-o'.
222 *** Changes in GDB 5.1.1
224 Fix compile problem on DJGPP.
226 Fix a problem with floating-point registers on the i386 being
229 Fix to stop GDB crashing on .debug_str debug info.
231 Numerous documentation fixes.
233 Numerous testsuite fixes.
235 *** Changes in GDB 5.1:
237 * New native configurations
239 Alpha FreeBSD alpha*-*-freebsd*
240 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
241 MIPS GNU/Linux mips*-*-linux*
242 MIPS SGI Irix 6.x mips*-sgi-irix6*
244 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
248 Motorola 68HC11 and 68HC12 m68hc11-elf
250 UltraSparc running GNU/Linux sparc64-*-linux*
252 * OBSOLETE configurations and files
254 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
255 Harris/CXUX m88k m88*-harris-cxux*
256 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
257 ns32k-utek-sysv* ns32k-utek-*
258 TI TMS320C80 tic80-*-*
260 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
261 PowerPC Solaris powerpcle-*-solaris*
262 PowerPC Windows NT powerpcle-*-cygwin32
263 PowerPC Netware powerpc-*-netware*
264 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
265 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
266 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
267 Apple Macintosh (MPW) host N/A
269 stuff.c (Program to stuff files into a specially prepared space in kdb)
270 kdb-start.c (Main loop for the standalone kernel debugger)
272 Configurations that have been declared obsolete in this release have
273 been commented out. Unless there is activity to revive these
274 configurations, the next release of GDB will have their sources
277 * REMOVED configurations and files
279 Altos 3068 m68*-altos-*
280 Convex c1-*-*, c2-*-*
282 ARM RISCix arm-*-* (as host)
286 * GDB has been converted to ISO C.
288 GDB's source code has been converted to ISO C. In particular, the
289 sources are fully protoized, and rely on standard headers being
294 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
296 * The MI enabled by default.
298 The new machine oriented interface (MI) introduced in GDB 5.0 has been
299 revised and enabled by default. Packages which use GDB as a debugging
300 engine behind a UI or another front end are encouraged to switch to
301 using the GDB/MI interface, instead of the old annotations interface
302 which is now deprecated.
304 * Support for debugging Pascal programs.
306 GDB now includes support for debugging Pascal programs. The following
307 main features are supported:
309 - Pascal-specific data types such as sets;
311 - automatic recognition of Pascal sources based on file-name
314 - Pascal-style display of data types, variables, and functions;
316 - a Pascal expression parser.
318 However, some important features are not yet supported.
320 - Pascal string operations are not supported at all;
322 - there are some problems with boolean types;
324 - Pascal type hexadecimal constants are not supported
325 because they conflict with the internal variables format;
327 - support for Pascal objects and classes is not full yet;
329 - unlike Pascal, GDB is case-sensitive for symbol names.
331 * Changes in completion.
333 Commands such as `shell', `run' and `set args', which pass arguments
334 to inferior programs, now complete on file names, similar to what
335 users expect at the shell prompt.
337 Commands which accept locations, such as `disassemble', `print',
338 `breakpoint', `until', etc. now complete on filenames as well as
339 program symbols. Thus, if you type "break foob TAB", and the source
340 files linked into the programs include `foobar.c', that file name will
341 be one of the candidates for completion. However, file names are not
342 considered for completion after you typed a colon that delimits a file
343 name from a name of a function in that file, as in "break foo.c:bar".
345 `set demangle-style' completes on available demangling styles.
347 * New platform-independent commands:
349 It is now possible to define a post-hook for a command as well as a
350 hook that runs before the command. For more details, see the
351 documentation of `hookpost' in the GDB manual.
353 * Changes in GNU/Linux native debugging.
355 Support for debugging multi-threaded programs has been completely
356 revised for all platforms except m68k and sparc. You can now debug as
357 many threads as your system allows you to have.
359 Attach/detach is supported for multi-threaded programs.
361 Support for SSE registers was added for x86. This doesn't work for
362 multi-threaded programs though.
364 * Changes in MIPS configurations.
366 Multi-arch support is enabled for all MIPS configurations.
368 GDB can now be built as native debugger on SGI Irix 6.x systems for
369 debugging n32 executables. (Debugging 64-bit executables is not yet
372 * Unified support for hardware watchpoints in all x86 configurations.
374 Most (if not all) native x86 configurations support hardware-assisted
375 breakpoints and watchpoints in a unified manner. This support
376 implements debug register sharing between watchpoints, which allows to
377 put a virtually infinite number of watchpoints on the same address,
378 and also supports watching regions up to 16 bytes with several debug
381 The new maintenance command `maintenance show-debug-regs' toggles
382 debugging print-outs in functions that insert, remove, and test
383 watchpoints and hardware breakpoints.
385 * Changes in the DJGPP native configuration.
387 New command ``info dos sysinfo'' displays assorted information about
388 the CPU, OS, memory, and DPMI server.
390 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
391 display information about segment descriptors stored in GDT, LDT, and
394 New commands ``info dos pde'' and ``info dos pte'' display entries
395 from Page Directory and Page Tables (for now works with CWSDPMI only).
396 New command ``info dos address-pte'' displays the Page Table entry for
397 a given linear address.
399 GDB can now pass command lines longer than 126 characters to the
400 program being debugged (requires an update to the libdbg.a library
401 which is part of the DJGPP development kit).
403 DWARF2 debug info is now supported.
405 It is now possible to `step' and `next' through calls to `longjmp'.
407 * Changes in documentation.
409 All GDB documentation was converted to GFDL, the GNU Free
410 Documentation License.
412 Tracepoints-related commands are now fully documented in the GDB
415 TUI, the Text-mode User Interface, is now documented in the manual.
417 Tracepoints-related commands are now fully documented in the GDB
420 The "GDB Internals" manual now has an index. It also includes
421 documentation of `ui_out' functions, GDB coding standards, x86
422 hardware watchpoints, and memory region attributes.
424 * GDB's version number moved to ``version.in''
426 The Makefile variable VERSION has been replaced by the file
427 ``version.in''. People creating GDB distributions should update the
428 contents of this file.
432 GUD support is now a standard part of the EMACS distribution.
434 *** Changes in GDB 5.0:
436 * Improved support for debugging FP programs on x86 targets
438 Unified and much-improved support for debugging floating-point
439 programs on all x86 targets. In particular, ``info float'' now
440 displays the FP registers in the same format on all x86 targets, with
441 greater level of detail.
443 * Improvements and bugfixes in hardware-assisted watchpoints
445 It is now possible to watch array elements, struct members, and
446 bitfields with hardware-assisted watchpoints. Data-read watchpoints
447 on x86 targets no longer erroneously trigger when the address is
450 * Improvements in the native DJGPP version of GDB
452 The distribution now includes all the scripts and auxiliary files
453 necessary to build the native DJGPP version on MS-DOS/MS-Windows
454 machines ``out of the box''.
456 The DJGPP version can now debug programs that use signals. It is
457 possible to catch signals that happened in the debuggee, deliver
458 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
459 would kill the program being debugged.) Programs that hook hardware
460 interrupts (keyboard, timer, etc.) can also be debugged.
462 It is now possible to debug DJGPP programs that redirect their
463 standard handles or switch them to raw (as opposed to cooked) mode, or
464 even close them. The command ``run < foo > bar'' works as expected,
465 and ``info terminal'' reports useful information about the debuggee's
466 terminal, including raw/cooked mode, redirection, etc.
468 The DJGPP version now uses termios functions for console I/O, which
469 enables debugging graphics programs. Interrupting GDB with Ctrl-C
472 DOS-style file names with drive letters are now fully supported by
475 It is now possible to debug DJGPP programs that switch their working
476 directory. It is also possible to rerun the debuggee any number of
477 times without restarting GDB; thus, you can use the same setup,
478 breakpoints, etc. for many debugging sessions.
480 * New native configurations
482 ARM GNU/Linux arm*-*-linux*
483 PowerPC GNU/Linux powerpc-*-linux*
487 Motorola MCore mcore-*-*
488 x86 VxWorks i[3456]86-*-vxworks*
489 PowerPC VxWorks powerpc-*-vxworks*
490 TI TMS320C80 tic80-*-*
492 * OBSOLETE configurations
494 Altos 3068 m68*-altos-*
495 Convex c1-*-*, c2-*-*
497 ARM RISCix arm-*-* (as host)
500 Configurations that have been declared obsolete will be commented out,
501 but the code will be left in place. If there is no activity to revive
502 these configurations before the next release of GDB, the sources will
503 be permanently REMOVED.
505 * Gould support removed
507 Support for the Gould PowerNode and NP1 has been removed.
509 * New features for SVR4
511 On SVR4 native platforms (such as Solaris), if you attach to a process
512 without first loading a symbol file, GDB will now attempt to locate and
513 load symbols from the running process's executable file.
515 * Many C++ enhancements
517 C++ support has been greatly improved. Overload resolution now works properly
518 in almost all cases. RTTI support is on the way.
520 * Remote targets can connect to a sub-program
522 A popen(3) style serial-device has been added. This device starts a
523 sub-process (such as a stand-alone simulator) and then communicates
524 with that. The sub-program to run is specified using the syntax
525 ``|<program> <args>'' vis:
527 (gdb) set remotedebug 1
528 (gdb) target extended-remote |mn10300-elf-sim program-args
530 * MIPS 64 remote protocol
532 A long standing bug in the mips64 remote protocol where by GDB
533 expected certain 32 bit registers (ex SR) to be transfered as 32
534 instead of 64 bits has been fixed.
536 The command ``set remote-mips64-transfers-32bit-regs on'' has been
537 added to provide backward compatibility with older versions of GDB.
539 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
541 The command ``set remotebinarydownload'' command has been replaced by
542 ``set remote X-packet''. Other commands in ``set remote'' family
543 include ``set remote P-packet''.
545 * Breakpoint commands accept ranges.
547 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
548 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
549 ``tracepoint passcount'' also accepts a range of tracepoints.
551 * ``apropos'' command added.
553 The ``apropos'' command searches through command names and
554 documentation strings, printing out matches, making it much easier to
555 try to find a command that does what you are looking for.
559 A new machine oriented interface (MI) has been added to GDB. This
560 interface is designed for debug environments running GDB as a separate
561 process. This is part of the long term libGDB project. See the
562 "GDB/MI" chapter of the GDB manual for further information. It can be
563 enabled by configuring with:
565 .../configure --enable-gdbmi
567 *** Changes in GDB-4.18:
569 * New native configurations
571 HP-UX 10.20 hppa*-*-hpux10.20
572 HP-UX 11.x hppa*-*-hpux11.0*
573 M68K GNU/Linux m68*-*-linux*
577 Fujitsu FR30 fr30-*-elf*
578 Intel StrongARM strongarm-*-*
579 Mitsubishi D30V d30v-*-*
581 * OBSOLETE configurations
583 Gould PowerNode, NP1 np1-*-*, pn-*-*
585 Configurations that have been declared obsolete will be commented out,
586 but the code will be left in place. If there is no activity to revive
587 these configurations before the next release of GDB, the sources will
588 be permanently REMOVED.
592 As a compatibility experiment, GDB's source files buildsym.h and
593 buildsym.c have been converted to pure standard C, no longer
594 containing any K&R compatibility code. We believe that all systems in
595 use today either come with a standard C compiler, or have a GCC port
596 available. If this is not true, please report the affected
597 configuration to bug-gdb@gnu.org immediately. See the README file for
598 information about getting a standard C compiler if you don't have one
603 GDB now uses readline 2.2.
605 * set extension-language
607 You can now control the mapping between filename extensions and source
608 languages by using the `set extension-language' command. For instance,
609 you can ask GDB to treat .c files as C++ by saying
610 set extension-language .c c++
611 The command `info extensions' lists all of the recognized extensions
612 and their associated languages.
614 * Setting processor type for PowerPC and RS/6000
616 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
617 you can use the `set processor' command to specify what variant of the
618 PowerPC family you are debugging. The command
622 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
623 following PowerPC and RS6000 variants:
625 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
626 rs6000 IBM RS6000 ("POWER") architecture, user-level view
628 403GC IBM PowerPC 403GC
629 505 Motorola PowerPC 505
630 860 Motorola PowerPC 860 or 850
631 601 Motorola PowerPC 601
632 602 Motorola PowerPC 602
633 603 Motorola/IBM PowerPC 603 or 603e
634 604 Motorola PowerPC 604 or 604e
635 750 Motorola/IBM PowerPC 750 or 750
637 At the moment, this command just tells GDB what to name the
638 special-purpose processor registers. Since almost all the affected
639 registers are inaccessible to user-level programs, this command is
640 only useful for remote debugging in its present form.
644 Thanks to a major code donation from Hewlett-Packard, GDB now has much
645 more extensive support for HP-UX. Added features include shared
646 library support, kernel threads and hardware watchpoints for 11.00,
647 support for HP's ANSI C and C++ compilers, and a compatibility mode
648 for xdb and dbx commands.
652 HP's donation includes the new concept of catchpoints, which is a
653 generalization of the old catch command. On HP-UX, it is now possible
654 to catch exec, fork, and vfork, as well as library loading.
656 This means that the existing catch command has changed; its first
657 argument now specifies the type of catch to be set up. See the
658 output of "help catch" for a list of catchpoint types.
660 * Debugging across forks
662 On HP-UX, you can choose which process to debug when a fork() happens
667 HP has donated a curses-based terminal user interface (TUI). To get
668 it, build with --enable-tui. Although this can be enabled for any
669 configuration, at present it only works for native HP debugging.
671 * GDB remote protocol additions
673 A new protocol packet 'X' that writes binary data is now available.
674 Default behavior is to try 'X', then drop back to 'M' if the stub
675 fails to respond. The settable variable `remotebinarydownload'
676 allows explicit control over the use of 'X'.
678 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
679 full 64-bit address. The command
681 set remoteaddresssize 32
683 can be used to revert to the old behaviour. For existing remote stubs
684 the change should not be noticed, as the additional address information
687 In order to assist in debugging stubs, you may use the maintenance
688 command `packet' to send any text string to the stub. For instance,
690 maint packet heythere
692 sends the packet "$heythere#<checksum>". Note that it is very easy to
693 disrupt a debugging session by sending the wrong packet at the wrong
696 The compare-sections command allows you to compare section data on the
697 target to what is in the executable file without uploading or
698 downloading, by comparing CRC checksums.
700 * Tracing can collect general expressions
702 You may now collect general expressions at tracepoints. This requires
703 further additions to the target-side stub; see tracepoint.c and
704 doc/agentexpr.texi for further details.
706 * mask-address variable for Mips
708 For Mips targets, you may control the zeroing of the upper 32 bits of
709 a 64-bit address by entering `set mask-address on'. This is mainly
710 of interest to users of embedded R4xxx and R5xxx processors.
712 * Higher serial baud rates
714 GDB's serial code now allows you to specify baud rates 57600, 115200,
715 230400, and 460800 baud. (Note that your host system may not be able
716 to achieve all of these rates.)
720 The i960 configuration now includes an initial implementation of a
721 builtin simulator, contributed by Jim Wilson.
724 *** Changes in GDB-4.17:
726 * New native configurations
728 Alpha GNU/Linux alpha*-*-linux*
729 Unixware 2.x i[3456]86-unixware2*
730 Irix 6.x mips*-sgi-irix6*
731 PowerPC GNU/Linux powerpc-*-linux*
732 PowerPC Solaris powerpcle-*-solaris*
733 Sparc GNU/Linux sparc-*-linux*
734 Motorola sysV68 R3V7.1 m68k-motorola-sysv
738 Argonaut Risc Chip (ARC) arc-*-*
739 Hitachi H8/300S h8300*-*-*
740 Matsushita MN10200 w/simulator mn10200-*-*
741 Matsushita MN10300 w/simulator mn10300-*-*
742 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
743 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
744 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
745 Mitsubishi D10V w/simulator d10v-*-*
746 Mitsubishi M32R/D w/simulator m32r-*-elf*
747 Tsqware Sparclet sparclet-*-*
748 NEC V850 w/simulator v850-*-*
750 * New debugging protocols
752 ARM with RDI protocol arm*-*-*
753 M68K with dBUG monitor m68*-*-{aout,coff,elf}
754 DDB and LSI variants of PMON protocol mips*-*-*
755 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
756 PowerPC with SDS protocol powerpc{,le}-*-eabi
757 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
761 All configurations can now understand and use the DWARF 2 debugging
762 format. The choice is automatic, if the symbol file contains DWARF 2
767 GDB now includes basic Java language support. This support is
768 only useful with Java compilers that produce native machine code.
770 * solib-absolute-prefix and solib-search-path
772 For SunOS and SVR4 shared libraries, you may now set the prefix for
773 loading absolute shared library symbol files, and the search path for
774 locating non-absolute shared library symbol files.
776 * Live range splitting
778 GDB can now effectively debug code for which GCC has performed live
779 range splitting as part of its optimization. See gdb/doc/LRS for
780 more details on the expected format of the stabs information.
784 GDB's support for the GNU Hurd, including thread debugging, has been
785 updated to work with current versions of the Hurd.
789 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
790 instruction set. ARM GDB automatically detects when Thumb
791 instructions are in use, and adjusts disassembly and backtracing
796 GDB's MIPS target configurations now handle the MIP16 16-bit
801 GDB now includes support for overlays; if an executable has been
802 linked such that multiple sections are based at the same address, GDB
803 will decide which section to use for symbolic info. You can choose to
804 control the decision manually, using overlay commands, or implement
805 additional target-side support and use "overlay load-target" to bring
806 in the overlay mapping. Do "help overlay" for more detail.
810 The command "info symbol <address>" displays information about
811 the symbol at the specified address.
815 The standard remote protocol now includes an extension that allows
816 asynchronous collection and display of trace data. This requires
817 extensive support in the target-side debugging stub. Tracing mode
818 includes a new interaction mode in GDB and new commands: see the
819 file tracepoint.c for more details.
823 Configurations for embedded MIPS now include a simulator contributed
824 by Cygnus Solutions. The simulator supports the instruction sets
825 of most MIPS variants.
829 Sparc configurations may now include the ERC32 simulator contributed
830 by the European Space Agency. The simulator is not built into
831 Sparc targets by default; configure with --enable-sim to include it.
835 For target configurations that may include multiple variants of a
836 basic architecture (such as MIPS and SH), you may now set the
837 architecture explicitly. "set arch" sets, "info arch" lists
838 the possible architectures.
840 *** Changes in GDB-4.16:
842 * New native configurations
844 Windows 95, x86 Windows NT i[345]86-*-cygwin32
845 M68K NetBSD m68k-*-netbsd*
846 PowerPC AIX 4.x powerpc-*-aix*
847 PowerPC MacOS powerpc-*-macos*
848 PowerPC Windows NT powerpcle-*-cygwin32
849 RS/6000 AIX 4.x rs6000-*-aix4*
853 ARM with RDP protocol arm-*-*
854 I960 with MON960 i960-*-coff
855 MIPS VxWorks mips*-*-vxworks*
856 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
857 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
859 Matra Sparclet sparclet-*-*
863 The powerpc-eabi configuration now includes the PSIM simulator,
864 contributed by Andrew Cagney, with assistance from Mike Meissner.
865 PSIM is a very elaborate model of the PowerPC, including not only
866 basic instruction set execution, but also details of execution unit
867 performance and I/O hardware. See sim/ppc/README for more details.
871 GDB now works with Solaris 2.5.
873 * Windows 95/NT native
875 GDB will now work as a native debugger on Windows 95 and Windows NT.
876 To build it from source, you must use the "gnu-win32" environment,
877 which uses a DLL to emulate enough of Unix to run the GNU tools.
878 Further information, binaries, and sources are available at
879 ftp.cygnus.com, under pub/gnu-win32.
881 * dont-repeat command
883 If a user-defined command includes the command `dont-repeat', then the
884 command will not be repeated if the user just types return. This is
885 useful if the command is time-consuming to run, so that accidental
886 extra keystrokes don't run the same command many times.
888 * Send break instead of ^C
890 The standard remote protocol now includes an option to send a break
891 rather than a ^C to the target in order to interrupt it. By default,
892 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
894 * Remote protocol timeout
896 The standard remote protocol includes a new variable `remotetimeout'
897 that allows you to set the number of seconds before GDB gives up trying
898 to read from the target. The default value is 2.
900 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
902 By default GDB will automatically keep track of objects as they are
903 loaded and unloaded by the dynamic linker. By using the command `set
904 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
905 when shared library events occur, thus allowing you to set breakpoints
906 in shared libraries which are explicitly loaded by the inferior.
908 Note this feature does not work on hpux8. On hpux9 you must link
909 /usr/lib/end.o into your program. This feature should work
910 automatically on hpux10.
912 * Irix 5.x hardware watchpoint support
914 Irix 5 configurations now support the use of hardware watchpoints.
916 * Mips protocol "SYN garbage limit"
918 When debugging a Mips target using the `target mips' protocol, you
919 may set the number of characters that GDB will ignore by setting
920 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
921 every character. The default value is 1050.
923 * Recording and replaying remote debug sessions
925 If you set `remotelogfile' to the name of a file, gdb will write to it
926 a recording of a remote debug session. This recording may then be
927 replayed back to gdb using "gdbreplay". See gdbserver/README for
928 details. This is useful when you have a problem with GDB while doing
929 remote debugging; you can make a recording of the session and send it
930 to someone else, who can then recreate the problem.
932 * Speedups for remote debugging
934 GDB includes speedups for downloading and stepping MIPS systems using
935 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
936 and more efficient S-record downloading.
938 * Memory use reductions and statistics collection
940 GDB now uses less memory and reports statistics about memory usage.
941 Try the `maint print statistics' command, for example.
943 *** Changes in GDB-4.15:
947 The symbol reader for AIX GDB now uses partial symbol tables. This
948 can greatly improve startup time, especially for large executables.
950 * Remote targets use caching
952 Remote targets now use a data cache to speed up communication with the
953 remote side. The data cache could lead to incorrect results because
954 it doesn't know about volatile variables, thus making it impossible to
955 debug targets which use memory mapped I/O devices. `set remotecache
956 off' turns the the data cache off.
958 * Remote targets may have threads
960 The standard remote protocol now includes support for multiple threads
961 in the target system, using new protocol commands 'H' and 'T'. See
962 gdb/remote.c for details.
966 If GDB is configured with `--enable-netrom', then it will include
967 support for the NetROM ROM emulator from XLNT Designs. The NetROM
968 acts as though it is a bank of ROM on the target board, but you can
969 write into it over the network. GDB's support consists only of
970 support for fast loading into the emulated ROM; to debug, you must use
971 another protocol, such as standard remote protocol. The usual
972 sequence is something like
974 target nrom <netrom-hostname>
976 target remote <netrom-hostname>:1235
980 GDB now includes support for the Apple Macintosh, as a host only. It
981 may be run as either an MPW tool or as a standalone application, and
982 it can debug through the serial port. All the usual GDB commands are
983 available, but to the target command, you must supply "serial" as the
984 device type instead of "/dev/ttyXX". See mpw-README in the main
985 directory for more information on how to build. The MPW configuration
986 scripts */mpw-config.in support only a few targets, and only the
987 mips-idt-ecoff target has been tested.
991 GDB configuration now uses autoconf. This is not user-visible,
992 but does simplify configuration and building.
996 GDB now supports hpux10.
998 *** Changes in GDB-4.14:
1000 * New native configurations
1002 x86 FreeBSD i[345]86-*-freebsd
1003 x86 NetBSD i[345]86-*-netbsd
1004 NS32k NetBSD ns32k-*-netbsd
1005 Sparc NetBSD sparc-*-netbsd
1009 A29K VxWorks a29k-*-vxworks
1010 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1011 CPU32 EST-300 emulator m68*-*-est*
1012 PowerPC ELF powerpc-*-elf
1015 * Alpha OSF/1 support for procfs
1017 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1018 possible to attach to running processes. As the mounting of the /proc
1019 filesystem is optional on the Alpha, GDB automatically determines
1020 the availability of /proc during startup. This can lead to problems
1021 if /proc is unmounted after GDB has been started.
1023 * Arguments to user-defined commands
1025 User commands may accept up to 10 arguments separated by whitespace.
1026 Arguments are accessed within the user command via $arg0..$arg9. A
1029 print $arg0 + $arg1 + $arg2
1031 To execute the command use:
1034 Defines the command "adder" which prints the sum of its three arguments.
1035 Note the arguments are text substitutions, so they may reference variables,
1036 use complex expressions, or even perform inferior function calls.
1038 * New `if' and `while' commands
1040 This makes it possible to write more sophisticated user-defined
1041 commands. Both commands take a single argument, which is the
1042 expression to evaluate, and must be followed by the commands to
1043 execute, one per line, if the expression is nonzero, the list being
1044 terminated by the word `end'. The `if' command list may include an
1045 `else' word, which causes the following commands to be executed only
1046 if the expression is zero.
1048 * Fortran source language mode
1050 GDB now includes partial support for Fortran 77. It will recognize
1051 Fortran programs and can evaluate a subset of Fortran expressions, but
1052 variables and functions may not be handled correctly. GDB will work
1053 with G77, but does not yet know much about symbols emitted by other
1056 * Better HPUX support
1058 Most debugging facilities now work on dynamic executables for HPPAs
1059 running hpux9 or later. You can attach to running dynamically linked
1060 processes, but by default the dynamic libraries will be read-only, so
1061 for instance you won't be able to put breakpoints in them. To change
1062 that behavior do the following before running the program:
1068 This will cause the libraries to be mapped private and read-write.
1069 To revert to the normal behavior, do this:
1075 You cannot set breakpoints or examine data in the library until after
1076 the library is loaded if the function/data symbols do not have
1079 GDB can now also read debug symbols produced by the HP C compiler on
1080 HPPAs (sorry, no C++, Fortran or 68k support).
1082 * Target byte order now dynamically selectable
1084 You can choose which byte order to use with a target system, via the
1085 commands "set endian big" and "set endian little", and you can see the
1086 current setting by using "show endian". You can also give the command
1087 "set endian auto", in which case GDB will use the byte order
1088 associated with the executable. Currently, only embedded MIPS
1089 configurations support dynamic selection of target byte order.
1091 * New DOS host serial code
1093 This version uses DPMI interrupts to handle buffered I/O, so you
1094 no longer need to run asynctsr when debugging boards connected to
1097 *** Changes in GDB-4.13:
1099 * New "complete" command
1101 This lists all the possible completions for the rest of the line, if it
1102 were to be given as a command itself. This is intended for use by emacs.
1104 * Trailing space optional in prompt
1106 "set prompt" no longer adds a space for you after the prompt you set. This
1107 allows you to set a prompt which ends in a space or one that does not.
1109 * Breakpoint hit counts
1111 "info break" now displays a count of the number of times the breakpoint
1112 has been hit. This is especially useful in conjunction with "ignore"; you
1113 can ignore a large number of breakpoint hits, look at the breakpoint info
1114 to see how many times the breakpoint was hit, then run again, ignoring one
1115 less than that number, and this will get you quickly to the last hit of
1118 * Ability to stop printing at NULL character
1120 "set print null-stop" will cause GDB to stop printing the characters of
1121 an array when the first NULL is encountered. This is useful when large
1122 arrays actually contain only short strings.
1124 * Shared library breakpoints
1126 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1127 breakpoints in shared libraries before the executable is run.
1129 * Hardware watchpoints
1131 There is a new hardware breakpoint for the watch command for sparclite
1132 targets. See gdb/sparclite/hw_breakpoint.note.
1134 Hardware watchpoints are also now supported under GNU/Linux.
1138 Annotations have been added. These are for use with graphical interfaces,
1139 and are still experimental. Currently only gdba.el uses these.
1141 * Improved Irix 5 support
1143 GDB now works properly with Irix 5.2.
1145 * Improved HPPA support
1147 GDB now works properly with the latest GCC and GAS.
1149 * New native configurations
1151 Sequent PTX4 i[34]86-sequent-ptx4
1152 HPPA running OSF/1 hppa*-*-osf*
1153 Atari TT running SVR4 m68*-*-sysv4*
1154 RS/6000 LynxOS rs6000-*-lynxos*
1158 OS/9000 i[34]86-*-os9k
1159 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1162 * Hitachi SH7000 and E7000-PC ICE support
1164 There is now support for communicating with the Hitachi E7000-PC ICE.
1165 This is available automatically when GDB is configured for the SH.
1169 As usual, a variety of small fixes and improvements, both generic
1170 and configuration-specific. See the ChangeLog for more detail.
1172 *** Changes in GDB-4.12:
1174 * Irix 5 is now supported
1178 GDB-4.12 on the HPPA has a number of changes which make it unable
1179 to debug the output from the currently released versions of GCC and
1180 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1181 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1182 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1185 *** Changes in GDB-4.11:
1187 * User visible changes:
1191 The "set remotedebug" option is now consistent between the mips remote
1192 target, remote targets using the gdb-specific protocol, UDI (AMD's
1193 debug protocol for the 29k) and the 88k bug monitor. It is now an
1194 integer specifying a debug level (normally 0 or 1, but 2 means more
1195 debugging info for the mips target).
1197 * DEC Alpha native support
1199 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1200 debug info, but GDB works fairly well with the DEC compiler and should
1201 work with a future GCC release. See the README file for a few
1202 Alpha-specific notes.
1204 * Preliminary thread implementation
1206 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1208 * LynxOS native and target support for 386
1210 This release has been hosted on LynxOS 2.2, and also can be configured
1211 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1214 * Improvements in C++ mangling/demangling.
1216 This release has much better g++ debugging, specifically in name
1217 mangling/demangling, virtual function calls, print virtual table,
1218 call methods, ...etc.
1220 *** Changes in GDB-4.10:
1222 * User visible changes:
1224 Remote debugging using the GDB-specific (`target remote') protocol now
1225 supports the `load' command. This is only useful if you have some
1226 other way of getting the stub to the target system, and you can put it
1227 somewhere in memory where it won't get clobbered by the download.
1229 Filename completion now works.
1231 When run under emacs mode, the "info line" command now causes the
1232 arrow to point to the line specified. Also, "info line" prints
1233 addresses in symbolic form (as well as hex).
1235 All vxworks based targets now support a user settable option, called
1236 vxworks-timeout. This option represents the number of seconds gdb
1237 should wait for responses to rpc's. You might want to use this if
1238 your vxworks target is, perhaps, a slow software simulator or happens
1239 to be on the far side of a thin network line.
1243 This release contains support for using a DEC alpha as a GDB host for
1244 cross debugging. Native alpha debugging is not supported yet.
1247 *** Changes in GDB-4.9:
1251 This is the first GDB release which is accompanied by a matching testsuite.
1252 The testsuite requires installation of dejagnu, which should be available
1253 via ftp from most sites that carry GNU software.
1257 'Cfront' style demangling has had its name changed to 'ARM' style, to
1258 emphasize that it was written from the specifications in the C++ Annotated
1259 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1260 disclaimers, it still generated too much confusion with users attempting to
1261 use gdb with AT&T cfront.
1265 GDB now uses a standard remote interface to a simulator library.
1266 So far, the library contains simulators for the Zilog Z8001/2, the
1267 Hitachi H8/300, H8/500 and Super-H.
1269 * New targets supported
1271 H8/300 simulator h8300-hitachi-hms or h8300hms
1272 H8/500 simulator h8500-hitachi-hms or h8500hms
1273 SH simulator sh-hitachi-hms or sh
1274 Z8000 simulator z8k-zilog-none or z8ksim
1275 IDT MIPS board over serial line mips-idt-ecoff
1277 Cross-debugging to GO32 targets is supported. It requires a custom
1278 version of the i386-stub.c module which is integrated with the
1279 GO32 memory extender.
1281 * New remote protocols
1283 MIPS remote debugging protocol.
1285 * New source languages supported
1287 This version includes preliminary support for Chill, a Pascal like language
1288 used by telecommunications companies. Chill support is also being integrated
1289 into the GNU compiler, but we don't know when it will be publically available.
1292 *** Changes in GDB-4.8:
1294 * HP Precision Architecture supported
1296 GDB now supports HP PA-RISC machines running HPUX. A preliminary
1297 version of this support was available as a set of patches from the
1298 University of Utah. GDB does not support debugging of programs
1299 compiled with the HP compiler, because HP will not document their file
1300 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
1301 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
1303 Many problems in the preliminary version have been fixed.
1305 * Faster and better demangling
1307 We have improved template demangling and fixed numerous bugs in the GNU style
1308 demangler. It can now handle type modifiers such as `static' or `const'. Wide
1309 character types (wchar_t) are now supported. Demangling of each symbol is now
1310 only done once, and is cached when the symbol table for a file is read in.
1311 This results in a small increase in memory usage for C programs, a moderate
1312 increase in memory usage for C++ programs, and a fantastic speedup in
1315 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
1316 from the specifications in the Annotated Reference Manual, which AT&T's
1317 compiler does not actually implement.
1319 * G++ multiple inheritance compiler problem
1321 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
1322 inheritance lattices was reworked to properly discover ambiguities. We
1323 recently found an example which causes this new algorithm to fail in a
1324 very subtle way, producing bad debug information for those classes.
1325 The file 'gcc.patch' (in this directory) can be applied to gcc to
1326 circumvent the problem. A future GCC release will contain a complete
1329 The previous G++ debug info problem (mentioned below for the gdb-4.7
1330 release) is fixed in gcc version 2.3.2.
1332 * Improved configure script
1334 The `configure' script will now attempt to guess your system type if
1335 you don't supply a host system type. The old scheme of supplying a
1336 host system triplet is preferable over using this. All the magic is
1337 done in the new `config.guess' script. Examine it for details.
1339 We have also brought our configure script much more in line with the FSF's
1340 version. It now supports the --with-xxx options. In particular,
1341 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
1342 The resulting GDB will not be able to read arbitrary object file formats --
1343 only the format ``expected'' to be used on the configured target system.
1344 We hope to make this the default in a future release.
1346 * Documentation improvements
1348 There's new internal documentation on how to modify GDB, and how to
1349 produce clean changes to the code. We implore people to read it
1350 before submitting changes.
1352 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
1353 M4 macros. The new texinfo.tex is provided in this release. Pre-built
1354 `info' files are also provided. To build `info' files from scratch,
1355 you will need the latest `makeinfo' release, which will be available in
1356 a future texinfo-X.Y release.
1358 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
1359 We're not sure exactly which versions have this problem, but it has
1360 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
1361 or better. If that isn't possible, there is a patch in
1362 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
1363 around this problem.
1367 GDB now supports array constants that can be used in expressions typed in by
1368 the user. The syntax is `{element, element, ...}'. Ie: you can now type
1369 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
1372 The new directory `gdb/sparclite' contains a program that demonstrates
1373 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
1375 * New native hosts supported
1377 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
1378 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
1380 * New targets supported
1382 AMD 29k family via UDI a29k-amd-udi or udi29k
1384 * New file formats supported
1386 BFD now supports reading HP/PA-RISC executables (SOM file format?),
1387 HPUX core files, and SCO 3.2v2 core files.
1391 Attaching to processes now works again; thanks for the many bug reports.
1393 We have also stomped on a bunch of core dumps caused by
1394 printf_filtered("%s") problems.
1396 We eliminated a copyright problem on the rpc and ptrace header files
1397 for VxWorks, which was discovered at the last minute during the 4.7
1398 release. You should now be able to build a VxWorks GDB.
1400 You can now interrupt gdb while an attached process is running. This
1401 will cause the attached process to stop, and give control back to GDB.
1403 We fixed problems caused by using too many file descriptors
1404 for reading symbols from object files and libraries. This was
1405 especially a problem for programs that used many (~100) shared
1408 The `step' command now only enters a subroutine if there is line number
1409 information for the subroutine. Otherwise it acts like the `next'
1410 command. Previously, `step' would enter subroutines if there was
1411 any debugging information about the routine. This avoids problems
1412 when using `cc -g1' on MIPS machines.
1414 * Internal improvements
1416 GDB's internal interfaces have been improved to make it easier to support
1417 debugging of multiple languages in the future.
1419 GDB now uses a common structure for symbol information internally.
1420 Minimal symbols (derived from linkage symbols in object files), partial
1421 symbols (from a quick scan of debug information), and full symbols
1422 contain a common subset of information, making it easier to write
1423 shared code that handles any of them.
1425 * New command line options
1427 We now accept --silent as an alias for --quiet.
1431 The memory-mapped-malloc library is now licensed under the GNU Library
1432 General Public License.
1434 *** Changes in GDB-4.7:
1436 * Host/native/target split
1438 GDB has had some major internal surgery to untangle the support for
1439 hosts and remote targets. Now, when you configure GDB for a remote
1440 target, it will no longer load in all of the support for debugging
1441 local programs on the host. When fully completed and tested, this will
1442 ensure that arbitrary host/target combinations are possible.
1444 The primary conceptual shift is to separate the non-portable code in
1445 GDB into three categories. Host specific code is required any time GDB
1446 is compiled on that host, regardless of the target. Target specific
1447 code relates to the peculiarities of the target, but can be compiled on
1448 any host. Native specific code is everything else: it can only be
1449 built when the host and target are the same system. Child process
1450 handling and core file support are two common `native' examples.
1452 GDB's use of /proc for controlling Unix child processes is now cleaner.
1453 It has been split out into a single module under the `target_ops' vector,
1454 plus two native-dependent functions for each system that uses /proc.
1456 * New hosts supported
1458 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
1459 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1460 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
1462 * New targets supported
1464 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
1465 68030 and CPU32 m68030-*-*, m68332-*-*
1467 * New native hosts supported
1469 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1470 (386bsd is not well tested yet)
1471 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
1473 * New file formats supported
1475 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
1476 supports reading of `a.out.adobe' object files, which are an a.out
1477 format extended with minimal information about multiple sections.
1481 `show copying' is the same as the old `info copying'.
1482 `show warranty' is the same as `info warrantee'.
1483 These were renamed for consistency. The old commands continue to work.
1485 `info handle' is a new alias for `info signals'.
1487 You can now define pre-command hooks, which attach arbitrary command
1488 scripts to any command. The commands in the hook will be executed
1489 prior to the user's command. You can also create a hook which will be
1490 executed whenever the program stops. See gdb.texinfo.
1494 We now deal with Cfront style name mangling, and can even extract type
1495 info from mangled symbols. GDB can automatically figure out which
1496 symbol mangling style your C++ compiler uses.
1498 Calling of methods and virtual functions has been improved as well.
1502 The crash that occured when debugging Sun Ansi-C compiled binaries is
1503 fixed. This was due to mishandling of the extra N_SO stabs output
1506 We also finally got Ultrix 4.2 running in house, and fixed core file
1507 support, with help from a dozen people on the net.
1509 John M. Farrell discovered that the reason that single-stepping was so
1510 slow on all of the Mips based platforms (primarily SGI and DEC) was
1511 that we were trying to demangle and lookup a symbol used for internal
1512 purposes on every instruction that was being stepped through. Changing
1513 the name of that symbol so that it couldn't be mistaken for a C++
1514 mangled symbol sped things up a great deal.
1516 Rich Pixley sped up symbol lookups in general by getting much smarter
1517 about when C++ symbol mangling is necessary. This should make symbol
1518 completion (TAB on the command line) much faster. It's not as fast as
1519 we'd like, but it's significantly faster than gdb-4.6.
1523 A new user controllable variable 'call_scratch_address' can
1524 specify the location of a scratch area to be used when GDB
1525 calls a function in the target. This is necessary because the
1526 usual method of putting the scratch area on the stack does not work
1527 in systems that have separate instruction and data spaces.
1529 We integrated changes to support the 29k UDI (Universal Debugger
1530 Interface), but discovered at the last minute that we didn't have all
1531 of the appropriate copyright paperwork. We are working with AMD to
1532 resolve this, and hope to have it available soon.
1536 We have sped up the remote serial line protocol, especially for targets
1537 with lots of registers. It now supports a new `expedited status' ('T')
1538 message which can be used in place of the existing 'S' status message.
1539 This allows the remote stub to send only the registers that GDB
1540 needs to make a quick decision about single-stepping or conditional
1541 breakpoints, eliminating the need to fetch the entire register set for
1542 each instruction being stepped through.
1544 The GDB remote serial protocol now implements a write-through cache for
1545 registers, only re-reading the registers if the target has run.
1547 There is also a new remote serial stub for SPARC processors. You can
1548 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
1549 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
1550 processor with a serial port.
1554 Configure.in files have become much easier to read and modify. A new
1555 `table driven' format makes it more obvious what configurations are
1556 supported, and what files each one uses.
1560 There is a new opcodes library which will eventually contain all of the
1561 disassembly routines and opcode tables. At present, it only contains
1562 Sparc and Z8000 routines. This will allow the assembler, debugger, and
1563 disassembler (binutils/objdump) to share these routines.
1565 The libiberty library is now copylefted under the GNU Library General
1566 Public License. This allows more liberal use, and was done so libg++
1567 can use it. This makes no difference to GDB, since the Library License
1568 grants all the rights from the General Public License.
1572 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
1573 reference to the stabs symbol info used by the debugger. It is (as far
1574 as we know) the only published document on this fascinating topic. We
1575 encourage you to read it, compare it to the stabs information on your
1576 system, and send improvements on the document in general (to
1577 bug-gdb@prep.ai.mit.edu).
1579 And, of course, many bugs have been fixed.
1582 *** Changes in GDB-4.6:
1584 * Better support for C++ function names
1586 GDB now accepts as input the "demangled form" of C++ overloaded function
1587 names and member function names, and can do command completion on such names
1588 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
1589 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
1590 Make use of command completion, it is your friend.
1592 GDB also now accepts a variety of C++ mangled symbol formats. They are
1593 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
1594 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
1595 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
1596 for the list of formats.
1598 * G++ symbol mangling problem
1600 Recent versions of gcc have a bug in how they emit debugging information for
1601 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
1602 directory) can be applied to gcc to fix the problem. Alternatively, if you
1603 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
1604 usual symptom is difficulty with setting breakpoints on methods. GDB complains
1605 about the method being non-existent. (We believe that version 2.2.2 of GCC has
1608 * New 'maintenance' command
1610 All of the commands related to hacking GDB internals have been moved out of
1611 the main command set, and now live behind the 'maintenance' command. This
1612 can also be abbreviated as 'mt'. The following changes were made:
1614 dump-me -> maintenance dump-me
1615 info all-breakpoints -> maintenance info breakpoints
1616 printmsyms -> maintenance print msyms
1617 printobjfiles -> maintenance print objfiles
1618 printpsyms -> maintenance print psymbols
1619 printsyms -> maintenance print symbols
1621 The following commands are new:
1623 maintenance demangle Call internal GDB demangler routine to
1624 demangle a C++ link name and prints the result.
1625 maintenance print type Print a type chain for a given symbol
1627 * Change to .gdbinit file processing
1629 We now read the $HOME/.gdbinit file before processing the argv arguments
1630 (e.g. reading symbol files or core files). This allows global parameters to
1631 be set, which will apply during the symbol reading. The ./.gdbinit is still
1632 read after argv processing.
1634 * New hosts supported
1636 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
1638 GNU/Linux support i386-unknown-linux or linux
1640 We are also including code to support the HP/PA running BSD and HPUX. This
1641 is almost guaranteed not to work, as we didn't have time to test or build it
1642 for this release. We are including it so that the more adventurous (or
1643 masochistic) of you can play with it. We also had major problems with the
1644 fact that the compiler that we got from HP doesn't support the -g option.
1647 * New targets supported
1649 Hitachi H8/300 h8300-hitachi-hms or h8300hms
1651 * More smarts about finding #include files
1653 GDB now remembers the compilation directory for all include files, and for
1654 all files from which C is generated (like yacc and lex sources). This
1655 greatly improves GDB's ability to find yacc/lex sources, and include files,
1656 especially if you are debugging your program from a directory different from
1657 the one that contains your sources.
1659 We also fixed a bug which caused difficulty with listing and setting
1660 breakpoints in include files which contain C code. (In the past, you had to
1661 try twice in order to list an include file that you hadn't looked at before.)
1663 * Interesting infernals change
1665 GDB now deals with arbitrary numbers of sections, where the symbols for each
1666 section must be relocated relative to that section's landing place in the
1667 target's address space. This work was needed to support ELF with embedded
1668 stabs used by Solaris-2.0.
1670 * Bug fixes (of course!)
1672 There have been loads of fixes for the following things:
1673 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
1674 i960, stabs, DOS(GO32), procfs, etc...
1676 See the ChangeLog for details.
1678 *** Changes in GDB-4.5:
1680 * New machines supported (host and target)
1682 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
1684 SGI Irix-4.x mips-sgi-irix4 or iris4
1686 * New malloc package
1688 GDB now uses a new memory manager called mmalloc, based on gmalloc.
1689 Mmalloc is capable of handling mutiple heaps of memory. It is also
1690 capable of saving a heap to a file, and then mapping it back in later.
1691 This can be used to greatly speedup the startup of GDB by using a
1692 pre-parsed symbol table which lives in a mmalloc managed heap. For
1693 more details, please read mmalloc/mmalloc.texi.
1697 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
1698 'help info proc' for details.
1700 * MIPS ecoff symbol table format
1702 The code that reads MIPS symbol table format is now supported on all hosts.
1703 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
1706 * File name changes for MS-DOS
1708 Many files in the config directories have been renamed to make it easier to
1709 support GDB on MS-DOSe systems (which have very restrictive file name
1710 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
1711 environment) is close to working but has some remaining problems. Note
1712 that debugging of DOS programs is not supported, due to limitations
1713 in the ``operating system'', but it can be used to host cross-debugging.
1715 * Cross byte order fixes
1717 Many fixes have been made to support cross debugging of Sparc and MIPS
1718 targets from hosts whose byte order differs.
1720 * New -mapped and -readnow options
1722 If memory-mapped files are available on your system through the 'mmap'
1723 system call, you can use the -mapped option on the `file' or
1724 `symbol-file' commands to cause GDB to write the symbols from your
1725 program into a reusable file. If the program you are debugging is
1726 called `/path/fred', the mapped symbol file will be `./fred.syms'.
1727 Future GDB debugging sessions will notice the presence of this file,
1728 and will quickly map in symbol information from it, rather than reading
1729 the symbol table from the executable program. Using the '-mapped'
1730 option in a GDB `file' or `symbol-file' command has the same effect as
1731 starting GDB with the '-mapped' command-line option.
1733 You can cause GDB to read the entire symbol table immediately by using
1734 the '-readnow' option with any of the commands that load symbol table
1735 information (or on the GDB command line). This makes the command
1736 slower, but makes future operations faster.
1738 The -mapped and -readnow options are typically combined in order to
1739 build a `fred.syms' file that contains complete symbol information.
1740 A simple GDB invocation to do nothing but build a `.syms' file for future
1743 gdb -batch -nx -mapped -readnow programname
1745 The `.syms' file is specific to the host machine on which GDB is run.
1746 It holds an exact image of GDB's internal symbol table. It cannot be
1747 shared across multiple host platforms.
1749 * longjmp() handling
1751 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
1752 siglongjmp() without losing control. This feature has not yet been ported to
1753 all systems. It currently works on many 386 platforms, all MIPS-based
1754 platforms (SGI, DECstation, etc), and Sun3/4.
1758 Preliminary work has been put in to support the new Solaris OS from Sun. At
1759 this time, it can control and debug processes, but it is not capable of
1764 As always, many many bug fixes. The major areas were with g++, and mipsread.
1765 People using the MIPS-based platforms should experience fewer mysterious
1766 crashes and trashed symbol tables.
1768 *** Changes in GDB-4.4:
1770 * New machines supported (host and target)
1772 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1774 BSD Reno on Vax vax-dec-bsd
1775 Ultrix on Vax vax-dec-ultrix
1777 * New machines supported (target)
1779 AMD 29000 embedded, using EBMON a29k-none-none
1783 GDB continues to improve its handling of C++. `References' work better.
1784 The demangler has also been improved, and now deals with symbols mangled as
1785 per the Annotated C++ Reference Guide.
1787 GDB also now handles `stabs' symbol information embedded in MIPS
1788 `ecoff' symbol tables. Since the ecoff format was not easily
1789 extensible to handle new languages such as C++, this appeared to be a
1790 good way to put C++ debugging info into MIPS binaries. This option
1791 will be supported in the GNU C compiler, version 2, when it is
1794 * New features for SVR4
1796 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
1797 shared libraries. Debugging dynamically linked programs should present
1798 only minor differences from debugging statically linked programs.
1800 The `info proc' command will print out information about any process
1801 on an SVR4 system (including the one you are debugging). At the moment,
1802 it prints the address mappings of the process.
1804 If you bring up GDB on another SVR4 system, please send mail to
1805 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
1807 * Better dynamic linking support in SunOS
1809 Reading symbols from shared libraries which contain debugging symbols
1810 now works properly. However, there remain issues such as automatic
1811 skipping of `transfer vector' code during function calls, which
1812 make it harder to debug code in a shared library, than to debug the
1813 same code linked statically.
1817 GDB is now using the latest `getopt' routines from the FSF. This
1818 version accepts the -- prefix for options with long names. GDB will
1819 continue to accept the old forms (-option and +option) as well.
1820 Various single letter abbreviations for options have been explicity
1821 added to the option table so that they won't get overshadowed in the
1822 future by other options that begin with the same letter.
1826 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
1827 Many assorted bugs have been handled. Many more remain to be handled.
1828 See the various ChangeLog files (primarily in gdb and bfd) for details.
1831 *** Changes in GDB-4.3:
1833 * New machines supported (host and target)
1835 Amiga 3000 running Amix m68k-cbm-svr4 or amix
1836 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
1837 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
1839 * Almost SCO Unix support
1841 We had hoped to support:
1842 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1843 (except for core file support), but we discovered very late in the release
1844 that it has problems with process groups that render gdb unusable. Sorry
1845 about that. I encourage people to fix it and post the fixes.
1847 * Preliminary ELF and DWARF support
1849 GDB can read ELF object files on System V Release 4, and can handle
1850 debugging records for C, in DWARF format, in ELF files. This support
1851 is preliminary. If you bring up GDB on another SVR4 system, please
1852 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
1857 GDB now uses the latest `readline' library. One user-visible change
1858 is that two tabs will list possible command completions, which previously
1859 required typing M-? (meta-question mark, or ESC ?).
1863 The `stepi' bug that many of you noticed has been squashed.
1864 Many bugs in C++ have been handled. Many more remain to be handled.
1865 See the various ChangeLog files (primarily in gdb and bfd) for details.
1867 * State of the MIPS world (in case you wondered):
1869 GDB can understand the symbol tables emitted by the compilers
1870 supplied by most vendors of MIPS-based machines, including DEC. These
1871 symbol tables are in a format that essentially nobody else uses.
1873 Some versions of gcc come with an assembler post-processor called
1874 mips-tfile. This program is required if you want to do source-level
1875 debugging of gcc-compiled programs. I believe FSF does not ship
1876 mips-tfile with gcc version 1, but it will eventually come with gcc
1879 Debugging of g++ output remains a problem. g++ version 1.xx does not
1880 really support it at all. (If you're lucky, you should be able to get
1881 line numbers and stack traces to work, but no parameters or local
1882 variables.) With some work it should be possible to improve the
1885 When gcc version 2 is released, you will have somewhat better luck.
1886 However, even then you will get confusing results for inheritance and
1889 We will eventually provide full debugging of g++ output on
1890 DECstations. This will probably involve some kind of stabs-in-ecoff
1891 encapulation, but the details have not been worked out yet.
1894 *** Changes in GDB-4.2:
1896 * Improved configuration
1898 Only one copy of `configure' exists now, and it is not self-modifying.
1899 Porting BFD is simpler.
1903 The `step' and `next' commands now only stop at the first instruction
1904 of a source line. This prevents the multiple stops that used to occur
1905 in switch statements, for-loops, etc. `Step' continues to stop if a
1906 function that has debugging information is called within the line.
1910 Lots of small bugs fixed. More remain.
1912 * New host supported (not target)
1914 Intel 386 PC clone running Mach i386-none-mach
1917 *** Changes in GDB-4.1:
1919 * Multiple source language support
1921 GDB now has internal scaffolding to handle several source languages.
1922 It determines the type of each source file from its filename extension,
1923 and will switch expression parsing and number formatting to match the
1924 language of the function in the currently selected stack frame.
1925 You can also specifically set the language to be used, with
1926 `set language c' or `set language modula-2'.
1930 GDB now has preliminary support for the GNU Modula-2 compiler,
1931 currently under development at the State University of New York at
1932 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
1933 continue through the fall of 1991 and into 1992.
1935 Other Modula-2 compilers are currently not supported, and attempting to
1936 debug programs compiled with them will likely result in an error as the
1937 symbol table is read. Feel free to work on it, though!
1939 There are hooks in GDB for strict type checking and range checking,
1940 in the `Modula-2 philosophy', but they do not currently work.
1944 GDB can now write to executable and core files (e.g. patch
1945 a variable's value). You must turn this switch on, specify
1946 the file ("exec foo" or "core foo"), *then* modify it, e.g.
1947 by assigning a new value to a variable. Modifications take
1950 * Automatic SunOS shared library reading
1952 When you run your program, GDB automatically determines where its
1953 shared libraries (if any) have been loaded, and reads their symbols.
1954 The `share' command is no longer needed. This also works when
1955 examining core files.
1959 You can specify the number of lines that the `list' command shows.
1962 * New machines supported (host and target)
1964 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
1965 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
1966 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
1968 * New hosts supported (not targets)
1970 IBM RT/PC: romp-ibm-aix or rtpc
1972 * New targets supported (not hosts)
1974 AMD 29000 embedded with COFF a29k-none-coff
1975 AMD 29000 embedded with a.out a29k-none-aout
1976 Ultracomputer remote kernel debug a29k-nyu-kern
1978 * New remote interfaces
1984 *** Changes in GDB-4.0:
1988 Wide output is wrapped at good places to make the output more readable.
1990 Gdb now supports cross-debugging from a host machine of one type to a
1991 target machine of another type. Communication with the target system
1992 is over serial lines. The ``target'' command handles connecting to the
1993 remote system; the ``load'' command will download a program into the
1994 remote system. Serial stubs for the m68k and i386 are provided. Gdb
1995 also supports debugging of realtime processes running under VxWorks,
1996 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
1997 stub on the target system.
1999 New CPUs supported include the AMD 29000 and Intel 960.
2001 GDB now reads object files and symbol tables via a ``binary file''
2002 library, which allows a single copy of GDB to debug programs of multiple
2003 object file types such as a.out and coff.
2005 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2006 refcard.dvi and refcard.ps are available to format it).
2009 * Control-Variable user interface simplified
2011 All variables that control the operation of the debugger can be set
2012 by the ``set'' command, and displayed by the ``show'' command.
2014 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2015 ``Show prompt'' produces the response:
2016 Gdb's prompt is new-gdb=>.
2018 What follows are the NEW set commands. The command ``help set'' will
2019 print a complete list of old and new set commands. ``help set FOO''
2020 will give a longer description of the variable FOO. ``show'' will show
2021 all of the variable descriptions and their current settings.
2023 confirm on/off: Enables warning questions for operations that are
2024 hard to recover from, e.g. rerunning the program while
2025 it is already running. Default is ON.
2027 editing on/off: Enables EMACS style command line editing
2028 of input. Previous lines can be recalled with
2029 control-P, the current line can be edited with control-B,
2030 you can search for commands with control-R, etc.
2033 history filename NAME: NAME is where the gdb command history
2034 will be stored. The default is .gdb_history,
2035 or the value of the environment variable
2038 history size N: The size, in commands, of the command history. The
2039 default is 256, or the value of the environment variable
2042 history save on/off: If this value is set to ON, the history file will
2043 be saved after exiting gdb. If set to OFF, the
2044 file will not be saved. The default is OFF.
2046 history expansion on/off: If this value is set to ON, then csh-like
2047 history expansion will be performed on
2048 command line input. The default is OFF.
2050 radix N: Sets the default radix for input and output. It can be set
2051 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2052 in the current radix, so "set radix 10" is always a no-op.
2054 height N: This integer value is the number of lines on a page. Default
2055 is 24, the current `stty rows'' setting, or the ``li#''
2056 setting from the termcap entry matching the environment
2059 width N: This integer value is the number of characters on a line.
2060 Default is 80, the current `stty cols'' setting, or the ``co#''
2061 setting from the termcap entry matching the environment
2064 Note: ``set screensize'' is obsolete. Use ``set height'' and
2065 ``set width'' instead.
2067 print address on/off: Print memory addresses in various command displays,
2068 such as stack traces and structure values. Gdb looks
2069 more ``symbolic'' if you turn this off; it looks more
2070 ``machine level'' with it on. Default is ON.
2072 print array on/off: Prettyprint arrays. New convenient format! Default
2075 print demangle on/off: Print C++ symbols in "source" form if on,
2078 print asm-demangle on/off: Same, for assembler level printouts
2081 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2084 * Support for Epoch Environment.
2086 The epoch environment is a version of Emacs v18 with windowing. One
2087 new command, ``inspect'', is identical to ``print'', except that if you
2088 are running in the epoch environment, the value is printed in its own
2092 * Support for Shared Libraries
2094 GDB can now debug programs and core files that use SunOS shared libraries.
2095 Symbols from a shared library cannot be referenced
2096 before the shared library has been linked with the program (this
2097 happens after you type ``run'' and before the function main() is entered).
2098 At any time after this linking (including when examining core files
2099 from dynamically linked programs), gdb reads the symbols from each
2100 shared library when you type the ``sharedlibrary'' command.
2101 It can be abbreviated ``share''.
2103 sharedlibrary REGEXP: Load shared object library symbols for files
2104 matching a unix regular expression. No argument
2105 indicates to load symbols for all shared libraries.
2107 info sharedlibrary: Status of loaded shared libraries.
2112 A watchpoint stops execution of a program whenever the value of an
2113 expression changes. Checking for this slows down execution
2114 tremendously whenever you are in the scope of the expression, but is
2115 quite useful for catching tough ``bit-spreader'' or pointer misuse
2116 problems. Some machines such as the 386 have hardware for doing this
2117 more quickly, and future versions of gdb will use this hardware.
2119 watch EXP: Set a watchpoint (breakpoint) for an expression.
2121 info watchpoints: Information about your watchpoints.
2123 delete N: Deletes watchpoint number N (same as breakpoints).
2124 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2125 enable N: Re-enables watchpoint number N (same as breakpoints).
2128 * C++ multiple inheritance
2130 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2133 * C++ exception handling
2135 Gdb now supports limited C++ exception handling. Besides the existing
2136 ability to breakpoint on an exception handler, gdb can breakpoint on
2137 the raising of an exception (before the stack is peeled back to the
2140 catch FOO: If there is a FOO exception handler in the dynamic scope,
2141 set a breakpoint to catch exceptions which may be raised there.
2142 Multiple exceptions (``catch foo bar baz'') may be caught.
2144 info catch: Lists all exceptions which may be caught in the
2145 current stack frame.
2148 * Minor command changes
2150 The command ``call func (arg, arg, ...)'' now acts like the print
2151 command, except it does not print or save a value if the function's result
2152 is void. This is similar to dbx usage.
2154 The ``up'' and ``down'' commands now always print the frame they end up
2155 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2156 frames without printing.
2158 * New directory command
2160 'dir' now adds directories to the FRONT of the source search path.
2161 The path starts off empty. Source files that contain debug information
2162 about the directory in which they were compiled can be found even
2163 with an empty path; Sun CC and GCC include this information. If GDB can't
2164 find your source file in the current directory, type "dir .".
2166 * Configuring GDB for compilation
2168 For normal use, type ``./configure host''. See README or gdb.texinfo
2171 GDB now handles cross debugging. If you are remotely debugging between
2172 two different machines, type ``./configure host -target=targ''.
2173 Host is the machine where GDB will run; targ is the machine
2174 where the program that you are debugging will run.
projects / external / binutils.git / blob