Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Niko Sams <niko.sams@gmail.com>
To: gdb <gdb@sourceware.org>
Subject: Re: -stack-list-locals and children
Date: Mon, 29 Jun 2009 09:30:00 -0000	[thread overview]
Message-ID: <629542d40906290230n4da6f347s1566847defb9a1c0@mail.gmail.com> (raw)
In-Reply-To: <200906291217.58961.vladimir@codesourcery.com>

On Mon, Jun 29, 2009 at 10:17, Vladimir Prus<vladimir@codesourcery.com> wrote:
> [I assume you did not CC list accidentally, readding it back]
>
> On Monday 29 June 2009 you wrote:
>
>> >> Basic tests showed me that -var-create is relatively slow for large lists.
>> >
>> > How slow and how did you measure this? I would not expect variable objects to
>> > be considerably slower than printing the value in any other way.
>> I measured using -enable-timings. I did -var-create for a QStringList
>> with 1000 items,
>> took 0.6sec.
>
> This is the current problem with GDB -- it will always try to fetch all
> children, which has other problems besides performance. In particular,
> if you try to get children of an invalid object, gdb might never finish.
> Tom is planning to address this issue soon, and we'll be able to have
> incremental fetch of varobj children -- much like we have for stack
> frames in KDevelop already.
ok, I see.
When this is fixed -var-create should be faster?

> Also, is -stack-list-locals any better here? I'd expect it to either have
> exactly the same performance problems, or ignore pretty-printing. If it
> is considerably faster while still reporting 1000 children, it's performance
> bug somewhere.
It's much faster. I get about 100 children in the value followed by ....

Niko


  reply	other threads:[~2009-06-29  9:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28 19:03 Niko Sams
2009-06-28 19:31 ` Vladimir Prus
2009-06-28 19:56   ` Niko Sams
2009-06-29  5:26     ` Vladimir Prus
2009-06-29  7:13       ` Niko Sams
     [not found]       ` <629542d40906290012p33c5504pde20ddcd7da3474a@mail.gmail.com>
2009-06-29  8:18         ` Vladimir Prus
2009-06-29  9:30           ` Niko Sams [this message]
2009-06-29  9:45             ` Vladimir Prus
2009-06-29 11:49             ` Nick Roberts
2009-06-29  7:42 ` André Pönitz
2009-06-29  8:13   ` Nick Roberts
2009-06-29  8:37     ` André Pönitz
2009-06-29  9:33       ` Niko Sams
2009-06-30 10:14       ` Nick Roberts
2009-06-29 15:34     ` Pawel Piech
2009-06-29 16:40       ` Vladimir Prus
2009-06-29 16:55         ` Vladimir Prus
2009-06-29 22:46       ` Nick Roberts
2009-06-29 23:07         ` Pawel Piech
2009-06-30  3:26           ` Pawel Piech
2009-06-29  8:59   ` Vladimir Prus
2009-06-29  9:32     ` André Pönitz
2009-06-29  9:39       ` Vladimir Prus
2009-06-29 10:13         ` André Pönitz
2009-06-30  9:42           ` Vladimir Prus
2009-06-29  9:36     ` Niko Sams

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=629542d40906290230n4da6f347s1566847defb9a1c0@mail.gmail.com \
    --to=niko.sams@gmail.com \
    --cc=gdb@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