From patchwork Mon Mar 31 02:08:14 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Doug Evans X-Patchwork-Id: 347 Return-Path: X-Original-To: siddhesh@wilcox.dreamhost.com Delivered-To: siddhesh@wilcox.dreamhost.com Received: from homiemail-mx21.g.dreamhost.com (peon2454.g.dreamhost.com [208.113.200.127]) by wilcox.dreamhost.com (Postfix) with ESMTP id E6CAD36067E for ; Sun, 30 Mar 2014 19:08:23 -0700 (PDT) Received: by homiemail-mx21.g.dreamhost.com (Postfix, from userid 14314964) id 93920E44F90; Sun, 30 Mar 2014 19:08:23 -0700 (PDT) X-Original-To: gdb@patchwork.siddhesh.in Delivered-To: x14314964@homiemail-mx21.g.dreamhost.com Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by homiemail-mx21.g.dreamhost.com (Postfix) with ESMTPS id 6C360E44F4A for ; Sun, 30 Mar 2014 19:08:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:subject:date:message-id:mime-version :content-type; q=dns; s=default; b=n1CkYdIVTe7WPuaFBUSRwUH0SLAdY vAMyX4Engi8KdDvUkdM23QPM9Az8bljlFypLms5QJCXzf3sCKl+vnYQYNnW9k/tq VPYbslBfRPuSroBgSI5uku16u/5kH/4kHM3ebcllUwXzsFyT8PD33BKP4Tr6hCdp jA88fOUVxz5Q5E= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:from:to:subject:date:message-id:mime-version :content-type; s=default; bh=uEz2Nyy0UzdkD2ArisWVuRuFc8k=; b=MZ4 J+AFnSjvmO048o/5GARmXcWJfbiFiVA+QKnYTB0/PhDI4i8KCmPXxc7zR0qYuDYu aKvtSePtkAZfmK9xPnF5d/3LG1Wt7FYR53yloXKTrvHRMf8zlN6F2V9hbXNGTJfx TkQzSedcEzals1z3reO6D409Xd/fbUY+LLuLIJIc= Received: (qmail 30550 invoked by alias); 31 Mar 2014 02:08:20 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Delivered-To: mailing list gdb-patches@sourceware.org Received: (qmail 30540 invoked by uid 89); 31 Mar 2014 02:08:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.2 required=5.0 tests=AWL, BAYES_00, RCVD_IN_DNSWL_LOW, RP_MATCHES_RCVD, SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qc0-f202.google.com Received: from mail-qc0-f202.google.com (HELO mail-qc0-f202.google.com) (209.85.216.202) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 31 Mar 2014 02:08:17 +0000 Received: by mail-qc0-f202.google.com with SMTP id m20so1027309qcx.3 for ; Sun, 30 Mar 2014 19:08:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-type; bh=IaxjZGDJivCY28bnWkvtzVqAnALHxM5zPK/HNxAkD/o=; b=KG7Sh095gLExTsYQBfWDflanS0Aw4shRhYGNc6AScWRn2bacDcYA2GUaYaedD7JJET LKc+K7rgliWv8bxasv1j9RUKbWMJDPQFJKsRwSDumfldXjOFqg05Srqv7itK+I8prhj8 zzu/5xhzqLpvfda1/6KxQlhPFUgPm4qQ3gaqWQvjK7Am4X3dK7z9E2esQkBV1DTedrK8 /tj4yIhYJkrrcvicr/tOBpvpompRPynKreqyPBLl3a5iyf8xfCTGfkPNqcxbQan/BDR/ ZM9N9BN83/nDckTSAZnlTze+eRE2Zmb6IB8vMOaWY/R2VQ92aMIOugIXZa7sFtBq8oXt yvzQ== X-Gm-Message-State: ALoCoQk5T0O8VMSb2fIqT/IKYLK/b+iCzr+PLfw5DfglGBtueMclmJFk5HOyJ8Bo+hVUz9YG5K6NXIAaHHfAKKH98fQt1IZP5SMod5yZCTCWoODUiQp6fk/1Qh4xtFu8MSpk1zUGyZZRnLUObvL2Zc52iknCeXOrurUhhwMlWNwAULJzVKlGjnJv7bKH4738HIdIxYe4lGRhszYZg4dStYsVJrqMyesPYebiKlT/MEKTAD19+Vk+n/E= X-Received: by 10.224.167.8 with SMTP id o8mr8805407qay.0.1396231695148; Sun, 30 Mar 2014 19:08:15 -0700 (PDT) Received: from corp2gmr1-1.hot.corp.google.com (corp2gmr1-1.hot.corp.google.com [172.24.189.92]) by gmr-mx.google.com with ESMTPS id r61si952187yhf.1.2014.03.30.19.08.15 for (version=TLSv1.1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 30 Mar 2014 19:08:15 -0700 (PDT) Received: from ruffy.mtv.corp.google.com (ruffy.mtv.corp.google.com [172.17.128.44]) by corp2gmr1-1.hot.corp.google.com (Postfix) with ESMTP id BF47B31C1A3 for ; Sun, 30 Mar 2014 19:08:14 -0700 (PDT) From: Doug Evans To: gdb-patches@sourceware.org Subject: [commit] gdb.texinfo (Non-Stop Mode): Remove trailing whitespace. Date: Sun, 30 Mar 2014 19:08:14 -0700 Message-ID: MIME-Version: 1.0 X-IsSubscribed: yes X-DH-Original-To: gdb@patchwork.siddhesh.in Hi. While editing the docs for the interrupt command I found some trailing whitespace, deleted here. 2014-03-30 Doug Evans * gdb.texinfo (Non-Stop Mode): Remove trailing whitespace. (Background Execution): Ditto. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 1df3ca0..0bf33b7 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -5701,13 +5701,13 @@ multiple processes. @cindex non-stop mode @c This section is really only a place-holder, and needs to be expanded -@c with more details. +@c with more details. For some multi-threaded targets, @value{GDBN} supports an optional mode of operation in which you can examine stopped program threads in the debugger while other threads continue to execute freely. This -minimizes intrusion when debugging live systems, such as programs -where some threads have real-time constraints or must continue to +minimizes intrusion when debugging live systems, such as programs +where some threads have real-time constraints or must continue to respond to external events. This is referred to as @dfn{non-stop} mode. In non-stop mode, when a thread stops to report a debugging event, @@ -5716,16 +5716,16 @@ threads as well, in contrast to the all-stop mode behavior. Additionally, execution commands such as @code{continue} and @code{step} apply by default only to the current thread in non-stop mode, rather than all threads as in all-stop mode. This allows you to control threads explicitly in -ways that are not possible in all-stop mode --- for example, stepping +ways that are not possible in all-stop mode --- for example, stepping one thread while allowing others to run freely, stepping -one thread while holding all others stopped, or stepping several threads +one thread while holding all others stopped, or stepping several threads independently and simultaneously. To enter non-stop mode, use this sequence of commands before you run or attach to your program: @smallexample -# Enable the async interface. +# Enable the async interface. set target-async 1 # If using the CLI, pagination breaks non-stop. @@ -5749,35 +5749,35 @@ Show the current non-stop enablement setting. @end table Note these commands only reflect whether non-stop mode is enabled, -not whether the currently-executing program is being run in non-stop mode. +not whether the currently-executing program is being run in non-stop mode. In particular, the @code{set non-stop} preference is only consulted when -@value{GDBN} starts or connects to the target program, and it is generally +@value{GDBN} starts or connects to the target program, and it is generally not possible to switch modes once debugging has started. Furthermore, since not all targets support non-stop mode, even when you have enabled non-stop mode, @value{GDBN} may still fall back to all-stop operation by default. In non-stop mode, all execution commands apply only to the current thread -by default. That is, @code{continue} only continues one thread. +by default. That is, @code{continue} only continues one thread. To continue all threads, issue @code{continue -a} or @code{c -a}. -You can use @value{GDBN}'s background execution commands +You can use @value{GDBN}'s background execution commands (@pxref{Background Execution}) to run some threads in the background -while you continue to examine or step others from @value{GDBN}. +while you continue to examine or step others from @value{GDBN}. The MI execution commands (@pxref{GDB/MI Program Execution}) are always executed asynchronously in non-stop mode. Suspending execution is done with the @code{interrupt} command when -running in the background, or @kbd{Ctrl-c} during foreground execution. -In all-stop mode, this stops the whole process; -but in non-stop mode the interrupt applies only to the current thread. +running in the background, or @kbd{Ctrl-c} during foreground execution. +In all-stop mode, this stops the whole process; +but in non-stop mode the interrupt applies only to the current thread. To stop the whole program, use @code{interrupt -a}. Other execution commands do not currently support the @code{-a} option. In non-stop mode, when a thread stops, @value{GDBN} doesn't automatically make that thread current, as it does in all-stop mode. This is because the -thread stop notifications are asynchronous with respect to @value{GDBN}'s +thread stop notifications are asynchronous with respect to @value{GDBN}'s command interpreter, and it would be confusing if @value{GDBN} unexpectedly changed to a different thread just as you entered a command to operate on the previously current thread. @@ -5792,7 +5792,7 @@ previously current thread. @value{GDBN}'s execution commands have two variants: the normal foreground (synchronous) behavior, and a background -(asynchronous) behavior. In foreground execution, @value{GDBN} waits for +(asynchronous) behavior. In foreground execution, @value{GDBN} waits for 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. @@ -5874,9 +5874,9 @@ using the @code{interrupt} command. @item interrupt @itemx interrupt -a -Suspend execution of the running program. In all-stop mode, +Suspend execution of the running program. In all-stop mode, @code{interrupt} stops the whole process, but in non-stop mode, it stops -only the current thread. To stop the whole program in non-stop mode, +only the current thread. To stop the whole program in non-stop mode, use @code{interrupt -a}. @end table