What has changed in GDB?
(Organized release by release)
-*** Changes since GDB 6.6
+*** Changes since GDB 6.7
+
+*** Changes in GDB 6.6
+
+* 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
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
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