From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "'Eli Zaretskii'" <eliz@gnu.org>
Subject: Mention non-stop mode in NEWS.
Date: Sun, 04 Oct 2009 15:51:00 -0000 [thread overview]
Message-ID: <200910041651.26172.pedro@codesourcery.com> (raw)
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...
--
Pedro Alves
2009-10-04 Pedro Alves <pedro@codesourcery.com>
* NEWS: Mention non-stop mode.
---
gdb/NEWS | 14 ++++++++++++++
1 file changed, 14 insertions(+)
Index: src/gdb/NEWS
===================================================================
--- 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
+ targets.
+
* New commands (for set/show, see "New options" below)
catch syscall [NAME(S) | NUMBER(S)]
--
Pedro Alves
next reply other threads:[~2009-10-04 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-04 15:51 Pedro Alves [this message]
2009-10-04 15:57 ` Pedro Alves
2009-10-04 16:55 ` Eli Zaretskii
2009-10-04 17:48 ` Pedro Alves
2009-10-04 16:53 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200910041651.26172.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox