This is the mail archive of the
mailing list for the GDB project.
Mention non-stop mode in NEWS.
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: "'Eli Zaretskii'" <eliz at gnu dot org>
- Date: Sun, 4 Oct 2009 16:51:25 +0100
- Subject: Mention non-stop mode in NEWS.
Non-stop mode isn't described in the NEWS yet.
Okay for main trunk and branch?
Very sorry for the delay in getting to this...
2009-10-04 Pedro Alves <email@example.com>
* NEWS: Mention non-stop mode.
gdb/NEWS | 14 ++++++++++++++
1 file changed, 14 insertions(+)
--- src.orig/gdb/NEWS 2009-10-04 15:56:42.000000000 +0100
+++ src/gdb/NEWS 2009-10-04 16:42:56.000000000 +0100
@@ -232,6 +232,20 @@ Cell/B.E. debugging, you need to configu
powerpc-linux or powerpc64-linux and the spu-elf targets, using the
--enable-targets configure option.
+* Non-stop mode debugging.
+ For some targets, GDB 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 "Remote Non-Stop" section. The GDB remote stub,
+ gdbserver, has been adjusted to support these extensions on linux
* New commands (for set/show, see "New options" below)
catch syscall [NAME(S) | NUMBER(S)]