From: Pedro Alves Date: Sun, 4 Oct 2009 17:34:43 +0000 (+0000) Subject: * NEWS: Mention non-stop mode. X-Git-Tag: gdb_7_0-2009-10-06-release~5 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=563a209643b60b4f49fcccac1ed5cc1a78b7c984;p=thirdparty%2Fbinutils-gdb.git * NEWS: Mention non-stop mode. --- diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 9dff1a008b1..b2b32fba7d1 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2009-10-04 Pedro Alves + + * NEWS: Mention non-stop mode. + 2009-10-02 H.J. Lu PR gdb/10649 diff --git a/gdb/NEWS b/gdb/NEWS index 4fc6dcde137..731d7e4d1ac 100644 --- 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)]