From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21127 invoked by alias); 16 Jul 2013 20:29:46 -0000 Mailing-List: contact archer-commits-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: Received: (qmail 21092 invoked by uid 306); 16 Jul 2013 20:29:46 -0000 Date: Tue, 16 Jul 2013 20:29:00 -0000 Message-ID: <20130716202945.21064.qmail@sourceware.org> From: tromey@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] tromey/always-async: rework target-async docs X-Git-Refname: refs/heads/tromey/always-async X-Git-Reftype: branch X-Git-Oldrev: de4d7b9c1bfaecf49be1f73e2a403552cf189afa X-Git-Newrev: 3d9baabfad8ba67ed14696fb2be4d58d83777e6c X-SW-Source: 2013-q3/txt/msg00005.txt.bz2 List-Id: The branch, tromey/always-async has been updated via 3d9baabfad8ba67ed14696fb2be4d58d83777e6c (commit) from de4d7b9c1bfaecf49be1f73e2a403552cf189afa (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit 3d9baabfad8ba67ed14696fb2be4d58d83777e6c Author: Tom Tromey Date: Fri Jul 12 08:21:03 2013 -0600 rework target-async docs ----------------------------------------------------------------------- Summary of changes: gdb/doc/gdb.texinfo | 29 +++++++++++------------------ 1 files changed, 11 insertions(+), 18 deletions(-) First 500 lines of diff: diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index fae54e4..b311fb9 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -5672,9 +5672,6 @@ To enter non-stop mode, use this sequence of commands before you run or attach to your program: @smallexample -# Enable the async interface. -set target-async 1 - # If using the CLI, pagination breaks non-stop. set pagination off @@ -5744,21 +5741,6 @@ the program to report that some thread has stopped before prompting for another command. In background execution, @value{GDBN} immediately gives a command prompt so that you can issue other commands while your program runs. -You need to explicitly enable asynchronous mode before you can use -background execution commands. You can use these commands to -manipulate the asynchronous mode setting: - -@table @code -@kindex set target-async -@item set target-async on -Enable asynchronous mode. -@item set target-async off -Disable asynchronous mode. -@kindex show target-async -@item show target-async -Show the current target-async setting. -@end table - If the target doesn't support async mode, @value{GDBN} issues an error message if you attempt to use the background execution commands. @@ -28488,6 +28470,17 @@ frontend has started the executable or attached to the target, it can find if asynchronous execution is enabled using the @code{-list-target-features} command. +@table @code +@kindex -gdb-set target-async +@item -gdb-set target-async on +Enable asynchronous mode. This mode only affects MI commands. +@item -gdb-set target-async off +Disable asynchronous mode. +@kindex -gdb-show target-async +@item -gdb-show target-async +Show the current target-async setting. +@end table + Even if @value{GDBN} can accept a command while target is running, many commands that access the target do not work when the target is running. Therefore, asynchronous command execution is most useful hooks/post-receive -- Repository for Project Archer.