Add handling for 64-bit module addresses in Cygwin core dumps

[deliverable/binutils-gdb.git] / gdb / NEWS

diff --git a/gdb/NEWS b/gdb/NEWS
index 29db0734f87451b20b3aafe040ea67d6dc0793fc..0ac0ff18f2fe1bfa6c719a934dac549666bebe26 100644 (file)
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -1,7 +1,24 @@
                What has changed in GDB?
             (Organized release by release)
 
-*** Changes since GDB 9
+*** Changes since GDB 10
+
+* MI changes
+
+ ** '-break-insert --qualified' and '-dprintf-insert --qualified'
+
+    The MI -break-insert and -dprintf-insert commands now support a
+    new "--qualified" option that makes GDB interpret a specified
+    function name as a complete fully-qualified name.  This is the
+    equivalent of the CLI's "break -qualified" and "dprintf
+    -qualified".
+
+*** Changes in GDB 10
+
+* There are new feature names for ARC targets: "org.gnu.gdb.arc.core"
+  and "org.gnu.gdb.arc.aux".  The old names are still supported but
+  must be considered obsolete.  They will be deprecated after some
+  grace period.
 
 * Help and apropos commands will now show the documentation of a
   command only once, even if that command has one or more aliases.
@@ -25,6 +42,21 @@
 
   You can get the latest version from https://sourceware.org/elfutils.
 
+* Multi-target debugging support
+
+  GDB now supports debugging multiple target connections
+  simultaneously.  For example, you can now have each inferior
+  connected to different remote servers running in different machines,
+  or have one inferior debugging a local native process, an inferior
+  debugging a core dump, etc.
+
+  This support is experimental and comes with some limitations -- you
+  can only resume multiple targets simultaneously if all targets
+  support non-stop mode, and all remote stubs or servers must support
+  the same set of remote protocol features exactly.  See also "info
+  connections" and "add-inferior -no-connection" below, and "maint set
+  target-non-stop" in the user manual.
+
 * New features in the GDB remote stub, GDBserver
 
   ** GDBserver is now supported on RISC-V GNU/Linux.
@@ -85,6 +117,10 @@ maintenance print xml-tdesc [FILE]
   the target description is read from FILE into GDB, and then
   reprinted.
 
+maintenance print core-file-backed-mappings
+  Prints file-backed mappings loaded from a core file's note section.
+  Output is expected to be similar to that of "info proc mappings".
+
 * Changed commands
 
 alias [-a] [--] ALIAS = COMMAND [DEFAULT-ARGS...]
@@ -103,6 +139,7 @@ alias [-a] [--] ALIAS = COMMAND [DEFAULT-ARGS...]
 * New targets
 
 GNU/Linux/RISC-V (gdbserver)   riscv*-*-linux*
+BPF                            bpf-unknown-none
 
 * Python API
 
@@ -120,6 +157,26 @@ GNU/Linux/RISC-V (gdbserver)       riscv*-*-linux*
   ** New method gdb.PendingFrame.architecture () to retrieve the
      architecture of the pending frame.
 
+  ** New gdb.Architecture.registers method that returns a
+     gdb.RegisterDescriptorIterator object, an iterator that returns
+     gdb.RegisterDescriptor objects.  The new RegisterDescriptor is a
+     way to query the registers available for an architecture.
+
+  ** New gdb.Architecture.register_groups method that returns a
+     gdb.RegisterGroupIterator object, an iterator that returns
+     gdb.RegisterGroup objects.  The new RegisterGroup is a way to
+     discover the available register groups.
+
+* Guile API
+
+  ** GDB can now be built with GNU Guile 3.0 and 2.2 in addition to 2.0.
+
+  ** Procedures 'memory-port-read-buffer-size',
+     'set-memory-port-read-buffer-size!', 'memory-port-write-buffer-size',
+     and 'set-memory-port-write-buffer-size!' are deprecated.  When
+     using Guile 2.2 and later, users who need to control the size of
+     a memory port's internal buffer can use the 'setvbuf' procedure.
+
 *** Changes in GDB 9
 
 * 'thread-exited' event is now available in the annotations interface.
@@ -187,21 +244,6 @@ GNU/Linux/RISC-V (gdbserver)       riscv*-*-linux*
   This feature is still in testing, so it is disabled by default.  You
   can turn it on using 'maint set worker-threads unlimited'.
 
-* Multi-target debugging support
-
-  GDB now supports debugging multiple target connections
-  simultaneously.  For example, you can now have each inferior
-  connected to different remote servers running in different machines,
-  or have one inferior debugging a local native process, an inferior
-  debugging a core dump, etc.
-
-  This support is experimental and comes with some limitations -- you
-  can only resume multiple targets simultaneously if all targets
-  support non-stop mode, and all remote stubs or servers must support
-  the same set of remote protocol features exactly.  See also "info
-  connections" and "add-inferior -no-connection" below, and "maint set
-  target-non-stop" in the user manual.
-
 * Python API
 
   ** The gdb.Value type has a new method 'format_string' which returns a