What has changed in GDB?
(Organized release by release)
-*** Changes since GDB 6.6
+*** Changes since GDB 6.7
+
+* Change in command line behavior -- corefiles vs. process ids.
+
+ When the '-p NUMBER' or '--pid NUMBER' options are used, and
+ attaching to process NUMBER fails, GDB no longer attempts to open a
+ core file named NUMBER. Attaching to a program using the -c option
+ is no longer supported. Instead, use the '-p' or '--pid' options.
+
+* New commands
+
+set print frame-arguments (all|scalars|none)
+show print frame-arguments
+ The value of this variable can be changed to control which argument
+ values should be printed by the debugger when displaying a frame.
+
+* GDB can now be built as a native debugger for debugging Windows x86
+(mingw32) Portable Executable (PE) programs.
+
+* Pending breakpoints no longer change their number when their address
+is resolved.
+
+* GDB now supports breakpoints with multiple locations,
+including breakpoints on C++ constructors, inside C++ templates,
+and in inlined functions.
+
+* GDB's ability to debug optimized code has been improved. GDB more
+accurately identifies function bodies and lexical blocks that occupy
+more than one contiguous range of addresses.
+
+* Target descriptions can now describe registers for PowerPC.
+
+* The GDB remote stub, gdbserver, now supports the AltiVec and SPE
+registers on PowerPC targets.
+
+* The GDB remote stub, gdbserver, now supports thread debugging on GNU/Linux
+targets even when the libthread_db library is not available.
+
+* The GDB remote stub, gdbserver, now supports the new file transfer
+commands (remote put, remote get, and remote delete).
+
+* hppa*64*-*-hpux11* target broken
+ The debugger is unable to start a program and fails with the following
+ error: "Error trying to get information about dynamic linker".
+ The gdb-6.7 release is also affected.
+
+* GDB now supports the --enable-targets= configure option to allow
+building a single GDB executable that supports multiple remote
+target architectures.
+
+* New commands
+
+remote put
+remote get
+remote delete
+ Transfer files to and from a remote target, and delete remote files.
+
+* New MI commands
+
+-target-file-put
+-target-file-get
+-target-file-delete
+ Transfer files to and from a remote target, and delete remote files.
+
+* New remote packets
+
+vFile:open:
+vFile:close:
+vFile:pread:
+vFile:pwrite:
+vFile:unlink:
+ Open, close, read, write, and delete files on the remote system.
+
+*** Changes in GDB 6.7
+
+* Resolved 101 resource leaks, null pointer dereferences, etc. in gdb,
+bfd, libiberty and opcodes, as revealed by static analysis donated by
+Coverity, Inc. (http://scan.coverity.com).
+
+* When looking up multiply-defined global symbols, GDB will now prefer the
+symbol definition in the current shared library if it was built using the
+-Bsymbolic linker option.
+
+* When the Text User Interface (TUI) is not configured, GDB will now
+recognize the -tui command-line option and print a message that the TUI
+is not supported.
* The GDB remote stub, gdbserver, now has lower overhead for high
frequency signals (e.g. SIGALRM) via the QPassSignals packet.
target's overall architecture. GDB can read a description from
a local file or over the remote serial protocol.
-* Arrays of explicitly SIGNED or UNSIGNED CHARs are now printed as arrays
- of numbers.
+* Vectors of single-byte data use a new integer type which is not
+automatically displayed as character or string data.
+
+* The /s format now works with the print command. It displays
+arrays of single-byte integers and pointers to single-byte integers
+as strings.
* Target descriptions can now describe target-specific registers,
for architectures which have implemented the support (currently
-only ARM).
+only ARM, M68K, and MIPS).
* GDB and the GDB remote stub, gdbserver, now support the XScale
iWMMXt coprocessor.
+* The GDB remote stub, gdbserver, has been updated to support
+ARM Windows CE (mingw32ce) debugging, and GDB Windows CE support
+has been rewritten to use the standard GDB remote protocol.
+
+* GDB can now step into C++ functions which are called through thunks.
+
+* GDB for the Cell/B.E. SPU now supports overlay debugging.
+
+* The GDB remote protocol "qOffsets" packet can now honor ELF segment
+layout. It also supports a TextSeg= and DataSeg= response when only
+segment base addresses (rather than offsets) are available.
+
+* The /i format now outputs any trailing branch delay slot instructions
+immediately following the last instruction within the count specified.
+
+* The GDB remote protocol "T" stop reply packet now supports a
+"library" response. Combined with the new "qXfer:libraries:read"
+packet, this response allows GDB to debug shared libraries on targets
+where the operating system manages the list of loaded libraries (e.g.
+Windows and SymbianOS).
+
+* The GDB remote stub, gdbserver, now supports dynamic link libraries
+(DLLs) on Windows and Windows CE targets.
+
+* GDB now supports a faster verification that a .debug file matches its binary
+according to its build-id signature, if the signature is present.
+
* New commands
+set remoteflow
+show remoteflow
+ Enable or disable hardware flow control (RTS/CTS) on the serial port
+ when debugging using remote targets.
+
set mem inaccessible-by-default
show mem inaccessible-by-default
If the target supplies a memory map, for instance via the remote
general version of "set solib-absolute-prefix", which is now
an alias to "set sysroot".
+info spu
+ Provide extended SPU facility status information. This set of
+ commands is available only when debugging the Cell/B.E. SPU
+ architecture.
+
* New native configurations
OpenBSD/sh sh*-*openbsd*
Read an XML target description from the target, which describes its
features.
+qXfer:spu:read:
+qXfer:spu:write:
+ Read or write contents of an spufs file on the target system. These
+ packets are available only on the Cell/B.E. SPU architecture.
+
+qXfer:libraries:read:
+ Report the loaded shared libraries. Combined with new "T" packet
+ response, this packet allows GDB to debug shared libraries on
+ targets where the operating system manages the list of loaded
+ libraries (e.g. Windows and SymbianOS).
+
* Removed targets
Support for these obsolete configurations has been removed.
+alpha*-*-osf1*
+alpha*-*-osf2*
+d10v-*-*
hppa*-*-hiux*
i[34567]86-ncr-*
i[34567]86-*-dgux*
i[34567]86-*-isc*
m68*-cisco*-*
m68*-tandem-*
+mips*-*-pe
rs6000-*-lynxos*
+sh*-*-pe
+
+* Other removed features
+
+target abug
+target cpu32bug
+target est
+target rom68k
+
+ Various m68k-only ROM monitors.
+
+target hms
+target e7000
+target sh3
+target sh3e
+
+ Various Renesas ROM monitors and debugging interfaces for SH and
+ H8/300.
+
+target ocd
+
+ Support for a Macraigor serial interface to on-chip debugging.
+ GDB does not directly support the newer parallel or USB
+ interfaces.
+
+DWARF 1 support
+
+ A debug information format. The predecessor to DWARF 2 and
+ DWARF 3, which are still supported.
+
+Support for the HP aCC compiler on HP-UX/PA-RISC
+
+ SOM-encapsulated symbolic debugging information, automatic
+ invocation of pxdb, and the aCC custom C++ ABI. This does not
+ affect HP-UX for Itanium or GCC for HP-UX/PA-RISC. Code compiled
+ with aCC can still be debugged on an assembly level.
+
+MIPS ".pdr" sections
+
+ A MIPS-specific format used to describe stack frame layout
+ in debugging information.
+
+Scheme support
+
+ GDB could work with an older version of Guile to debug
+ the interpreter and Scheme programs running in it.
+
+set mips stack-arg-size
+set mips saved-gpreg-size
+
+ Use "set mips abi" to control parameter passing for MIPS.
*** Changes in GDB 6.6