public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/31324] -var-create: slowdown due to children printing
Date: Thu, 01 Feb 2024 16:20:40 +0000	[thread overview]
Message-ID: <bug-31324-4717-CpsR4ZYA2K@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31324-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31324

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Dmitry Neverov from comment #1)
> To reproduce, one needs to register a pretty-printer for arrays:

>     def to_string(self):
>         return None

I wouldn't expect this to be slow.

Anyway, an MI feature to support this would be ok, I guess.
Normally it's better to just fix the pretty-printer though,
since if that is slow it's going to impact interactive
use as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-02-01 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 12:17 [Bug mi/31324] New: " dmitry.neverov at jetbrains dot com
2024-02-01 12:51 ` [Bug mi/31324] " dmitry.neverov at jetbrains dot com
2024-02-01 16:20 ` tromey at sourceware dot org [this message]
2024-02-02  9:07 ` dmitry.neverov at jetbrains dot com

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=bug-31324-4717-CpsR4ZYA2K@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).