public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: tromey@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] tromey/always-async: rework target-async docs Date: Tue, 16 Jul 2013 20:29:00 -0000 [thread overview] Message-ID: <20130716202945.21064.qmail@sourceware.org> (raw) 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 <tromey@redhat.com> 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.
next reply other threads:[~2013-07-16 20:29 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-16 20:29 tromey [this message] 2013-07-22 19:21 tromey
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=20130716202945.21064.qmail@sourceware.org \ --to=tromey@sourceware.org \ --cc=archer-commits@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).