public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dmitry.neverov at jetbrains dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/31324] -var-create: slowdown due to children printing
Date: Fri, 02 Feb 2024 09:07:29 +0000 [thread overview]
Message-ID: <bug-31324-4717-73tUmXiBLt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31324-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31324
--- Comment #3 from Dmitry Neverov <dmitry.neverov at jetbrains dot com> ---
Created attachment 15348
--> https://sourceware.org/bugzilla/attachment.cgi?id=15348&action=edit
slow array pretty-printing reproducible
> I wouldn't expect this to be slow.
It is slow because children's pretty-printing result is included into
the parent value. The attached script is instant with gdb 13.2, but
takes several seconds in gdb 14.1.
> 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.
The pretty-printer can be slow due to slow symbol lookup
(e.g. https://sourceware.org/bugzilla/show_bug.cgi?id=30520). It is
not clear how to fix it.
In an interactive front-end with gdb 13.2 there was a slow-down only
when array is expanded, so users could avoid it if they didn't want to
inspect array elements.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-02-02 9:07 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
2024-02-02 9:07 ` dmitry.neverov at jetbrains dot com [this message]
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-73tUmXiBLt@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).