1 What has changed in GDB?
2 (Organized release by release)
4 *** Changes since GDB 5.3:
6 *** Changes in GDB 5.3:
8 * ``gdbserver'' now supports multi-threaded applications on some targets
10 Support for debugging multi-threaded applications which use
11 the GNU/Linux LinuxThreads package has been added for
12 arm*-*-linux*-gnu*, i[3456]86-*-linux*-gnu*, mips*-*-linux*-gnu*,
13 powerpc*-*-linux*-gnu*, and sh*-*-linux*-gnu*.
15 * GDB now supports C/C++ preprocessor macros.
17 GDB now expands preprocessor macro invocations in C/C++ expressions,
18 and provides various commands for showing macro definitions and how
21 The new command `macro expand EXPRESSION' expands any macro
22 invocations in expression, and shows the result.
24 The new command `show macro MACRO-NAME' shows the definition of the
25 macro named MACRO-NAME, and where it was defined.
27 Most compilers don't include information about macros in the debugging
28 information by default. In GCC 3.1, for example, you need to compile
29 your program with the options `-gdwarf-2 -g3'. If the macro
30 information is present in the executable, GDB will read it.
32 * Multi-arched targets.
34 DEC Alpha (partial) alpha*-*-*
35 DEC VAX (partial) vax-*-*
37 National Semiconductor NS32000 (partial) ns32k-*-*
38 Motorola 68000 (partial) m68k-*-*
39 Motorola MCORE mcore-*-*
43 Fujitsu FRV architecture added by Red Hat frv*-*-*
46 * New native configurations
48 Alpha NetBSD alpha*-*-netbsd*
49 SH NetBSD sh*-*-netbsdelf*
50 MIPS NetBSD mips*-*-netbsd*
51 UltraSPARC NetBSD sparc64-*-netbsd*
53 * OBSOLETE configurations and files
55 Configurations that have been declared obsolete in this release have
56 been commented out. Unless there is activity to revive these
57 configurations, the next release of GDB will have their sources
60 Mitsubishi D30V d30v-*-*
61 OS/9000 i[34]86-*-os9k
62 IBM AIX PS/2 i[3456]86-*-aix
63 Fujitsu FR30 fr30-*-elf*
64 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
65 Argonaut Risc Chip (ARC) arc-*-*
66 i386 running Mach 3.0 i[3456]86-*-mach3*
67 i386 running Mach i[3456]86-*-mach*
68 i386 running OSF/1 i[3456]86-*osf1mk*
69 HP/Apollo 68k Family m68*-apollo*-sysv*,
71 m68*-hp-bsd*, m68*-hp-hpux*
72 I960 with MON960 i960-*-coff
76 CHILL, a Pascal like language used by telecommunications companies.
78 * REMOVED configurations and files
80 AMD 29k family via UDI a29k-amd-udi, udi29k
81 A29K VxWorks a29k-*-vxworks
82 AMD 29000 embedded, using EBMON a29k-none-none
83 AMD 29000 embedded with COFF a29k-none-coff
84 AMD 29000 embedded with a.out a29k-none-aout
86 testsuite/gdb.hp/gdb.threads-hp/ directory
88 * New command "set max-user-call-depth <nnn>"
90 This command allows the user to limit the call depth of user-defined
91 commands. The default is 1024.
93 * Changes in FreeBSD/i386 native debugging.
95 Support for the "generate-core-file" has been added.
97 * New commands "dump", "append", and "restore".
99 These commands allow data to be copied from target memory
100 to a bfd-format or binary file (dump and append), and back
101 from a file into memory (restore).
103 * Improved "next/step" support on multi-processor Alpha Tru64.
105 The previous single-step mechanism could cause unpredictable problems,
106 including the random appearance of SIGSEGV or SIGTRAP signals. The use
107 of a software single-step mechanism prevents this.
109 *** Changes in GDB 5.2.1:
117 gdb/182: gdb/323: gdb/237: On alpha, gdb was reporting:
118 mdebugread.c:2443: gdb-internal-error: sect_index_data not initialized
119 Fix, by Joel Brobecker imported from mainline.
121 gdb/439: gdb/291: On some ELF object files, gdb was reporting:
122 dwarf2read.c:1072: gdb-internal-error: sect_index_text not initialize
123 Fix, by Fred Fish, imported from mainline.
125 Dwarf2 .debug_frame & .eh_frame handler improved in many ways.
126 Surprisingly enough, it works now.
127 By Michal Ludvig, imported from mainline.
129 i386 hardware watchpoint support:
130 avoid misses on second run for some targets.
131 By Pierre Muller, imported from mainline.
133 *** Changes in GDB 5.2:
135 * New command "set trust-readonly-sections on[off]".
137 This command is a hint that tells gdb that read-only sections
138 really are read-only (ie. that their contents will not change).
139 In this mode, gdb will go to the object file rather than the
140 target to read memory from read-only sections (such as ".text").
141 This can be a significant performance improvement on some
142 (notably embedded) targets.
144 * New command "generate-core-file" (or "gcore").
146 This new gdb command allows the user to drop a core file of the child
147 process state at any time. So far it's been implemented only for
148 GNU/Linux and Solaris, but should be relatively easily ported to other
149 hosts. Argument is core file name (defaults to core.<pid>).
151 * New command line option
153 GDB now accepts --pid or -p followed by a process id.
155 * Change in command line behavior -- corefiles vs. process ids.
157 There is a subtle behavior in the way in which GDB handles
158 command line arguments. The first non-flag argument is always
159 a program to debug, but the second non-flag argument may either
160 be a corefile or a process id. Previously, GDB would attempt to
161 open the second argument as a corefile, and if that failed, would
162 issue a superfluous error message and then attempt to attach it as
163 a process. Now, if the second argument begins with a non-digit,
164 it will be treated as a corefile. If it begins with a digit,
165 GDB will attempt to attach it as a process, and if no such process
166 is found, will then attempt to open it as a corefile.
168 * Changes in ARM configurations.
170 Multi-arch support is enabled for all ARM configurations. The ARM/NetBSD
171 configuration is fully multi-arch.
173 * New native configurations
175 ARM NetBSD arm*-*-netbsd*
176 x86 OpenBSD i[3456]86-*-openbsd*
177 AMD x86-64 running GNU/Linux x86_64-*-linux-*
178 Sparc64 running FreeBSD sparc64-*-freebsd*
182 Sanyo XStormy16 xstormy16-elf
184 * OBSOLETE configurations and files
186 Configurations that have been declared obsolete in this release have
187 been commented out. Unless there is activity to revive these
188 configurations, the next release of GDB will have their sources
191 AMD 29k family via UDI a29k-amd-udi, udi29k
192 A29K VxWorks a29k-*-vxworks
193 AMD 29000 embedded, using EBMON a29k-none-none
194 AMD 29000 embedded with COFF a29k-none-coff
195 AMD 29000 embedded with a.out a29k-none-aout
197 testsuite/gdb.hp/gdb.threads-hp/ directory
199 * REMOVED configurations and files
201 TI TMS320C80 tic80-*-*
203 PowerPC Solaris powerpcle-*-solaris*
204 PowerPC Windows NT powerpcle-*-cygwin32
205 PowerPC Netware powerpc-*-netware*
206 Harris/CXUX m88k m88*-harris-cxux*
207 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
208 ns32k-utek-sysv* ns32k-utek-*
209 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
210 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
211 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
212 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
213 Apple Macintosh (MPW) host and target N/A host, powerpc-*-macos*
215 * Changes to command line processing
217 The new `--args' feature can be used to specify command-line arguments
218 for the inferior from gdb's command line.
220 * Changes to key bindings
222 There is a new `operate-and-get-next' function bound to `C-o'.
224 *** Changes in GDB 5.1.1
226 Fix compile problem on DJGPP.
228 Fix a problem with floating-point registers on the i386 being
231 Fix to stop GDB crashing on .debug_str debug info.
233 Numerous documentation fixes.
235 Numerous testsuite fixes.
237 *** Changes in GDB 5.1:
239 * New native configurations
241 Alpha FreeBSD alpha*-*-freebsd*
242 x86 FreeBSD 3.x and 4.x i[3456]86*-freebsd[34]*
243 MIPS GNU/Linux mips*-*-linux*
244 MIPS SGI Irix 6.x mips*-sgi-irix6*
246 s390 and s390x GNU/Linux {s390,s390x}-*-linux*
250 Motorola 68HC11 and 68HC12 m68hc11-elf
252 UltraSparc running GNU/Linux sparc64-*-linux*
254 * OBSOLETE configurations and files
256 x86 FreeBSD before 2.2 i[3456]86*-freebsd{1,2.[01]}*,
257 Harris/CXUX m88k m88*-harris-cxux*
258 Most ns32k hosts and targets ns32k-*-mach3* ns32k-umax-*
259 ns32k-utek-sysv* ns32k-utek-*
260 TI TMS320C80 tic80-*-*
262 Ultracomputer (29K) running Sym1 a29k-nyu-sym1 a29k-*-kern*
263 PowerPC Solaris powerpcle-*-solaris*
264 PowerPC Windows NT powerpcle-*-cygwin32
265 PowerPC Netware powerpc-*-netware*
266 SunOS 4.0.Xi on i386 i[3456]86-*-sunos*
267 Sony NEWS (68K) running NEWSOS 3.x m68*-sony-sysv news
268 ISI Optimum V (3.05) under 4.3bsd. m68*-isi-*
269 Apple Macintosh (MPW) host N/A
271 stuff.c (Program to stuff files into a specially prepared space in kdb)
272 kdb-start.c (Main loop for the standalone kernel debugger)
274 Configurations that have been declared obsolete in this release have
275 been commented out. Unless there is activity to revive these
276 configurations, the next release of GDB will have their sources
279 * REMOVED configurations and files
281 Altos 3068 m68*-altos-*
282 Convex c1-*-*, c2-*-*
284 ARM RISCix arm-*-* (as host)
288 * GDB has been converted to ISO C.
290 GDB's source code has been converted to ISO C. In particular, the
291 sources are fully protoized, and rely on standard headers being
296 * "info symbol" works on platforms which use COFF, ECOFF, XCOFF, and NLM.
298 * The MI enabled by default.
300 The new machine oriented interface (MI) introduced in GDB 5.0 has been
301 revised and enabled by default. Packages which use GDB as a debugging
302 engine behind a UI or another front end are encouraged to switch to
303 using the GDB/MI interface, instead of the old annotations interface
304 which is now deprecated.
306 * Support for debugging Pascal programs.
308 GDB now includes support for debugging Pascal programs. The following
309 main features are supported:
311 - Pascal-specific data types such as sets;
313 - automatic recognition of Pascal sources based on file-name
316 - Pascal-style display of data types, variables, and functions;
318 - a Pascal expression parser.
320 However, some important features are not yet supported.
322 - Pascal string operations are not supported at all;
324 - there are some problems with boolean types;
326 - Pascal type hexadecimal constants are not supported
327 because they conflict with the internal variables format;
329 - support for Pascal objects and classes is not full yet;
331 - unlike Pascal, GDB is case-sensitive for symbol names.
333 * Changes in completion.
335 Commands such as `shell', `run' and `set args', which pass arguments
336 to inferior programs, now complete on file names, similar to what
337 users expect at the shell prompt.
339 Commands which accept locations, such as `disassemble', `print',
340 `breakpoint', `until', etc. now complete on filenames as well as
341 program symbols. Thus, if you type "break foob TAB", and the source
342 files linked into the programs include `foobar.c', that file name will
343 be one of the candidates for completion. However, file names are not
344 considered for completion after you typed a colon that delimits a file
345 name from a name of a function in that file, as in "break foo.c:bar".
347 `set demangle-style' completes on available demangling styles.
349 * New platform-independent commands:
351 It is now possible to define a post-hook for a command as well as a
352 hook that runs before the command. For more details, see the
353 documentation of `hookpost' in the GDB manual.
355 * Changes in GNU/Linux native debugging.
357 Support for debugging multi-threaded programs has been completely
358 revised for all platforms except m68k and sparc. You can now debug as
359 many threads as your system allows you to have.
361 Attach/detach is supported for multi-threaded programs.
363 Support for SSE registers was added for x86. This doesn't work for
364 multi-threaded programs though.
366 * Changes in MIPS configurations.
368 Multi-arch support is enabled for all MIPS configurations.
370 GDB can now be built as native debugger on SGI Irix 6.x systems for
371 debugging n32 executables. (Debugging 64-bit executables is not yet
374 * Unified support for hardware watchpoints in all x86 configurations.
376 Most (if not all) native x86 configurations support hardware-assisted
377 breakpoints and watchpoints in a unified manner. This support
378 implements debug register sharing between watchpoints, which allows to
379 put a virtually infinite number of watchpoints on the same address,
380 and also supports watching regions up to 16 bytes with several debug
383 The new maintenance command `maintenance show-debug-regs' toggles
384 debugging print-outs in functions that insert, remove, and test
385 watchpoints and hardware breakpoints.
387 * Changes in the DJGPP native configuration.
389 New command ``info dos sysinfo'' displays assorted information about
390 the CPU, OS, memory, and DPMI server.
392 New commands ``info dos gdt'', ``info dos ldt'', and ``info dos idt''
393 display information about segment descriptors stored in GDT, LDT, and
396 New commands ``info dos pde'' and ``info dos pte'' display entries
397 from Page Directory and Page Tables (for now works with CWSDPMI only).
398 New command ``info dos address-pte'' displays the Page Table entry for
399 a given linear address.
401 GDB can now pass command lines longer than 126 characters to the
402 program being debugged (requires an update to the libdbg.a library
403 which is part of the DJGPP development kit).
405 DWARF2 debug info is now supported.
407 It is now possible to `step' and `next' through calls to `longjmp'.
409 * Changes in documentation.
411 All GDB documentation was converted to GFDL, the GNU Free
412 Documentation License.
414 Tracepoints-related commands are now fully documented in the GDB
417 TUI, the Text-mode User Interface, is now documented in the manual.
419 Tracepoints-related commands are now fully documented in the GDB
422 The "GDB Internals" manual now has an index. It also includes
423 documentation of `ui_out' functions, GDB coding standards, x86
424 hardware watchpoints, and memory region attributes.
426 * GDB's version number moved to ``version.in''
428 The Makefile variable VERSION has been replaced by the file
429 ``version.in''. People creating GDB distributions should update the
430 contents of this file.
434 GUD support is now a standard part of the EMACS distribution.
436 *** Changes in GDB 5.0:
438 * Improved support for debugging FP programs on x86 targets
440 Unified and much-improved support for debugging floating-point
441 programs on all x86 targets. In particular, ``info float'' now
442 displays the FP registers in the same format on all x86 targets, with
443 greater level of detail.
445 * Improvements and bugfixes in hardware-assisted watchpoints
447 It is now possible to watch array elements, struct members, and
448 bitfields with hardware-assisted watchpoints. Data-read watchpoints
449 on x86 targets no longer erroneously trigger when the address is
452 * Improvements in the native DJGPP version of GDB
454 The distribution now includes all the scripts and auxiliary files
455 necessary to build the native DJGPP version on MS-DOS/MS-Windows
456 machines ``out of the box''.
458 The DJGPP version can now debug programs that use signals. It is
459 possible to catch signals that happened in the debuggee, deliver
460 signals to it, interrupt it with Ctrl-C, etc. (Previously, a signal
461 would kill the program being debugged.) Programs that hook hardware
462 interrupts (keyboard, timer, etc.) can also be debugged.
464 It is now possible to debug DJGPP programs that redirect their
465 standard handles or switch them to raw (as opposed to cooked) mode, or
466 even close them. The command ``run < foo > bar'' works as expected,
467 and ``info terminal'' reports useful information about the debuggee's
468 terminal, including raw/cooked mode, redirection, etc.
470 The DJGPP version now uses termios functions for console I/O, which
471 enables debugging graphics programs. Interrupting GDB with Ctrl-C
474 DOS-style file names with drive letters are now fully supported by
477 It is now possible to debug DJGPP programs that switch their working
478 directory. It is also possible to rerun the debuggee any number of
479 times without restarting GDB; thus, you can use the same setup,
480 breakpoints, etc. for many debugging sessions.
482 * New native configurations
484 ARM GNU/Linux arm*-*-linux*
485 PowerPC GNU/Linux powerpc-*-linux*
489 Motorola MCore mcore-*-*
490 x86 VxWorks i[3456]86-*-vxworks*
491 PowerPC VxWorks powerpc-*-vxworks*
492 TI TMS320C80 tic80-*-*
494 * OBSOLETE configurations
496 Altos 3068 m68*-altos-*
497 Convex c1-*-*, c2-*-*
499 ARM RISCix arm-*-* (as host)
502 Configurations that have been declared obsolete will be commented out,
503 but the code will be left in place. If there is no activity to revive
504 these configurations before the next release of GDB, the sources will
505 be permanently REMOVED.
507 * Gould support removed
509 Support for the Gould PowerNode and NP1 has been removed.
511 * New features for SVR4
513 On SVR4 native platforms (such as Solaris), if you attach to a process
514 without first loading a symbol file, GDB will now attempt to locate and
515 load symbols from the running process's executable file.
517 * Many C++ enhancements
519 C++ support has been greatly improved. Overload resolution now works properly
520 in almost all cases. RTTI support is on the way.
522 * Remote targets can connect to a sub-program
524 A popen(3) style serial-device has been added. This device starts a
525 sub-process (such as a stand-alone simulator) and then communicates
526 with that. The sub-program to run is specified using the syntax
527 ``|<program> <args>'' vis:
529 (gdb) set remotedebug 1
530 (gdb) target extended-remote |mn10300-elf-sim program-args
532 * MIPS 64 remote protocol
534 A long standing bug in the mips64 remote protocol where by GDB
535 expected certain 32 bit registers (ex SR) to be transfered as 32
536 instead of 64 bits has been fixed.
538 The command ``set remote-mips64-transfers-32bit-regs on'' has been
539 added to provide backward compatibility with older versions of GDB.
541 * ``set remotebinarydownload'' replaced by ``set remote X-packet''
543 The command ``set remotebinarydownload'' command has been replaced by
544 ``set remote X-packet''. Other commands in ``set remote'' family
545 include ``set remote P-packet''.
547 * Breakpoint commands accept ranges.
549 The breakpoint commands ``enable'', ``disable'', and ``delete'' now
550 accept a range of breakpoints, e.g. ``5-7''. The tracepoint command
551 ``tracepoint passcount'' also accepts a range of tracepoints.
553 * ``apropos'' command added.
555 The ``apropos'' command searches through command names and
556 documentation strings, printing out matches, making it much easier to
557 try to find a command that does what you are looking for.
561 A new machine oriented interface (MI) has been added to GDB. This
562 interface is designed for debug environments running GDB as a separate
563 process. This is part of the long term libGDB project. See the
564 "GDB/MI" chapter of the GDB manual for further information. It can be
565 enabled by configuring with:
567 .../configure --enable-gdbmi
569 *** Changes in GDB-4.18:
571 * New native configurations
573 HP-UX 10.20 hppa*-*-hpux10.20
574 HP-UX 11.x hppa*-*-hpux11.0*
575 M68K GNU/Linux m68*-*-linux*
579 Fujitsu FR30 fr30-*-elf*
580 Intel StrongARM strongarm-*-*
581 Mitsubishi D30V d30v-*-*
583 * OBSOLETE configurations
585 Gould PowerNode, NP1 np1-*-*, pn-*-*
587 Configurations that have been declared obsolete will be commented out,
588 but the code will be left in place. If there is no activity to revive
589 these configurations before the next release of GDB, the sources will
590 be permanently REMOVED.
594 As a compatibility experiment, GDB's source files buildsym.h and
595 buildsym.c have been converted to pure standard C, no longer
596 containing any K&R compatibility code. We believe that all systems in
597 use today either come with a standard C compiler, or have a GCC port
598 available. If this is not true, please report the affected
599 configuration to bug-gdb@gnu.org immediately. See the README file for
600 information about getting a standard C compiler if you don't have one
605 GDB now uses readline 2.2.
607 * set extension-language
609 You can now control the mapping between filename extensions and source
610 languages by using the `set extension-language' command. For instance,
611 you can ask GDB to treat .c files as C++ by saying
612 set extension-language .c c++
613 The command `info extensions' lists all of the recognized extensions
614 and their associated languages.
616 * Setting processor type for PowerPC and RS/6000
618 When GDB is configured for a powerpc*-*-* or an rs6000*-*-* target,
619 you can use the `set processor' command to specify what variant of the
620 PowerPC family you are debugging. The command
624 sets the PowerPC/RS6000 variant to NAME. GDB knows about the
625 following PowerPC and RS6000 variants:
627 ppc-uisa PowerPC UISA - a PPC processor as viewed by user-level code
628 rs6000 IBM RS6000 ("POWER") architecture, user-level view
630 403GC IBM PowerPC 403GC
631 505 Motorola PowerPC 505
632 860 Motorola PowerPC 860 or 850
633 601 Motorola PowerPC 601
634 602 Motorola PowerPC 602
635 603 Motorola/IBM PowerPC 603 or 603e
636 604 Motorola PowerPC 604 or 604e
637 750 Motorola/IBM PowerPC 750 or 750
639 At the moment, this command just tells GDB what to name the
640 special-purpose processor registers. Since almost all the affected
641 registers are inaccessible to user-level programs, this command is
642 only useful for remote debugging in its present form.
646 Thanks to a major code donation from Hewlett-Packard, GDB now has much
647 more extensive support for HP-UX. Added features include shared
648 library support, kernel threads and hardware watchpoints for 11.00,
649 support for HP's ANSI C and C++ compilers, and a compatibility mode
650 for xdb and dbx commands.
654 HP's donation includes the new concept of catchpoints, which is a
655 generalization of the old catch command. On HP-UX, it is now possible
656 to catch exec, fork, and vfork, as well as library loading.
658 This means that the existing catch command has changed; its first
659 argument now specifies the type of catch to be set up. See the
660 output of "help catch" for a list of catchpoint types.
662 * Debugging across forks
664 On HP-UX, you can choose which process to debug when a fork() happens
669 HP has donated a curses-based terminal user interface (TUI). To get
670 it, build with --enable-tui. Although this can be enabled for any
671 configuration, at present it only works for native HP debugging.
673 * GDB remote protocol additions
675 A new protocol packet 'X' that writes binary data is now available.
676 Default behavior is to try 'X', then drop back to 'M' if the stub
677 fails to respond. The settable variable `remotebinarydownload'
678 allows explicit control over the use of 'X'.
680 For 64-bit targets, the memory packets ('M' and 'm') can now contain a
681 full 64-bit address. The command
683 set remoteaddresssize 32
685 can be used to revert to the old behaviour. For existing remote stubs
686 the change should not be noticed, as the additional address information
689 In order to assist in debugging stubs, you may use the maintenance
690 command `packet' to send any text string to the stub. For instance,
692 maint packet heythere
694 sends the packet "$heythere#<checksum>". Note that it is very easy to
695 disrupt a debugging session by sending the wrong packet at the wrong
698 The compare-sections command allows you to compare section data on the
699 target to what is in the executable file without uploading or
700 downloading, by comparing CRC checksums.
702 * Tracing can collect general expressions
704 You may now collect general expressions at tracepoints. This requires
705 further additions to the target-side stub; see tracepoint.c and
706 doc/agentexpr.texi for further details.
708 * mask-address variable for Mips
710 For Mips targets, you may control the zeroing of the upper 32 bits of
711 a 64-bit address by entering `set mask-address on'. This is mainly
712 of interest to users of embedded R4xxx and R5xxx processors.
714 * Higher serial baud rates
716 GDB's serial code now allows you to specify baud rates 57600, 115200,
717 230400, and 460800 baud. (Note that your host system may not be able
718 to achieve all of these rates.)
722 The i960 configuration now includes an initial implementation of a
723 builtin simulator, contributed by Jim Wilson.
726 *** Changes in GDB-4.17:
728 * New native configurations
730 Alpha GNU/Linux alpha*-*-linux*
731 Unixware 2.x i[3456]86-unixware2*
732 Irix 6.x mips*-sgi-irix6*
733 PowerPC GNU/Linux powerpc-*-linux*
734 PowerPC Solaris powerpcle-*-solaris*
735 Sparc GNU/Linux sparc-*-linux*
736 Motorola sysV68 R3V7.1 m68k-motorola-sysv
740 Argonaut Risc Chip (ARC) arc-*-*
741 Hitachi H8/300S h8300*-*-*
742 Matsushita MN10200 w/simulator mn10200-*-*
743 Matsushita MN10300 w/simulator mn10300-*-*
744 MIPS NEC VR4100 mips64*vr4100*{,el}-*-elf*
745 MIPS NEC VR5000 mips64*vr5000*{,el}-*-elf*
746 MIPS Toshiba TX39 mips64*tx39*{,el}-*-elf*
747 Mitsubishi D10V w/simulator d10v-*-*
748 Mitsubishi M32R/D w/simulator m32r-*-elf*
749 Tsqware Sparclet sparclet-*-*
750 NEC V850 w/simulator v850-*-*
752 * New debugging protocols
754 ARM with RDI protocol arm*-*-*
755 M68K with dBUG monitor m68*-*-{aout,coff,elf}
756 DDB and LSI variants of PMON protocol mips*-*-*
757 PowerPC with DINK32 monitor powerpc{,le}-*-eabi
758 PowerPC with SDS protocol powerpc{,le}-*-eabi
759 Macraigor OCD (Wiggler) devices powerpc{,le}-*-eabi
763 All configurations can now understand and use the DWARF 2 debugging
764 format. The choice is automatic, if the symbol file contains DWARF 2
769 GDB now includes basic Java language support. This support is
770 only useful with Java compilers that produce native machine code.
772 * solib-absolute-prefix and solib-search-path
774 For SunOS and SVR4 shared libraries, you may now set the prefix for
775 loading absolute shared library symbol files, and the search path for
776 locating non-absolute shared library symbol files.
778 * Live range splitting
780 GDB can now effectively debug code for which GCC has performed live
781 range splitting as part of its optimization. See gdb/doc/LRS for
782 more details on the expected format of the stabs information.
786 GDB's support for the GNU Hurd, including thread debugging, has been
787 updated to work with current versions of the Hurd.
791 GDB's ARM target configuration now handles the ARM7T (Thumb) 16-bit
792 instruction set. ARM GDB automatically detects when Thumb
793 instructions are in use, and adjusts disassembly and backtracing
798 GDB's MIPS target configurations now handle the MIP16 16-bit
803 GDB now includes support for overlays; if an executable has been
804 linked such that multiple sections are based at the same address, GDB
805 will decide which section to use for symbolic info. You can choose to
806 control the decision manually, using overlay commands, or implement
807 additional target-side support and use "overlay load-target" to bring
808 in the overlay mapping. Do "help overlay" for more detail.
812 The command "info symbol <address>" displays information about
813 the symbol at the specified address.
817 The standard remote protocol now includes an extension that allows
818 asynchronous collection and display of trace data. This requires
819 extensive support in the target-side debugging stub. Tracing mode
820 includes a new interaction mode in GDB and new commands: see the
821 file tracepoint.c for more details.
825 Configurations for embedded MIPS now include a simulator contributed
826 by Cygnus Solutions. The simulator supports the instruction sets
827 of most MIPS variants.
831 Sparc configurations may now include the ERC32 simulator contributed
832 by the European Space Agency. The simulator is not built into
833 Sparc targets by default; configure with --enable-sim to include it.
837 For target configurations that may include multiple variants of a
838 basic architecture (such as MIPS and SH), you may now set the
839 architecture explicitly. "set arch" sets, "info arch" lists
840 the possible architectures.
842 *** Changes in GDB-4.16:
844 * New native configurations
846 Windows 95, x86 Windows NT i[345]86-*-cygwin32
847 M68K NetBSD m68k-*-netbsd*
848 PowerPC AIX 4.x powerpc-*-aix*
849 PowerPC MacOS powerpc-*-macos*
850 PowerPC Windows NT powerpcle-*-cygwin32
851 RS/6000 AIX 4.x rs6000-*-aix4*
855 ARM with RDP protocol arm-*-*
856 I960 with MON960 i960-*-coff
857 MIPS VxWorks mips*-*-vxworks*
858 MIPS VR4300 with PMON mips64*vr4300{,el}-*-elf*
859 PowerPC with PPCBUG monitor powerpc{,le}-*-eabi*
861 Matra Sparclet sparclet-*-*
865 The powerpc-eabi configuration now includes the PSIM simulator,
866 contributed by Andrew Cagney, with assistance from Mike Meissner.
867 PSIM is a very elaborate model of the PowerPC, including not only
868 basic instruction set execution, but also details of execution unit
869 performance and I/O hardware. See sim/ppc/README for more details.
873 GDB now works with Solaris 2.5.
875 * Windows 95/NT native
877 GDB will now work as a native debugger on Windows 95 and Windows NT.
878 To build it from source, you must use the "gnu-win32" environment,
879 which uses a DLL to emulate enough of Unix to run the GNU tools.
880 Further information, binaries, and sources are available at
881 ftp.cygnus.com, under pub/gnu-win32.
883 * dont-repeat command
885 If a user-defined command includes the command `dont-repeat', then the
886 command will not be repeated if the user just types return. This is
887 useful if the command is time-consuming to run, so that accidental
888 extra keystrokes don't run the same command many times.
890 * Send break instead of ^C
892 The standard remote protocol now includes an option to send a break
893 rather than a ^C to the target in order to interrupt it. By default,
894 GDB will send ^C; to send a break, set the variable `remotebreak' to 1.
896 * Remote protocol timeout
898 The standard remote protocol includes a new variable `remotetimeout'
899 that allows you to set the number of seconds before GDB gives up trying
900 to read from the target. The default value is 2.
902 * Automatic tracking of dynamic object loading (HPUX and Solaris only)
904 By default GDB will automatically keep track of objects as they are
905 loaded and unloaded by the dynamic linker. By using the command `set
906 stop-on-solib-events 1' you can arrange for GDB to stop the inferior
907 when shared library events occur, thus allowing you to set breakpoints
908 in shared libraries which are explicitly loaded by the inferior.
910 Note this feature does not work on hpux8. On hpux9 you must link
911 /usr/lib/end.o into your program. This feature should work
912 automatically on hpux10.
914 * Irix 5.x hardware watchpoint support
916 Irix 5 configurations now support the use of hardware watchpoints.
918 * Mips protocol "SYN garbage limit"
920 When debugging a Mips target using the `target mips' protocol, you
921 may set the number of characters that GDB will ignore by setting
922 the `syn-garbage-limit'. A value of -1 means that GDB will ignore
923 every character. The default value is 1050.
925 * Recording and replaying remote debug sessions
927 If you set `remotelogfile' to the name of a file, gdb will write to it
928 a recording of a remote debug session. This recording may then be
929 replayed back to gdb using "gdbreplay". See gdbserver/README for
930 details. This is useful when you have a problem with GDB while doing
931 remote debugging; you can make a recording of the session and send it
932 to someone else, who can then recreate the problem.
934 * Speedups for remote debugging
936 GDB includes speedups for downloading and stepping MIPS systems using
937 the IDT monitor, fast downloads to the Hitachi SH E7000 emulator,
938 and more efficient S-record downloading.
940 * Memory use reductions and statistics collection
942 GDB now uses less memory and reports statistics about memory usage.
943 Try the `maint print statistics' command, for example.
945 *** Changes in GDB-4.15:
949 The symbol reader for AIX GDB now uses partial symbol tables. This
950 can greatly improve startup time, especially for large executables.
952 * Remote targets use caching
954 Remote targets now use a data cache to speed up communication with the
955 remote side. The data cache could lead to incorrect results because
956 it doesn't know about volatile variables, thus making it impossible to
957 debug targets which use memory mapped I/O devices. `set remotecache
958 off' turns the the data cache off.
960 * Remote targets may have threads
962 The standard remote protocol now includes support for multiple threads
963 in the target system, using new protocol commands 'H' and 'T'. See
964 gdb/remote.c for details.
968 If GDB is configured with `--enable-netrom', then it will include
969 support for the NetROM ROM emulator from XLNT Designs. The NetROM
970 acts as though it is a bank of ROM on the target board, but you can
971 write into it over the network. GDB's support consists only of
972 support for fast loading into the emulated ROM; to debug, you must use
973 another protocol, such as standard remote protocol. The usual
974 sequence is something like
976 target nrom <netrom-hostname>
978 target remote <netrom-hostname>:1235
982 GDB now includes support for the Apple Macintosh, as a host only. It
983 may be run as either an MPW tool or as a standalone application, and
984 it can debug through the serial port. All the usual GDB commands are
985 available, but to the target command, you must supply "serial" as the
986 device type instead of "/dev/ttyXX". See mpw-README in the main
987 directory for more information on how to build. The MPW configuration
988 scripts */mpw-config.in support only a few targets, and only the
989 mips-idt-ecoff target has been tested.
993 GDB configuration now uses autoconf. This is not user-visible,
994 but does simplify configuration and building.
998 GDB now supports hpux10.
1000 *** Changes in GDB-4.14:
1002 * New native configurations
1004 x86 FreeBSD i[345]86-*-freebsd
1005 x86 NetBSD i[345]86-*-netbsd
1006 NS32k NetBSD ns32k-*-netbsd
1007 Sparc NetBSD sparc-*-netbsd
1011 A29K VxWorks a29k-*-vxworks
1012 HP PA PRO embedded (WinBond W89K & Oki OP50N) hppa*-*-pro*
1013 CPU32 EST-300 emulator m68*-*-est*
1014 PowerPC ELF powerpc-*-elf
1017 * Alpha OSF/1 support for procfs
1019 GDB now supports procfs under OSF/1-2.x and higher, which makes it
1020 possible to attach to running processes. As the mounting of the /proc
1021 filesystem is optional on the Alpha, GDB automatically determines
1022 the availability of /proc during startup. This can lead to problems
1023 if /proc is unmounted after GDB has been started.
1025 * Arguments to user-defined commands
1027 User commands may accept up to 10 arguments separated by whitespace.
1028 Arguments are accessed within the user command via $arg0..$arg9. A
1031 print $arg0 + $arg1 + $arg2
1033 To execute the command use:
1036 Defines the command "adder" which prints the sum of its three arguments.
1037 Note the arguments are text substitutions, so they may reference variables,
1038 use complex expressions, or even perform inferior function calls.
1040 * New `if' and `while' commands
1042 This makes it possible to write more sophisticated user-defined
1043 commands. Both commands take a single argument, which is the
1044 expression to evaluate, and must be followed by the commands to
1045 execute, one per line, if the expression is nonzero, the list being
1046 terminated by the word `end'. The `if' command list may include an
1047 `else' word, which causes the following commands to be executed only
1048 if the expression is zero.
1050 * Fortran source language mode
1052 GDB now includes partial support for Fortran 77. It will recognize
1053 Fortran programs and can evaluate a subset of Fortran expressions, but
1054 variables and functions may not be handled correctly. GDB will work
1055 with G77, but does not yet know much about symbols emitted by other
1058 * Better HPUX support
1060 Most debugging facilities now work on dynamic executables for HPPAs
1061 running hpux9 or later. You can attach to running dynamically linked
1062 processes, but by default the dynamic libraries will be read-only, so
1063 for instance you won't be able to put breakpoints in them. To change
1064 that behavior do the following before running the program:
1070 This will cause the libraries to be mapped private and read-write.
1071 To revert to the normal behavior, do this:
1077 You cannot set breakpoints or examine data in the library until after
1078 the library is loaded if the function/data symbols do not have
1081 GDB can now also read debug symbols produced by the HP C compiler on
1082 HPPAs (sorry, no C++, Fortran or 68k support).
1084 * Target byte order now dynamically selectable
1086 You can choose which byte order to use with a target system, via the
1087 commands "set endian big" and "set endian little", and you can see the
1088 current setting by using "show endian". You can also give the command
1089 "set endian auto", in which case GDB will use the byte order
1090 associated with the executable. Currently, only embedded MIPS
1091 configurations support dynamic selection of target byte order.
1093 * New DOS host serial code
1095 This version uses DPMI interrupts to handle buffered I/O, so you
1096 no longer need to run asynctsr when debugging boards connected to
1099 *** Changes in GDB-4.13:
1101 * New "complete" command
1103 This lists all the possible completions for the rest of the line, if it
1104 were to be given as a command itself. This is intended for use by emacs.
1106 * Trailing space optional in prompt
1108 "set prompt" no longer adds a space for you after the prompt you set. This
1109 allows you to set a prompt which ends in a space or one that does not.
1111 * Breakpoint hit counts
1113 "info break" now displays a count of the number of times the breakpoint
1114 has been hit. This is especially useful in conjunction with "ignore"; you
1115 can ignore a large number of breakpoint hits, look at the breakpoint info
1116 to see how many times the breakpoint was hit, then run again, ignoring one
1117 less than that number, and this will get you quickly to the last hit of
1120 * Ability to stop printing at NULL character
1122 "set print null-stop" will cause GDB to stop printing the characters of
1123 an array when the first NULL is encountered. This is useful when large
1124 arrays actually contain only short strings.
1126 * Shared library breakpoints
1128 In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set
1129 breakpoints in shared libraries before the executable is run.
1131 * Hardware watchpoints
1133 There is a new hardware breakpoint for the watch command for sparclite
1134 targets. See gdb/sparclite/hw_breakpoint.note.
1136 Hardware watchpoints are also now supported under GNU/Linux.
1140 Annotations have been added. These are for use with graphical interfaces,
1141 and are still experimental. Currently only gdba.el uses these.
1143 * Improved Irix 5 support
1145 GDB now works properly with Irix 5.2.
1147 * Improved HPPA support
1149 GDB now works properly with the latest GCC and GAS.
1151 * New native configurations
1153 Sequent PTX4 i[34]86-sequent-ptx4
1154 HPPA running OSF/1 hppa*-*-osf*
1155 Atari TT running SVR4 m68*-*-sysv4*
1156 RS/6000 LynxOS rs6000-*-lynxos*
1160 OS/9000 i[34]86-*-os9k
1161 MIPS R4000 mips64*{,el}-*-{ecoff,elf}
1164 * Hitachi SH7000 and E7000-PC ICE support
1166 There is now support for communicating with the Hitachi E7000-PC ICE.
1167 This is available automatically when GDB is configured for the SH.
1171 As usual, a variety of small fixes and improvements, both generic
1172 and configuration-specific. See the ChangeLog for more detail.
1174 *** Changes in GDB-4.12:
1176 * Irix 5 is now supported
1180 GDB-4.12 on the HPPA has a number of changes which make it unable
1181 to debug the output from the currently released versions of GCC and
1182 GAS (GCC 2.5.8 and GAS-2.2 or PAGAS-1.36). Until the next major release
1183 of GCC and GAS, versions of these tools designed to work with GDB-4.12
1184 can be retrieved via anonymous ftp from jaguar.cs.utah.edu:/dist.
1187 *** Changes in GDB-4.11:
1189 * User visible changes:
1193 The "set remotedebug" option is now consistent between the mips remote
1194 target, remote targets using the gdb-specific protocol, UDI (AMD's
1195 debug protocol for the 29k) and the 88k bug monitor. It is now an
1196 integer specifying a debug level (normally 0 or 1, but 2 means more
1197 debugging info for the mips target).
1199 * DEC Alpha native support
1201 GDB now works on the DEC Alpha. GCC 2.4.5 does not produce usable
1202 debug info, but GDB works fairly well with the DEC compiler and should
1203 work with a future GCC release. See the README file for a few
1204 Alpha-specific notes.
1206 * Preliminary thread implementation
1208 GDB now has preliminary thread support for both SGI/Irix and LynxOS.
1210 * LynxOS native and target support for 386
1212 This release has been hosted on LynxOS 2.2, and also can be configured
1213 to remotely debug programs running under LynxOS (see gdb/gdbserver/README
1216 * Improvements in C++ mangling/demangling.
1218 This release has much better g++ debugging, specifically in name
1219 mangling/demangling, virtual function calls, print virtual table,
1220 call methods, ...etc.
1222 *** Changes in GDB-4.10:
1224 * User visible changes:
1226 Remote debugging using the GDB-specific (`target remote') protocol now
1227 supports the `load' command. This is only useful if you have some
1228 other way of getting the stub to the target system, and you can put it
1229 somewhere in memory where it won't get clobbered by the download.
1231 Filename completion now works.
1233 When run under emacs mode, the "info line" command now causes the
1234 arrow to point to the line specified. Also, "info line" prints
1235 addresses in symbolic form (as well as hex).
1237 All vxworks based targets now support a user settable option, called
1238 vxworks-timeout. This option represents the number of seconds gdb
1239 should wait for responses to rpc's. You might want to use this if
1240 your vxworks target is, perhaps, a slow software simulator or happens
1241 to be on the far side of a thin network line.
1245 This release contains support for using a DEC alpha as a GDB host for
1246 cross debugging. Native alpha debugging is not supported yet.
1249 *** Changes in GDB-4.9:
1253 This is the first GDB release which is accompanied by a matching testsuite.
1254 The testsuite requires installation of dejagnu, which should be available
1255 via ftp from most sites that carry GNU software.
1259 'Cfront' style demangling has had its name changed to 'ARM' style, to
1260 emphasize that it was written from the specifications in the C++ Annotated
1261 Reference Manual, not necessarily to be compatible with AT&T cfront. Despite
1262 disclaimers, it still generated too much confusion with users attempting to
1263 use gdb with AT&T cfront.
1267 GDB now uses a standard remote interface to a simulator library.
1268 So far, the library contains simulators for the Zilog Z8001/2, the
1269 Hitachi H8/300, H8/500 and Super-H.
1271 * New targets supported
1273 H8/300 simulator h8300-hitachi-hms or h8300hms
1274 H8/500 simulator h8500-hitachi-hms or h8500hms
1275 SH simulator sh-hitachi-hms or sh
1276 Z8000 simulator z8k-zilog-none or z8ksim
1277 IDT MIPS board over serial line mips-idt-ecoff
1279 Cross-debugging to GO32 targets is supported. It requires a custom
1280 version of the i386-stub.c module which is integrated with the
1281 GO32 memory extender.
1283 * New remote protocols
1285 MIPS remote debugging protocol.
1287 * New source languages supported
1289 This version includes preliminary support for Chill, a Pascal like language
1290 used by telecommunications companies. Chill support is also being integrated
1291 into the GNU compiler, but we don't know when it will be publically available.
1294 *** Changes in GDB-4.8:
1296 * HP Precision Architecture supported
1298 GDB now supports HP PA-RISC machines running HPUX. A preliminary
1299 version of this support was available as a set of patches from the
1300 University of Utah. GDB does not support debugging of programs
1301 compiled with the HP compiler, because HP will not document their file
1302 format. Instead, you must use GCC (version 2.3.2 or later) and PA-GAS
1303 (as available from jaguar.cs.utah.edu:/dist/pa-gas.u4.tar.Z).
1305 Many problems in the preliminary version have been fixed.
1307 * Faster and better demangling
1309 We have improved template demangling and fixed numerous bugs in the GNU style
1310 demangler. It can now handle type modifiers such as `static' or `const'. Wide
1311 character types (wchar_t) are now supported. Demangling of each symbol is now
1312 only done once, and is cached when the symbol table for a file is read in.
1313 This results in a small increase in memory usage for C programs, a moderate
1314 increase in memory usage for C++ programs, and a fantastic speedup in
1317 `Cfront' style demangling still doesn't work with AT&T cfront. It was written
1318 from the specifications in the Annotated Reference Manual, which AT&T's
1319 compiler does not actually implement.
1321 * G++ multiple inheritance compiler problem
1323 In the 2.3.2 release of gcc/g++, how the compiler resolves multiple
1324 inheritance lattices was reworked to properly discover ambiguities. We
1325 recently found an example which causes this new algorithm to fail in a
1326 very subtle way, producing bad debug information for those classes.
1327 The file 'gcc.patch' (in this directory) can be applied to gcc to
1328 circumvent the problem. A future GCC release will contain a complete
1331 The previous G++ debug info problem (mentioned below for the gdb-4.7
1332 release) is fixed in gcc version 2.3.2.
1334 * Improved configure script
1336 The `configure' script will now attempt to guess your system type if
1337 you don't supply a host system type. The old scheme of supplying a
1338 host system triplet is preferable over using this. All the magic is
1339 done in the new `config.guess' script. Examine it for details.
1341 We have also brought our configure script much more in line with the FSF's
1342 version. It now supports the --with-xxx options. In particular,
1343 `--with-minimal-bfd' can be used to make the GDB binary image smaller.
1344 The resulting GDB will not be able to read arbitrary object file formats --
1345 only the format ``expected'' to be used on the configured target system.
1346 We hope to make this the default in a future release.
1348 * Documentation improvements
1350 There's new internal documentation on how to modify GDB, and how to
1351 produce clean changes to the code. We implore people to read it
1352 before submitting changes.
1354 The GDB manual uses new, sexy Texinfo conditionals, rather than arcane
1355 M4 macros. The new texinfo.tex is provided in this release. Pre-built
1356 `info' files are also provided. To build `info' files from scratch,
1357 you will need the latest `makeinfo' release, which will be available in
1358 a future texinfo-X.Y release.
1360 *NOTE* The new texinfo.tex can cause old versions of TeX to hang.
1361 We're not sure exactly which versions have this problem, but it has
1362 been seen in 3.0. We highly recommend upgrading to TeX version 3.141
1363 or better. If that isn't possible, there is a patch in
1364 `texinfo/tex3patch' that will modify `texinfo/texinfo.tex' to work
1365 around this problem.
1369 GDB now supports array constants that can be used in expressions typed in by
1370 the user. The syntax is `{element, element, ...}'. Ie: you can now type
1371 `print {1, 2, 3}', and it will build up an array in memory malloc'd in
1374 The new directory `gdb/sparclite' contains a program that demonstrates
1375 how the sparc-stub.c remote stub runs on a Fujitsu SPARClite processor.
1377 * New native hosts supported
1379 HP/PA-RISC under HPUX using GNU tools hppa1.1-hp-hpux
1380 386 CPUs running SCO Unix 3.2v4 i386-unknown-sco3.2v4
1382 * New targets supported
1384 AMD 29k family via UDI a29k-amd-udi or udi29k
1386 * New file formats supported
1388 BFD now supports reading HP/PA-RISC executables (SOM file format?),
1389 HPUX core files, and SCO 3.2v2 core files.
1393 Attaching to processes now works again; thanks for the many bug reports.
1395 We have also stomped on a bunch of core dumps caused by
1396 printf_filtered("%s") problems.
1398 We eliminated a copyright problem on the rpc and ptrace header files
1399 for VxWorks, which was discovered at the last minute during the 4.7
1400 release. You should now be able to build a VxWorks GDB.
1402 You can now interrupt gdb while an attached process is running. This
1403 will cause the attached process to stop, and give control back to GDB.
1405 We fixed problems caused by using too many file descriptors
1406 for reading symbols from object files and libraries. This was
1407 especially a problem for programs that used many (~100) shared
1410 The `step' command now only enters a subroutine if there is line number
1411 information for the subroutine. Otherwise it acts like the `next'
1412 command. Previously, `step' would enter subroutines if there was
1413 any debugging information about the routine. This avoids problems
1414 when using `cc -g1' on MIPS machines.
1416 * Internal improvements
1418 GDB's internal interfaces have been improved to make it easier to support
1419 debugging of multiple languages in the future.
1421 GDB now uses a common structure for symbol information internally.
1422 Minimal symbols (derived from linkage symbols in object files), partial
1423 symbols (from a quick scan of debug information), and full symbols
1424 contain a common subset of information, making it easier to write
1425 shared code that handles any of them.
1427 * New command line options
1429 We now accept --silent as an alias for --quiet.
1433 The memory-mapped-malloc library is now licensed under the GNU Library
1434 General Public License.
1436 *** Changes in GDB-4.7:
1438 * Host/native/target split
1440 GDB has had some major internal surgery to untangle the support for
1441 hosts and remote targets. Now, when you configure GDB for a remote
1442 target, it will no longer load in all of the support for debugging
1443 local programs on the host. When fully completed and tested, this will
1444 ensure that arbitrary host/target combinations are possible.
1446 The primary conceptual shift is to separate the non-portable code in
1447 GDB into three categories. Host specific code is required any time GDB
1448 is compiled on that host, regardless of the target. Target specific
1449 code relates to the peculiarities of the target, but can be compiled on
1450 any host. Native specific code is everything else: it can only be
1451 built when the host and target are the same system. Child process
1452 handling and core file support are two common `native' examples.
1454 GDB's use of /proc for controlling Unix child processes is now cleaner.
1455 It has been split out into a single module under the `target_ops' vector,
1456 plus two native-dependent functions for each system that uses /proc.
1458 * New hosts supported
1460 HP/Apollo 68k (under the BSD domain) m68k-apollo-bsd or apollo68bsd
1461 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1462 386 CPUs running SCO Unix i386-unknown-scosysv322 or i386sco
1464 * New targets supported
1466 Fujitsu SPARClite sparclite-fujitsu-none or sparclite
1467 68030 and CPU32 m68030-*-*, m68332-*-*
1469 * New native hosts supported
1471 386 CPUs running various BSD ports i386-unknown-bsd or 386bsd
1472 (386bsd is not well tested yet)
1473 386 CPUs running SCO Unix i386-unknown-scosysv322 or sco
1475 * New file formats supported
1477 BFD now supports COFF files for the Zilog Z8000 microprocessor. It
1478 supports reading of `a.out.adobe' object files, which are an a.out
1479 format extended with minimal information about multiple sections.
1483 `show copying' is the same as the old `info copying'.
1484 `show warranty' is the same as `info warrantee'.
1485 These were renamed for consistency. The old commands continue to work.
1487 `info handle' is a new alias for `info signals'.
1489 You can now define pre-command hooks, which attach arbitrary command
1490 scripts to any command. The commands in the hook will be executed
1491 prior to the user's command. You can also create a hook which will be
1492 executed whenever the program stops. See gdb.texinfo.
1496 We now deal with Cfront style name mangling, and can even extract type
1497 info from mangled symbols. GDB can automatically figure out which
1498 symbol mangling style your C++ compiler uses.
1500 Calling of methods and virtual functions has been improved as well.
1504 The crash that occured when debugging Sun Ansi-C compiled binaries is
1505 fixed. This was due to mishandling of the extra N_SO stabs output
1508 We also finally got Ultrix 4.2 running in house, and fixed core file
1509 support, with help from a dozen people on the net.
1511 John M. Farrell discovered that the reason that single-stepping was so
1512 slow on all of the Mips based platforms (primarily SGI and DEC) was
1513 that we were trying to demangle and lookup a symbol used for internal
1514 purposes on every instruction that was being stepped through. Changing
1515 the name of that symbol so that it couldn't be mistaken for a C++
1516 mangled symbol sped things up a great deal.
1518 Rich Pixley sped up symbol lookups in general by getting much smarter
1519 about when C++ symbol mangling is necessary. This should make symbol
1520 completion (TAB on the command line) much faster. It's not as fast as
1521 we'd like, but it's significantly faster than gdb-4.6.
1525 A new user controllable variable 'call_scratch_address' can
1526 specify the location of a scratch area to be used when GDB
1527 calls a function in the target. This is necessary because the
1528 usual method of putting the scratch area on the stack does not work
1529 in systems that have separate instruction and data spaces.
1531 We integrated changes to support the 29k UDI (Universal Debugger
1532 Interface), but discovered at the last minute that we didn't have all
1533 of the appropriate copyright paperwork. We are working with AMD to
1534 resolve this, and hope to have it available soon.
1538 We have sped up the remote serial line protocol, especially for targets
1539 with lots of registers. It now supports a new `expedited status' ('T')
1540 message which can be used in place of the existing 'S' status message.
1541 This allows the remote stub to send only the registers that GDB
1542 needs to make a quick decision about single-stepping or conditional
1543 breakpoints, eliminating the need to fetch the entire register set for
1544 each instruction being stepped through.
1546 The GDB remote serial protocol now implements a write-through cache for
1547 registers, only re-reading the registers if the target has run.
1549 There is also a new remote serial stub for SPARC processors. You can
1550 find it in gdb-4.7/gdb/sparc-stub.c. This was written to support the
1551 Fujitsu SPARClite processor, but will run on any stand-alone SPARC
1552 processor with a serial port.
1556 Configure.in files have become much easier to read and modify. A new
1557 `table driven' format makes it more obvious what configurations are
1558 supported, and what files each one uses.
1562 There is a new opcodes library which will eventually contain all of the
1563 disassembly routines and opcode tables. At present, it only contains
1564 Sparc and Z8000 routines. This will allow the assembler, debugger, and
1565 disassembler (binutils/objdump) to share these routines.
1567 The libiberty library is now copylefted under the GNU Library General
1568 Public License. This allows more liberal use, and was done so libg++
1569 can use it. This makes no difference to GDB, since the Library License
1570 grants all the rights from the General Public License.
1574 The file gdb-4.7/gdb/doc/stabs.texinfo is a (relatively) complete
1575 reference to the stabs symbol info used by the debugger. It is (as far
1576 as we know) the only published document on this fascinating topic. We
1577 encourage you to read it, compare it to the stabs information on your
1578 system, and send improvements on the document in general (to
1579 bug-gdb@prep.ai.mit.edu).
1581 And, of course, many bugs have been fixed.
1584 *** Changes in GDB-4.6:
1586 * Better support for C++ function names
1588 GDB now accepts as input the "demangled form" of C++ overloaded function
1589 names and member function names, and can do command completion on such names
1590 (using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
1591 single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
1592 Make use of command completion, it is your friend.
1594 GDB also now accepts a variety of C++ mangled symbol formats. They are
1595 the GNU g++ style, the Cfront (ARM) style, and the Lucid (lcc) style.
1596 You can tell GDB which format to use by doing a 'set demangle-style {gnu,
1597 lucid, cfront, auto}'. 'gnu' is the default. Do a 'set demangle-style foo'
1598 for the list of formats.
1600 * G++ symbol mangling problem
1602 Recent versions of gcc have a bug in how they emit debugging information for
1603 C++ methods (when using dbx-style stabs). The file 'gcc.patch' (in this
1604 directory) can be applied to gcc to fix the problem. Alternatively, if you
1605 can't fix gcc, you can #define GCC_MANGLE_BUG when compling gdb/symtab.c. The
1606 usual symptom is difficulty with setting breakpoints on methods. GDB complains
1607 about the method being non-existent. (We believe that version 2.2.2 of GCC has
1610 * New 'maintenance' command
1612 All of the commands related to hacking GDB internals have been moved out of
1613 the main command set, and now live behind the 'maintenance' command. This
1614 can also be abbreviated as 'mt'. The following changes were made:
1616 dump-me -> maintenance dump-me
1617 info all-breakpoints -> maintenance info breakpoints
1618 printmsyms -> maintenance print msyms
1619 printobjfiles -> maintenance print objfiles
1620 printpsyms -> maintenance print psymbols
1621 printsyms -> maintenance print symbols
1623 The following commands are new:
1625 maintenance demangle Call internal GDB demangler routine to
1626 demangle a C++ link name and prints the result.
1627 maintenance print type Print a type chain for a given symbol
1629 * Change to .gdbinit file processing
1631 We now read the $HOME/.gdbinit file before processing the argv arguments
1632 (e.g. reading symbol files or core files). This allows global parameters to
1633 be set, which will apply during the symbol reading. The ./.gdbinit is still
1634 read after argv processing.
1636 * New hosts supported
1638 Solaris-2.0 !!! sparc-sun-solaris2 or sun4sol2
1640 GNU/Linux support i386-unknown-linux or linux
1642 We are also including code to support the HP/PA running BSD and HPUX. This
1643 is almost guaranteed not to work, as we didn't have time to test or build it
1644 for this release. We are including it so that the more adventurous (or
1645 masochistic) of you can play with it. We also had major problems with the
1646 fact that the compiler that we got from HP doesn't support the -g option.
1649 * New targets supported
1651 Hitachi H8/300 h8300-hitachi-hms or h8300hms
1653 * More smarts about finding #include files
1655 GDB now remembers the compilation directory for all include files, and for
1656 all files from which C is generated (like yacc and lex sources). This
1657 greatly improves GDB's ability to find yacc/lex sources, and include files,
1658 especially if you are debugging your program from a directory different from
1659 the one that contains your sources.
1661 We also fixed a bug which caused difficulty with listing and setting
1662 breakpoints in include files which contain C code. (In the past, you had to
1663 try twice in order to list an include file that you hadn't looked at before.)
1665 * Interesting infernals change
1667 GDB now deals with arbitrary numbers of sections, where the symbols for each
1668 section must be relocated relative to that section's landing place in the
1669 target's address space. This work was needed to support ELF with embedded
1670 stabs used by Solaris-2.0.
1672 * Bug fixes (of course!)
1674 There have been loads of fixes for the following things:
1675 mips, rs6000, 29k/udi, m68k, g++, type handling, elf/dwarf, m88k,
1676 i960, stabs, DOS(GO32), procfs, etc...
1678 See the ChangeLog for details.
1680 *** Changes in GDB-4.5:
1682 * New machines supported (host and target)
1684 IBM RS6000 running AIX rs6000-ibm-aix or rs6000
1686 SGI Irix-4.x mips-sgi-irix4 or iris4
1688 * New malloc package
1690 GDB now uses a new memory manager called mmalloc, based on gmalloc.
1691 Mmalloc is capable of handling mutiple heaps of memory. It is also
1692 capable of saving a heap to a file, and then mapping it back in later.
1693 This can be used to greatly speedup the startup of GDB by using a
1694 pre-parsed symbol table which lives in a mmalloc managed heap. For
1695 more details, please read mmalloc/mmalloc.texi.
1699 The 'info proc' command (SVR4 only) has been enhanced quite a bit. See
1700 'help info proc' for details.
1702 * MIPS ecoff symbol table format
1704 The code that reads MIPS symbol table format is now supported on all hosts.
1705 Thanks to MIPS for releasing the sym.h and symconst.h files to make this
1708 * File name changes for MS-DOS
1710 Many files in the config directories have been renamed to make it easier to
1711 support GDB on MS-DOSe systems (which have very restrictive file name
1712 conventions :-( ). MS-DOSe host support (under DJ Delorie's GO32
1713 environment) is close to working but has some remaining problems. Note
1714 that debugging of DOS programs is not supported, due to limitations
1715 in the ``operating system'', but it can be used to host cross-debugging.
1717 * Cross byte order fixes
1719 Many fixes have been made to support cross debugging of Sparc and MIPS
1720 targets from hosts whose byte order differs.
1722 * New -mapped and -readnow options
1724 If memory-mapped files are available on your system through the 'mmap'
1725 system call, you can use the -mapped option on the `file' or
1726 `symbol-file' commands to cause GDB to write the symbols from your
1727 program into a reusable file. If the program you are debugging is
1728 called `/path/fred', the mapped symbol file will be `./fred.syms'.
1729 Future GDB debugging sessions will notice the presence of this file,
1730 and will quickly map in symbol information from it, rather than reading
1731 the symbol table from the executable program. Using the '-mapped'
1732 option in a GDB `file' or `symbol-file' command has the same effect as
1733 starting GDB with the '-mapped' command-line option.
1735 You can cause GDB to read the entire symbol table immediately by using
1736 the '-readnow' option with any of the commands that load symbol table
1737 information (or on the GDB command line). This makes the command
1738 slower, but makes future operations faster.
1740 The -mapped and -readnow options are typically combined in order to
1741 build a `fred.syms' file that contains complete symbol information.
1742 A simple GDB invocation to do nothing but build a `.syms' file for future
1745 gdb -batch -nx -mapped -readnow programname
1747 The `.syms' file is specific to the host machine on which GDB is run.
1748 It holds an exact image of GDB's internal symbol table. It cannot be
1749 shared across multiple host platforms.
1751 * longjmp() handling
1753 GDB is now capable of stepping and nexting over longjmp(), _longjmp(), and
1754 siglongjmp() without losing control. This feature has not yet been ported to
1755 all systems. It currently works on many 386 platforms, all MIPS-based
1756 platforms (SGI, DECstation, etc), and Sun3/4.
1760 Preliminary work has been put in to support the new Solaris OS from Sun. At
1761 this time, it can control and debug processes, but it is not capable of
1766 As always, many many bug fixes. The major areas were with g++, and mipsread.
1767 People using the MIPS-based platforms should experience fewer mysterious
1768 crashes and trashed symbol tables.
1770 *** Changes in GDB-4.4:
1772 * New machines supported (host and target)
1774 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1776 BSD Reno on Vax vax-dec-bsd
1777 Ultrix on Vax vax-dec-ultrix
1779 * New machines supported (target)
1781 AMD 29000 embedded, using EBMON a29k-none-none
1785 GDB continues to improve its handling of C++. `References' work better.
1786 The demangler has also been improved, and now deals with symbols mangled as
1787 per the Annotated C++ Reference Guide.
1789 GDB also now handles `stabs' symbol information embedded in MIPS
1790 `ecoff' symbol tables. Since the ecoff format was not easily
1791 extensible to handle new languages such as C++, this appeared to be a
1792 good way to put C++ debugging info into MIPS binaries. This option
1793 will be supported in the GNU C compiler, version 2, when it is
1796 * New features for SVR4
1798 GDB now handles SVR4 shared libraries, in the same fashion as SunOS
1799 shared libraries. Debugging dynamically linked programs should present
1800 only minor differences from debugging statically linked programs.
1802 The `info proc' command will print out information about any process
1803 on an SVR4 system (including the one you are debugging). At the moment,
1804 it prints the address mappings of the process.
1806 If you bring up GDB on another SVR4 system, please send mail to
1807 bug-gdb@prep.ai.mit.edu to let us know what changes were reqired (if any).
1809 * Better dynamic linking support in SunOS
1811 Reading symbols from shared libraries which contain debugging symbols
1812 now works properly. However, there remain issues such as automatic
1813 skipping of `transfer vector' code during function calls, which
1814 make it harder to debug code in a shared library, than to debug the
1815 same code linked statically.
1819 GDB is now using the latest `getopt' routines from the FSF. This
1820 version accepts the -- prefix for options with long names. GDB will
1821 continue to accept the old forms (-option and +option) as well.
1822 Various single letter abbreviations for options have been explicity
1823 added to the option table so that they won't get overshadowed in the
1824 future by other options that begin with the same letter.
1828 The `cleanup_undefined_types' bug that many of you noticed has been squashed.
1829 Many assorted bugs have been handled. Many more remain to be handled.
1830 See the various ChangeLog files (primarily in gdb and bfd) for details.
1833 *** Changes in GDB-4.3:
1835 * New machines supported (host and target)
1837 Amiga 3000 running Amix m68k-cbm-svr4 or amix
1838 NCR 3000 386 running SVR4 i386-ncr-svr4 or ncr3000
1839 Motorola Delta 88000 running Sys V m88k-motorola-sysv or delta88
1841 * Almost SCO Unix support
1843 We had hoped to support:
1844 SCO Unix on i386 IBM PC clones i386-sco-sysv or i386sco
1845 (except for core file support), but we discovered very late in the release
1846 that it has problems with process groups that render gdb unusable. Sorry
1847 about that. I encourage people to fix it and post the fixes.
1849 * Preliminary ELF and DWARF support
1851 GDB can read ELF object files on System V Release 4, and can handle
1852 debugging records for C, in DWARF format, in ELF files. This support
1853 is preliminary. If you bring up GDB on another SVR4 system, please
1854 send mail to bug-gdb@prep.ai.mit.edu to let us know what changes were
1859 GDB now uses the latest `readline' library. One user-visible change
1860 is that two tabs will list possible command completions, which previously
1861 required typing M-? (meta-question mark, or ESC ?).
1865 The `stepi' bug that many of you noticed has been squashed.
1866 Many bugs in C++ have been handled. Many more remain to be handled.
1867 See the various ChangeLog files (primarily in gdb and bfd) for details.
1869 * State of the MIPS world (in case you wondered):
1871 GDB can understand the symbol tables emitted by the compilers
1872 supplied by most vendors of MIPS-based machines, including DEC. These
1873 symbol tables are in a format that essentially nobody else uses.
1875 Some versions of gcc come with an assembler post-processor called
1876 mips-tfile. This program is required if you want to do source-level
1877 debugging of gcc-compiled programs. I believe FSF does not ship
1878 mips-tfile with gcc version 1, but it will eventually come with gcc
1881 Debugging of g++ output remains a problem. g++ version 1.xx does not
1882 really support it at all. (If you're lucky, you should be able to get
1883 line numbers and stack traces to work, but no parameters or local
1884 variables.) With some work it should be possible to improve the
1887 When gcc version 2 is released, you will have somewhat better luck.
1888 However, even then you will get confusing results for inheritance and
1891 We will eventually provide full debugging of g++ output on
1892 DECstations. This will probably involve some kind of stabs-in-ecoff
1893 encapulation, but the details have not been worked out yet.
1896 *** Changes in GDB-4.2:
1898 * Improved configuration
1900 Only one copy of `configure' exists now, and it is not self-modifying.
1901 Porting BFD is simpler.
1905 The `step' and `next' commands now only stop at the first instruction
1906 of a source line. This prevents the multiple stops that used to occur
1907 in switch statements, for-loops, etc. `Step' continues to stop if a
1908 function that has debugging information is called within the line.
1912 Lots of small bugs fixed. More remain.
1914 * New host supported (not target)
1916 Intel 386 PC clone running Mach i386-none-mach
1919 *** Changes in GDB-4.1:
1921 * Multiple source language support
1923 GDB now has internal scaffolding to handle several source languages.
1924 It determines the type of each source file from its filename extension,
1925 and will switch expression parsing and number formatting to match the
1926 language of the function in the currently selected stack frame.
1927 You can also specifically set the language to be used, with
1928 `set language c' or `set language modula-2'.
1932 GDB now has preliminary support for the GNU Modula-2 compiler,
1933 currently under development at the State University of New York at
1934 Buffalo. Development of both GDB and the GNU Modula-2 compiler will
1935 continue through the fall of 1991 and into 1992.
1937 Other Modula-2 compilers are currently not supported, and attempting to
1938 debug programs compiled with them will likely result in an error as the
1939 symbol table is read. Feel free to work on it, though!
1941 There are hooks in GDB for strict type checking and range checking,
1942 in the `Modula-2 philosophy', but they do not currently work.
1946 GDB can now write to executable and core files (e.g. patch
1947 a variable's value). You must turn this switch on, specify
1948 the file ("exec foo" or "core foo"), *then* modify it, e.g.
1949 by assigning a new value to a variable. Modifications take
1952 * Automatic SunOS shared library reading
1954 When you run your program, GDB automatically determines where its
1955 shared libraries (if any) have been loaded, and reads their symbols.
1956 The `share' command is no longer needed. This also works when
1957 examining core files.
1961 You can specify the number of lines that the `list' command shows.
1964 * New machines supported (host and target)
1966 SGI Iris (MIPS) running Irix V3: mips-sgi-irix or iris
1967 Sony NEWS (68K) running NEWSOS 3.x: m68k-sony-sysv or news
1968 Ultracomputer (29K) running Sym1: a29k-nyu-sym1 or ultra3
1970 * New hosts supported (not targets)
1972 IBM RT/PC: romp-ibm-aix or rtpc
1974 * New targets supported (not hosts)
1976 AMD 29000 embedded with COFF a29k-none-coff
1977 AMD 29000 embedded with a.out a29k-none-aout
1978 Ultracomputer remote kernel debug a29k-nyu-kern
1980 * New remote interfaces
1986 *** Changes in GDB-4.0:
1990 Wide output is wrapped at good places to make the output more readable.
1992 Gdb now supports cross-debugging from a host machine of one type to a
1993 target machine of another type. Communication with the target system
1994 is over serial lines. The ``target'' command handles connecting to the
1995 remote system; the ``load'' command will download a program into the
1996 remote system. Serial stubs for the m68k and i386 are provided. Gdb
1997 also supports debugging of realtime processes running under VxWorks,
1998 using SunRPC Remote Procedure Calls over TCP/IP to talk to a debugger
1999 stub on the target system.
2001 New CPUs supported include the AMD 29000 and Intel 960.
2003 GDB now reads object files and symbol tables via a ``binary file''
2004 library, which allows a single copy of GDB to debug programs of multiple
2005 object file types such as a.out and coff.
2007 There is now a GDB reference card in "doc/refcard.tex". (Make targets
2008 refcard.dvi and refcard.ps are available to format it).
2011 * Control-Variable user interface simplified
2013 All variables that control the operation of the debugger can be set
2014 by the ``set'' command, and displayed by the ``show'' command.
2016 For example, ``set prompt new-gdb=>'' will change your prompt to new-gdb=>.
2017 ``Show prompt'' produces the response:
2018 Gdb's prompt is new-gdb=>.
2020 What follows are the NEW set commands. The command ``help set'' will
2021 print a complete list of old and new set commands. ``help set FOO''
2022 will give a longer description of the variable FOO. ``show'' will show
2023 all of the variable descriptions and their current settings.
2025 confirm on/off: Enables warning questions for operations that are
2026 hard to recover from, e.g. rerunning the program while
2027 it is already running. Default is ON.
2029 editing on/off: Enables EMACS style command line editing
2030 of input. Previous lines can be recalled with
2031 control-P, the current line can be edited with control-B,
2032 you can search for commands with control-R, etc.
2035 history filename NAME: NAME is where the gdb command history
2036 will be stored. The default is .gdb_history,
2037 or the value of the environment variable
2040 history size N: The size, in commands, of the command history. The
2041 default is 256, or the value of the environment variable
2044 history save on/off: If this value is set to ON, the history file will
2045 be saved after exiting gdb. If set to OFF, the
2046 file will not be saved. The default is OFF.
2048 history expansion on/off: If this value is set to ON, then csh-like
2049 history expansion will be performed on
2050 command line input. The default is OFF.
2052 radix N: Sets the default radix for input and output. It can be set
2053 to 8, 10, or 16. Note that the argument to "radix" is interpreted
2054 in the current radix, so "set radix 10" is always a no-op.
2056 height N: This integer value is the number of lines on a page. Default
2057 is 24, the current `stty rows'' setting, or the ``li#''
2058 setting from the termcap entry matching the environment
2061 width N: This integer value is the number of characters on a line.
2062 Default is 80, the current `stty cols'' setting, or the ``co#''
2063 setting from the termcap entry matching the environment
2066 Note: ``set screensize'' is obsolete. Use ``set height'' and
2067 ``set width'' instead.
2069 print address on/off: Print memory addresses in various command displays,
2070 such as stack traces and structure values. Gdb looks
2071 more ``symbolic'' if you turn this off; it looks more
2072 ``machine level'' with it on. Default is ON.
2074 print array on/off: Prettyprint arrays. New convenient format! Default
2077 print demangle on/off: Print C++ symbols in "source" form if on,
2080 print asm-demangle on/off: Same, for assembler level printouts
2083 print vtbl on/off: Prettyprint C++ virtual function tables. Default is OFF.
2086 * Support for Epoch Environment.
2088 The epoch environment is a version of Emacs v18 with windowing. One
2089 new command, ``inspect'', is identical to ``print'', except that if you
2090 are running in the epoch environment, the value is printed in its own
2094 * Support for Shared Libraries
2096 GDB can now debug programs and core files that use SunOS shared libraries.
2097 Symbols from a shared library cannot be referenced
2098 before the shared library has been linked with the program (this
2099 happens after you type ``run'' and before the function main() is entered).
2100 At any time after this linking (including when examining core files
2101 from dynamically linked programs), gdb reads the symbols from each
2102 shared library when you type the ``sharedlibrary'' command.
2103 It can be abbreviated ``share''.
2105 sharedlibrary REGEXP: Load shared object library symbols for files
2106 matching a unix regular expression. No argument
2107 indicates to load symbols for all shared libraries.
2109 info sharedlibrary: Status of loaded shared libraries.
2114 A watchpoint stops execution of a program whenever the value of an
2115 expression changes. Checking for this slows down execution
2116 tremendously whenever you are in the scope of the expression, but is
2117 quite useful for catching tough ``bit-spreader'' or pointer misuse
2118 problems. Some machines such as the 386 have hardware for doing this
2119 more quickly, and future versions of gdb will use this hardware.
2121 watch EXP: Set a watchpoint (breakpoint) for an expression.
2123 info watchpoints: Information about your watchpoints.
2125 delete N: Deletes watchpoint number N (same as breakpoints).
2126 disable N: Temporarily turns off watchpoint number N (same as breakpoints).
2127 enable N: Re-enables watchpoint number N (same as breakpoints).
2130 * C++ multiple inheritance
2132 When used with a GCC version 2 compiler, GDB supports multiple inheritance
2135 * C++ exception handling
2137 Gdb now supports limited C++ exception handling. Besides the existing
2138 ability to breakpoint on an exception handler, gdb can breakpoint on
2139 the raising of an exception (before the stack is peeled back to the
2142 catch FOO: If there is a FOO exception handler in the dynamic scope,
2143 set a breakpoint to catch exceptions which may be raised there.
2144 Multiple exceptions (``catch foo bar baz'') may be caught.
2146 info catch: Lists all exceptions which may be caught in the
2147 current stack frame.
2150 * Minor command changes
2152 The command ``call func (arg, arg, ...)'' now acts like the print
2153 command, except it does not print or save a value if the function's result
2154 is void. This is similar to dbx usage.
2156 The ``up'' and ``down'' commands now always print the frame they end up
2157 at; ``up-silently'' and `down-silently'' can be used in scripts to change
2158 frames without printing.
2160 * New directory command
2162 'dir' now adds directories to the FRONT of the source search path.
2163 The path starts off empty. Source files that contain debug information
2164 about the directory in which they were compiled can be found even
2165 with an empty path; Sun CC and GCC include this information. If GDB can't
2166 find your source file in the current directory, type "dir .".
2168 * Configuring GDB for compilation
2170 For normal use, type ``./configure host''. See README or gdb.texinfo
2173 GDB now handles cross debugging. If you are remotely debugging between
2174 two different machines, type ``./configure host -target=targ''.
2175 Host is the machine where GDB will run; targ is the machine
2176 where the program that you are debugging will run.
projects / deliverable / binutils-gdb.git / blob