public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Gareth Rees <grees@undo.io>
To: Tom Tromey <tom@tromey.com>
Cc: Gareth Rees via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v6] [gdb/mi] Don't treat references to compound values as "simple".
Date: Thu, 6 Apr 2023 18:18:55 +0100	[thread overview]
Message-ID: <CAA8DSpGUvqQdsuLeWW0_3quHajn8Q4WSe9RUTDAcBN5RQFgdpw@mail.gmail.com> (raw)
In-Reply-To: <87tty6clfz.fsf@tromey.com>

Tom Tromey wrote:
>
> >>>>> "Gareth" == Gareth Rees via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Gareth> The '--simple-values' argument to '-stack-list-arguments' and similar
> Gareth> GDB/MI commands does not take reference types into account, so that
> Gareth> references to arbitrarily large structures are considered "simple" and
> Gareth> printed. This means that the '--simple-values' argument cannot be used
> Gareth> by IDEs when tracing the stack due to the time taken to print large
> Gareth> structures passed by reference.
>
> This looks good to me.  I haven't been following the progress of this
> patch -- have the documentation changes been reviewed?  If so, please
> check it in.

Following up again. I don't have commit rights, so I can't check it in
myself. Could you check it in for me? But before you do, I just want
to check that you're happy with the solution I've picked here.

There are two ways to fix the problem of '--simple-values' printing
references to compound values:

First, if it's acceptable to modify the behaviour of the
'--simple-values' option, then we can suppress the printing of
references to compound types, as in this patch. This solution was
preferred by Andrew Burgess [1] [2] [3] out of concern about the
maintenance cost of accumulating backwards-compatible but arguably
broken features. I added an argument that the original behaviour was a
bug, and that it remains hard to use correctly [4].

Second, if we have to preserve the behaviour of the '--simple-values'
option, then we need to add a new option. This solution was preferred
by Eli Zaretskii [5] [6] out of concern about backwards compatibility.

I've proposed a patch that applies the first solution, but I could
work with either. So I need someone to break the tie between Andrew
and Eli. Take a look at the cited messages and let me know if you're
happy, and if you are, then commit the patch.

[1] https://sourceware.org/pipermail/gdb-patches/2022-September/191747.html
[2] https://sourceware.org/pipermail/gdb-patches/2023-March/197736.html
[3] https://sourceware.org/pipermail/gdb-patches/2023-March/197894.html
[4] https://sourceware.org/pipermail/gdb-patches/2023-March/197799.html
[5] https://sourceware.org/pipermail/gdb-patches/2022-September/191754.html
[6] https://sourceware.org/pipermail/gdb-patches/2023-March/197798.html

  parent reply	other threads:[~2023-04-06 17:19 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  7:18 [PATCH] " 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
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 [this message]
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=CAA8DSpGUvqQdsuLeWW0_3quHajn8Q4WSe9RUTDAcBN5RQFgdpw@mail.gmail.com \
    --to=grees@undo.io \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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).