From: Eli Zaretskii <eliz@gnu.org>
To: Gareth Rees <grees@undo.io>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING] [PATCH v3] [PR mi/29554] New PRINT-VALUES option '--scalar-values'.
Date: Sun, 25 Sep 2022 13:16:02 +0300 [thread overview]
Message-ID: <83a66nn4il.fsf@gnu.org> (raw)
In-Reply-To: <CAA8DSpGW71wX=iKr5O2eQ404EhTMXtEX4s4Z1mEq8tnw_GWTXw@mail.gmail.com> (message from Gareth Rees via Gdb-patches on Sun, 25 Sep 2022 09:15:49 +0100)
> Date: Sun, 25 Sep 2022 09:15:49 +0100
> From: Gareth Rees via Gdb-patches <gdb-patches@sourceware.org>
>
> > --- a/gdb/NEWS
> > +++ b/gdb/NEWS
> > @@ -114,6 +114,15 @@ maintenance info line-table
> > entry corresponds to an address where a breakpoint should be placed
> > to be at the first instruction past a function's prologue.
> >
> > +* MI changes
> > +
> > + ** The '-stack-list-arguments', '-stack-list-locals',
> > + '-stack-list-variables', and '-var-list-children' commands
> > + support the '--scalar-values' option, which requests the command
> > + to print values only for scalar types. Support for this feature
^^
Two spaces between sentences.
Otherwise, the documentation parts are OK, thanks.
next prev parent reply other threads:[~2022-09-25 10:16 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 7:18 [PATCH] [gdb/mi] Don't treat references to compound values as "simple" Gareth Rees
2022-09-08 10:27 ` Andrew Burgess
2022-09-08 11:02 ` [PATCH v2] " Gareth Rees
2022-09-08 13:30 ` Eli Zaretskii
2022-09-08 13:58 ` Gareth Rees
2022-09-08 14:07 ` Eli Zaretskii
2022-09-09 8:01 ` [PATCH v3] [PR mi/29554] New PRINT-VALUES option '--scalar-values' Gareth Rees
2022-09-15 9:06 ` [PING] " Gareth Rees
2022-09-25 8:15 ` Gareth Rees
2022-09-25 8:25 ` Eli Zaretskii
2022-09-25 9:00 ` Gareth Rees
2022-09-25 10:16 ` Eli Zaretskii
2022-09-26 12:48 ` Gareth Rees
2022-09-25 10:16 ` Eli Zaretskii [this message]
2022-09-26 12:46 ` [PATCH v4] " Gareth Rees
2022-10-04 9:08 ` [PING] " Gareth Rees
2022-10-18 11:59 ` Gareth Rees
2022-10-12 16:38 ` Andrew Burgess
2022-10-20 17:47 ` [PATCH v5] " Gareth Rees
2022-10-20 18:00 ` Eli Zaretskii
2022-11-03 16:20 ` [PING] " Gareth Rees
2022-11-14 9:25 ` Gareth Rees
2022-12-01 13:41 ` Gareth Rees
2022-12-14 8:50 ` Gareth Rees
2023-02-01 10:00 ` Gareth Rees
2023-02-16 10:08 ` Gareth Rees
2023-03-06 9:52 ` Gareth Rees
2023-03-08 12:35 ` Andrew Burgess
2023-03-10 11:04 ` Gareth Rees
2023-03-10 12:05 ` Eli Zaretskii
2023-03-10 12:58 ` Gareth Rees
2023-03-13 17:17 ` Andrew Burgess
2023-03-16 12:28 ` Gareth Rees
2023-03-11 11:58 ` Gareth Rees
2023-04-11 13:15 ` Pedro Alves
2023-03-11 11:49 ` [PATCH v6] [gdb/mi] Don't treat references to compound values as "simple" Gareth Rees
2023-03-21 9:50 ` [PING] " Gareth Rees
2023-03-26 9:56 ` Gareth Rees
2023-04-03 9:22 ` Gareth Rees
2023-05-04 15:08 ` Tom Tromey
2023-04-18 9:23 ` Gareth Rees
2023-04-24 9:53 ` Gareth Rees
2023-05-02 9:13 ` Gareth Rees
2023-03-27 14:34 ` Tom Tromey
2023-03-29 9:14 ` Gareth Rees
2023-04-06 17:18 ` Gareth Rees
2022-10-20 17:58 ` [PATCH v4] [PR mi/29554] New PRINT-VALUES option '--scalar-values' Gareth Rees
2022-09-09 8:04 ` [PATCH v2] [gdb/mi] Don't treat references to compound values as "simple" Gareth Rees
2022-09-08 11:09 ` [PATCH] " Gareth Rees
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=83a66nn4il.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=grees@undo.io \
/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).