public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Christina Schimpe <christina.schimpe@intel.com>
To: gdb-patches@sourceware.org
Cc: Christina Schimpe <christina.schimpe@intel.com>
Subject: [PATCH 1/1] gdb, doc: correct argument description for info connections/inferiors
Date: Mon, 27 Mar 2023 13:39:22 +0200	[thread overview]
Message-ID: <20230327113922.618826-2-christina.schimpe@intel.com> (raw)
In-Reply-To: <20230327113922.618826-1-christina.schimpe@intel.com>

From: Nils-Christian Kempke <nils-christian.kempke@intel.com>

It said for 'info inferiors' and 'info connections' that the argument
could be 'a space separated list of inferior numbers' which is correct
but incomplete.  In fact the arguments can be any space separated
combination of numbers and (ascending) ranges.

The beginning of the section now describes the ID list as a new keyword.

Co-Authored-By: Christina Schimpe <christina.schimpe@intel.com>
---
 gdb/doc/gdb.texinfo | 23 ++++++++++++++++-------
 1 file changed, 16 insertions(+), 7 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 6c811b8be2e..da008e34dfa 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -3216,6 +3216,16 @@ embedded targets may have several inferiors running in different parts
 of a single address space.  Each inferior may in turn have multiple
 threads running in it.
 
+@anchor{ID list}
+@cindex ID list
+The commands @code{info inferiors} and @code{info connections}, which will be
+introduced below, accept a space-separated @dfn{ID list} as their argument
+specifying one or more elements on which to operate.  A list element can be
+either a single non-negative number, like @samp{5}, or an ascending range of
+such numbers, like @samp{5-7}.  A list can consist of any combination of such
+elements, even duplicates or overlapping ranges are valid.  E.g.@:
+@samp{1 4-6 5 4-4} or @samp{1 2 4-7}.
+
 To find out what inferiors exist at any moment, use @w{@code{info
 inferiors}}:
 
@@ -3223,9 +3233,9 @@ inferiors}}:
 @kindex info inferiors [ @var{id}@dots{} ]
 @item info inferiors
 Print a list of all inferiors currently being managed by @value{GDBN}.
-By default all inferiors are printed, but the argument @var{id}@dots{}
--- a space separated list of inferior numbers -- can be used to limit
-the display to just the requested inferiors.
+By default all inferiors are printed, but the ID list (@pxref{ID list})
+@var{id}@dots{} can be used to limit the display to just the requested
+inferiors.
 
 @value{GDBN} displays for each inferior (in this order):
 
@@ -3284,10 +3294,9 @@ To find out what open target connections exist at any moment, use
 @kindex info connections [ @var{id}@dots{} ]
 @item info connections
 Print a list of all open target connections currently being managed by
-@value{GDBN}.  By default all connections are printed, but the
-argument @var{id}@dots{} -- a space separated list of connections
-numbers -- can be used to limit the display to just the requested
-connections.
+@value{GDBN}.  By default all connections are printed, but the ID list
+(@pxref{ID list}) @var{id}@dots{} can be used to limit the display to just the
+requested connections.
 
 @value{GDBN} displays for each connection (in this order):
 
-- 
2.25.1

Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928


  reply	other threads:[~2023-03-27 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 11:39 [PATCH 0/1] Correct " Christina Schimpe
2023-03-27 11:39 ` Christina Schimpe [this message]
2023-03-27 13:47   ` [PATCH 1/1] gdb, doc: correct " Eli Zaretskii
2023-03-30 16:59     ` Schimpe, Christina

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=20230327113922.618826-2-christina.schimpe@intel.com \
    --to=christina.schimpe@intel.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).