* NEWS: Mention non-stop mode.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 9dff1a008b1340bea89db698dfe371fd7f835c34..b2b32fba7d1942fc34ebf11756c2ff14ca4d7cb2 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2009-10-04  Pedro Alves  <pedro@codesourcery.com>
+
+       * NEWS: Mention non-stop mode.
+
 2009-10-02  H.J. Lu  <hongjiu.lu@intel.com>
 
        PR gdb/10649

diff --git a/gdb/NEWS b/gdb/NEWS
index 4fc6dcde137478497b399e3bd5d624cfbdd3a947..731d7e4d1acc278be2380105058e52b44b423756 100644 (file)
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -232,6 +232,20 @@ Cell/B.E. debugging, you need to configure GDB to support both the
 powerpc-linux or powerpc64-linux and the spu-elf targets, using the
 --enable-targets configure option.
 
+* Non-stop mode debugging.
+
+  For some targets, GDB now supports an optional mode of operation in
+  which you can examine stopped threads while other threads continue
+  to execute freely.  This is referred to as non-stop mode, with the
+  old mode referred to as all-stop mode.  See the "Non-Stop Mode"
+  section in the user manual for more information.
+
+  To be able to support remote non-stop debugging, a remote stub needs
+  to implement the non-stop mode remote protocol extensions, as
+  described in the "Remote Non-Stop" section of the user manual.  The
+  GDB remote stub, gdbserver, has been adjusted to support these
+  extensions on linux targets.
+
 * New commands (for set/show, see "New options" below)
 
 catch syscall [NAME(S) | NUMBER(S)]