From: "Maciej W. Rozycki" <macro@embecosm.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org, Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH v2] gdb: split array and string limiting options
Date: Tue, 4 Jan 2022 23:15:57 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.20.2201042314390.22504@tpp.orcam.me.uk> (raw)
In-Reply-To: <20211215180101.GO175541@redhat.com>
On Wed, 15 Dec 2021, Andrew Burgess wrote:
> > Index: src/gdb/NEWS
> > ===================================================================
> > --- src.orig/gdb/NEWS
> > +++ src/gdb/NEWS
> > @@ -53,6 +53,24 @@ maint packet
> > as escaped hex, e.g. \x?? where '??' is replaces with the value of
> > the non-printable character.
> >
> > +set print characters LIMIT
> > +show print characters
> > +print -characters LIMIT
> > + This new setting is like 'set print elements', but controls how many
> > + characters of a string are printed. This functionality used to be
> > + covered by 'set print elements', but is now a separate setting.
> > + LIMIT can be set to 'unlimited' to print all characters of a string.
> > + The default value for LIMIT is 200.
> > +
> > +* Changed commands
> > +
> > +set print elements LIMIT
> > +show print elements
> > +print -elements LIMIT
> > + This setting no longer affects how many characters of a string are
> > + printed, instead the new 'set print characters' setting should be
> > + used.
> > +
> > * Python API
>
> I suspect something went wrong with the rebase here. The 'set print
> characters' block should be under 'New commands', and the 'set print
> elements' block should, indeed, be under 'Changed commands'. But, I
> think the 'Changed commands' you're adding here is now the second such
> title for the current release of GDB.
Indeed, good catch! Thank you, I have posted v3 with this piece fixed
only.
Maciej
next prev parent reply other threads:[~2022-01-04 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 16:38 Maciej W. Rozycki
2021-12-14 17:24 ` Eli Zaretskii
2021-12-15 18:01 ` Andrew Burgess
2022-01-04 23:15 ` Maciej W. Rozycki [this message]
2022-01-06 7:58 Simon Sobisch
2022-01-06 9:33 ` Andrew Burgess
2022-01-06 13:32 ` Simon Sobisch
2022-01-06 14:18 ` Andrew Burgess
2022-01-26 15:48 ` Maciej W. Rozycki
2022-01-26 16:52 ` Simon Sobisch
2022-01-26 18:18 ` Maciej W. Rozycki
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=alpine.DEB.2.20.2201042314390.22504@tpp.orcam.me.uk \
--to=macro@embecosm.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).