Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2 5/5] gdb: Introduce 'print max-depth' feature
Date: Thu, 18 Apr 2019 01:07:00 -0000	[thread overview]
Message-ID: <20190418010726.GS2737@embecosm.com> (raw)
In-Reply-To: <83h8awg0nk.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2019-04-17 17:35:27 +0300]:

> > From: Andrew Burgess <andrew.burgess@embecosm.com>
> > Cc: Andrew Burgess <andrew.burgess@embecosm.com>
> > Date: Wed, 17 Apr 2019 00:06:10 +0100
> > 
> > Introduce a new print setting max-depth which can be set with 'set
> > print max-depth DEPTH'.  The default value of DEPTH is 20, but this
> > can also be set to unlimited.
> 
> OK for the documentation parts, with one minor comment:
> 
> > +To see the contents of structures that have been hidden the user can
> > +either increase the print max-depth to increase, or they can print
> 
> "increase ... to increase" sounds awkward and perhaps even confusing.
> Can we come up with a better wording?

You're right, that doesn't read well, how about simply dropping the
'...to increase' like this:


    +To see the contents of structures that have been hidden the user
    +can either increase the print max-depth, or they can print the
    +elements of the structure that are visible, for example
    +
    +@smallexample
    +(gdb) p var
    +$1 = @{d = @{c = @{...@}@}@}
    +(gdb) p var.d
    +$2 = @{c = @{b = @{...@}@}@}
    +(gdb) p var.d.c
    +$3 = @{b = @{a = 3@}@}
    +@end smallexample
    +

Thanks,
Andrew


> 
> Thanks.


  reply	other threads:[~2019-04-18  1:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 23:06 [PATCHv2 0/5] Add new " Andrew Burgess
2019-03-27 21:53 ` [PATCH 0/2] " Andrew Burgess
2019-03-27 21:53   ` [PATCH 2/2] gdb: Introduce " Andrew Burgess
2019-03-28 16:08     ` Eli Zaretskii
2019-03-27 21:53   ` [PATCH 1/2] gdb: Introduce new language field la_struct_too_deep_ellipsis Andrew Burgess
2019-03-28 12:43     ` Pedro Alves
2019-03-28 12:47   ` [PATCH 0/2] Add new 'print max-depth' feature Pedro Alves
2019-03-28 22:48     ` Andrew Burgess
2019-03-28 23:47       ` Marco Barisione
2019-04-16 23:06   ` [PATCHv2 1/5] gdb/ada: Update some predicate functions to return bool Andrew Burgess
2019-04-18  0:03     ` Joel Brobecker
2019-04-16 23:06   ` [PATCHv2 5/5] gdb: Introduce 'print max-depth' feature Andrew Burgess
2019-04-17  7:42     ` Philippe Waroquiers
2019-04-17 14:35     ` Eli Zaretskii
2019-04-18  1:07       ` Andrew Burgess [this message]
2019-04-18  2:38         ` Eli Zaretskii
2019-04-18 21:52           ` Andrew Burgess
2019-04-19  6:50             ` Eli Zaretskii
2019-04-18 17:08     ` Pedro Alves
2019-04-16 23:06   ` [PATCHv2 3/5] gdb: Introduce new language field la_struct_too_deep_ellipsis Andrew Burgess
2019-04-19 14:37     ` Tom Tromey
2019-04-16 23:06   ` [PATCHv2 2/5] gdb/testsuite: Don't add gcc flags when compiling rust tests Andrew Burgess
2019-04-19 14:31     ` Tom Tromey
2019-04-16 23:06   ` [PATCHv2 4/5] gdb: Introduce new language field la_is_string_type_p Andrew Burgess
2019-04-18 17:08     ` Pedro Alves
2019-04-19 21:00       ` Andrew Burgess
2019-04-19 14:45     ` Tom Tromey
2019-04-19 22:22       ` Andrew Burgess
2019-04-24 19:32         ` Tom Tromey
2019-04-19 22:45       ` Andrew Burgess
2019-04-24 19:33         ` Tom Tromey
2019-04-29 21:14 ` [PATCHv2 0/5] Add new 'print max-depth' feature Andrew Burgess

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=20190418010726.GS2737@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=eliz@gnu.org \
    --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