Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/doc: improve 'show print elements' description
Date: Wed, 6 Oct 2021 14:47:29 +0200	[thread overview]
Message-ID: <8bd7e2ef-d807-aa37-926f-62557cdecbdd@suse.de> (raw)
In-Reply-To: <20211006113159.2503732-1-andrew.burgess@embecosm.com>

On 10/6/21 1:31 PM, Andrew Burgess wrote:
> The documentation for 'show print elements' contains the line:
> 
>   If the number is 0, then the printing is unlimited.
> 
> However, this line is now out of date as can be seen by this GDB
> session:
> 
>   (gdb) set print elements 0
>   (gdb) show print elements
>   Limit on string chars or array elements to print is unlimited.
> 
> The value 0 does indeed mean unlimited, and this is described in the
> 'set print elements' section, however, for 'show print elements' the
> user will never see the value 0, so lets just remove that bit from the
> docs.

LGTM..

Thanks,
- Tom

> ---
>  gdb/doc/gdb.texinfo | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index c156a1d6739..a6f207a41a7 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -11376,7 +11376,6 @@
>  
>  @item show print elements
>  Display the number of elements of a large array that @value{GDBN} will print.
> -If the number is 0, then the printing is unlimited.
>  
>  @anchor{set print frame-arguments}
>  @item set print frame-arguments @var{value}
> 

  reply	other threads:[~2021-10-06 12:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 11:31 Andrew Burgess
2021-10-06 12:47 ` Tom de Vries via Gdb-patches [this message]
2021-10-06 13:01 ` Eli Zaretskii via Gdb-patches

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=8bd7e2ef-d807-aa37-926f-62557cdecbdd@suse.de \
    --to=gdb-patches@sourceware.org \
    --cc=andrew.burgess@embecosm.com \
    --cc=tdevries@suse.de \
    /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